skills-best-practicesBuild high-quality Agent Skills for Claude following official Anthropic best practices. Covers SKILL.md structure, frontmatter, description writing, progress...
Install via ClawdBot CLI:
clawdbot install tenequm/skills-best-practicesGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://agentskills.ioAudited Apr 18, 2026 · audit v1.0
Generated May 5, 2026
A developer needs to create a new skill for processing invoices. They use the best practices guide to set up the directory structure, write a concise SKILL.md with proper frontmatter, and craft an effective description that ensures the skill triggers correctly.
A team lead reviews a repository of skills to ensure they follow Anthropic best practices. They check for proper naming conventions, progressive disclosure, and appropriate description wording to improve skill activation rates.
A user reports that a skill rarely activates. Using the guide, the developer rewrites the description to include specific trigger phrases and adjusts the wording to be more 'pushy', resolving the undertriggering issue.
A product manager wants to create a skill for generating reports in Claude.ai. The guide helps them structure instructions with progressive disclosure, keeping the SKILL.md concise and referencing external documents for advanced options.
An AI engineer refactors a large skill that was exceeding token limits. They apply progressive disclosure by moving detailed documentation to separate files and keeping the SKILL.md under 500 lines, reducing startup token cost.
Developers create and sell high-quality skills on a platform, following best practices to ensure reliability. Revenue comes from per-skill sales or subscription access to skill libraries.
Consultants use the guide to build custom skills for clients, integrating with their workflows. Revenue is generated through project-based consulting or retainers for ongoing skill maintenance.
Companies adopt the best practices internally to create skills for their teams, improving automation and reducing manual work. Value is captured through increased efficiency and cost savings, indirectly boosting profitability.
💬 Integration Tip
Apply progressive disclosure from the start: keep SKILL.md under 500 lines and move detailed instructions to reference files to minimize token usage.
Scored Apr 19, 2026
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use the @steipete/oracle CLI to bundle a prompt plus the right files and get a second-model review (API or browser) for debugging, refactors, design checks, or cross-validation.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.