Guidelines for optimal skill usage and development.
For Users
Activation Best Practices
Use Clear Trigger Phrases
Match phrases from skill description
Be specific about intent
Provide necessary context
Provide Sufficient Context
Include relevant file paths
Specify scope of analysis
Mention any constraints
Understand Tool Permissions
Check allowed-tools in frontmatter
Know what the skill can/cannot do
Request appropriate actions
Workflow Optimization
Start with simple requests
Build up to complex workflows
Verify each step before proceeding
Use skill consistently for related tasks
For Developers
Skill Development Guidelines
Clear Descriptions
Include explicit trigger phrases
Document all capabilities
Specify limitations
Proper Tool Permissions
Use minimal necessary tools
Document security implications
Test with restricted tools
Comprehensive Documentation
Provide usage examples
Document common pitfalls
Include troubleshooting guide
Maintenance
Keep version updated
Test after tool updates
Monitor user feedback
Iterate on descriptions
Performance Tips
Scope skills to specific domains
Avoid overlapping trigger phrases
Keep descriptions under 1024 chars
Test activation reliability
Security Considerations
Never include secrets in skill files
Validate all inputs
Use read-only tools when possible
Document security requirements
1---2name: 290-best-practices-c8f32b353description: Skill Best Practices4---5# Skill Best Practices67Guidelines for optimal skill usage and development.89## For Users1011### Activation Best Practices12131. **Use Clear Trigger Phrases**14 - Match phrases from skill description15 - Be specific about intent16 - Provide necessary context17182. **Provide Sufficient Context**19 - Include relevant file paths20 - Specify scope of analysis21 - Mention any constraints22233. **Understand Tool Permissions**24 - Check allowed-tools in frontmatter25 - Know what the skill can/cannot do26 - Request appropriate actions2728### Workflow Optimization2930- Start with simple requests31- Build up to complex workflows32- Verify each step before proceeding33- Use skill consistently for related tasks3435## For Developers3637### Skill Development Guidelines38391. **Clear Descriptions**40 - Include explicit trigger phrases41 - Document all capabilities42 - Specify limitations43442. **Proper Tool Permissions**45 - Use minimal necessary tools46 - Document security implications47 - Test with restricted tools48493. **Comprehensive Documentation**50 - Provide usage examples51 - Document common pitfalls52 - Include troubleshooting guide5354### Maintenance5556- Keep version updated57- Test after tool updates58- Monitor user feedback59- Iterate on descriptions6061## Performance Tips6263- Scope skills to specific domains64- Avoid overlapping trigger phrases65- Keep descriptions under 1024 chars66- Test activation reliability6768## Security Considerations6970- Never include secrets in skill files71- Validate all inputs72- Use read-only tools when possible73- Document security requirements
Run npx skillmds@latest add tools-only/290-best-practices-c8f32b35 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Skill Best Practices It is listed under Productivity on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
tools-only (@tools-only) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tools-only