A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them
AIThis post was created with the assistance of artificial intelligence (AI).

📊 Full opportunity report: A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them on ThorstenMeyerAI.com — validation score, market gap, and execution plan.

Buying for a business?Offer from Amazon

Get business pricing on tech for your team

  • Business-only prices and quantity discounts
  • Tax-exempt purchasing
  • Multiple users, one account, clear invoices
As an affiliate, we earn on qualifying purchases.

TL;DR

Anthropic has demonstrated that effective AI Skills are better represented as folders containing instructions, scripts, and assets rather than simple prompts. This approach enhances consistency, onboarding, and long-term improvement in AI workflows, marking a shift in how organizations build and manage AI capabilities.

Anthropic has announced a new approach to building AI Skills, defining them as folders containing instructions, scripts, and assets rather than just prompts. This shift aims to create more durable, consistent, and scalable AI workflows within organizations, moving away from ad-hoc prompting towards institutionalized capabilities.

According to a detailed write-up from a Claude Code engineer, Anthropic’s internal experiments show that packaging knowledge into structured folders—called Skills—enables AI agents to discover, read, and execute complex workflows. These Skills include not only instructions but also reference documents, scripts, templates, and configuration data, making them more like organizational assets than simple prompts.

This approach improves output consistency across team members, simplifies onboarding by encapsulating tribal knowledge, and allows Skills to evolve and improve over time through iterative refinement. Anthropic’s internal analysis identified nine categories of Skills, ranging from library references to operational runbooks, with verification Skills identified as the highest-value for quality assurance.

Anthropic emphasizes that building Skills is a deliberate process, where quality depends on including non-obvious, specific instructions and ‘gotchas’—trap points for the AI—based on real-world experience. The description of each Skill acts as a trigger for the agent, ensuring relevant Skills activate reliably during tasks.

At a glance
reportWhen: published in early 2024
The developmentAnthropic published insights from running hundreds of Skills internally, revealing that Skills are folders, not prompts, leading to more durable and scalable AI practices.
A Skill Is a Folder, Not a Prompt — Insights
AI Dispatch · Insights · 1 July 2026

A Skill is a folder, not a prompt

Anthropic published what it learned running hundreds of Skills across its own engineering org. Read as a business memo, the point is bigger than a coding trick: this is how ad-hoc prompting becomes durable institutional capability — the SOPs your agents actually follow, versioned and shared.

✕ The misconception

“A Skill is just a clever markdown prompt you save in a file.”

✓ What it actually is

A folder the agent can discover, read & run — instructions, scripts, references, templates, config & on-demand hooks.

Anatomy of a Skill — the file system is context engineering
my-skill/the unit you share & version
├─ SKILL.mdroot instructions + a description written for the model (its trigger)
├─ references/deep detail pulled in only when needed — progressive disclosure
├─ scripts/real code, so the agent composes instead of rebuilding boilerplate
├─ assets/templates & files to copy into the output
├─ config.jsonsetup the agent asks for if it’s missing (e.g. which Slack channel)
└─ hooks + memoryon-demand guardrails + an append-only log so it remembers
Why it matters: the folder itself is the knowledge base. The agent reads the root, then reaches deeper only when the task demands it — the same way you’d hand a new hire a one-pager that points to the detailed docs.
The nine types — a gap-analysis map for your own library
1Library / API reference
2Product verification ★ top impact
3Data fetching & analysis
4Business-process automation
5Code scaffolding & templates
6Code quality & review
7CI/CD & deployment
8Runbooks
9Infrastructure operations
By Anthropic’s own measurement, verification Skills — the ones that check the work — moved output quality the most. If you build one category well, build that one.
The craft — what separates a good Skill from a useless one
Gotchas = highest-signal section Describe for the model, not humans (it’s the trigger) Don’t state the obvious Ship scripts, not just prose On-demand guardrail hooks (/careful, /freeze) Let it remember (log / SQLite) Don’t railroad — leave room to adapt
The take

The knowledge of how your organization actually operates can be captured, versioned, shared & executed — and the thing capturing it is a humble folder with a script and a gotchas list inside. For the builder, that’s context engineering with real tools attached. For whoever owns the budget, it’s the difference between AI that starts from zero every morning and an asset that compounds. Caveats: best practices are still evolving, checked-in Skills cost context, and curation beats accumulation. Start with one Skill, one gotcha, and the category that catches your mistakes.

