add-new-opc-skill

Guides the checklist-driven process of adding and publishing a new skill to the OPC Skills repository.

1.7k|158|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/ReScienceLab/opc-skills --skill add-new-opc-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-new-opc-skill
Source: https://github.com/ReScienceLab/opc-skills/tree/main/.factory/skills/add-new-opc-skill
Command: npx skills add https://github.com/ReScienceLab/opc-skills --skill add-new-opc-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing a new skill to the OPC Skills project requires updating many scattered files (SKILL.md, skills.json, README.md, worker.js, CHANGELOG.md, logos), and missing any one of them breaks the release. This Skill provides a complete checklist and verification workflow so nothing is forgotten.

Core Features & Use Cases

  • Step-by-step publishing checklist: Covers directory structure, YAML frontmatter, pixel-art SVG logo generation, skills.json entries, README table rows, website worker.js entries, and CHANGELOG updates.
  • Verification commands: Provides ready-to-run shell and Python snippets that validate frontmatter, JSON schema fields, and the presence of every listing before committing.
  • Git workflow guidance: Defines the branch naming convention (feature/skill/<skill-name>), commit message format, and PR creation against the develop branch.
  • Use Case: A maintainer wants to release a new 'seo-audit' skill. Following this Skill, they scaffold the directory from the template, generate a logo, register it in skills.json and worker.js, run the verification script, and open a PR with confidence.

Quick Start

Ask the agent to walk through the add-new-opc-skill checklist to prepare and publish a new skill named 'my-new-skill' in the OPC Skills repository.

Frequently Asked Questions about add-new-opc-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a new skill to the OPC Skills repository?

Create a directory under skills/<skill-name> with a SKILL.md containing YAML frontmatter (name and description), then register the skill in skills.json, README.md, website/worker.js, and CHANGELOG.md. The checklist in this Skill walks through each required file and field.

What files must be updated when publishing a new skill?

Six items are required: the skill's SKILL.md, a pixel-art SVG logo in skill-logos/, an entry in skills.json, a row in the README.md skills table, an entry in website/worker.js, and CHANGELOG.md matrix and release entries.

How do I validate a skills.json entry before release?

Run the provided Python snippet that loads skills.json and checks the new entry for required fields: name, version, description, logo, icon, color, triggers, dependencies, auth, install, and links. It prints PASS or lists missing fields.

What git branch naming convention does OPC Skills use?

New skills are developed on a branch named feature/skill/<skill-name> created from the develop branch. After committing, push the branch and open a pull request targeting develop.

How is the pixel-art skill logo generated?

Logos are generated with the logo-creator skill's batch_generate.py script using a pixel-art prompt, then cropped with crop_logo.py and converted to SVG with vectorize.py into the skill-logos/ directory.