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 shifted from prompt-based AI instructions to organizing knowledge into reusable ‘Skills’—folders containing instructions, scripts, and assets. This approach enhances consistency, onboarding, and institutional memory, representing a significant change in AI operational practices.

Anthropic has announced a new approach to AI agent management, defining ‘Skills’ as comprehensive folders that contain instructions, scripts, and reference assets, rather than simple prompts. This shift aims to make AI outputs more consistent, facilitate onboarding, and build a durable institutional knowledge base. The development is based on Anthropic’s experience running hundreds of Skills internally, offering a new model for organizations deploying AI at scale.

In a recent publication, Anthropic detailed its findings from deploying hundreds of Skills across its engineering teams. Unlike traditional prompt engineering, where instructions are often single text prompts, a Skill is now understood as a folder that can include instructions, reference documents, runnable scripts, templates, data, configurations, and even hooks that activate during operation. This change redefines how organizations can structure their AI workflows, making them more modular, reusable, and maintainable.

Anthropic emphasizes that Skills serve three core functions: ensuring consistent output regardless of who runs the agent, compressing onboarding processes by encapsulating tribal knowledge, and enabling continuous improvement through iteration. The company reports that its best Skills began as simple caveats but became more refined, accumulating edge cases and best practices over time. The result is a library of Skills that act as an organizational asset, not just a prompt or note.

Anthropic identified nine categories of Skills, ranging from library references and product verification to code scaffolding and infrastructure operations. The most impactful, according to the company, is verification Skills—those that check and validate outputs—because they directly improve output quality and reduce errors. The approach encourages organizations to focus on building robust, specific Skills that push the model off its defaults and capture institutional knowledge.

At a glance
reportWhen: published recently, with ongoing implem…
The developmentAnthropic published insights from its internal experience running hundreds of AI Skills, redefining Skills as folders rather than prompts, with implications for organizational AI deployment.
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

Transforming AI Workflow Management in Organizations

This development matters because it shifts the way organizations think about deploying AI agents. Moving from ad-hoc prompts to structured Skills as folders creates a durable, scalable framework for operational consistency, knowledge retention, and continuous improvement. It reduces reliance on individual expertise and helps embed best practices into the AI system itself, potentially lowering costs and increasing reliability over time.

For businesses, adopting this approach could mean more predictable AI outputs, faster onboarding of new team members, and a strategic asset that grows more valuable as it accumulates institutional knowledge. It also signals a move toward more formalized, versioned, and sharable AI assets within organizations, akin to software libraries or operational playbooks.

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

Prior to this shift, most AI teams relied heavily on prompt engineering—crafting specific prompts to guide model behavior. These prompts were often one-off and lacked durability, requiring repeated re-creation or adjustment. Anthropic’s internal experience revealed that prompts alone are insufficient for scaling AI deployment in complex workflows.

By contrast, the concept of Skills as folders encapsulates knowledge, procedures, and code into a single, versioned asset. This approach aligns with broader trends in software engineering, emphasizing modularity, reusability, and institutional memory. Anthropic’s insights are based on running hundreds of Skills internally, which demonstrated the value of structured, comprehensive units for operational consistency and continuous improvement.

This development builds on prior work in AI prompt engineering but represents a significant evolution toward more durable, organizationally embedded AI capabilities.

“A Skill is not just a prompt saved in a file; it’s a container that includes instructions, scripts, and assets, making it a true organizational asset.”

— Thorsten Meyer, AI researcher

Amazon

AI instruction scripting tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

What Aspects of Skills Are Still Unclear?

It is not yet clear how widely this approach will be adopted outside Anthropic or how it will scale in different organizational contexts. Details about the specific technical implementation, integration challenges, and long-term maintenance are still emerging. Additionally, the precise impact on productivity and error rates across diverse teams remains to be quantified.

Amazon

AI asset organization folders

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Future Steps for Organizational AI Asset Management

Organizations interested in this approach should begin cataloging their internal procedures and knowledge into structured folders, testing how these Skills improve consistency and onboarding. Further research and case studies are expected to evaluate the scalability and long-term benefits of this model. Anthropic itself is likely to refine its Skills library and share best practices for broader adoption.

Amazon

AI verification and validation tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does defining a Skill as a folder improve AI deployment?

It creates a durable, reusable asset that encapsulates instructions, scripts, and knowledge, leading to more consistent outputs, easier onboarding, and continuous improvement.

What are the main categories of Skills identified by Anthropic?

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

Can this approach be applied outside of AI development teams?

Yes, any organization seeking to formalize and institutionalize procedural knowledge could benefit from structuring it into Skills folders, though implementation details may vary.

What challenges might organizations face adopting this model?

Potential challenges include technical integration, maintaining version control, ensuring proper documentation, and training staff to develop and update Skills effectively.

Source: ThorstenMeyerAI.com

You May Also Like

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

Ukraine’s Avengers Labs leverages its unique combat drone data to develop advanced AI for battlefield use, transforming war data into a strategic export.

The Model Is Only 10%: The Real Lesson of the New SDLC

A new Google whitepaper reveals that AI models are only a small part of effective AI systems; the real focus is on harness design and context engineering.

Sovereignty Is A Pipe, Not A Passport

European AI firm Mistral highlights that sovereignty depends on data flow control, not just company nationality or server location, exposing legal and infrastructural limits.

China Sphere Capability Gap, Q2 2026 Update: Five Labs, Five Strategies, One Narrowing Frontier

Five Chinese labs launched frontier-tier models within four weeks, narrowing the capability gap with US leaders while maintaining cost advantages.