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 are better understood as folders containing instructions and assets rather than just prompts. This approach improves consistency, onboarding, and asset management in AI workflows. The company ran hundreds of Skills internally, emphasizing their value as durable assets.

Anthropic has revealed that its AI Skills are not merely prompts but are structured as folders containing instructions, scripts, and assets, fundamentally changing how AI capabilities are built and maintained. This approach, based on internal experiments with hundreds of Skills, aims to make AI deployment more consistent, scalable, and durable, providing a new model for organizations leveraging AI tools.

According to a detailed write-up from a Claude Code engineer, a Skill is defined as a folder that can include various components such as instructions, reference documents, runnable scripts, templates, data, configuration, and hooks. This contrasts with the common misconception that Skills are simply saved prompts or markdown notes. The folder structure allows the AI agent to discover, read, and execute the contained assets, creating a more robust and reusable organizational asset.

Anthropic’s internal use of hundreds of Skills has demonstrated that this container approach enhances output consistency across different team members and roles. It also facilitates onboarding by encapsulating tribal knowledge and guardrails in a single, versioned asset. The company emphasizes that Skills are an appreciating asset, improving over time as they are refined through edge cases and real-world use, with teams investing significant effort—up to an engineer-week—to perfect specific categories of Skills.

Anthropic identified nine core Skill categories, including library references, product verification, data analysis, business process automation, code scaffolding, quality review, deployment, runbooks, and infrastructure operations. Among these, verification Skills—used to check the correctness of outputs—are considered the most valuable, as they directly impact output quality and safety.

At a glance
reportWhen: published recently; insights from Anthr…
The developmentAnthropic shared insights from its internal experience running hundreds of Skills, redefining Skills as folders that bundle instructions, scripts, and assets for organizational use.
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

How Skills Reshape Organizational AI Capabilities

This shift from prompts to folder-based Skills represents a significant evolution in AI deployment strategies. It enables organizations to create standardized, durable procedures that improve consistency, reduce onboarding time, and capture institutional knowledge effectively. By treating Skills as assets that can be versioned and refined, companies can build a more scalable and reliable AI infrastructure, potentially reducing costs and increasing trust in AI outputs.

Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results

Claude AI for Beginners Bible: [5 in 1] The Ultimate Guide to Automate Your Work, Save Hours Every Week, and Use AI for Real-World Results

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on AI Skill Development and Usage

Traditionally, organizations using AI have relied on ad-hoc prompting, often retyping instructions daily or creating one-off prompts that lack durability. Anthropic’s internal experience, shared in the recent write-up, challenges this approach by emphasizing the importance of structured, reusable assets. The company’s experimentation with hundreds of Skills has shown that organizing knowledge into folders improves both technical performance and organizational efficiency. This development aligns with broader trends toward modular, maintainable AI systems.

“A Skill is a folder — one that can contain instructions, reference documents, runnable scripts, templates, data, configuration, and even hooks that fire only while the Skill is active.”

— Thorsten Meyer, AI engineer at Anthropic

Amazon

AI instruction and asset management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Skill Implementation

It is not yet clear how widely other organizations will adopt this folder-based approach or how it scales in different operational contexts. Details on the specific technical implementation and integration with existing systems remain limited, and the long-term impact on AI safety and reliability is still under evaluation.
Amazon

AI workflow organization tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Validation

Organizations interested in this approach will likely experiment with creating their own Skills folders, focusing on categories most relevant to their workflows. Further technical details and case studies from Anthropic are expected to emerge, providing guidance on best practices. Additionally, industry-wide discussions may follow to evaluate the scalability and security implications of this container-based model.

Amazon

AI skills folder structure

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does a Skill differ from a traditional prompt?

A Skill is a structured folder containing instructions, scripts, and assets, making it a reusable organizational asset, whereas a prompt is typically a single, static instruction or question.

What benefits does organizing Skills as folders provide?

It improves consistency, facilitates onboarding, captures institutional knowledge, and allows Skills to be refined and versioned over time, acting as assets that grow in value.

Can this approach be applied outside of Anthropic?

Yes, the concept of containerized, reusable assets for AI workflows can be adopted by other organizations aiming for scalable and reliable AI deployment, though technical implementation details may vary.

What are the main categories of Skills identified?

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

What remains uncertain about this approach?

Widespread adoption, technical scalability, integration challenges, and long-term safety implications are still under discussion and evaluation.

Source: ThorstenMeyerAI.com

This content is for general information only and is not financial, tax or legal advice. Consult a qualified professional for decisions about your money.
You May Also Like

The High-End PC and Workstation Tax

Memory prices soar in 2026, making high-end PC and workstation builds more expensive and challenging for DIY builders. Here’s what you need to know.

Technology Operations Signal Monitor: The Future Of Flipper Zero Development

A new technology operations signal monitor is being tested to track updates on Flipper Zero development, targeting product leads at small software firms.

Search as Code: Perplexity Is Right About the Future — Just Not First to It

Perplexity introduces Search as Code (SaC), enabling AI systems to build custom retrieval pipelines. This could reshape search for AI agents, but some claims remain unverified.

Forezai · TradingAgents: A Trading Firm Made of Agents

Forezai introduces TradingAgents, an open-source framework mimicking a trading desk with specialized AI agents debating and vetting market decisions.