Agent skill · Workflow & Productivity

add-new-opc-skill

Checklist and automation guide for adding a new skill to the OPC Skills project. Ensures all required files, metadata, logos, and listings are created before release. Use when adding a new skill, publishing a skill, or preparing a skill for release.

ReScienceLabgithub.com/ReScienceLabGitHub ↗
claude-codeApache-2.0
Install
npx skills add ReScienceLab/opc-skills --skill add-new-opc-skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Path: .factory/skills/add-new-opc-skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,192
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Add New OPC Skill Use this skill when adding a new skill to the OPC Skills project. Follow every step below to ensure the skill meets all publishing requirements. ## Pre-flight Before starting, confirm: - You are on a feature branch: `feature/skill/<skill-name>` (branched from `develop`) - The skill name is kebab-case (e.g., `my-new-skill`) ## Checklist ### 1. Skill Directory Structure Create the skill directory with required files: ``` skills/<skill-name>/ ├── SKILL.md (required) Main skill documentation ├── scripts/ (if skill has scripts) │ └── *.py / *.sh ├── examples/ (recommended) Usage examples │ └── *.md └── references/ (optional) API docs, templates └── *.md ``` **SKILL.md** must include YAML frontmatter: ```yaml --- name: <skill-name> description: Clear description. Include trigger keywords and "Use when..." contexts. --- ``` Use `template/SKILL.md` as a starting point: ```bash cp -r template skills/<skill-name> ``` ### 2. Skill Logo Generate a pixel-art style SVG logo matching existing skill logos: ```bash # Use the logo-creator skill python3 skills/nanobanana/scripts/batch_generate.py \ "Pixel art <subject> logo, 8-bit retro style, black pixels on white background, min

What's inside
Steps it walks through
  1. Pre-flight
  2. Checklist
  3. 1. Skill Directory Structure
  4. 2. Skill Logo
  5. 3. skills.json Entry
  6. 4. README.md
  7. 5. Website (worker.js)
  8. 6. CHANGELOG.md
  9. Verification
  10. Git Workflow
Commands it runs
cp -r template skills/<skill-name>
Use the logo-creator skill
python3 skills/nanobanana/scripts/batch_generate.py \
Open preview to pick a logo
cp skills/logo-creator/templates/preview.html .skill-archive/logo-creator/<date>-<skill-name>/
open .skill-archive/logo-creator/<date>-<skill-name>/preview.html
After picking (e.g., #5):
python3 skills/logo-creator/scripts/crop_logo.py <input>.png <output>-cropped.png
python3 skills/logo-creator/scripts/vectorize.py <output>-cropped.png skill-logos/<skill-name>.svg
python3 -c "import json; json.load(open('skills.json')); print('valid')"
More from opc-skills
All skills →
About this skill
What does the add-new-opc-skill skill do?

Checklist and automation guide for adding a new skill to the OPC Skills project. Ensures all required files, metadata, logos, and listings are created before release. Use when adding a new skill, publishing a skill, or preparing a skill for release.

How do I install it?

Run `npx skills add ReScienceLab/opc-skills --skill add-new-opc-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From ReScienceLab/opc-skills, a repository with 1,192 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going