milestone
Analyze and summarize GitHub milestone status for this repository.
npx skills add majiayu000/claude-skill-registry --skill milestone-zeroae-zae-limiter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
--- description: When users mention a milestone version (e.g., "0.4.0", "v0.4.0") or ask about release status, invoke this skill to analyze GitHub milestone progress, issues, and suggest next steps. argument-hint: [version] | list allowed-tools: Bash(gh api:*), Bash(gh issue list:*), Bash(gh issue view:*) context: fork model: haiku --- # Milestone Skill Analyze and summarize GitHub milestone status for this repository. ## Arguments - `$ARGUMENTS`: One of: - `<version>` - Analyze a specific milestone (e.g., "v0.4.0" or "0.4.0") - `list` - List all open milestones - (empty) - List all open milestones ## Subcommand Instructions Each subcommand has detailed instructions in a separate file: | Command | Instructions | |---------|--------------| | `list` or empty | See `list.md` | | `<version>` | See `status.md` | Read the appropriate file based on the argument, then follow its instructions.
- Arguments
- Subcommand Instructions
What does the milestone skill do?
Analyze and summarize GitHub milestone status for this repository.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill milestone-zeroae-zae-limiter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
