📊 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’ in AI agents are best conceptualized as folders containing instructions, scripts, and knowledge, not just prompts. This approach improves consistency, onboarding, and scalability of AI systems.

Anthropic has announced a significant shift in how AI agents are developed and maintained, emphasizing that Skills are not merely saved prompts but folders containing instructions, scripts, and knowledge. This approach, tested across hundreds of internal Skills, aims to standardize and improve the durability of AI-driven workflows, making them more reliable and easier to scale.

The core insight from Anthropic is that a Skill should be viewed as a container—a folder that includes not only prompts but also reference documents, executable scripts, templates, configuration files, and hooks. This redefinition moves away from the idea that Skills are just text prompts, emphasizing their role as comprehensive organizational assets.

Anthropic’s internal implementation involves cataloging Skills into nine categories, ranging from library references and data analysis to operational runbooks and automation. The most impactful category, according to the company, is verification Skills, which ensure the correctness of AI output by checking for mistakes and enforcing standards. This focus on verification has led to notable improvements in output quality and consistency.

Experts involved in the project note that this approach makes AI agents’ behavior more predictable and easier to onboard new team members, as the knowledge is embedded directly into the Skills folders. The process also allows continuous refinement, with Skills improving over time as edge cases are documented and addressed.

At a glance
reportWhen: announced March 2024
The developmentAnthropic shared insights from running hundreds of Skills internally, emphasizing that Skills are folders with comprehensive organizational content, not simple prompts.
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 Development with Modular Skills

This development matters because it shifts the paradigm from ad-hoc prompting to building durable, reusable organizational assets. By treating Skills as folders that encapsulate knowledge and tools, companies can achieve more consistent AI outputs, streamline onboarding, and create a scalable library of best practices. For organizations heavily reliant on AI automation, this approach could significantly reduce errors and operational risks, making AI deployment more reliable and manageable.

Create a Podcast with AI (No Experience Needed) : A Step-by-Step Guide to Planning, Scripting, Recording, Editing, and Launching a Podcast Using ChatGPT, AI Tools, and Automation

Create a Podcast with AI (No Experience Needed) : A Step-by-Step Guide to Planning, Scripting, Recording, Editing, and Launching a Podcast Using ChatGPT, AI Tools, and Automation

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Organizational Assets

Prior to this revelation, most AI teams relied on prompt engineering—crafting specific instructions for each task, often retyping or copying prompts. Anthropic’s internal experiments with hundreds of Skills have demonstrated that organizing knowledge into folders enhances robustness and reusability. This insight aligns with broader industry trends towards modular AI components but emphasizes the importance of comprehensive organizational design rather than isolated prompt tweaks.

The concept was developed through internal testing and documentation, with Anthropic’s engineers documenting their processes and categorizing Skills into nine distinct types. This methodology aims to replace brittle, one-off prompts with durable, versioned assets that reflect actual organizational workflows.

“A Skill is not just a prompt; it’s a folder containing instructions, scripts, and knowledge that can be discovered and executed by the agent.”

— Thorsten Meyer, AI engineer at Anthropic

Agentic Spec-Driven Development: A Practical Method for Using AI to Build Complete Specifications for Software, Products, and Knowledge Work

Agentic Spec-Driven Development: A Practical Method for Using AI to Build Complete Specifications for Software, Products, and Knowledge Work

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unclear Aspects of Skill Implementation and Adoption

It is not yet clear how widely this approach will be adopted outside Anthropic or how it will integrate with existing AI development pipelines. Details about the specific tooling, standards, or best practices for creating and managing Skills as folders remain under development, and industry-wide adoption may face challenges related to tooling and organizational change.

AI-Native Software Delivery: Proven Practices to Produce High-Quality Software Faster

AI-Native Software Delivery: Proven Practices to Produce High-Quality Software Faster

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Industry Adoption and Tooling Development

Anthropic plans to further refine its Skills framework and share best practices with the broader AI community. Future developments may include standardized tools for creating, versioning, and managing Skills as folders, as well as integration with popular AI development platforms. Industry observers expect other organizations to experiment with similar approaches, potentially leading to more modular, maintainable AI systems.

The Human-Agent Orchestrator: Leading and Scaling AI-Driven Organizations

The Human-Agent Orchestrator: Leading and Scaling AI-Driven Organizations

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does treating Skills as folders improve AI performance?

By encapsulating instructions, scripts, and knowledge in a structured container, Skills become more consistent, easier to update, and less prone to errors, leading to more reliable AI outputs.

What are the main categories of Skills identified by Anthropic?

Anthropic identified nine categories, including library references, data analysis, verification, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations.

Will this approach work for all types of AI tasks?

While promising for automation and operational workflows, the effectiveness of folder-based Skills may vary depending on the complexity and domain of the AI application. Further testing is needed across different use cases.

What challenges might organizations face adopting this model?

Challenges include developing tooling for managing folder-based Skills, training teams to design effective containers, and integrating this approach into existing workflows and systems.

Source: ThorstenMeyerAI.com

You May Also Like

Implementing Observability: Tracing and Log Analytics at Scale

Implementing observability with scalable tracing and log analytics reveals critical insights that can transform your system’s reliability—discover how to unlock its full potential.

RHEO On Steam: One Toy, Every Screen

RHEO is launching on Steam, offering a fluid art experience across PC, Steam Deck, VR, and more with seamless sync and device compatibility.

Disk Is the Contract: Inside Threlmark’s Local-First Architecture

Threlmark treats local disk storage as the definitive source of truth, simplifying sync and enhancing offline usability. Here’s how this approach works.

The Gulf: Own the Capital

Gulf states are investing heavily in AI infrastructure, aiming to own the technology displacing labor, funded by oil wealth and sovereign funds.