Zyniverse Skills Registry

Production-grade agent skills by the Zysk & Zyni teams — curated, versioned, and installable as a Claude Code plugin.

Each skill is a self-contained folder under skills/ with a SKILL.md (instructions + metadata) and any scripts, references, or assets it needs. Skills are reviewed before they’re merged, so the registry stays small, sharp, and non-overlapping rather than a dumping ground.

Install

The registry is a Claude Code plugin marketplace. Add it once, then install skills individually:

/plugin marketplace add zyniverse-hq/skills-registry
/plugin install @zyniverse-skills

For example, /plugin install daily-status@zyniverse-skills. Browse every available skill with /plugin, or on the site below. Installed skills are available to Claude immediately — no extra setup.

Already added the marketplace? Pull new and updated skills with /plugin marketplace update zyniverse-skills.

Browse

→ zyniverse-hq.github.io/skills-registry/website

Search and filter the full, always-current catalog. The site is driven by index.json, which is generated from the skills — never edited by hand.

What’s inside

Skills span these categories:

• 🧪 QA & Testing Automation
• 🛡️ Pre-Deployment & Release Safety
• 💼 Business & Sales Automation
• 🤝 HR & Recruiting
• 🛠️ Engineering Practice & Decision Support
• 🔌 Frontend & Backend Integration
• 🔐 Infrastructure, Ops & Security
• 📊 Data, Analysis & Reporting
• 🤖 AI Agents & Prompts
• 💬 Communications & Content

See the website for the complete, current list.

Contributing

Contributions are welcome and curated — every skill goes through a GitHub Pull Request and review. Quick start:

git clone https://github.com/zyniverse-hq/skills-registry.git
cd skills-registry
git checkout -b add-my-skill
cp -r skills/_template skills/my-skill          # folder name == the skill's name
$EDITOR skills/my-skill/SKILL.md                # write it
pip install pyyaml
python scripts/validate_skill.py skills/my-skill/SKILL.md   # must pass
# commit (Conventional Commits), push, open a PR

There’s no one-skill-per-PR or branch-name rule — cohesive multi-skill PRs are fine. See CONTRIBUTING.md for the full standard and frontmatter reference, and the Authoring Guide for writing a skill that triggers reliably and stays maintainable.

Repository structure

skills-registry/
├── skills/                     # the skills (one folder each)