Loading...
Loading...
Found 10,067 Skills
Code review skill for analyzing code quality, detecting bugs, and ensuring best practices. Provides comprehensive code review with actionable feedback. Use proactively when user requests code review, quality check, or bug detection. Triggers: code review, review code, check code, analyze code, bug detection, 코드 리뷰, 코드 검토, 버그 검사, コードレビュー, バグ検出, 代码审查, 代码检查, revisión de código, revisar código, detección de errores, revue de code, réviser le code, détection de bugs, Code-Review, Code überprüfen, Fehlererkennung, revisione del codice, rivedere codice, rilevamento bug Do NOT use for: design document creation, deployment tasks, or gap analysis (use phase-8-review).
Analyzes the conversation and tool usage to propose improvements to skills or store user preferences.
The slogan unpacked — seven readings of 'Manufacturing Intelligence'
Complex migration strategies for LangChain applications. Use when migrating from legacy LLM frameworks, refactoring large codebases, or implementing phased migration approaches. Trigger with phrases like "langchain migration strategy", "migrate to langchain", "langchain refactor", "legacy LLM migration", "langchain transition".
Hybrid memory strategy combining OpenClaw's built-in QMD vector memory with Graphiti temporal knowledge graph. Use for all memory recall requests.
Use when order-of-magnitude cost estimates are needed to assess financial feasibility, compare cost-effectiveness of alternatives, or identify major cost drivers (not for detailed quotes—that's Procurement)
Use when parameter values appear in multiple documents and consistency must be verified, especially for quantitative values that may differ due to measurement context or require reconciliation
Use when substantive documents (reviews, analyses, synthesis documents) need adversarial review to strengthen arguments, identify weak points, and challenge assumptions before editorial polish (mandatory for Writer → Devil's Advocate pairing protocol)
Implement a task with automated LLM-as-Judge verification for critical steps
Dump all Hyvä CMS components from active modules. This skill should be used when the user wants to list all CMS components, view available components, debug component configurations, or see the merged components.json output. Trigger phrases include "list cms components", "dump components", "show all components", "view cms components", "components.json dump".
Store a lesson learned from the current conversation. Triggered by /lesson command. Use when Master signals that the recent conversation contains a pitfall, fix, or key insight that should be persisted to long-term memory.
CX Workflow - Task Execution and Contract Validation. Triggered when users mention phrases such as "execute task", "start development", "implement feature", "write code", "continue working", "next task". It follows a 5-step process: Read Task → Implementation → Contract Validation → Testing → Submission. It uses local task-{n}.md and status.json files to automatically verify whether the implementation conforms to the contract. cx-summary will be automatically triggered after all tasks are completed.