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 designing AI Skills as comprehensive folders, not just prompts, enhances consistency, onboarding, and scalability. This approach is now central to their operational strategy.

Anthropic has revealed that their AI Skills are structured as folders containing instructions, reference documents, scripts, and configurations, rather than just saved prompts. This approach, tested across hundreds of internal applications, aims to make AI-driven processes more consistent, maintainable, and scalable. The development signifies a shift from ad-hoc prompt engineering to building durable, reusable organizational assets, according to a detailed internal write-up shared by Anthropic.

The core discovery is that a Skill is a folder that can include various components: instructions, reference materials, executable scripts, templates, and hooks. This structure allows AI agents to discover, read, and execute the contents dynamically, rather than relying solely on static prompts. For business teams, this means encapsulating operational knowledge, guardrails, and tools into a single, versioned asset that improves output consistency and onboarding efficiency.

Anthropic’s internal experience involves running hundreds of Skills, which they categorize into nine types, including library references, product verification, data analysis, automation, code scaffolding, review, deployment, runbooks, and infrastructure operations. The most impactful Skills are those that verify outputs, catching errors before deployment, which the company emphasizes as a high-value area. Building these Skills involves capturing non-obvious, specific knowledge about the organization’s workflows, avoiding generic prompts or instructions.

At a glance
reportWhen: announced April 2024
The developmentAnthropic published insights from running hundreds of Skills internally, showing that Skills are folders with instructions, scripts, and knowledge, 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

Implications of Reusable Folder-Based Skills for AI Operations

This development indicates a paradigm shift in how organizations develop and manage AI agents. Moving from prompt retyping to structured, versioned Skills enables more consistent results, faster onboarding, and scalable maintenance. It also allows organizations to codify tribal knowledge and operational procedures into assets that improve over time, potentially reducing costs and increasing reliability of AI-driven workflows.

For businesses, adopting Skills as folders could transform operational procedures, making AI tools more dependable and easier to update. The emphasis on verification Skills highlights the importance of quality control, which could lead to fewer errors in deployment and higher trust in AI outputs.

Designing Instruction with Generative AI: 24/7 Support for Optimizing Teaching and Learning

Designing Instruction with Generative AI: 24/7 Support for Optimizing Teaching and Learning

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Asset Building: Anthropic’s Internal Evolution

Until now, most AI teams relied on prompt engineering—crafting instructions that guide model behavior temporarily. Anthropic’s internal experiments, as documented in their recent write-up, challenge this norm by demonstrating that organizing instructions, scripts, and knowledge into reusable folders creates a durable asset. This approach aligns with broader trends toward modular, maintainable AI systems and reflects lessons learned from hundreds of internal deployments.

Anthropic’s categorization of Skills into nine types provides a framework for organizations to identify gaps in their own processes, from data fetching to infrastructure maintenance. The focus on verification Skills underscores a shift toward embedding quality assurance into the core of AI workflows, rather than treating it as an afterthought.

“A Skill is not just a prompt; it’s a folder that contains everything needed to perform a task reliably.”

— Thorsten Meyer, AI researcher at Anthropic

Lua Programming with AI: A Complete Beginner's Guide to Lua Scripting, Game Development, Automation, and AI Integration

Lua Programming with AI: A Complete Beginner's Guide to Lua Scripting, Game Development, Automation, and AI Integration

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Implementing Folder-Based Skills

It is not yet clear how broadly this approach has been adopted outside Anthropic or how it performs in diverse organizational contexts. Details about the specific technical implementation, integration challenges, and scalability in large enterprises remain unpublished. Additionally, the long-term maintenance and versioning strategies for Skills as folders are still being developed and tested.

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.

Next Steps for Organizations Adopting Skills as Organizational Assets

Organizations interested in this approach should evaluate their current workflows and identify operational knowledge that can be codified into Skills. Developing a library of reusable Skills, especially verification and automation ones, could improve AI reliability and efficiency. Future updates from Anthropic and other AI developers are expected to clarify best practices, tooling, and scalability considerations for implementing folder-based Skills at scale.

AI Workflow Systems: AI Prompts for Freelance Consultants: Practical AI workflow prompts to automate client work, boost productivity, and scale consulting ... Frameworks for the Modern World Book 1)

AI Workflow Systems: AI Prompts for Freelance Consultants: Practical AI workflow prompts to automate client work, boost productivity, and scale consulting … Frameworks for the Modern World Book 1)

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

By encapsulating instructions, scripts, and knowledge into a single, versioned asset, Skills ensure that AI agents perform tasks in a uniform way, reducing variability caused by ad-hoc prompts.

What types of organizational knowledge are best suited for Skills?

Operational procedures, verification routines, data handling protocols, and automation workflows are prime candidates for encoding into Skills as folders.

Are folder-based Skills applicable to all AI platforms?

While Anthropic has demonstrated this internally, adapting the approach to other platforms depends on their support for dynamic instruction sets, scripting, and modular asset management. Broader adoption is still emerging.

What are the main challenges in implementing Skills as folders?

Technical integration, version control, and maintaining synchronization between scripts and instructions are potential hurdles. Additionally, training teams to think in terms of assets rather than prompts is a cultural shift.

Source: ThorstenMeyerAI.com

You May Also Like

Liquid vs Air Cooling for 24/7 Inference Rigs

Comparing liquid and air cooling for continuous AI inference systems, focusing on reliability, cost, and performance over long-term operation.

AmenGate: The Moment Before The Scroll

AmenGate introduces a faith-based prayer lock for iPhone, replacing scrolling with prayer, built on system-level security to foster meaningful phone use.

The Bottleneck Moved: Inside Anthropic’s Expansion of Project Glasswing

Anthropic extends Project Glasswing to over 150 organizations, shifting focus from vulnerability detection to fixing and deploying patches faster.

Different Game, or Already Lost? Reading Mistral’s Sovereignty Bet

Analyzing Mistral’s focus on European sovereignty in AI through open weights, local infrastructure, and small models amid Europe’s race to build independent AI capabilities.