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.

Prime Big Deal Days · Oct 6–7Offer from Amazon

Get school and study supplies delivered free — and shop member deals

  • Fast, free delivery on millions of items
  • Access to Prime Big Deal Days deals on October 6–7
  • Prime Video, Amazon Music and more included
Start your free Prime trial Free trial for eligible customers · Cancel anytime
As an affiliate, we earn on qualifying purchases.

TL;DR

Anthropic has demonstrated that AI Skills should be viewed as folders, not prompts. This approach enhances consistency, onboarding, and asset value, marking a shift in AI operational practices.

Anthropic has revealed that its internal approach to building AI capabilities centers on organizing Skills as folders—containing instructions, scripts, and assets—rather than simple prompts. This shift aims to improve consistency, onboarding, and asset management within AI systems, marking a significant evolution in operational AI practices.

According to a detailed write-up from a Claude Code engineer, Anthropic’s team packages knowledge into reusable ‘Skills’ that are structured as folders. These folders can include instructions, reference documents, runnable scripts, templates, data, and configuration, allowing AI agents to discover, read, and execute contained assets dynamically. This approach contrasts with the common practice of saving prompts as static text files, emphasizing a more comprehensive, asset-based method.

Anthropic’s internal analysis identified nine categories of Skills, ranging from library references and data analysis to automation and infrastructure operations. The most impactful, according to the company, is verification Skills—those that check output quality—highlighting the importance of error detection and correction in AI workflows. The company advocates investing significant effort into developing these Skills, viewing them as assets that improve over time through iteration and edge case handling.

Technical lessons emphasize that effective Skills should not restate obvious information but focus on non-obvious, organization-specific knowledge, including ‘gotchas’—trap points that can cause failures. Descriptions for Skills are trigger-based, matching user requests with specific internal slang or phrasing, ensuring precise activation. This method enhances reliability and reduces the need for ad-hoc prompting, making AI operations more durable and scalable.

At a glance
reportWhen: published recently, with ongoing implic…
The developmentAnthropic published a detailed internal report showing how their team developed hundreds of Skills structured as folders, emphasizing a new paradigm for AI capability management.
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 Operational Strategies

This development signals a shift from prompt engineering to asset management in AI workflows, enabling organizations to standardize, scale, and improve their AI capabilities systematically. By treating Skills as structured folders, companies can better capture institutional knowledge, reduce onboarding time, and ensure output consistency. The approach also positions Skills as valuable, appreciating assets that can be refined over time, potentially transforming AI deployment and maintenance practices across industries.

Amazon

AI development asset management tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on AI Skill Development and Anthropic’s Approach

Historically, many teams have relied on manually crafted prompts, often reusing or slightly modifying them. Anthropic’s recent publication challenges this by proposing a structured, asset-based model. The company’s internal experiments involved cataloging hundreds of Skills, which are now categorized into nine types, from reference management to operational automation. This approach aligns with broader trends toward modular, reusable AI components, but with a focus on organizational knowledge and process fidelity.

Prior to this, the industry lacked a formalized method for scaling and maintaining complex AI behaviors, often leading to inconsistent outputs and onboarding challenges. Anthropic’s method aims to address these gaps by creating durable, versioned, and sharable assets—Skills—that can evolve and improve over time, much like software libraries.

“Viewing Skills as folders containing instructions and assets fundamentally changes how organizations can manage AI capabilities.”

— Thorsten Meyer, AI researcher

Amazon

AI scripting and instruction organization software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Skill Implementation

It is not yet clear how broadly this approach has been adopted outside Anthropic or how easily other organizations can implement similar folder-based Skills at scale. Details about tooling, integration challenges, and real-world performance metrics remain limited, and the long-term asset value of Skills is still being evaluated.

Amazon

AI workflow automation assets

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Future Developments in AI Skill Management

Organizations are expected to experiment with structuring their own Skills as folders, potentially developing standardized frameworks and tools. Anthropic may release more detailed guidelines or software support to facilitate adoption. Monitoring how Skills evolve, their impact on AI reliability, and their integration into operational pipelines will be critical in the coming months.

Amazon

AI skills management folders

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 performance?

It allows for more comprehensive, organized knowledge management, leading to more consistent outputs, easier onboarding, and better error handling.

Can this approach be adopted by other AI teams?

Yes, but it requires developing infrastructure to manage, version, and discover folder-based Skills, which may involve significant tooling investment.

What types of Skills are most valuable?

According to Anthropic, verification Skills that check output quality are the most impactful, but other categories like automation and infrastructure are also critical.

Will this change how prompts are used?

Yes, moving from static prompts to structured folders reduces reliance on ad-hoc prompting and promotes more durable, reusable capabilities.

What are the main challenges in implementing folder-based Skills?

Developing tooling for managing, discovering, and updating Skills, as well as integrating them into existing workflows, remains a challenge for many organizations.

Source: ThorstenMeyerAI.com

HALLOWEEN

Halloween Picks

As an affiliate, we earn on qualifying purchases.

You May Also Like

How AI Agents Detect Files Hidden Beneath The Surface

New tests show AI agents’ ability to locate hidden information in files influences commercial outcomes and trustworthiness.

The $60 Billion Bargain: Why Cursor Could Be a Steal for SpaceX

SpaceX’s $60 billion all-stock purchase of AI coding startup Cursor marks a strategic move, potentially transforming its AI capabilities and market position.

Mobilised, Not Spent: What’s Left of Europe’s €200 Billion AI Offensive

Europe aims to mobilize €200 billion for AI, but only a small portion is committed and available now. The rest is uncertain, late, and largely hypothetical.

Outcome-First Decisions: The Friction Is The Feature

A new decision framework prioritizes decisive actions over elaborate plans, focusing on proof tests and clear verdicts to reduce costly missteps.