mcpField
S
skill-catalog-generator

skill-catalog-generator

github.com/sylphxaiAgent workflows147 installsUpdated today
Repository

About skill-catalog-generator

A skill that turns recurring product-operations work into reviewable catalog artifacts. It inventories skill materials, groups them by user job and product type, and evaluates evidence, gaps, and publishing readiness.

Key features

  1. 01Inventory skill folders and materials
  2. 02Group by user job and product type
  3. 03Score quality with observable evidence
  4. 04Produce catalog updates and gap matrices
  5. 05Prepare publish checklists and automation hooks

Use cases

  1. 01Organizing a skills marketplace catalog
  2. 02Finding gaps in skill documentation and evaluations
  3. 03Preparing a catalog publishing checklist

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill skill-catalog-generator

After installing, type/skill-catalog-generatorin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/catalog-generation-patterns.md

Details

From the project README

Skill Catalog Generator

Use this skill to turn a recurring product-operations problem into a concrete, reviewable artifact instead of generic advice.

Workflow

  1. Inventory every skill folder, frontmatter description, references, evals, examples, agents metadata, and install path.
  2. Read references/catalog-generation-patterns.md.
  3. Normalize skills by user job, lifecycle area, product type, and marketplace group instead of folder order alone.
  4. Score quality with observable evidence: trigger clarity, reference depth, eval coverage, behavior demo, installability, and freshness.
  5. Produce a catalog update, gap matrix, publish checklist, and automation hooks.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not fabricate quality signals; mark missing evidence as a gap.
  • Separate generated registry facts from editorial marketplace claims.
  • Keep private/internal skills and public catalog content separated.
  • Prefer stable skill names, links, and install commands over marketing-heavy copy.

Output format

Catalog source:
Skill count / install source:

Grouping model:
- <group> -> <skills>

Quality score table:
| Skill | Trigger | Depth | Eval | Demo | Install | Gaps |
| --- | --- | --- | --- | --- | --- | --- |

Coverage gaps:
- <gap> -> <next skill or reference>

Publish actions:
- <registry/catalog/docs/verification step>

Comments

Markdown supported