📊 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 effective AI skills are best understood as folders containing instructions, scripts, and assets, not just prompts. This approach enhances consistency, onboarding, and continuous improvement in AI workflows, signaling a shift in how organizations build and manage AI capabilities.

Anthropic has announced a significant shift in how organizations should think about AI ‘Skills,’ emphasizing that a Skill is not just a prompt, but a folder containing instructions, scripts, and assets. This approach, derived from their internal experiments with hundreds of Skills, aims to make AI capabilities more durable, consistent, and easier to maintain, representing a fundamental change in prompt engineering and organizational knowledge management.

According to a detailed write-up from a Claude Code engineer, Anthropic’s approach involves packaging knowledge into folders rather than simple prompts. Each Skill folder can include instructions, reference documents, scripts, templates, data, configuration, and hooks that activate during operation. This structure allows AI agents to discover, read, and execute complex workflows, making the process more robust and reusable.

Anthropic’s internal experiments revealed that organizing Skills as folders enhances consistency across outputs, simplifies onboarding by capturing tribal knowledge, and allows continuous improvement through iterative refinement. They identified nine core categories of Skills, ranging from library references to infrastructure operations, with verification Skills deemed most valuable for quality control.

The technical insight emphasizes that effective Skills should avoid restating obvious facts and instead focus on non-obvious, specific content. The description of each Skill acts as a trigger, matching user requests with the appropriate folder, making the system more reliable and context-aware. This approach transforms prompt engineering into a systematic, asset-based process that organizations can version, share, and improve over time.

At a glance
reportWhen: published recently, based on Anthropic’…
The developmentAnthropic published insights from its internal experience running hundreds of ‘Skills’ as organized folders, redefining how AI capabilities are structured and maintained.
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 Capabilities Into Organizational Assets

This development signals a shift from ad-hoc prompt tuning to building structured, reusable organizational assets for AI. By treating Skills as folders, companies can achieve more consistent outputs, streamline knowledge transfer, and foster iterative refinement. This approach could significantly improve the scalability and reliability of AI deployment across industries, moving beyond simple prompt tweaking to a more disciplined, asset-based methodology.

Pydantic AI for Automation Workflows: Build Typed, Reliable, and Production-Ready AI Automations in Python

Pydantic AI for Automation Workflows: Build Typed, Reliable, and Production-Ready AI Automations in Python

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompt Engineering to Asset Management

Prior to this, most organizations relied on prompt engineering—crafting specific instructions for each task—an approach that is fragile and hard to scale. Anthropic’s internal experiments with hundreds of Skills revealed that packaging instructions, scripts, and knowledge into folders creates a more durable and maintainable system. This aligns with broader trends in AI towards modular, reusable components, and reflects lessons learned from deploying large language models in complex workflows.

The concept of Skills as folders builds on existing practices but formalizes them into a structured, version-controlled system. Anthropic’s categorization into nine Skill types offers a framework for organizations to identify gaps and build comprehensive capabilities, especially in areas like verification and automation that directly impact output quality.

“A Skill is a folder — one that can contain instructions, reference documents, runnable scripts, templates, data, configuration, and even hooks that fire only while the Skill is active.”

— Thorsten Meyer, AI engineer at Anthropic

General Tools 843/1 Pencil Compass and Scriber, 8 Inch Diameter

General Tools 843/1 Pencil Compass and Scriber, 8 Inch Diameter

COMPASS AND SCRIBE: Designed for marking contours and drawing circles or arcs.

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Uncertain Impact and Adoption Challenges

It remains unclear how widely this folder-based approach will be adopted outside Anthropic and how it will perform across diverse organizational contexts. The practical challenges of implementing such structured Skills at scale, including version control, integration with existing workflows, and user training, are still being evaluated. Additionally, the long-term benefits versus traditional prompt engineering are yet to be empirically validated in different industries.

Sooez 24 Packs Plastic Envelopes Plastic File Folders, Clear Document Organizer Folder US Letter A4 Size Folders for Documents with Label Pocket for School Office Work Home Organization, Fresh Colors

Sooez 24 Packs Plastic Envelopes Plastic File Folders, Clear Document Organizer Folder US Letter A4 Size Folders for Documents with Label Pocket for School Office Work Home Organization, Fresh Colors

Colorful Transparent Folders: Refresh your storage with 5 Pastels Colors:pink, yellow, green, blue, purple, transparent. Each color with…

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Implementation and Validation

Organizations interested in this approach should begin by cataloging their existing knowledge assets into structured folders, focusing on critical categories like verification and automation. Observing how these Skills perform in real workflows will inform best practices and potential tooling enhancements. Further, Anthropic is likely to publish more detailed case studies and tools to facilitate adoption, while industry peers may adapt these concepts into their own AI management frameworks.

AI Prompt Engineering: Foundations of Communication with LLMs – Building Generative AI and Agentic AI Prompt Systems Across Development, Testing, and Deployment (AI Engineering)

AI Prompt Engineering: Foundations of Communication with LLMs – Building Generative AI and Agentic AI Prompt Systems Across Development, Testing, and Deployment (AI Engineering)

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

How does a Skill as a folder improve AI reliability?

By containing comprehensive instructions, scripts, and knowledge, a folder-based Skill ensures that AI agents follow consistent, well-defined processes, reducing errors and variability in outputs.

Can this approach be applied to existing prompt engineering practices?

Yes, organizations can start by organizing their prompt instructions and related assets into folders, gradually replacing ad-hoc prompts with structured Skills for better maintainability and scalability.

What are the main categories of Skills identified by Anthropic?

They include library references, product verification, data analysis, business process automation, code scaffolding, quality review, deployment, runbooks, and infrastructure operations.

What challenges might organizations face in adopting this model?

Potential challenges include establishing effective version control, integrating Skills into existing workflows, training staff, and scaling the approach across complex organizations.

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

What Are The Best AI Automation Software Tools For 2026?

Explore the top AI automation tools for 2026, including OpenCode, Claude, and Microsoft 365, and learn how they support workflow automation across industries.

Apple Silicon’s Quiet Memory Advantage

Apple Silicon chips offer a unique memory architecture that enables large model capacity at lower cost and power, but with trade-offs in speed.

Public Test Results Highlight AI’s Effectiveness In Tracking Stability

Recent benchmark results demonstrate a 42% reduction in identity switches using an advanced AI tracker in synthetic scenes, confirming AI’s effectiveness.

The Delegation Ladder: The Four Agentic Loops, And What Each One Lets You Stop Doing

An analysis of the four agentic loops in AI design, detailing what each enables and how they shift control from humans to autonomous systems.