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 shifted from prompts to ‘Skills’—folders containing instructions, scripts, and knowledge—to improve AI agent consistency and organizational learning. This approach transforms ad-hoc prompting into durable, shareable assets.

Anthropic has introduced a new approach to managing AI capabilities by organizing them into ‘Skills’—comprehensive folders containing instructions, scripts, and reference materials—rather than relying on prompts. This shift aims to make AI outputs more consistent, facilitate onboarding, and capture organizational knowledge more effectively. The approach is based on internal experiments and is now shared as a best practice for AI teams seeking to institutionalize their workflows.

According to a detailed write-up from a Claude Code engineer, Anthropic’s ‘Skills’ are not merely saved prompts but are structured folders that can include instructions, reference documents, runnable scripts, templates, data, configuration, and hooks. These Skills enable AI agents to discover, read, and execute the contents within, creating a more durable and reusable asset for organizational tasks.

This method contrasts sharply with traditional prompt engineering, which often involves retyping or copying instructions. Instead, Skills encapsulate the knowledge and processes used by teams, making output consistent across different users and roles. They also significantly reduce onboarding time by embedding tribal knowledge directly into the AI’s operational framework.

Anthropic’s internal analysis identified nine categories of Skills, ranging from library references and product verification to infrastructure operations. The most valuable Skills, according to the company, are those that verify work quality—such as testing signup flows or checking code—because they directly improve output accuracy and reliability. The company advocates investing substantial effort—up to an engineer-week—for each category to refine and improve these Skills over time.

At a glance
reportWhen: published recently; insights shared by…
The developmentAnthropic published insights from running hundreds of Skills within its engineering team, demonstrating a new approach to organizing AI tasks as folders rather than 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 for AI Team Operations and Organizational Knowledge

This development suggests a paradigm shift in how organizations deploy and manage AI agents. By treating Skills as structured, shareable assets, companies can achieve greater consistency, reduce onboarding costs, and build a cumulative institutional memory. This approach also encourages a more disciplined, versioned, and scalable method of integrating AI into business processes, potentially setting a new standard for AI workflow management.

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.

From Prompt Engineering to Asset Building in AI Teams

Until now, most organizations relied on prompt engineering—crafting specific instructions for each task—leading to ad-hoc and inconsistent outputs. Anthropic’s move to organize capabilities into Skills reflects a broader effort to institutionalize AI workflows. This approach aligns with recent trends toward modular, reusable AI components, and is informed by internal experiments that demonstrated the benefits of structured knowledge management.

Anthropic’s internal documentation highlights that their best Skills started small and improved through iterative refinement, becoming assets that grow more valuable over time. The categorization into nine types provides a framework for assessing gaps and prioritizing development efforts, emphasizing verification and operational procedures as high-value areas.

“A Skill is not just a prompt saved in a text file; it’s a folder that contains instructions, scripts, and knowledge—an asset that organizations can reuse and improve over time.”

— Thorsten Meyer, AI researcher at Anthropic

AI Engineering: Building Applications with Foundation Models

AI Engineering: Building Applications with Foundation Models

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Skills Implementation and Scalability

It is not yet clear how widely this Skills approach has been adopted outside Anthropic or how it performs in different organizational contexts. The scalability of maintaining large Skills libraries, especially across diverse teams, remains to be tested. Additionally, the process for evolving Skills over time and integrating them with existing AI infrastructure is still being developed.

Amazon

AI scripting and instruction folders

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Method Refinement

Organizations interested in this approach should evaluate their current workflows and consider developing Skills as structured folders to improve consistency and knowledge sharing. Industry observers anticipate further case studies and best practices emerging as more teams experiment with this model. Anthropic is expected to refine its methodology and share additional insights on scaling and managing Skills in complex environments.

Agentic AI Playbook: A Practical Guide to Design, Build and Scale AI Agents

Agentic AI Playbook: A Practical Guide to Design, Build and Scale AI Agents

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How do Skills differ from traditional prompts?

Skills are structured folders containing instructions, scripts, and reference materials, making them reusable and durable assets, whereas prompts are typically just text instructions used once.

What are the main benefits of using Skills?

Skills improve output consistency, reduce onboarding time, and capture organizational knowledge as evolving assets that can be refined over time.

Are Skills applicable outside of AI coding teams?

Yes, the concept can be adapted to various operational domains where structured, reusable workflows and institutional knowledge are valuable.

What challenges might organizations face implementing Skills?

Maintaining large libraries, ensuring proper updates, and integrating Skills into existing systems may require significant effort and discipline.

Source: ThorstenMeyerAI.com

You May Also Like
When One Agent Isn’t Enough: Claude Now Builds Its Own Team of Agents on the Fly

When One Agent Isn’t Enough: Claude Now Builds Its Own Team of Agents on the Fly

Anthropic’s Claude now autonomously creates and manages teams of sub-agents for complex tasks, enhancing performance on high-value projects.
The City That Watches Itself: The Living Digital Twin, And The God’s-Eye View We’re Building

The City That Watches Itself: The Living Digital Twin, And The God’s-Eye View We’re Building

Cities are developing dynamic digital twins that combine real-time data and AI to improve planning and monitoring, raising both opportunities and privacy concerns.
RHEO on the Web: Find Your Flow

RHEO on the Web: Find Your Flow

Discover RHEO’s web version, offering instant, private, browser-based fluid simulations for relaxation, breathing, and creative play, with no downloads or sign-up.
The Menu: What Ten Answers Reveal

The Menu: What Ten Answers Reveal

Analyzing ten jurisdictions’ responses to automation and AI, revealing patterns and challenges in income, capital, work, skills, and institutions.