decebal
UserTwelve Claude skills, curated by exclusion. Each does what a one-line prompt can't — memory, proof, or a real binary.
Categories
Indexed Skills (11)
mcp-builder
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).
skill-creator
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
pr-atom-reviewer
Review a local git branch as a pull request with a bias toward minimum disruption and minimum reviewer scope. Splits sprawling PRs into independently-mergeable atoms of work — each one a single end-to-end behaviour describable in 2-3 sentences, each shippable to the trunk on its own without any other atom in the plan being merged first — and demands a screenshot/video/recording proving the verifiable acceptance criterion. If the AllSource Prime MCP server is available (`prime_*` tools), the skill recalls prior reviews of the same repo to calibrate its judgement and records the current review for the next one. Use this skill whenever the user asks to review a PR, review a branch, prep a PR for review, check if a branch is ready to merge, or mentions "this PR is too big", "split this PR", "atomic commits", "scope creep in PR", "PR review checklist", or anything about getting a branch in shape before peers look at it. Trigger even if the user just says "look at my branch" in a code review context.
pr-review-coach
Companion to the `pr-atom-reviewer` skill. Reads the review history stored in AllSource Prime (the `prime_*` MCP tools) and turns it into actionable improvements to how the reviewer works. Three jobs — (1) ingest post-merge outcomes for past reviews (was the split followed? did the PR cause a revert?), (2) cluster the repo's actual atom vocabulary so the calibration table reflects this team's work instead of generic examples, (3) surface contradictions across past reviews so the user can decide what to harden into the SKILL.md. Use this skill when the user asks "what have we learned from reviews", "audit my past reviews", "what should I tighten in the reviewer skill", "did my recommended splits get followed", "how is the reviewer doing", "weekly review retro", or runs a periodic skill-improvement pass. Trigger also on phrases like "PR retro", "review postmortem", "calibrate my reviewer", or when the user mentions wanting to update the calibration table or the SKILL.md for the reviewer.
ralph-tui-cn-beads
Convert PRDs to beads for ralph-tui execution using chronis (cn CLI). Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with chronis as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads, cn beads, cn create.
ralph-tui-cn-prd
Generate a Product Requirements Document (PRD) for ralph-tui task orchestration using chronis (cn CLI). Creates PRDs with user stories that can be converted to beads for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out, cn prd.
ralph-tui-create-beads-rust
Convert PRDs to beads for ralph-tui execution using beads-rust (cn CLI). Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads-rust as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads, br beads, cn beads.
ralph-tui-prd
Generate a Product Requirements Document (PRD) for ralph-tui task orchestration. Creates PRDs with user stories that can be converted to beads for automated execution. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
rust-perf
Detect and fix performance issues in Rust projects using a modern 2026 toolchain. Use when the user asks to "profile rust", "optimize rust binary", "make it faster", "flamegraph", "pgo", "bolt", "find hotspots", "why is this slow", or mentions latency/throughput regressions in Rust code. Adapts to what's already in the repo (hotpath, criterion, custom allocator) before suggesting new tools. Covers CPU sampling, in-process pprof, deterministic benchmarks, heap profiling, causal profiling, and the PGO+BOLT pipeline.
verify-db-change
End-to-end verification of a database change (new tables, columns, indexes, writers/projectors) against real Postgres before review or merge. Replaces vibes-only "looks fine" sign-off with a structured proof block — schema applied per tenant, behavioural SQL exercised inside BEGIN…ROLLBACK on the live dev DB, app booted with the new wiring, and migration reversibility proved against a throwaway schema clone. Produces a PR-ready markdown excerpt with real captured output. Use this skill whenever the user asks to verify a migration, test a migration, prove a schema change works, verify a projector / writer / repository, "run any manual test needed to prove completion", or anything that means "show me the database actually works, not just the unit tests". Also use proactively when reviewing a PR that touches migrations or DB writers and the existing description has no real-Postgres proof. Designed for TypeORM + Nest + Postgres monorepos with multi-tenant DBs and Docker-Compose local infra, but the principles app
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.