Source: “Lessons from building Claude Code: How we use skills,” Thariq Shihipar (Anthropic), Claude blog, 3 June 2026. Categories, examples & measured claims are Anthropic’s; framing is the author’s. Docs: code.claude.com/docs/en/skills.
thorstenmeyerai.com

Implications for AI Development and Organizational Knowledge

This development signals a fundamental shift in how organizations design, deploy, and maintain AI systems. Moving from prompt-based interactions to structured Skills as folders transforms AI from a tool with fleeting prompts into a durable, institutional asset. It enhances consistency, reduces onboarding time, and enables continuous improvement, making AI workflows more reliable and scalable. For businesses, this approach could lead to more predictable AI outputs, better compliance with operational procedures, and a clearer path for internal knowledge sharing and automation.

Amazon

AI workflow management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset Building in AI Workflows

Until now, most teams using AI coding agents relied on prompt engineering—repeatedly retyping instructions or prompts to guide AI behavior. Anthropic’s recent insights challenge this paradigm by framing Skills as folders that contain all necessary knowledge and tools for specific tasks. This approach reflects a broader trend towards institutionalizing AI capabilities, similar to software assets stored in repositories, rather than ad-hoc prompt snippets.

Anthropic’s internal experiments, conducted over hundreds of runs, reveal that Skills can be refined iteratively, accumulating improvements and capturing tribal knowledge. The approach aligns with best practices in software engineering—versioning, documentation, and modularity—applied to AI workflows.

While the concept of Skills as folders is new, it builds on existing ideas of automation and modular design, now extended into AI agent management at scale. The focus on verification, quality, and continuous refinement marks a significant evolution in enterprise AI deployment.

“By packaging tribal knowledge into Skills, we turn ad-hoc prompts into institutional assets that improve over time.”

— Anthropic engineer involved in the project

Amazon

AI instruction scripting tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Implementation and Scalability

It remains unclear how widely this Skills-as-folders approach has been adopted outside Anthropic, and whether other organizations can replicate its success at scale. Details about the tooling, integration with existing systems, and how Skills are maintained long-term are still emerging. Additionally, the impact on AI transparency and explainability warrants further exploration, as the internal complexity of Skills may introduce new challenges.

Amazon

AI knowledge management folders

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Industry Validation

Organizations interested in this approach should evaluate how to structure their own Skills folders, focusing on capturing tribal knowledge and automating workflows. Future developments may include standardized frameworks for Skills management, tools for versioning and testing, and industry-wide case studies demonstrating real-world benefits. Further research will clarify how this method scales across different AI applications and industries.

Amazon

AI asset organization tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does defining Skills as folders improve AI workflows?

It allows for more durable, consistent, and scalable AI operations by encapsulating instructions, scripts, and knowledge in a structured, discoverable format that can be refined over time.

What are the main categories of Skills identified by Anthropic?

They include library references, product verification, data analysis, business-process automation, code scaffolding, code review, deployment, runbooks, and infrastructure operations.

Can this approach be adopted by other organizations?

While promising, it remains to be seen how easily other organizations can implement and scale this approach. It requires a shift in mindset from prompt engineering to asset building and may depend on existing technical infrastructure.

What challenges might arise from using Skills as folders?

Potential challenges include managing version control, ensuring proper documentation, maintaining security, and integrating with legacy systems. Transparency and explainability may also become more complex.

Will this change how AI models are trained or just how they are used?

This primarily impacts how AI is used and maintained in operational settings, emphasizing structured knowledge assets over prompt-based interactions. It complements ongoing training efforts by providing durable procedural knowledge.

Source: ThorstenMeyerAI.com

FALL

Fall Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

Flint: A Visualization Language For The AI Era

Flint introduces a novel visualization language designed to enhance transparency and understanding of AI models, marking a significant step in AI interpretability.

When The Most Diligent AI Still Fails To Deliver

A detailed report on how highly thorough AI models, despite deep analysis, often fail to complete critical business actions, highlighting a key challenge in AI automation.

How to Choose AI Automation Tools For Small Businesses

Learn how small businesses can implement AI automation tools effectively, boosting efficiency and reducing costs with this step-by-step guide.

Gpt 6 Astra

Search interest in GPT-6 Astra surges amid unconfirmed reports, raising questions about OpenAI’s upcoming AI advancements and industry impact.