skill-curator
Skill Curator
Overview
This skill automates the process of discovering, extracting, and cataloging agent skills into a central README.md file. It ensures consistency in descriptions, categories, and installation commands.
Workflow
1. Research & Discovery
Use the most appropriate tool to explore the target repository. If you are equipped with the "Public Repo Explorer" skill, perform a local shallow clone. Otherwise, use tools like the GitHub MCP server to browse the remote files.
- You MUST explicitly locate the actual
SKILL.mdfiles to identify valid skills. Use comprehensive search tools (e.g.,find_by_nameorgrep_searchif local, or MCP search) across the entire codebase. - Why? Do not guess the directory structure based on folder names, because skills can be deeply nested (e.g.,
plugins/expo-app-design/skills/layout/SKILL.md). A folder is only a valid skill if it contains aSKILL.mdfile directly inside it.
2. Metadata Extraction
For each identified SKILL.md file, extract:
- Name: The display name of the skill (from
SKILL.mdfrontmatter). - Description: A concise summary of what the skill does (from
SKILL.mdfrontmatter). - Source Link: The direct GitHub URL to the
SKILL.mdfile itself (must end in/SKILL.md).
More from eho/agent-skills
user-story-implementer
Implement a single user story or task from a GitHub Issue backlog. Executes a single iteration by fetching the next open issue, assigning it, implementing the code, creating a branch and PR, and moving on. You MUST use this skill when asked to "implement a user story", "run one iteration", "do the next task", or "complete a task from the backlog".
39user-story-reviewer
Review an implemented user story or task (via GitHub Pull Request) for completeness, test coverage, and code quality. Use this when asked to QA, review a PR, verify implementation, or as a follow-up to the user-story-implementer skill.
32prd
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
26prd-to-github-milestone
Parses a Product Requirements Document (PRD) to extract User Stories and creates corresponding GitHub Issues. It can optionally link them to a GitHub Milestone. This skill acts as a setup phase for GitHub-native issue tracking. Make sure to use this skill whenever the user asks to "send the PRD to GitHub", "create issues from the PRD", "setup the milestone", or mentions turning requirements into actionable GitHub issues.
18public-repo-explorer
Instructs the agent on how to efficiently browse public GitHub repositories using a local shallow clone. You MUST use this skill whenever the user asks you to scan, examine, clone, or extract information from a public Git repository, or whenever they provide a GitHub URL to explore.
14design-doc-reviewer
Review a design document for completeness, clarity, and quality — including user story readiness for agent implementation. Produces structured feedback with specific gaps, strengths, and a prioritized improvement checklist. Use when asked to review a design doc, critique a design, check a spec, review the PRD, or audit the requirements.
13