📊 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.
Turn your quiet moments into listening time
- Thousands of audiobooks, podcasts and originals
- Listen on your phone, tablet or Echo — also offline
- Cancel anytime
TL;DR
Anthropic has shifted from prompts to ‘Skills’ structured as folders containing instructions, scripts, and assets. This approach enhances AI consistency, onboarding, and institutional knowledge. The development emerged from their internal experiments with hundreds of Skills.
Anthropic has revealed that its internal AI systems rely on ‘Skills’ structured as folders containing instructions, scripts, and reference materials, rather than traditional prompts. This approach, based on extensive internal testing, aims to create more durable, reusable, and consistent capabilities for AI agents, marking a significant shift in how organizations can manage AI workflows.
According to a recent publication from Anthropic, a ‘Skill’ is defined as a folder that bundles instructions, reference documents, scripts, templates, data, and configuration settings. Unlike prompts, which are often simple text instructions, Skills serve as comprehensive containers that the AI can discover, read, and execute. This design allows for more consistent output across different users and roles, simplifies onboarding by embedding tribal knowledge, and enables continuous improvement through iteration. Anthropic’s engineers have run hundreds of these Skills internally, developing a library that they categorize into nine types, ranging from code scaffolding to operational runbooks. The most impactful Skills, as identified by Anthropic, are those that verify outputs and catch errors, significantly improving AI reliability and quality.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.
“A Skill is just a clever markdown prompt you save in a file.”
A folder the agent can discover, read & run — instructions, scripts, references, templates, config & on-demand hooks.
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.
Implications for AI Development and Business Operations
This shift from prompt-based instructions to folder-structured Skills represents a foundational change in managing AI capabilities. It enables organizations to standardize processes, reduce reliance on ad-hoc prompts, and build a library of institutional knowledge that improves over time. For businesses, this means more reliable AI outputs, easier onboarding of new team members, and a scalable way to evolve AI workflows. The approach also encourages viewing Skills as assets that appreciate in value, rather than static prompts, potentially transforming how companies deploy and maintain AI systems at scale.Products Worth Considering
Fitbit Charge 5 Health and Fitness Tracker with Built-In GPS, Stress Management, Sleep Tracking, and 24/7 Heart Rate Monitoring
Withings ScanWatch Light Hybrid Smartwatch, Black
Oura Ring 5 Smart Ring, Silver, Size 10
As an affiliate, we earn on qualifying purchases.
Internal Experiments and the Evolution of AI Capabilities
Anthropic’s internal experiments involved running hundreds of Skills across its engineering teams, leading to the realization that organizing capabilities as folders enhances durability and reusability. Previously, most teams relied on prompts that had to be rewritten or adjusted for each task, which was inefficient and error-prone. The concept of Skills as containers originated from the need to codify tribal knowledge, guardrails, and scripts into a single, versioned asset. This approach aligns with broader trends in software engineering, where modular, reusable components improve reliability and scalability. Anthropic’s categorization into nine Skill types provides a framework for identifying organizational gaps and prioritizing development efforts.“A Skill is not just a prompt saved as text; it’s a folder that encapsulates instructions, code, and assets, making AI capabilities more durable and shareable.”
— Thorsten Meyer, AI researcher at Anthropic
Unresolved Questions About Skills Deployment
It is not yet clear how widely this Skills approach will be adopted outside Anthropic or how it will scale in different organizational contexts. Details about the specific tooling, integration into existing workflows, and long-term maintenance strategies remain to be seen.Next Steps for Broader Adoption and Development
Anthropic plans to further develop its Skills library, refining categories and best practices. The company may also share tools or frameworks to help other organizations adopt this approach. Observers will be watching to see if other AI developers follow suit, potentially leading to industry-wide shifts in how AI capabilities are structured and managed.
Key Questions
How does organizing Skills as folders improve AI capabilities?
It allows for more durable, reusable, and consistent capabilities by bundling instructions, scripts, and assets into a single container that can be discovered and executed by the AI.
What are the main categories of Skills identified by Anthropic?
They include 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.
Will this approach work for other organizations?
It depends on the organization’s ability to develop and maintain a library of Skills. The approach is promising for standardizing workflows but requires investment in creating and versioning Skills as assets.
Are Skills intended to replace prompts entirely?
No, Skills are designed as a more durable, organized alternative to ad-hoc prompts, serving as reusable assets that embed tribal knowledge and guardrails.
What challenges might organizations face adopting Skills?
Challenges include developing a comprehensive library, maintaining version control, integrating with existing tools, and training teams to think in terms of Skills as assets rather than simple prompts.
Source: ThorstenMeyerAI.com
