📊 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’ for AI agents are not just prompts but comprehensive folders with instructions, scripts, and assets. This approach improves consistency, onboarding, and institutional knowledge. The development emphasizes a shift from ad-hoc prompting to durable, reusable organizational assets.

Anthropic has announced a new approach to building AI agents: defining Skills as folders containing instructions, scripts, and reference materials, rather than simple prompts. This method aims to make AI output more consistent and organizational knowledge more durable, representing a significant shift in how AI capabilities are developed and maintained.According to a detailed write-up from an Anthropic Claude Code engineer, Skills are now understood as comprehensive folders that include instructions, reference documents, runnable scripts, templates, data, and configuration settings. This redefinition moves away from viewing Skills as mere prompts or markdown snippets. Instead, Skills serve as containers for how organizations actually perform tasks, encapsulating tribal knowledge, guardrails, and tools in a reusable format. Anthropic’s internal experiments show that this approach enhances consistency across AI outputs, simplifies onboarding by embedding organizational knowledge into the agent, and allows Skills to improve iteratively as they are refined over time. The company identified nine core categories of Skills, ranging from code scaffolding to operational runbooks, with verification Skills deemed most valuable for quality control. Technical lessons emphasize that effective Skills avoid stating the obvious, focus on non-trivial, non-default knowledge, and include ‘Gotchas’—traps and edge cases that capture institutional memory. Descriptions for Skills are trigger phrases designed for the agent to recognize when to activate a particular Skill, including internal slang and specific language used within the organization. This methodology aims to embed institutional knowledge directly into AI systems, making them more reliable and easier to maintain.
At a glance
reportWhen: published in early 2024, recent interna…
The developmentAnthropic published insights from running hundreds of Skills internally, revealing that Skills are folders with instructions and assets, not just prompts, which enhances AI deployment and organizational knowledge.
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 Organizational AI with Reusable Skill Folders

This development signifies a shift from ad-hoc prompt engineering to structured, reusable assets that embed organizational knowledge into AI systems. By treating Skills as folders containing instructions, scripts, and reference materials, companies can achieve greater consistency, reduce onboarding time, and create a durable knowledge base that improves with use. This approach has the potential to make AI deployment more scalable and reliable, especially in complex operational environments. It also highlights a move toward treating AI capabilities as institutional assets rather than transient prompts, which could redefine best practices in enterprise AI deployment.
Amazon

AI automation scripting tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Asset-Based AI Development

Prior to this shift, most organizations relied on prompt engineering—crafting specific instructions for AI models each time—resulting in inconsistent outputs and high onboarding costs. Anthropic’s internal experiments, as shared in their recent write-up, reveal that packaging knowledge into Skills as folders enables more stable, repeatable results. This approach aligns with broader trends toward modular, reusable AI components that can be versioned, shared, and improved over time. The concept builds on existing ideas of prompt tuning but expands them into a more comprehensive framework for organizational knowledge management. The nine categories of Skills identified by Anthropic reflect common operational needs, from code scaffolding to verification and operational procedures, emphasizing a holistic approach to AI integration. The focus on capturing edge cases and institutional memory through ‘Gotchas’ is a notable innovation, aiming to prevent recurring errors and ensure quality control.

“Redefining Skills as folders with instructions, scripts, and assets transforms how organizations embed knowledge into AI systems, making deployment more reliable and scalable.”

— Thorsten Meyer, AI researcher

Amazon

AI organizational knowledge management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unanswered Questions About Skill Implementation and Scaling

It is not yet clear how widely this folder-based Skills approach has been adopted outside Anthropic or how it performs in large-scale, real-world enterprise environments. The long-term impact on AI reliability, maintenance, and evolution remains to be seen, and some technical details about integrating these Skills into existing systems are still emerging.
Amazon

AI training and onboarding tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Next Steps for Broader Adoption and Validation

Organizations are expected to experiment with adopting folder-based Skills, potentially creating their own categories and refining the approach. Further case studies and technical reports will clarify how this methodology scales and integrates with existing AI workflows. Industry leaders may also explore standardization efforts to formalize Skills as reusable organizational assets, enhancing AI reliability and efficiency across sectors.
Amazon

AI development environment with templates

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

What exactly differentiates a Skill from a prompt?

A Skill is a comprehensive folder containing instructions, scripts, reference documents, and configuration, whereas a prompt is a simple instruction or question sent to the AI. Skills serve as reusable assets that encapsulate organizational knowledge and procedures.

How does this approach improve AI consistency?

By embedding detailed instructions, reference materials, and guardrails within Skills, the AI can perform tasks in a uniform manner, reducing variability caused by different prompt formulations or user interpretations.

Can this method be applied outside of Anthropic?

While Anthropic’s internal results are promising, broader adoption depends on how well organizations can develop and maintain such Skills, and whether the approach scales effectively in diverse operational contexts.

What are the main challenges in implementing Skills as folders?

Challenges include designing comprehensive and triggerable descriptions, maintaining consistency across Skills, and integrating these assets into existing AI workflows without adding complexity.

Will this approach reduce the need for prompt engineering?

Yes, by encapsulating knowledge and procedures into reusable Skills, organizations can move away from ad-hoc prompt crafting and toward more stable, reliable AI deployment.

Source: ThorstenMeyerAI.com

You May Also Like

Regulating Workplace AI: Will New Laws Protect Workers or Stifle Innovation?

Only by understanding these new laws can we determine if they truly safeguard workers or hinder innovation’s future.

Why the Fastest Growing Work Skill Might Be Workflow Design

Mastering workflow design is crucial because it can dramatically boost productivity and adaptability, but there’s more to uncover about its growing importance.

Ai-Driven Design Takes Center Stage at the 2026 3D Printing Conference.

The 2026 3D Printing Conference highlights how AI-driven design is transforming manufacturing, promising unprecedented innovation—discover how this revolution unfolds.

How Fast Does Claude, Acting as a User Space IP Stack, Respond to Pings?

A test measures how quickly Claude, functioning as a user space IP stack, responds to ICMP ping requests, revealing insights into AI-based network processing.