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 AI Skills internally, emphasizing that Skills are more like folders containing instructions and tools than simple prompts. This approach improves consistency, onboarding, and scalability for AI-driven workflows.

Anthropic has revealed that its internal approach to building AI Skills involves creating comprehensive folders—containing instructions, scripts, and assets—rather than relying on simple prompts. This shift aims to make AI outputs more consistent, scalable, and maintainable, marking a significant evolution in how organizations develop AI capabilities. The company’s detailed write-up, authored by a Claude Code engineer, emphasizes that Skills are durable assets that encapsulate organizational knowledge, rather than transient prompt instructions. This development has implications for both technical implementation and business operations.

According to Anthropic, a Skill is best understood as a folder—containing instructions, reference documents, scripts, templates, data, configuration, and hooks—that the AI agent can discover and execute. This contrasts sharply with the common misconception that Skills are merely saved prompts or markdown notes. For technical teams, this redefinition emphasizes a structured, asset-based approach to AI development, enabling more reliable and repeatable outputs.

Anthropic’s internal experience shows that organizing Skills into categories—such as verification, data analysis, automation, and infrastructure—helps identify gaps and improve workflows. Notably, the most valuable Skills are those that verify outputs, catching mistakes before they reach users. The company advocates investing significant effort into perfecting these verification Skills, viewing them as high-value, long-term assets that improve over time.

From a business perspective, the approach streamlines onboarding and institutional memory. Instead of relying on individual tribal knowledge or scattered wiki pages, organizations can develop comprehensive Skills that encapsulate best practices, guardrails, and operational procedures. This makes AI-driven processes more consistent across teams and reduces reliance on ad-hoc instructions.

At a glance
reportWhen: published recently, based on latest int…
The developmentAnthropic published a detailed account of their experience transforming ad-hoc prompts into reusable, organized Skills, redefining how organizations develop and manage 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

Implications for Organizational AI Development

This approach transforms how companies develop, maintain, and scale AI capabilities. By treating Skills as organized assets—folders with instructions and scripts—organizations can achieve greater consistency, reduce onboarding time, and continuously improve their AI workflows. It shifts the focus from one-off prompts to durable, sharable organizational assets, enabling AI to become a more reliable operational tool rather than a black box.

AI for Bookkeeping Automation and Workflows: Automate Data Entry, Receipts, Categorization, Reconciliation, and Month-End Reporting Using AI and No-Code Tools, Save Hours Every Week for Bookkeepers

AI for Bookkeeping Automation and Workflows: Automate Data Entry, Receipts, Categorization, Reconciliation, and Month-End Reporting Using AI and No-Code Tools, Save Hours Every Week for Bookkeepers

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset Management

Traditional AI prompt engineering has often involved crafting specific instructions for each task, which are then reused with minor variations. However, this method is fragile, inconsistent, and difficult to scale. Anthropic’s internal experiments with hundreds of Skills have demonstrated that packaging knowledge into structured folders significantly improves performance and reliability. This insight aligns with broader industry trends toward making AI systems more maintainable and transparent.

Previously, organizations relied on ad-hoc prompts, wiki pages, or tribal knowledge to guide AI behavior. Anthropic’s experience shows that formalizing this knowledge into Skills—comprehensive containers—enables better version control, sharing, and continuous improvement. The concept of Skills as organizational assets is a departure from the ephemeral nature of prompt-based workflows.

“A Skill is a folder—containing instructions, scripts, and assets—that the agent can discover and execute. It’s not just a prompt saved in markdown.”

— Thorsten Meyer, AI researcher at Anthropic

Amazon

AI development asset management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

What Aspects of Skills Development Are Still Unclear?

It remains uncertain how widely this approach will be adopted outside Anthropic, and whether other organizations will find it scalable for their specific workflows. Details about the tooling, integration, and management of Skills at scale are still emerging, and it is not yet clear how this model performs in diverse operational environments or with different AI architectures.

Amazon

AI verification scripts templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Implementing Skills in AI Operations

Organizations interested in this approach should evaluate how to structure their own Skills as folders containing instructions, scripts, and assets. Further development of tooling for managing, versioning, and sharing Skills is expected, along with case studies demonstrating the impact of this method on operational reliability and scalability. Industry-wide adoption may accelerate as more companies recognize the long-term value of durable organizational assets for AI.

Amazon

AI organizational knowledge folders

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 that the AI agent can discover and execute, whereas a prompt is a simple instruction or question sent to the AI. Skills are designed to be reusable, versioned, and maintainable assets, not just ephemeral instructions.

What benefits does organizing Skills as folders provide?

Organizing Skills as folders improves consistency, simplifies onboarding, enables continuous improvement, and creates durable organizational assets that can be shared and version-controlled across teams.

Will this approach work for all types of AI workflows?

While promising, the effectiveness of this approach depends on the specific use case and organizational maturity. Further testing and tooling are needed to determine scalability across diverse operational environments.

How much effort is required to develop high-quality Skills?

Anthropic suggests dedicating significant time—potentially a week or more—to perfect a Skill category, especially verification Skills, as these have the highest impact on output quality and reliability.

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

Build vs Buy a Prebuilt AI Workstation

Exploring the tradeoffs between building and buying AI workstations in 2026, including costs, deployment speed, and customization options.

7 Best PC Routers for Prime Day Deals in 2026

Discover the best PC routers on Prime Day 2026, including WiFi 7 models, wired options, and gaming routers, with expert picks and buying tips.

Mobilisiert, Nicht Ausgegeben: Was Von Europas €200-Milliarden-KI-Offensive üBrig Bleibt

Die EU kündigt €200 Milliarden für KI an, doch nur ein Bruchteil ist garantiert. Die tatsächlichen Investitionen sind deutlich geringer und verzögert.

Acoustic Dampening, Placement, and the “Rig in the Closet” Setup

Learn effective strategies for reducing noise from AI workstations, including placement, acoustic dampening, and the ‘rig in the closet’ setup, with expert insights.