
I don't have enough information about this skill to write a meaningful editor's note. The source you provided is a template with placeholder text ("skill-name", "Brief description of the skill and its purpose") rather than actual details about a specific skill. To write a useful note, I'd need to know what the skill actually does, what problem it solves, or at least have a real skill name and description to work from. If you can provide the actual skill details or point me to a specific skill from the resciencelab/opc-skills repository, I can write a proper editor's note for it.
$ npx -y skills add resciencelab/opc-skills --skill skill-name --agent claude-codeInstalls into .claude/skills of the current project.
Brief description of the skill and its purpose.
List any setup requirements:
Example setup:
export SKILL_API_KEY="your_api_key"
How to use the skill quickly:
cd <skill_directory>
python3 scripts/command.py --option value
python3 scripts/script.py "input"
Output:
Expected output here
python3 scripts/script.py "input" --flag --option value
All commands run from the skill directory.
python3 scripts/script1.py --help
python3 scripts/script1.py "param1" --option value
python3 scripts/script2.py "param1" "param2"
script1.py - Description of what this script doesscript2.py - Description of what this script doesSymptom: Description of the problem
Solution:
Symptom: Description of the problem
Solution:
See examples/ directory for full workflow examples.
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. |
skills/your-skill-name/scripts/examples/skills.json with your skill entrySponsors