AIThis post was created with the assistance of artificial intelligence (AI).

📊 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 Skills are not just prompts but comprehensive folders containing instructions, scripts, and assets. This approach enhances consistency, onboarding, and organizational learning in AI deployment.

Anthropic has revealed that its Skills are not simple prompts but folders that contain instructions, scripts, and assets, fundamentally changing how AI agents are built and maintained. This approach, based on extensive internal testing, aims to improve consistency, onboarding, and institutional knowledge management within organizations deploying AI.

In a detailed write-up from a Claude Code engineer, Anthropic explains that a Skill is a container—a folder that can include instructions, reference documents, runnable scripts, templates, data, and configuration. Unlike traditional prompts, these folders enable agents to discover, read, and execute complex workflows, making the process more durable and scalable.

This shift allows organizations to embed tribal knowledge and guardrails directly into the agent’s operational assets, rather than relying on ad-hoc prompting. The company emphasizes that Skills serve three core functions: ensuring output consistency, simplifying onboarding, and enabling continuous improvement through iteration.

Anthropic has identified nine categories of Skills, ranging from library references and product verification to infrastructure operations. The most valuable category, according to the company, is verification—skills that check the work—because they most significantly improve output quality. The approach is designed to turn repetitive tasks into reliable, automated procedures that can be versioned and shared across teams.

At a glance
reportWhen: announced March 2024
The developmentAnthropic shared insights from running hundreds of Skills internally, showing that packaging knowledge into folders improves AI agent reliability and operational capability.
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

How Skills Transform Organizational AI Deployment

This development matters because it shifts AI development from a manual, prompt-based process to a systematic, asset-based approach. Packaging knowledge into folders reduces variability, enhances reliability, and accelerates onboarding for new team members. It also creates a living library of institutional knowledge that improves over time, making AI tools more aligned with organizational practices and guardrails.

For businesses, this means more predictable AI output, faster integration of new workflows, and a foundation for scaling AI capabilities securely and efficiently. The approach signals a move toward operationalizing AI as a core organizational asset rather than a set of ad-hoc prompts, potentially setting new standards in enterprise AI deployment.

Building AI Agents for Network Operations: Design LLM-powered NetOps workflows with Python, Ollama, MCP, and tool calling

Building AI Agents for Network Operations: Design LLM-powered NetOps workflows with Python, Ollama, MCP, and tool calling

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Internal Testing and the Nine Skill Categories

Anthropic’s internal experiments involved cataloging Skills into nine categories, from reference management and code scaffolding to operational runbooks. These categories serve as a gap analysis tool, helping organizations identify missing capabilities or areas for improvement.

The company highlights that its best Skills started small—just a few lines of instructions—and improved through iterative refinement, especially in verification tasks. This process emphasizes that Skills are not static but evolve with organizational learning, capturing subtle institutional knowledge that prevents errors and enhances consistency.

Prior to this, most teams relied on prompt engineering, which often led to inconsistent outputs and onboarding difficulties. Anthropic’s approach aims to formalize and version control workflows, making AI deployment more reliable and scalable.

“A Skill is a folder, not just a prompt. It’s a container for instructions, scripts, and knowledge that the agent can discover and execute.”

— Thorsten Meyer, AI engineer at Anthropic

The Agentic AI Bible: The Complete and Up-to-Date Guide to Design, Develop, and Scale Goal-Driven, LLM-Powered Agents that Think, Execute and Evolve

The Agentic AI Bible: The Complete and Up-to-Date Guide to Design, Develop, and Scale Goal-Driven, LLM-Powered Agents that Think, Execute and Evolve

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unconfirmed Aspects of Skills Implementation

It is not yet clear how widely adopted this approach will be outside Anthropic or how it will scale across different organizational sizes and industries. Details on how Skills are maintained, updated, and governed over time are still emerging. Additionally, the precise impact on AI safety and control measures remains to be evaluated as organizations implement these practices.

AI Real Estate Playbook: How to Reclaim Your Time, Multiply Your Income, and Clone Yourself

AI Real Estate Playbook: How to Reclaim Your Time, Multiply Your Income, and Clone Yourself

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Validation

Organizations interested in this approach should begin cataloging their own Skills into similar categories, focusing on verification and institutional knowledge capture. Further research and case studies are expected to validate the long-term benefits and best practices for maintaining Skills libraries. Anthropic plans to share more detailed guidelines and tools to facilitate wider adoption.

MixPad Free Multitrack Recording Studio and Music Mixing Software [Download]

MixPad Free Multitrack Recording Studio and Music Mixing Software [Download]

  • Multitrack Recording and Mixing: Create mixes with audio, music, and voice tracks
  • Track Customization: Add effects and editing tools to tracks
  • Music Creation Tools: Includes Beat Maker and MIDI Creator

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

A Skill is a folder containing instructions, scripts, and assets, making it a reusable, versioned asset that encapsulates organizational knowledge, unlike a simple prompt which is just a text instruction.

What are the main benefits of using Skills?

Skills improve output consistency, simplify onboarding, and enable continuous improvement through iterative refinement, making AI deployment more reliable and scalable.

Can Skills be updated or refined over time?

Yes, Skills are designed to evolve through iterative improvements, capturing lessons learned and adapting to new edge cases, much like a living document or asset library.

Is this approach applicable to all organizations?

While promising, the approach’s effectiveness depends on organizational complexity and maturity. Larger or more process-driven organizations may benefit most initially, with broader applicability as best practices develop.

What challenges might organizations face adopting this model?

Potential challenges include establishing governance for Skills updates, integrating with existing workflows, and ensuring team buy-in for a shift from prompt engineering to asset management.

Source: ThorstenMeyerAI.com

You May Also Like

The Top AI Tools To Transform Your Business In 2026

Discover the leading AI tools in 2026 that are reshaping industries, from automation platforms to machine learning libraries, with confirmed developments and expert insights.

How Meta’s Muse Code AI Is Revolutionizing VR Development For Large-Scale Projects

Meta’s new Muse Code AI simplifies VR development for large projects, promising faster, more efficient creation of immersive environments.

AI Takes the Creative Reins in Tomorrow’s Marketing Teams

Harnessing AI’s creative power is transforming marketing teams, but understanding its full potential and future implications is essential—continue reading to explore more.

Government 2.0: AI in Public Services and Bureaucracy

AIThis post was created with the assistance of artificial intelligence (AI).Government 2.0…