Antv Skills Maintainer
Repo maintainers use it to keep AntV chart skills README and Claude marketplace.json aligned whenever skills under skills/ change.
Overview
AntV Skills Maintainer is an agent skill for the Build phase that keeps AntV skills README listings and Claude marketplace.json in sync after every skill add, edit, or removal.
Install
npx skills add https://github.com/antvis/chart-visualization-skills --skill antv-skills-maintainerWhat is this skill?
- Runs on always trigger after code changes that touch skills/
- Syncs README.md Available Skills with each skill’s SKILL.md description
- Updates .claude-plugin/marketplace.json to match the live skill set
- Explicitly excludes antv-skills-maintainer from public skill listings
- Covers add, update, and remove/deprecate skill directory events
- Keeps 2 artifacts in sync: README.md Available Skills and .claude-plugin/marketplace.json
Adoption & trust: 725 installs on skills.sh; 337 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You changed skills in the repo but README and marketplace.json still advertise the old catalog.
Who is it for?
Maintainers of the AntV chart skills repo who trigger on every AI code execution and want zero drift between skills/ and published indexes.
Skip if: Solo builders who only want chart skills for their app—this skill is internal-only and must not appear in Available Skills.
When should I use this skill?
Automatically after every code change—especially new, updated, or removed skills under skills/ (triggers: always).
What do I get? / Deliverables
After each change, public docs and the Claude plugin manifest list only user-facing skills with descriptions matching SKILL.md frontmatter.
- Updated README.md Available Skills section
- Updated .claude-plugin/marketplace.json excluding internal maintainer skill
Recommended Skills
Journey fit
Canonical shelf is Build because the skill only runs while iterating the skills package and agent-plugin manifest—not while shipping a SaaS product. Agent-tooling fits catalog and marketplace maintenance for Claude plugin distribution.
How it compares
Use instead of hand-editing README bullets whenever the skill set changes; it is repo hygiene, not a visualization or MCP integration.
Common Questions / FAQ
Who is antv-skills-maintainer for?
Contributors and maintainers of the AntV chart-visualization skills repository who manage the skills/ directory and Claude plugin marketplace file—not end users installing chart skills for data viz.
When should I use antv-skills-maintainer?
Apply automatically after every code change, especially when adding a skill under skills/, editing a skill’s SKILL.md name or description, or deprecating or removing a skill.
Is antv-skills-maintainer safe to install?
Review the Security Audits panel on this Prism page for install risk; the skill is designed for maintainer workflows that edit README and marketplace config and should not be exposed as a user-facing catalog entry.
SKILL.md
READMESKILL.md - Antv Skills Maintainer
# AntV Skills Maintainer This skill ensures that all documentation and configuration files remain in sync whenever a skill is added or updated in this repository. ## Important The `antv-skills-maintainer` skill is **internal-only** — it is used solely for this repository's iteration workflow. Do **not** add it to `README.md` "Available Skills" or `.claude-plugin/marketplace.json`. Only user-facing skills should appear in those files. ## When to Apply Apply this skill automatically after **every code change** — especially when: - A new skill directory is added under `skills/` - An existing skill's `SKILL.md` is modified (name, description, capabilities) - A skill is removed or deprecated ## What to Keep in Sync ### 1. README.md — "Available Skills" Section The `## Available Skills` section in `README.md` must list every skill under `skills/` with: - An appropriate emoji icon - The skill **name** (bold, matching the directory name) - A one-line description matching the skill's `SKILL.md` frontmatter `description` field - A short paragraph elaborating on the skill's capabilities **Format:** ```markdown - 🔧 **skill-name**: One-line description from SKILL.md frontmatter. `Skill Display Name` elaboration paragraph... ``` **Steps:** 1. Scan `skills/` directory to list all available skills. 2. Read each skill's `SKILL.md` frontmatter (`name`, `description`). 3. Compare with the current `## Available Skills` section in `README.md`. 4. Add entries for new skills, update entries for changed skills, remove entries for deleted skills. 5. Preserve the section's existing formatting style. ### 2. `.claude-plugin/marketplace.json` — Plugins Array The `plugins` array in `.claude-plugin/marketplace.json` must contain an entry for every skill under `skills/`. **Entry format:** ```json { "name": "skill-name", "description": "Description from SKILL.md frontmatter.", "source": "./", "strict": false, "skills": [ "./skills/skill-name" ] } ``` **Steps:** 1. Scan `skills/` directory to list all available skills. 2. Read each skill's `SKILL.md` frontmatter (`name`, `description`). 3. Compare with the current `plugins` array in `.claude-plugin/marketplace.json`. 4. Add entries for new skills, update `description` for changed skills, remove entries for deleted skills. 5. Keep the JSON properly formatted and valid. ## Execution Checklist After any skill-related code change, run through this checklist: - [ ] All skill directories in `skills/` are listed in `README.md` under `## Available Skills` - [ ] All skill descriptions in `README.md` match the corresponding `SKILL.md` frontmatter - [ ] All skill directories in `skills/` have a corresponding entry in `.claude-plugin/marketplace.json` - [ ] All `description` fields in `marketplace.json` match the corresponding `SKILL.md` frontmatter - [ ] No stale entries exist in either `README.md` or `marketplace.json` for removed skills - [ ] `marketplace.json` remains valid JSON after changes