Comprehensive guide for skill assessment, career evaluation, learning paths, knowledge testing, and professional development. Use when assessing technical skills, planning learning journeys, or evaluating career progress.
Detect cognitive biases, logical fallacies, and thought pattern vulnerabilities.
Create detailed implementation plans through interactive research and iteration
Personalized AI mentorship for learning any creative or technical skill. Adaptive teaching that meets you where you are and guides you to mastery. Premium skill for deep learning journeys.
This skill should be used when the user asks to "create a skill", "add a skill", "write a new skill", "improve skill description", "organize skill content", or "validate skill structure". Provides guidance on skill development best practices for OpenCode.
MANDATORY skill creation framework for ALL skill creation requests. USE WHEN user wants to create, validate, update, or canonicalize a skill, OR user mentions skill creation, skill development, new skill, build skill, OR user references skill compliance, skill structure, or skill architecture.
Categorize and display available skills. Use when listing or selecting skills.
Interactive catalog of all available skills. Use when: user asks for help, wants to discover skills, or asks what you can do.
Use when starting any conversation - establishes how to find and use Flutter development skills, requiring Skill tool invocation before ANY response including clarifying questions
Generate structured skill specifications for independent skill creators. Use when asked to ideate, brainstorm, or specify multiple skills for a domain, workflow, or problem space. Outputs self-contained specs with list-level context so each skill can be built independently. Triggers on requests like "what skills would help with X", "generate skill ideas for Y", "specify skills to cover Z workflow".
Lightweight tactical guidance during implementation. Just MCP suggestions and quick lookups, no heavy Graphiti searches.
Conduct technical interviews about project plans to uncover hidden assumptions and identify potential issues before implementation. Use when the user wants to be interviewed about a plan, spec, or project idea.
Archive of past customer interviews. Contains full transcripts, summaries, pain points, outcomes, and skills used. Use for referencing previous conversations with the same company or finding similar case patterns.
Use when a user asks for UI design tips or quick critique about layout, hierarchy, CTAs, forms, navigation, cards, tooltips, charts, or confirmation patterns.
Generates Bill of Materials (BOM) from project descriptions for Arduino/ESP32/RP2040 projects. Use when user needs component lists, parts shopping lists, cost estimates, or asks "what parts do I need". Outputs formatted BOMs with part numbers, quantities, suppliers (DigiKey, Mouser, Amazon, AliExpress), and compatibility warnings. Run scripts/generate_bom.py for xlsx/csv export.
Identify and resolve ambiguities in specifications through structured questioning. Use when specification has [NEEDS CLARIFICATION] markers, when user mentions unclear or ambiguous requirements, before creating implementation plans, or when planning reveals specification gaps.
(opencode-project - Skill) Template and guidelines for breaking features into implementation tasks
Use for root cause analysis of bugs or issues. Systematically investigates problems to identify underlying causes.
"Domain vocabulary and entity relationships for {project}. Ensures consistent terminology and model understanding."
Reference and adhere to the project's technical stack including frameworks, languages, tools, and dependencies. Use this skill when choosing libraries, frameworks, or tools for implementing features. Use this skill when understanding which technologies are available and standardized in the project. Use this skill when making architectural or technology decisions. Use this skill when working with any part of the application to ensure consistency with the established tech stack. Use this skill when adding new dependencies or third-party services. Use this skill to maintain awareness of the project's runtime environment, database, testing tools, and deployment infrastructure.
Find conceptual gaps in plan/spec documents. Use when user explicitly asks start-gap-finder.
This skill should be used when the user wants to triage an issue, review a specification, or assess requirements completeness. Trigger when user mentions "triage", "review this spec", "is this requirement complete", "what questions should I ask", or provides a description/acceptance criteria that needs evaluation before implementation. The skill analyzes input against the codebase and project documentation to surface implicit requirements and generate clarifying questions.
Master business documentation including BRD, FRD, specifications, and technical documentation for clear communication and requirements management.
