Discover Business skills, compare source repositories and read the instructions for each workflow.
Genera ejercicio R-exams tipo CLOZE (pregunta compuesta) - Despu\u00e9s requiere Ciclo de Validación. (project) Usa cuando el análisis ICFES indica tipo cloze, necesites pregunta con múltiples partes, o quieras...
Transform reverse-engineering documentation into GitHub Spec Kit format. Initializes .specify/ directory, creates constitution.md, generates specifications from reverse-engineered docs, and sets up for /speckit...
Automatic mode - shift through all 6 gears sequentially without stopping. Like cruise control or automatic transmission, this runs the entire StackShift workflow from analysis to implementation in one go. Perfe...
Deep codebase analysis to generate 8 comprehensive documentation files. Adapts based on path choice - Greenfield extracts business logic only (tech-agnostic), Brownfield extracts business logic + technical impl...
Perform initial analysis of a codebase - detect tech stack, directory structure, and completeness. This is Step 1 of the 6-step reverse engineering process that transforms incomplete applications into spec-driv...
Route-aware gap analysis. For Brownfield - uses /speckit.analyze to compare specs against implementation. For Greenfield - validates spec completeness and asks about target tech stack for new implementation. Th...
Assess assumptions on certainty and risk to prioritize validation efforts. Use at project start or before phase transitions.
Create clear leadership presentations that communicate findings and enable good decisions. Use at end of each phase or before major commitments.
Create structured visualizations of stakeholder perspectives (says, thinks, does, feels) to build deep understanding. Use when conducting user research or validating assumptions.
Distinguish user wants from underlying needs to guide solution design. Use when stakeholders make feature requests or during Define phase.
Assess solution ideas on impact and feasibility to prioritize prototyping. Use during Ideate phase when deciding which ideas to pursue.
Transform raw research into actionable insights that inform design decisions. Use during Define phase after completing research.
Define what to build at what fidelity to learn what you need without over-investing. Use before starting any prototype.
Test whether assumptions are true before making commitments. Use when assumptions have low certainty and high risk.
제텔카스텐 방식의 원자적 노트를 생성합니다. 공부한 개념을 정리하거나 새로운 지식을 추가할 때 사용하세요.
블로그 글 초안을 생성합니다. 개발 블로그나 취미 블로그 글을 쓰기 시작할 때 사용하세요.
작성 완료된 블로그 글을 발행 처리합니다. 블로그 글 발행, 아카이브 이동, 글 완료 처리할 때 사용하세요.
Token-efficient proxy for Naki's 47 MCP tools. Routes user intent to optimal MCP tool via agent isolation, saving 40-70% tokens. Use for any Naki game control, bot status, or UI operation.
Create, modify, and manage MCP tools for the Naki mahjong AI assistant. Use when adding new MCP tools, modifying existing tools, or fixing tool-related issues. This skill understands the Protocol-based MCPTool...
Build, package, tag, and release Naki app to GitHub. Use when the user asks to "release", "publish", "tag", "build DMG/ZIP", or "upgrade version". Handles the complete release workflow from build to GitHub rele...
Test, debug, and modify Majsoul WebUI (Laya engine) within the Naki app. Use when the user asks to adjust "the screen" or "UI" - clarify whether they mean Naki's SwiftUI app or Majsoul's WebUI. This skill handl...
Use buzzllm CLI to perform web searches, execute Python code in Docker, search/analyze local codebases, or generate code change blocks. Trigger when user asks for web search, Python execution, code analysis, or...
Implement based on an approved plan. Use after cc-plan is finalized.
Research codebase and dependencies to support planning. Use when evidence is missing.
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.