add-new-opc-skill_skill

This skill guides you to add a new OPC skill by enforcing structure, logos, metadata, and release checks for clean publishing.

Python

472

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill resciencelab/opc-skills --skill add-new-opc-skill

SKILL.md7.4 KB

Overview

This skill is a checklist and automation guide for adding a new OPC skill. It ensures every required file, metadata entry, logo, website listing, and changelog entry is created and validated before release. Use it to standardize new-skill onboarding and to avoid missing publish steps.

How this skill works

The guide inspects your branch and enforces a standardized directory layout, including the main skill document, example and reference folders, and any runtime scripts. It walks through pixel-art logo creation, adds a complete metadata entry to the central skills index, updates the public website listing, and records the release in the changelog. Finally, it provides verification commands and a recommended git workflow for committing and opening a pull request.

When to use it

When creating a new skill feature branch and preparing the skill for review.
Before publishing a skill to ensure all metadata and assets are present.
When adding or updating a pixel-art logo and verifying visual consistency.
Prior to opening a pull request to the develop integration branch.
When validating that the website and changelog reflect the new skill.

Best practices

Work on a feature branch named feature/skill/<skill-name> branched from develop.
Use kebab-case for skill identifiers and filenames to avoid inconsistencies.
Follow the provided directory layout: main skill doc, scripts, examples, and references.
Generate and pick a pixel-art SVG logo consistent with existing assets.
Add a full metadata entry for the central index with triggers, install commands, and auth info.
Run the supplied verification commands before committing to catch missing fields early.

Example use cases

Creating a new LLM tool skill and preparing it for the project's website listing.
Publishing a skill that requires optional API keys and documenting required env variables.
Updating the central skills index and ensuring install commands are accurate for different agents.
Adding a minimalist pixel-art logo and validating it appears correctly on the skills gallery.

FAQ

Create a feature branch from develop using the pattern feature/skill/<skill-name>.

How do I name the skill folder and identifier?

Use kebab-case (lowercase with hyphens) for the skill name and directory.

What must be included in the central metadata entry?

Include name, version, description, logo URL, icon, color, triggers, dependencies, auth, install, commands, and links.