A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them

📊 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.

TL;DR

Anthropic has demonstrated that Skills for AI agents should be viewed as folders containing instructions, code, and assets rather than simple prompts. This approach enhances consistency, onboarding, and institutional knowledge. The company ran hundreds of Skills internally, emphasizing their value as evolving organizational assets.

Anthropic has introduced a new conceptual framework for AI agent Skills, defining them as folders containing instructions, scripts, and reference materials, rather than simple prompts. This shift aims to improve consistency, onboarding, and institutional knowledge within organizations using AI coding agents. The company shared its internal learnings, emphasizing that Skills are reusable, versioned assets that encapsulate how tasks are performed, not just static prompts.

In a recent publication, Anthropic explained that a Skill is best understood as a folder—a container that holds instructions, reference documents, scripts, templates, data, and configuration settings. This redefinition moves away from viewing Skills as mere text prompts, instead framing them as organized assets that can be discovered, read, and executed by AI agents.

Anthropic’s internal experiments involved running hundreds of Skills across its engineering teams, leading to three key benefits: output consistency regardless of who runs the agent, faster onboarding by encapsulating tribal knowledge, and a process of continuous improvement where Skills evolve through edge cases and refinements. The company considers Skills as assets that appreciate in value over time, justifying significant investment in their development.

The company identified nine categories of Skills, including library references, verification, data analysis, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations. Among these, verification Skills—used to check code and workflows—are deemed the most impactful in improving output quality.

Technical insights emphasize that effective Skills should avoid restating obvious information, instead focusing on non-obvious, specific guidance. The description of a Skill acts as a trigger for the agent, matching user requests to the appropriate folder based on internal slang and phrasing. Bundling real code and helper functions within Skills further enhances their utility and robustness.

At a glance
reportWhen: published recent, ongoing implementation
The developmentAnthropic published insights from its internal use of Skills, showing they are folders with instructions and assets, not just prompts, to improve AI agent reliability and organizational knowledge.
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

Why Reframing Skills as Folders Changes AI Deployment

This approach shifts how organizations think about implementing AI agents, moving from ad-hoc prompting to systematic, reusable assets that encode tribal knowledge and operational procedures. It enables consistent outputs across teams, accelerates onboarding, and creates a foundation for continuous improvement. The concept of Skills as evolving, versioned folders turns AI deployment into a more reliable and scalable organizational capability, potentially transforming enterprise AI workflows.

Amazon

AI development instruction management tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Internal Practices and Broader Implications for AI Teams

Prior to this development, most teams relied on manually retyping prompts or maintaining static prompts stored in text files. Anthropic’s insight stems from running hundreds of Skills internally, which revealed that organizing instructions and assets into folders significantly improves reliability and knowledge retention. This aligns with broader industry trends toward modular, reusable AI components, but Anthropic’s emphasis on Skills as organized containers is a notable conceptual shift. The company’s focus on verification Skills highlights the importance of quality control in AI outputs, especially in enterprise settings.

While the concept is still being adopted, it signals a move toward more structured and maintainable AI workflows, where Skills serve as the building blocks of institutional knowledge and operational procedures.

“Viewing Skills as folders containing instructions and assets fundamentally changes how organizations design and maintain AI agents.”

— Thorsten Meyer, AI researcher

Amazon

AI agent scripting and asset organization software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Skills Implementation

While Anthropic’s internal results are promising, it is not yet clear how broadly applicable this approach is across different industries or AI platforms. The specifics of integrating Skills into existing workflows, managing version control at scale, and ensuring that Skills remain up-to-date as organizational knowledge evolves are still being explored. Additionally, the long-term impact on AI reliability and maintenance costs remains to be seen.

Amazon

version control tools for AI skills

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Adoption and Standardization

Organizations interested in adopting this approach will likely experiment with creating their own Skills folders, focusing on categories most relevant to their operations. Industry-wide, there may be efforts to develop standards for Skills description, versioning, and discovery mechanisms. Anthropic may also release tools or frameworks to facilitate broader adoption. Monitoring how these practices influence AI reliability and operational efficiency will be key in the coming months.

Amazon

AI automation and workflow templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does viewing Skills as folders improve AI reliability?

It ensures that instructions, reference materials, and scripts are organized and versioned, reducing errors and inconsistencies in AI outputs.

Can Skills be reused across different AI models or platforms?

While Anthropic’s approach is tailored to their systems, the concept of organizing assets in folders can be adapted for other platforms with appropriate tooling.

What are the main benefits of this approach for organizations?

It enhances output consistency, accelerates onboarding, and creates a living knowledge base that improves over time.

What challenges might organizations face in implementing Skills as folders?

Managing version control, keeping Skills up-to-date, and integrating them into existing workflows could require significant effort and tooling development.

Source: ThorstenMeyerAI.com

You May Also Like

Avengers Labs: How Ukraine Turned Its Front Line Into the World’s Scarcest AI Dataset

Ukraine leverages battlefield drone data via Avengers Labs to develop advanced AI for combat, transforming war data into a strategic asset amid ongoing conflict.

Europe Regulated the Interface and Forgot to Build the Engine

Europe prioritized regulating AI interfaces like cookie banners but overlooked building the underlying AI engines, risking technological lag.

The Switch: You Never Owned the AI You Depend On

Exploring how governments and companies can suddenly disable AI models, exposing dependency risks and control chokepoints in AI infrastructure.

Autonomous Flying Umbrella Follows And Shields Users From Rain And Sunlight

A new autonomous flying umbrella can follow users and provide protection from rain and sunlight, marking a significant innovation in personal weather shielding.