skill-registry

Reusable AI agent skills for Claude Code, Codex, and compatible CLI tools.

Install as a plugin

claude plugins install wm4n/skill-registry

Add as a marketplace source

claude plugins marketplace add wm4n/skill-registry

Available Skills

Skill	Description
jira-fetch	Fetch a JIRA issue and output structured markdown. Supports Atlassian Cloud Basic Auth.
learn-from-repo	Build a team knowledge base from a repo's merged PRs (with linked Jira tickets and GitHub issues) — extracts business logic, architecture decisions, and lessons-learnt into docs/knowledge/, with human confirmation before every write.
self-evolution	Agent self-improvement loop: learns from user corrections (root-cause → prevention rule), retrospects on detours, proposes new skills when it notices repeated work, and detects habit/inertia — persisting lessons to ~/.claude/evolution/ and a capped block in the global ~/.claude/CLAUDE.md.

Usage

After installing, invoke a skill by name:

/jira-fetch JIRA-12345
/jira-fetch JIRA-12345 --comments 10
/learn-from-repo

learn-from-repo runs an interactive init on first use in a repo (Jira settings, branch-pattern detection, module list), then learns incrementally from a checkpoint on later runs. Prerequisites: inside a git repo with a GitHub remote, gh authenticated, jq installed.

self-evolution is trigger-based rather than slash-invoked: it activates automatically when the user corrects the agent, when a task involved rework, or at task end (a silent quick screen). It maintains its own storage at ~/.claude/evolution/ (created on first trigger) and manages a dedicated lessons block at the end of the global ~/.claude/CLAUDE.md (max 20 entries; existing content is never touched). New-skill proposals it drafts only take effect after explicit user approval. Instructions are written in Traditional Chinese.

Required Environment Variables

Variable	Description
JIRA_TOKEN	Atlassian API token
JIRA_EMAIL	Atlassian account email
JIRA_BASE_URL	JIRA instance URL, e.g. https://yourorg.atlassian.net

learn-from-repo reads Jira credentials from env vars whose names you register in the target repo's docs/knowledge/config.json during init (defaults suggested: JIRA_EMAIL / JIRA_API_TOKEN); token values never enter the repo.