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 shared insights from running hundreds of ‘Skills’ internally, emphasizing that Skills are folders containing instructions and assets, not just prompts. This approach improves consistency, onboarding, and institutional knowledge for AI agents.

Anthropic has announced a new approach to developing AI capabilities, emphasizing that Skills are structured as folders containing instructions, scripts, and reference assets, rather than simple prompts. This shift aims to create durable, reusable organizational assets that improve consistency and knowledge sharing across teams. The company has tested this method internally by running hundreds of Skills, which serve as standardized units of operational knowledge for AI agents.

In a detailed write-up from a Claude Code engineer, Anthropic explains that a Skill is fundamentally a container—akin to a folder—that can include instructions, reference documents, scripts, templates, and hooks. Unlike prompts, which are ephemeral and often retyped daily, Skills are designed to be versioned assets that encapsulate how tasks are performed within the organization. This approach transforms ad-hoc prompting into a durable, institutional capability, allowing teams to share and improve Skills over time.

Anthropic identified nine categories of Skills, ranging from library references and data analysis to business process automation and infrastructure operations. The most valuable, according to the company, is verification—checking the quality of generated output—since it directly impacts output reliability. The company advocates for investing significant effort into building high-quality Skills, viewing them as assets that grow sharper with use and iteration.

At a glance
reportWhen: published recently, ongoing implementat…
The developmentAnthropic’s recent publication details its internal approach of packaging AI capabilities as folder-based Skills, shifting from prompt-based methods to reusable, structured units.
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 Capabilities into Reusable Organizational Assets

This approach signifies a fundamental shift in how organizations develop and maintain AI systems. By treating Skills as structured, versioned folders, companies can standardize procedures, reduce onboarding time, and cultivate institutional memory. The method also enables continuous improvement, as Skills evolve through iterations based on real-world edge cases, making AI deployment more reliable and scalable.

For businesses, this means moving beyond one-off prompts toward a systematic, asset-based approach that can be shared across teams and projects. It enhances consistency in AI output, reduces reliance on individual knowledge, and creates a foundation for more sophisticated automation and quality control processes. As a result, organizations can better leverage AI as a core operational tool rather than a ad-hoc experiment.

Amazon

AI development folder structure tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Structured Knowledge Management

Anthropic’s internal experiments with hundreds of Skills reveal that organizations often rely on repetitive prompt engineering, which is inefficient and fragile. The company’s new methodology stems from recognizing that prompts are ephemeral, whereas Skills—structured folders containing instructions, scripts, and assets—serve as durable, reusable building blocks. This insight aligns with broader industry trends toward modular, asset-based AI development.

Historically, AI teams have built capabilities through trial-and-error prompt tuning, which hampers scalability and consistency. Anthropic’s experience demonstrates that organizing institutional knowledge into Skills improves reliability and accelerates onboarding, as new team members can access comprehensive, versioned assets rather than scattered notes or unstructured prompts.

“A Skill is a folder that can contain instructions, reference documents, scripts, and hooks—it’s a container for how your organization actually does a thing, not just a prompt.”

— Thorsten Meyer, AI engineer at Anthropic

Generative AI Apps with LangChain and Python: A Project-Based Approach to Building Real-World LLM Apps

Generative AI Apps with LangChain and Python: A Project-Based Approach to Building Real-World LLM Apps

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Aspects of Skill Implementation and Scalability

It is not yet clear how broadly this folder-based Skills approach can be adopted across different organizations or AI platforms. The specifics of integrating Skills into existing workflows, especially at scale, remain under development. Additionally, the process for maintaining, updating, and governing Skills over time is still being refined, and how this impacts long-term operational efficiency is uncertain.

Asset Management & AI: How AI integrates to optimize IT Asset Management

Asset Management & AI: How AI integrates to optimize IT Asset Management

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Standardization

Anthropic plans to further develop its Skills framework, potentially releasing tools and best practices for other organizations to adopt this model. Industry observers anticipate that more companies will experiment with structured asset-based approaches, and standardization efforts may emerge around Skills management. Monitoring how these practices influence AI reliability and operational automation will be key in the coming months.

AI-Assisted Creative Asset Version Control: Digital Content Management That Tracks Project Evolution

AI-Assisted Creative Asset Version Control: Digital Content Management That Tracks Project Evolution

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How is a Skill different from a prompt?

A Skill is a structured folder containing instructions, scripts, and assets, serving as a reusable, versioned unit of organizational knowledge. In contrast, a prompt is a simple text instruction that is often ephemeral and retyped.

What benefits does this approach offer?

It improves consistency of AI output, accelerates onboarding, captures institutional knowledge, and creates assets that improve with use. It also enables more reliable automation and quality control.

Can this model be applied outside of Anthropic?

While Anthropic developed this approach internally, the principles of structuring AI capabilities as reusable folders could be adapted by other organizations seeking more reliable and scalable AI deployment.

What challenges remain in implementing Skills broadly?

Integrating Skills into existing workflows, managing updates, and establishing governance are ongoing challenges. Scalability and cross-team collaboration are also areas needing development.

Will this approach reduce prompt engineering efforts?

Yes, by encapsulating knowledge into Skills, organizations can reduce repetitive prompt tuning and focus on improving the underlying assets, leading to more stable and maintainable systems.

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

ChannelHelm: One Video, Every Platform

ChannelHelm automates creating multi-platform content from a single video, reducing manual effort and expanding reach efficiently.

The rails. Why European agentic commerce is co-defined by two converging regimes.

European law is shaping agentic commerce through two regulatory regimes—PSD3/PSR and the AI Act—creating a complex, statutory infrastructure that differs from US models.

Readiness: Before You Fund the Answer

A new diagnostic tool offers companies a quick, 20-minute assessment to determine AI deployment readiness, aiming to prevent costly failures.

The Deploy Button Became the Bottleneck — and Cloudflare Just Bought the Build Step

Cloudflare’s acquisition of VoidZero aims to streamline deployment pipelines, integrating build tools directly into its edge network, marking a major industry shift.