# Review

Analyze the available skill set and recommend candidate groups that could be...

- Repository: https://github.com/MoonshotAI/kimi-code (8095 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add MoonshotAI/kimi-code --skill review -g -a claude-code -y`
Codex: `npx skills add MoonshotAI/kimi-code --skill review -g -a codex -y`
Cursor: `npx skills add MoonshotAI/kimi-code --skill review -g -a cursor -y`
Gemini CLI: `npx skills add MoonshotAI/kimi-code --skill review -g -a gemini-cli -y`

## Description

Analyze the available skill set and recommend candidate groups that could be consolidated into sub-skill bundles. Read-only, proposes a plan, does not move files.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Review sub-skills (`sub-skill.review`)

Analyze the current skill inventory and identify candidate groups that could be consolidated into sub-skill bundles. This sub-skill is **read-only**: it produces a proposal for the user to review before any file changes are made by `sub-skill.consolidate`.

## When to use

- The user asks to review, reorganize, or audit the skill inventory.
- There are many loosely-related skills that might benefit from hierarchical grouping.
- The user wants to evaluate whether a new skill should be a sub-skill of an existing parent.

## Process

1. **List the current inventory.** Use the skill registry (or scan the configured skill roots) to get a full list of skill names, descriptions, and source scopes.
2. **Categorize by domain.** Group skills by functional domain, e.g. file operations, web tools, collaboration, observability.
3. **Detect coupling.** Identify skills that are frequently used together or share similar `whenToUse` conditions.
4. **Flag granularity issues.** Call out skills that are too fine-grained (e.g. one skill per CLI flag) or too broad to land in any single domain.
5. **Propose sub-skill structures.** For each candidate group, list:
   - The parent skill name and a one-line description.
   - The children that should move under it.
   - Any documentation, reference, example, asset, or template directories that must move with each child so the final directory layout stays aligned.
   - Whether the parent needs `has-sub-skill: true` (it does, if children should be discovered).
6. **Output a summary report.** Present findings as a concise grouped list with rationale, and stop. Do **not** edit any file, that's `sub-skill.consolidate`'s job.

## Criteria for a good sub-skill grouping

The rest: https://github.com/MoonshotAI/kimi-code/blob/HEAD/packages/agent-core-v2/src/features/skill/catalog/builtin/sub-skill/review/SKILL.md