In my last article, I shared find out how to use MCP to combine LLMs into your full information science workflow. I additionally briefly talked about one other .
A ability is a reusable bundle of directions and optionally available supporting information. 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 the way the ability ought to work. Individuals typically bundle it with scripts, templates, and examples for standardization and accuracy.
At this level, you is perhaps questioning why we use abilities as a substitute of simply writing the entire thing straight into the Claude Code or Codex context. One benefit is that abilities assist hold the principle context shorter. AI solely must load the light-weight metadata at first—it could possibly learn the remaining directions and bundled assets when it decides that the ability is related. Yow will discover an amazing public assortment of abilities at skills.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 — in case you are 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 an amazing candidate for automation with abilities.
Workflow with out AI
Right here is my weekly routine:
- Discover a dataset that pursuits me. Web sites I normally go for inspiration embody Tableau Viz of the Day, Voronoi, the Economics Daily by BLS, r/dataisbeautiful, and so forth.
- Open Tableau, play with the info, discover insights, and construct one visualization that tells the story intuitively.
- Publish it to my personal website.
AI workflow
Whereas the dataset search step continues to be handbook, I created two abilities to automate steps 2 and three:
- A storytelling-viz ability that analyzes the dataset, identifies insights, suggests visualization sorts, and generates an interactive visualization that’s intuitive, concise, and storytelling-oriented.
- A viz-publish ability that publishes the visualization to my web site as embedded HTML — I’m not going to share this one, as it is rather particular to my web site repo construction.
Beneath is an instance the place I triggered the storytelling-viz ability in Codex Desktop. I used the identical Apple Well being dataset as last time, asking Codex to question the info from the Google BigQuery database, then use the ability 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 info supply. I’ve been testing the ability with my previous few weekly visualizations, and you’ll find extra visualization examples within the skill repo.
How I Really Constructed It
Now that we’ve got seemed on the output, let me stroll you thru how I constructed the ability.
Step 1: Begin with a plan
As I shared in my final article, I wish to decide on a plan with AI first earlier than implementation. Right here, I began by describing my weekly visualization workflow and my objective 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 ability.
The good half is that you simply don’t must create the SKILL.md file manually — merely ask Claude Code or Codex to create a ability in your use case, and it could possibly bootstrap the preliminary model for you (it can set off a ability to create a ability).
Step 2: Take a look at and iterate
Nevertheless, that first model solely received me 10% of my best visualization workflow — it may generate visualizations, however the chart sorts had been typically suboptimal, the visible types had been inconsistent, and the principle takeaway was not all the time highlighted, and so forth.
These remaining 90% required iterative enhancements. Listed here are some methods that helped.
1. Share my very own information
Over the previous eight years, I’ve established my very own visualization greatest practices and preferences. I needed AI to comply with these patterns as a substitute of inventing a unique model every time. Due to this fact, I shared my visualization screenshots together with my model steering. AI was capable of summarize the widespread ideas and replace the ability directions accordingly.
2. Analysis exterior assets
There are such a lot of assets on-line about good information visualization design. One other helpful step I took was to ask AI to analysis higher visualization methods from well-known sources and related public abilities. This added views that I had not explicitly documented myself, and made the ability extra scalable and sturdy.
3. Be taught from testing
Testing is crucial to establish enchancment areas. I examined this ability 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 recommend concrete updates, corresponding to:
- Standardizing the font decisions and format
- Checking desktop and cellular previews to keep away from overlapping labels and annotations
- Making charts comprehensible even with out tooltips
- All the time asking for the info supply and linking it within the visualization
- …
Yow will discover the newest model of the storytelling-viz ability here. Please be happy to play with it and let me know the way you prefer it 🙂
Takeaways for Knowledge Scientists
When abilities are helpful
My weekly visualization challenge is only one instance, however abilities might be helpful in lots of recurring information science workflows. They’re particularly worthwhile when you could have a process that comes up repeatedly, follows a semi-structured course of, will depend on 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 which you could bundle right into a ability, 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 verify different experiments operating in the identical space. Previously, you’ll search key phrases in Slack, dig via Google Docs, and open the interior experimentation platform to overview experiments tagged with the area. Now, you possibly can summarize these widespread steps right into a ability and ask LLMs to conduct complete analysis and generate a report of related experiments with their objectives, durations, site visitors, statuses, and docs.
In case your workflow consists of a number of impartial and reusable elements, you must cut up them into separate abilities. In my case, I created two abilities — 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.
Abilities and MCP work nicely collectively. I used BigQuery MCP and the visualization ability 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 ability helps it comply with the fitting course of for a given process. Due to this fact, this mixture is highly effective and enhances one another.
A last be aware on my weekly visualization challenge
Now that I can automate 80% of my weekly visualization course of, why am I nonetheless doing it?
Once I first began this behavior in 2018, the objective was to observe Tableau, which was the principle BI device utilized by my employer. Nevertheless, the aim has modified over time — now I exploit this weekly ritual to discover completely different datasets that I might by no means encounter at work, sharpen my information instinct and storytelling, and see the world via the lens of knowledge. So for me, it isn’t actually in regards to the device, however the means of discovery. And that’s the reason I plan to maintain doing it, even within the AI period.
