SkillsAdd

marcioaltoe/skills

skill-catalog-curation

Curates this repository's installable skills catalog.

First seen Aug 6, 2026

Installation

$ npx skills add marcioaltoe/skills --skill skill-catalog-curation
View on skills.sh ↗ GitHub repository ↗

Summary

  • Curates this repository's installable skills catalog.
  • Use when adding, replacing, moving, tagging, vendoring, or removing skills; editing skills-registry.json, setups, sync lockfiles, or the Astro GitHub Pages catalog.
  • Do not use for writing an individual SKILL.md only; use skill-creator and skill-best-practices for that.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

dataset-curation Similar name
wshobson/agents

Prepare, format, and validate datasets for supervised fine-tuning and preference training. Use …

1.3K installs
test-suite-curation Similar name
petrkindlmann/qa-skills

>- Audit a whole regression suite and prune/restructure it with evidence: per-test coverage fin…

10 installs
newsletter-creation-curation Similar name
brianrwagner/ai-marketing-claude-code-skills

Industry-adaptive B2B newsletter creation with stage, role, and geography-aware workflows

411 installs
photo-content-recognition-curation-expert Similar name
curiositech/some_claude_skills

Expert in photo content recognition, intelligent curation, and quality filtering. Specializes i…

318 installs

Also in this package

Other skills from marcioaltoe/skills · top by installs.

npx skills add marcioaltoe/skills
context7 76 grill-with-docs 68 architectural-analysis 67 handoff 66 no-workarounds 65 coding-guidelines 63 council 61 brainstorming 61 the-fool 60 crafting-effective-readmes 59

Browse all from marcioaltoe/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version0.1.0
More metadata
category
skill-authoring
version
0.1.0
tags
["skills","catalog","registry","astro","github-pages"]
author
Marcio Altoé
source
https://github.com/marcioaltoe/skills

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,966 B
  • docs SUMMARY.md 353 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Skill catalog curation

Keep the skill source tree, registry metadata, setup presets, sync lockfile, and Astro catalog aligned.

When to use

  • A skill is added, removed, renamed, moved between collections, vendored, or replaced.
  • skills-registry.json, skills-registry.lock.json, setups/, install.sh, install.ps1, web/, or .github/workflows/deploy-pages.yml changes.
  • The user asks to curate skills, update catalog metadata, adjust tags/authors/provenance, or change what the GitHub Pages catalog shows.

Curation workflow

  1. Identify the surface being changed:

- Skill body: skills/<collection>/<name>/SKILL.md - Catalog metadata: skills-registry.json - Setup presets: setups/_index.txt and setups/<preset>.txt - Astro catalog: web/ - Upstream sync: scripts/sync-skills.mjs and skills-registry.lock.json

  1. For new or replaced skills, verify whether an official upstream skill exists before writing a local one. Prefer official upstream sources; use community sources only when no official source fits or the user asks for that source.
  2. Keep one canonical skill folder under skills/<collection>/<skill-name>/. Do not duplicate a skill into multiple collections or add symlinks under skills/.
  3. Put catalog metadata in skills-registry.json, not in frontmatter:

- author - curated tags - local-path - collection - optional upstream repo, path, ref, update

  1. Keep frontmatter focused on agent loading: name, description, and optional metadata such as version or author tags.
  2. If setup presets change, run make setups-check.
  3. If the Astro catalog behavior or generated index changes, run the relevant web command from web/package.json and inspect the generated catalog behavior.
  4. Always run make list and git diff --check before claiming the curation work is ready.

Collection choice

Choose the collection by the skill's primary use case, not by every technology it mentions.

  • 00-setup: repo setup, local skills, agent guardrails, setup presets.
  • 01-discovery: research, assumption checks, problem discovery.
  • 02-planning: PRDs, product planning, GTM, communication planning.
  • 03-engineering-design: architecture, security, UX, documentation plans.
  • 04-issue-decomposition: issues, triage, acceptance criteria.
  • 05-implementation-loop: implementation, frameworks, migrations, tests.
  • 06-review-repair: review, debugging, quality repair, verification.
  • 07-evidence-delivery: delivery evidence, docs, commits, reports.
  • 08-release: release, deployment, observability, operations.
  • 09-learning-loop: skill authoring, evaluations, process improvement.
  • 10-marketing: marketing, sales, SEO, pitch material.

Astro catalog rules

  • The public catalog is static and lives under web/.
  • web/scripts/build-index.mjs reads skills-registry.json plus each SKILL.md.
  • src/data/skills.json is generated and git-ignored; do not commit it.
  • GitHub Pages deploys via .github/workflows/deploy-pages.yml.
  • Keep collection labels in web/scripts/build-index.mjs aligned with the repository's collection table.

Validation matrix

Change Required validation
Skill body only make list, git diff --check
Registry metadata make list, git diff --check
Setup presets make setups-check, make list, git diff --check
Astro catalog cd web && npm run build, git diff --check
Upstream sync script or lockfile Run the focused sync/check command and inspect sync-report.md

Anti-patterns

  • Editing author, tags, collection, or provenance in SKILL.md instead of skills-registry.json.
  • Adding a vendored skill without upstream provenance when the source is known.
  • Creating a setup preset that points to a missing skill or a path absent from the registry.
  • Treating the Astro page as separate from the registry; it is a projection of registry plus skill frontmatter.