Loading...
Loading...
Found 3,034 Skills
Writes structured blameless postmortems for production incidents. Use when an incident has occurred and you need to document what happened, the impact, root cause, timeline, and action items without blaming individuals.
Research, discuss, and write specs. Use this when creating or refining specs.
Proactively summarize and consolidate knowledge from AI conversation sessions. Auto-triggers when: (1) Starting a new session after meaningful previous work, (2) Session contains significant learnings worth preserving. Captures debugging insights, architecture decisions, patterns, configs, and lessons learned into structured knowledge documents. Explicit triggers: 'summarize', 'consolidate', 'save knowledge', 'document this'.
Use when you need to generate "page list → function points → business processes → business rules" with evidence from frontend code, and the project has non-unique routing entries, complex dynamic routes/permissions/backend menus, and the team is prone to making assumptions or missing evidence chains.
STUB — installed at ~/openclaw/skills/skill-creator/SKILL.md
PROACTIVELY track and document project design decisions without being asked. Activate automatically when detecting architecture discussions, implementation decisions, pattern choices, library selections, or any technical decisions. Also use when user explicitly says "record this", "what's our design status", or equivalent. Do NOT wait for user to ask - record important decisions immediately.
Use skill if you are testing a skill's instructional quality by following its workflow literally on a real task, documenting friction points, and fixing ambiguities.
Write structured strategic documents for small and medium businesses. Produces SWOT analyses, lean business plans, OKRs, and competitive analyses. Each mode has a defined structure and quality bar. Use when a business needs to articulate strategy, set goals, analyse competition, or plan for growth. Outputs actionable documents, not generic frameworks.
Generate various types of documents based on the current project/code, supporting four types: thesis chapters, project sorting, key issues, and resume project descriptions. Use this when the user mentions generating thesis chapters, project sorting, technical difficulties, or resume project descriptions.
Initialize a .spec-driven/ directory in a project. Creates config.yaml and specs/ scaffold, then guides the user to fill in project context.
Use before any non-instant feature work, refactor, behavior change, or requirements-shaping conversation where user intent is not yet locked. Extracts and confirms the decisions that planning will depend on, especially when the user knows what they want but has not fully thought through edge cases, scope boundaries, or expected behavior. Output is CONTEXT.md.
Guide for creating effective skills for Apollo Solutions and Field teams. Use this skill when: (1) users want to create a new skill for this repository, (2) users want to update an existing skill, (3) users ask about skill structure or best practices, (4) users need help writing SKILL.md files.