Loading...
Loading...
Found 6,423 Skills
General Architecture Governance Specification, providing layering constraints, impact analysis, interface contracts, and dependency injection baselines. Suitable for architecture review, refactoring, and new module design of any multi-layer system.
Create non-technical documentation for project features in the docs/ folder. Use when documenting completed features, writing feature documentation, explaining how features work, or when the user asks to document the project or create docs for non-developers.
Observe user interaction patterns, extract per-session facets, update a dual-matrix soul state, and periodically synthesize a personalized Soul profile for better collaboration.
Review and analyze a skill against best practices for length, intent scope, and trigger patterns
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This skill operates in two phases — (1) generating a structured analysis framework with chapter skeleton, data query requirements, and analysis logic, and (2) after data collection by other skills, producing the final consulting-grade report with structured narratives, embedded charts, and strategic insights.
Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.
Use when defending or maintaining social order, rule of law, and peaceful institutions. Applies when countering destabilization, upholding democratic norms, or reasoning through how stable civilizations resist and resolve chaos without violence.
Resume work from handoff document with context analysis and validation
Dispatches one subagent per independent domain to parallelize investigation/fixes. Use when you have 2+ unrelated failures (e.g., separate failing test files, subsystems, bugs) with no shared state or ordering dependencies.
Create and improve OpenAkita skills. It is used when you need to: (1) create new skills for repetitive tasks, (2) improve existing skills, (3) encapsulate temporary scripts into reusable skills. Skills are the core mechanism of OpenAkita's self-evolution.
Monitor repo changes made by another Claude Code instance, accumulate observations, and deliver a final review on request
Implement tasks from the change, writing actual code following the specs and design. Trigger: When the orchestrator launches you to implement one or more tasks from a change.