Skill Name
Bootstrap a new SKILL.md package with frontmatter, prerequisites, CLI examples, troubleshooting, and script inventory so your agent skill is shippable in the catalog.
Overview
Skill-name is a journey-wide agent skill that provides the SKILL.md and CLI-documentation template for authoring new catalog-ready agent capabilities before you wire domain logic.
Install
npx skills add https://github.com/resciencelab/opc-skills --skill skill-nameWhat is this skill?
- SKILL.md frontmatter pattern with inline when-to-use keywords in description
- Structured sections: Prerequisites, Quick Start, Usage Examples, Commands, Scripts, API Info, Troubleshooting
- Python script invocation examples with flags and expected output blocks
- Environment variable and API key setup boilerplate
- OPC-skills repo convention: commands run from the skill directory
Adoption & trust: 1.1k installs on skills.sh; 920 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have working Python scripts but no consistent SKILL.md shape, so agents cannot find triggers, commands, or troubleshooting when you need them.
Who is it for?
Solo builders creating or splitting skills in repos like opc-skills who want Anthropic-style structure without guessing section order.
Skip if: Teams that only consume third-party skills and never author SKILL.md files, or projects with no script/CLI surface to document.
When should I use this skill?
Use when user wants to create a new skill, document CLI scripts in SKILL.md, or match OPC-skills layout and trigger keywords in description.
What do I get? / Deliverables
You copy the template into a renamed skill folder, fill description triggers and script paths, and hand agents a discoverable skill package aligned with OPC conventions.
- Completed SKILL.md with frontmatter
- Documented command and troubleshooting sections for agent invoke
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Spin up a minimal SKILL.md around a landing-page scraper script before committing to a full integration skill.
Rename skill-name to your-domain-skill and list every script under scripts/ with --help examples.
Ensure troubleshooting and API sections are filled so reviewers know auth and rate limits before publish.
Document a new marketing automation command block the same way as core product skills for consistent agent discovery.
Add a fifth troubleshooting issue when on-call notices a recurring env-var misconfiguration.
How it compares
Authoring scaffold for SKILL.md—not a runtime MCP server and not a domain integration skill by itself.
Common Questions / FAQ
Who is skill-name for?
Indie agent builders packaging Python (or similar) helpers into skills.sh- or Prism-compatible directories with frontmatter and runnable examples.
When should I use skill-name?
At Build when adding agent-tooling; also during Validate when prototyping a skill-backed workflow; again in Grow or Operate when documenting new commands or APIs as skills.
Is skill-name safe to install?
It is documentation structure only—review the Security Audits panel on this page and audit any scripts you add after copying the template.
SKILL.md
READMESKILL.md - Skill Name
# Skill Name Brief description of the skill and its purpose. ## Prerequisites List any setup requirements: - Environment variables needed - API keys required - Dependencies (already listed in frontmatter above) Example setup: ```bash export SKILL_API_KEY="your_api_key" ``` ## Quick Start How to use the skill quickly: ```bash cd <skill_directory> python3 scripts/command.py --option value ``` ## Usage Examples ### Example 1: Basic usage ```bash python3 scripts/script.py "input" ``` Output: ``` Expected output here ``` ### Example 2: Advanced usage ```bash python3 scripts/script.py "input" --flag --option value ``` ## Commands All commands run from the skill directory. ### Command 1 ```bash python3 scripts/script1.py --help python3 scripts/script1.py "param1" --option value ``` ### Command 2 ```bash python3 scripts/script2.py "param1" "param2" ``` ## Scripts - `script1.py` - Description of what this script does - `script2.py` - Description of what this script does ## API Info - **Base URL**: (if applicable) - **Rate Limits**: (if applicable) - **Auth**: (how authentication works) - **Docs**: Link to official documentation ## Troubleshooting ### Issue 1 **Symptom**: Description of the problem **Solution**: 1. Step 1 2. Step 2 ### Issue 2 **Symptom**: Description of the problem **Solution**: 1. Step 1 2. Step 2 ## Examples See `examples/` directory for full workflow examples. ## References - [Official Documentation](https://example.com) - [API Reference](https://example.com/api) - [Related Skill](https://github.com/ReScienceLab/opc-skills/tree/main/skills/related-skill) ## Notes - Important note 1 - Important note 2 --- ## Frontmatter Guide The YAML frontmatter at the top of this file is required: | Field | Type | Required | Description | |-------|------|----------|-------------| | `name` | string | ✓ | Unique identifier (kebab-case) | | `description` | string | ✓ | What the skill does and when to use it. Include trigger keywords and "Use when..." contexts inline. | ## Creating Your Skill 1. Copy this template to `skills/your-skill-name/` 2. Update the YAML frontmatter 3. Write your SKILL.md documentation 4. Add Python/shell scripts in `scripts/` 5. Add usage examples in `examples/` 6. Update `skills.json` with your skill entry 7. Test with your agent before submitting PR