In my final article, I shared the way to use MCP to combine LLMs into your full knowledge science workflow. I additionally briefly talked about one other .
A talent is a reusable package deal of directions and optionally available supporting recordsdata. It helps AI deal with a recurring workflow extra reliably and persistently. At a minimal, it wants a SKILL.md file containing metadata (title and outline) and detailed directions for a way the talent ought to work. Folks usually bundle it with scripts, templates, and examples for standardization and accuracy.
At this level, you is perhaps questioning why we use expertise as an alternative of simply writing the entire thing immediately into the Claude Code or Codex context. One benefit is that expertise assist maintain the primary context shorter. AI solely must load the light-weight metadata at first—it could actually learn the remaining directions and bundled sources when it decides that the talent is related. You’ll find a terrific public assortment of expertise at expertise.sh.
Let me make the concept extra concrete with a easy instance.
My Instance — Weekly Visualization Ability
Context
I’ve been making one visualization each week since 2018 — if you’re curious, I wrote about my journey on this article. This course of is very repetitive and normally takes me about one hour each week. Due to this fact, I discovered it a terrific candidate for automation with expertise.
Workflow with out AI
Right here is my weekly routine:
- Discover a dataset that pursuits me. Web sites I normally go for inspiration embrace Tableau Viz of the Day, Voronoi, the Economics Every day by BLS, r/dataisbeautiful, and many others.
- Open Tableau, play with the information, discover insights, and construct one visualization that tells the story intuitively.
- Publish it to my private web site.
AI workflow
Whereas the dataset search step continues to be guide, I created two expertise to automate steps 2 and three:
- A storytelling-viz talent that analyzes the dataset, identifies insights, suggests visualization varieties, and generates an interactive visualization that’s intuitive, concise, and storytelling-oriented.
- A viz-publish talent that publishes the visualization to my web site as embedded HTML — I’m not going to share this one, as it is vitally particular to my web site repo construction.
Beneath is an instance the place I triggered the storytelling-viz talent in Codex Desktop. I used the identical Apple Well being dataset as final time, asking Codex to question the information from the Google BigQuery database, then use the talent to generate a visualization. It was capable of floor an perception round annual train time vs. energy burned, and suggest a chart sort with reasoning and tradeoffs.
The entire course of took lower than 10 minutes, and right here is the output — it leads with an insight-driven headline, adopted by a clear interactive visualization, caveats, and the information supply. I’ve been testing the talent with my previous few weekly visualizations, and yow will discover extra visualization examples within the talent repo.
How I Truly Constructed It
Now that we now have appeared on the output, let me stroll you thru how I constructed the talent.
Step 1: Begin with a plan
As I shared in my final article, I wish to choose a plan with AI first earlier than implementation. Right here, I began by describing my weekly visualization workflow and my purpose of automating it. We mentioned the tech stack, necessities, and what “good” output ought to appear to be. This results in my very first model of the talent.
The good half is that you just don’t have to create the SKILL.md file manually — merely ask Claude Code or Codex to create a talent on your use case, and it could actually bootstrap the preliminary model for you (it can set off a talent to create a talent).
Step 2: Take a look at and iterate
Nevertheless, that first model solely obtained me 10% of my supreme visualization workflow — it might generate visualizations, however the chart varieties had been usually suboptimal, the visible types had been inconsistent, and the primary takeaway was not all the time highlighted, and many others.
These remaining 90% required iterative enhancements. Listed below are some methods that helped.
1. Share my very own information
Over the previous eight years, I’ve established my very own visualization finest practices and preferences. I needed AI to comply with these patterns as an alternative of inventing a distinct type every time. Due to this fact, I shared my visualization screenshots together with my type steerage. AI was capable of summarize the widespread rules and replace the talent directions accordingly.
2. Analysis exterior sources
There are such a lot of sources on-line about good knowledge visualization design. One other helpful step I took was to ask AI to analysis higher visualization methods from well-known sources and comparable public expertise. This added views that I had not explicitly documented myself, and made the talent extra scalable and strong.
3. Be taught from testing
Testing is crucial to establish enchancment areas. I examined this talent with 15+ varied datasets to watch the way it behaved and the way its output in contrast with my very own visualizations. That course of helped me counsel concrete updates, comparable to:
- Standardizing the font selections and format
- Checking desktop and cell previews to keep away from overlapping labels and annotations
- Making charts comprehensible even with out tooltips
- At all times asking for the information supply and linking it within the visualization
- …
You’ll find the newest model of the storytelling-viz talent right here. Please be happy to play with it and let me know the way you prefer it 🙂
Takeaways for Information Scientists
When expertise are helpful
My weekly visualization challenge is only one instance, however expertise may be helpful in lots of recurring knowledge science workflows. They’re particularly precious when you’ve a job that comes up repeatedly, follows a semi-structured course of, is dependent upon area information, and is troublesome to deal with with a single immediate.
- For instance, investigating the motion of metric X. You most likely already know the widespread drivers of X, so that you all the time begin with slicing by segments A/B/C and checking upfunnel metrics D and E. That is precisely the method you could package deal right into a talent, so AI follows the identical analytical playbook and identifies the basis trigger for you.
- One other instance: suppose you intend to run an experiment in area A, and also you need to examine different experiments operating in the identical space. Previously, you’d search key phrases in Slack, dig by means of Google Docs, and open the inner experimentation platform to evaluate experiments tagged with the area. Now, you possibly can summarize these widespread steps right into a talent and ask LLMs to conduct complete analysis and generate a report of related experiments with their objectives, durations, visitors, statuses, and docs.
In case your workflow consists of a number of impartial and reusable parts, it’s best to break up them into separate expertise. In my case, I created two expertise — one for producing the visualization, and one other for publishing it to my weblog. That makes the items extra modular and simpler to reuse in different workflows later.
Expertise and MCP work effectively collectively. I used BigQuery MCP and the visualization talent in a single command, and it efficiently generated a visualization based mostly on my datasets in BigQuery. MCP helps the mannequin entry the exterior instruments easily, and talent helps it comply with the correct course of for a given job. Due to this fact, this mix is highly effective and enhances one another.
A closing word on my weekly visualization challenge
Now that I can automate 80% of my weekly visualization course of, why am I nonetheless doing it?
After I first began this behavior in 2018, the purpose was to apply Tableau, which was the primary BI instrument utilized by my employer. Nevertheless, the aim has modified over time — now I take advantage of this weekly ritual to discover completely different datasets that I might by no means encounter at work, sharpen my knowledge instinct and storytelling, and see the world by means of the lens of information. So for me, it isn’t actually in regards to the instrument, however the strategy of discovery. And that’s the reason I plan to maintain doing it, even within the AI period.
