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 building AI skills as comprehensive folders—containing instructions, scripts, and assets—improves consistency, onboarding, and institutional knowledge. This approach shifts the focus from prompts to reusable, durable organizational units.

Anthropic has revealed that effective AI skills are best conceptualized as folders, not prompts, based on their experience running hundreds of these structured units across their engineering teams. This approach emphasizes creating reusable containers that bundle instructions, scripts, and reference materials, leading to more consistent and maintainable AI operations. The development marks a shift from ad-hoc prompt engineering towards durable, institutionalized capabilities that can be versioned and shared across an organization.

In a detailed write-up from a Claude Code engineer, Anthropic explains that a Skill is a folder—not just a prompt—containing instructions, reference documents, runnable scripts, templates, data, configuration, and hooks. This redefinition changes how AI capabilities are built and maintained, emphasizing the importance of structured, multi-component assets that an agent can discover, read, and execute.

Anthropic’s internal experiments show that these Skills improve output consistency, streamline onboarding, and compound over time as they are refined through edge cases and real-world use. The company categorizes its Skills into nine clusters, including data analysis, code scaffolding, verification, and operational procedures, with verification being the most impactful in improving output quality, according to their metrics.

Technical lessons highlight that effective Skills avoid restating obvious information, instead focusing on non-obvious, organization-specific knowledge. The description and trigger definitions for each Skill are critical, ensuring the agent activates the correct Skill based on user input. Bundling real code and helper functions within Skills further enhances their utility and robustness.

At a glance
reportWhen: announced March 2024
The developmentAnthropic published findings from running hundreds of AI skills structured as folders, emphasizing a new approach to building reliable, reusable AI capabilities.
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

Impact of Folder-Based Skills on AI Development

This approach fundamentally alters how organizations develop and maintain AI capabilities. By shifting from prompt-based instructions to structured, reusable folders, companies can achieve more consistent outputs, reduce onboarding time, and build a durable institutional memory. This method also turns Skills into assets that improve with use, representing an investment in organizational knowledge rather than disposable prompts.

For businesses, this means AI can become more reliable and scalable, with capabilities that evolve systematically rather than through ad-hoc prompt tuning. The emphasis on verification Skills also suggests a focus on quality control, reducing errors and increasing trust in AI outputs, especially in operational or safety-critical contexts.

Amazon

AI development environment tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Background on Anthropic’s Approach to AI Skills

Prior to this development, most teams relied on prompt engineering—crafting specific instructions for each task—an approach that is flexible but often inconsistent and hard to maintain at scale. Anthropic’s internal research, shared publicly in their recent write-up, demonstrates that structuring Skills as folders with multiple components allows for better control, versioning, and reuse. Their categorization into nine skill types provides a framework for organizations to identify gaps and systematically improve their AI capabilities.

This shift aligns with broader trends in AI development, emphasizing modularity, robustness, and institutional memory, moving away from one-off prompts towards building organizational assets.

“A Skill is a folder—containing instructions, scripts, and assets—that can be discovered and executed by the agent, transforming prompt engineering into a durable capability.”

— Thorsten Meyer, AI researcher at Anthropic

Amazon

AI scripting and automation software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Folder-Based Skills

It is not yet clear how broadly this approach has been adopted outside Anthropic or how it performs in diverse operational environments. Details on how Skills are maintained, updated, and scaled across large organizations remain to be seen. Additionally, the long-term impact on AI safety, reliability, and ease of use is still under investigation.

Amazon

AI knowledge management systems

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Organizations Adopting Skills Frameworks

Organizations interested in this approach should begin cataloging existing capabilities into structured folders, focusing on verification and operational Skills. Further research and case studies are expected to emerge, demonstrating how Skills evolve and how they can be integrated into larger AI deployment pipelines. Anthropic is likely to continue refining their methodology and sharing best practices.

Amazon

AI instruction and script organization tools

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

A Skill is a structured folder containing instructions, scripts, and assets, whereas a prompt is a simple instruction or question. Skills enable reusable, versioned, and durable capabilities for AI agents.

What are the benefits of using folder-based Skills?

Skills improve output consistency, simplify onboarding, and accumulate organizational knowledge, making AI capabilities more robust and scalable over time.

Can this approach be applied outside of AI coding agents?

Yes, the principles of bundling instructions, reference materials, and scripts into reusable containers can be adapted to various AI applications and operational workflows.

What are the main categories of Skills identified by Anthropic?

They include library and API reference, product verification, data analysis, business process automation, code scaffolding, code review, CI/CD, runbooks, and infrastructure operations.

Source: ThorstenMeyerAI.com

You May Also Like

AI Changelog Digest For Open-source Maintainers

A new AI-powered weekly digest tool aims to help solo open-source maintainers summarize releases, dependencies, and issues across multiple repositories.

Building an AI Trading Bot — Week One: Why a 90 % Win Rate Can Still Lose Money

A week into testing an AI trading bot shows high win rates don’t guarantee profits. This analysis explains why, based on simulated crypto markets.

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

Threlmark’s innovative approach uses local disk storage as the single source of truth, enabling portable, restartable, and interoperable project workflows without a database.

ChannelHelm: One Video, Every Platform

ChannelHelm automates the creation of multi-platform content from a single video, reducing manual effort and increasing distribution efficiency.