moonshot-evaluate-complexity
Evaluates complexity (simple, medium, complex) based on estimated files/lines/time. Use after task classification.
Browse published AI skills maintained by munlucky. Compare skill descriptions and follow each source repository for setup instructions.
Evaluates complexity (simple, medium, complex) based on estimated files/lines/time. Use after task classification.
Collects and organizes code review feedback into actionable tasks.
Checks essential information and project status before starting a task.
Parses design assets (PDF, CSS) to generate a draft design spec.
Detects missing requirements and generates clarification questions. Use after classification/complexity to decide if user input is needed.
PM workflow orchestrator. Analyzes user requests and automatically runs the optimal agent chain.
Review implementation quality and regression risks via claude-delegator (Code Reviewer expert). Use after implementation for complex tasks, refactors, or API changes.
Validate integration impact and regression risks via claude-delegator (Code Reviewer expert). Use for complex tasks or API integration.
Synchronizes documentation across agents to reflect planning changes and status updates.
Tracks workflow status and generates a flow report.
Validate architecture/plan quality via claude-delegator (Plan Reviewer expert). Use after writing context.md for complex feature/refactor work.
Classifies a user request into task types (feature, modification, bugfix, refactor) and extracts intent keywords. Use at the start of PM analysis.
Performs implementation in the chain and records completion state and changed files in analysisContext. Use during implementation.
Analyze the current repository and create or refresh .claude/PROJECT.md to match the project. Use when PROJECT.md is missing, stale, or the user asks to generate/update project-specific rules, structure, comman...
Use after planning or implementing non-trivial tasks - runs Codex MCP background verification/review for quality gates (plan validation + implementation review)
Logs development sessions in real-time to track decisions and issues.
Determines phase and execution chain based on analysisContext (task type, complexity, signals). Use after uncertainty detection.
Log work sessions with timestamps, decisions, agent handoffs, issues, and outcomes. Use when a session log needs to be created or updated.
Track workflow timelines, blockers, verification results, and commits in flow-report.md. Use when recording execution flow or efficiency.
Perform pre-flight checks for required info, project state, and missing context. Use before starting work to avoid gaps.
Parse Figma/PDF design exports to extract UI specs and draft design-spec.md and pending-questions.md. Use when analyzing design assets.
Run Codex plan validation or implementation review as a quality gate for non-trivial tasks. Use after planning or implementation.
Triage code review feedback and reflect follow-up tasks in pending-questions/context. Use when incorporating review results.
Logs development sessions in real-time to track decisions and issues.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.