Explore skills

Systematic pricing auditor that builds a solid, defensible price step by step — even with incomplete data. Use when the user needs help pricing a project, service, or offer and doesn't know where to start, is guessing, or wants to pressure-test their number. Trigger on: "what should I charge", "how do I price this", "is this price fair", "I don't know what to ask for", "help me price", or any situ

Generates a branch-vs-default comparison report with plain-language explanations and senior dev review. Use when the user asks to summarize, compare, review, or explain branch changes, or wants a PR summary before merging.

Post formatted comments on GitHub PRs or issues, approve PRs, and merge PRs via gh CLI using purpose-specific templates (feedback, question, status, approval, request-changes). Use when commenting on a PR, leaving feedback, asking a question on an issue, posting a status update, approving a pull request, merging a PR, or any intent to interact with an existing PR or issue — even implicit phrases l

Use when working in this dotfiles repository - modifying shell configs, SSH, neovim, or scripts. Covers symlink architecture, agent selection, and permission model.

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

Use after execution completes when the user needs final quality verification and release-readiness review before closeout.

Use when the user asks for root-cause-first debugging of bugs, test failures, flaky behavior, build issues, or integration defects with tracked verification and regression lock-down.

Use after planning and before execution to verify approved current work is reality-fit, feasibility-ready, and explicitly approved at Gate 3.

Reviews product specs, requirements docs, RFCs, PRDs, and policy documents from text, markdown, or Figma. Use for completeness, consistency, edge-case coverage, ambiguity, policy conflicts, or compliance gaps. Triggers on "이 기획서 검토해줘", "스펙 리뷰", "정책 검토", "review this PRD", "is this complete?", "이 기획대로 구현하면 빠진게 뭐가 있을까", "스펙 갭", "요구사항 누락", or whenever a Figma URL is shared in a planning context. Trig

Use at the start of every conversation that touches a non-trivial code or design task. Establishes the ssep skill-matching matrix (4 specialized skills — reviewing-spec-and-policy, reviewing-design-fidelity, improving-feature-completeness, running-integration-tests) and requires the matrix to be evaluated BEFORE any other action, including clarifying questions, file reads, or implementation. Trigg

Read-only static analysis of SAP CAP Node.js code (a Pull Request, a branch comparison, or a specific file list). Classifies findings as Critical / High / Medium / Low, lists each finding with file:line, function/class, evidence and a *suggested* fix (always flagged as needing human validation), and writes the result to `CAP-CODE-REVIEW.md` at the project root. Use when the user asks to: - "analis

Test-only skill for SAP CAP Node.js projects. Its sole purpose is to scaffold and run automated tests using `cds test` (Node.js test runner wrapper) and, when (and only when) explicitly requested by the user, produce coverage with `c8`. The skill writes test files under `test/` (or the project's existing test folder), executes them, and emits two possible report files at the project root: - `CAP-T