📊 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 treating AI skills as comprehensive folders—containing instructions, scripts, and assets—improves consistency, onboarding, and scalability. This approach moves away from simple prompts toward durable, reusable organizational units.

Anthropic has announced a significant shift in how organizations should develop AI capabilities, emphasizing that skills are best understood as folders—containing instructions, scripts, and assets—rather than simple prompts. Learn more about skills as folders. This approach aims to create more durable, reusable, and consistent AI behaviors, moving beyond ad-hoc prompting towards institutionalized procedures.

In a detailed write-up from a Claude Code engineer, Anthropic explained that a Skill is fundamentally a folder—an organized container that can include instructions, reference documents, scripts, templates, data, and configuration settings. This structure allows AI agents to discover, read, and execute the contents dynamically, making the process more robust and maintainable than traditional prompt-based methods. The shift addresses common issues like output inconsistency and onboarding inefficiencies, enabling organizations to codify operational knowledge into reusable assets.

Anthropic’s internal analysis identified nine categories of Skills, ranging from library references and data analysis to process automation and infrastructure operations. The most impactful, according to the company, is verification Skills, which ensure output quality and mistake detection. The company advocates for investing engineering effort into refining these categories, emphasizing that Skills should capture non-obvious, specific knowledge—like traps, gotchas, and edge cases—rather than generic instructions.

The technical insight underscores that effective Skills require precise descriptions, code scripts, and contextual triggers, making them more like customizable modules than simple prompts. This approach aims to embed organizational knowledge directly into AI workflows, reducing reliance on manual instructions and increasing reliability over time.

At a glance
reportWhen: published March 2024
The developmentAnthropic published insights from running hundreds of AI skills as folders, emphasizing a shift from prompt-based to folder-based skill design, impacting AI deployment practices.
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 Development and Business Operations

This development signals a paradigm shift in AI deployment, moving from prompt engineering to building structured, maintainable assets. For organizations, this means more consistent AI outputs, simplified onboarding of new staff, and a scalable way to improve and refine AI capabilities over time. The approach also encourages viewing Skills as valuable, appreciating assets that grow in effectiveness, rather than ephemeral prompt snippets.

By adopting folder-based Skills, companies can embed tribal knowledge, guardrails, and operational procedures directly into their AI systems, reducing errors and increasing trust. This could influence how AI teams document, version, and share their work, aligning AI development more closely with software engineering best practices.

Amazon

AI development folder organization tools

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

From Prompting to Structured Asset Management

Historically, AI teams have relied heavily on prompt engineering—crafting specific instructions to elicit desired outputs. However, this method often leads to inconsistency and difficulty in scaling, especially as models and use cases grow complex. Anthropic’s recent publication builds on prior efforts to formalize AI workflows, emphasizing the importance of reusable, versioned assets. Their internal experiments with hundreds of Skills as folders demonstrate that this approach captures institutional knowledge and operational guardrails more effectively than prompts alone.

This shift aligns with broader trends in AI engineering, where modular, maintainable components replace ad-hoc prompts, enabling organizations to build more reliable and scalable AI systems. The nine-category Skills map provides a framework for identifying organizational gaps and prioritizing development efforts.

“Treating Skills as folders containing instructions, scripts, and data transforms how organizations codify their operational knowledge into AI capabilities.”

— Thorsten Meyer, AI researcher

Amazon

AI scripting and asset management software

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Unresolved Questions About Implementation and Scalability

While Anthropic’s approach is promising, it remains unclear how easily organizations can adopt the folder-based Skills model at scale, especially in non-technical teams. Details about tooling, version control, and integration with existing workflows are still emerging. Additionally, the long-term effectiveness of Skills in diverse operational contexts remains to be validated through broader industry adoption and real-world testing.

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.

Next Steps for Adoption and Industry Validation

Organizations interested in this approach should evaluate how to structure their own Skills folders, focusing on capturing non-obvious knowledge and guardrails. Anthropic plans to release more detailed tooling and best practices, which will help other teams implement the model. Industry-wide, the success of this approach will depend on how well it integrates with existing AI pipelines and how effectively it scales across different use cases.

Amazon

AI instruction and script management system

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 can be discovered and executed by an AI agent. Unlike prompts, which are single-use instructions, Skills are reusable, versioned assets that embody operational knowledge and guardrails.

What are the main benefits of using Skills as folders?

Skills as folders improve output consistency, simplify onboarding, and enable continuous improvement through versioning and documentation of organizational knowledge.

Can this approach be adopted by non-technical teams?

While technically oriented teams will find it more straightforward, the principles can be adapted for broader organizational use with appropriate tooling and documentation processes.

What categories of Skills did Anthropic identify?

Anthropic identified nine categories: library and API reference, product verification, data fetching and analysis, business-process automation, code scaffolding, code review, CI/CD and deployment, runbooks, and infrastructure operations.

What is the significance of verification Skills?

Verification Skills are considered the most valuable because they directly improve the quality and reliability of AI outputs, catching mistakes before they reach users.

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

Is the stock market closed on Friday? Trading details for July 3rd (SPY:NYSEARCA)

The NYSE and NASDAQ will be closed on July 3rd in observance of Independence Day, affecting trading of ETFs like SPY. Trading resumes on July 5th.

The Co-Founder’s Black Hole — A Structural Read on Jack Clark’s Automated AI R&D Essay

In May 2026, Jack Clark predicts over a 60% chance that AI systems capable of autonomously building their successors will emerge by 2028, raising concerns about institutional readiness.

Digital Wallet Interoperability: Why “Open Loop” Matters in 2025

Lifting barriers to seamless transactions, open loop digital wallet interoperability in 2025 promises a connected financial future—discover how it transforms your digital experience.

Single Digits: The April That Closed the Open-Weight Gap

April 2026 saw open-weight AI models matching closed models’ performance across key benchmarks, reshaping enterprise AI strategies and economics.