AGENT SKILLS · MISSION KIT

Useful agent skills ranked by real adoption

Browse verified skills from public repositories. Compare what each skill does, package contents, install activity, and source evidence before adding it to your agent.

CATALOG SCOPE
VERIFIED
skills
23,248
repositories
3589
last synced
Nov 4, 2026
23,248 skills
resend
Official

resend-cli

Operate the Resend platform from the terminal — send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, logs, automations, and events via the resend CLI. Use when the user wants to run Resend commands in the shell, scripts, or CI/CD pipelines, or send/preview React Email templates. Always load this skill before running resend commands — it contains the non-interactive flag contract and gotchas that prevent silent

1h installs
3
GitHub stars
212
Updated
Nov 3
shmulc8
Community

captain-obvious

Audit TypeScript and Python tests for assertions that cannot fail or check nothing, and guide test authoring with a contract and regression gate. Use when writing or changing tests to avoid low-value coverage, or cleaning redundant, tautological, duplicated, or AI-generated tests. Cleanup runs bundled deterministic scanners; authoring guidance needs no scan during red-green TDD.

1h installs
3
GitHub stars
15
Updated
Sep 30
leonxlnx
Community

imagegen-frontend-web

Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a singl

1h installs
3
GitHub stars
65
Updated
Oct 19
leonxlnx
Community

gpt-taste

Classic skill for GPT and Codex, opt-in: it runs only when called by name. Layout variance, a strict AIDA page structure and GSAP scroll motion.

1h installs
3
GitHub stars
32
Updated
Oct 19
leonxlnx
Community

industrial-brutalist-ui

Classic style skill, opt-in: it runs only when called by name. A hard mechanical look with Swiss type, rigid grids, extreme scale contrast and utilitarian colour.

1h installs
3
GitHub stars
32
Updated
Oct 19
leonxlnx
Community

stitch-design-taste

Classic skill for Google Stitch, opt-in: it runs only when called by name. Writes an agent-friendly DESIGN.md with strict type, colour and layout rules.

1h installs
3
GitHub stars
32
Updated
Oct 19
fetcher-sh
Community

reddit-api

A Reddit API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no OAuth app registration. Use when the user wants to search Reddit posts across every subreddit by keyword and sort by top, hot, new, or most-discussed, search subreddits or users by keyword, fetch a subreddit's info or its hot/new/top post feed, fetch a single post with its comment tree and comment replies, pull the sitewide best/hot/new/top feeds, or fetch a user's profile, posts, and

1h installs
3
GitHub stars
2
Updated
Sep 5
decisionnerd
Community

agents

Work agent systems with command arguments: slap (emergency-fix stupid agent behavior and safely drain dumb workflows), analyze, optimize, design, and sub / sub-agents (delegate via subagents). Use when the user says agents, /agents , agent loops are thrashing, workflows need draining, or they want agent architecture, analysis, or parallel subagent execution.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

architect-it

Design or evolve the architecture of a system, module, or feature — survey the codebase, frame the bet (boundaries, placement, data flow), propose options with tradeoffs, record the decision where the repo keeps decisions, and plan the first slice. Use when the user says "architect it", asks to design a system or module, review architecture, plan boundaries before building, or untangle a structural bet that refactoring alone cannot fix. Not for behavior-preserving mechanics (use refactor-it), co

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

check-readiness

Review whether a GitHub issue is complete enough for its current stage and decide the next PR or closure action. Use before PR, before closing an issue, after merge, or when auditing a closed issue for regressions or missing scope. For pre-PR checks, use CodeRabbit CLI review; when an open PR exists and corrective review work is needed, use autofix.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

council

Convene independent reviews from three model providers and reconcile their findings. Use when the user says council, asks for a multi-model review, or wants several providers to challenge a plan or implementation.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

diagnose-bug

Diagnose backend, API, worker, data-pipeline, or algorithm bugs by reproducing with inputs/tests, checking invariants and complexity assumptions, correlating logs/traces/metrics, and inspecting code. Use when a user reports wrong outputs, failing tests, timeouts, races, incorrect algorithms, flaky jobs, bad API responses, or asks why a non-UI system is broken. Diagnose, then implement the smallest fix and a regression test in the same run; stop first only for diagnosis-only requests, live-data/o

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

document-it

Improve or add repository documentation for work just done or for product-docs gaps. Use when the user says "document it", asks for README/runbook/API notes, architecture notes, changelogs, ADRs, or DocSlime product docs. Default to a surgical update of the nearest accurate home after a change — do not scaffold or fill a DocSlime tree unless the altitude truly needs it. When product/requirements/testing/observability contracts are in play, use DocSlime structures and methods. Keep docs accurate

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

fix-it

Create an implementation-ready repair plan from diagnosis evidence — live-app (troubleshoot-app), backend/algo (diagnose-bug), failing URLs, logs, data-plane findings, or clearly reported breakage. Use when the user asks to \"fix it\", \"plan this fix\", or wants a plan before implementation — especially diagnose → fix-it → check-readiness → merge-it. Not for behavior-preserving structure work (refactor-it) or greenfield features without a failing contract.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

idk-now

When the user doesn't know what to do next: briefly survey environment, repo, docs, and git history; guide them through clarifying questions; then suggest next steps using DecisionNerd/dev-skills plus DocSlime, ProductFeeling, Impeccable, and any vendored skills in the repo space — aimed at an achievable goal toward why the project exists. Use when the user says "idk", "I don't know", "what now", "stuck", "lost", or /idk-now. Prefer recon when they already know the domain and need a tactical nex

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

issues

Work GitHub issues with command arguments: create/draft, update, critique, narrow, widen, merge, clean, refine, explain, document, close, reopen, search, and status. Default with only an issue identifier (and optional details) is execute completion work — plan/diagnose/implement/test/ready-check/merge — not issue-admin. Explicit commands still do admin. Rough idea with no identifier defaults to create. Use when the user asks about issues, /issues , drafting or improving an issue, or finishing tr

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

kiss

Audit goals, processes, systems, and plans for needless complexity — then recommend simplification only when it is warranted. Use when the user says "kiss", "keep it simple", "is this overcomplicated", "simplify this", or asks whether to cut scope/steps/architecture. Weigh risks and benefits of simplifying; do not default to reductionist cuts when complexity is earned. Simple also means a straightforward DAG to completion with right-sized tasks (not too small, not overly big). Pair with idk-now,

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

merge-it

Drive delivery through the repository's actual Integrate, Stage, or Ship path. Use when asked to land, merge, stage, ship, or finish a branch end-to-end. Open or update the PR, fix verified findings, and monitor current-head checks and reviews. Use merge-it prepare for ready-for-human-merge requests; it never merges or enables automatic merging. Merge mode verifies deployment and issue closure for the requested phase. Repository instructions define the release path.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

milestones

Work GitHub milestones with command arguments: create, update, critique, narrow, widen, merge, clean, refine, explain, document, close, status, and plan. Default with only a milestone identifier (and optional details) is execute completion work through Integrate — critical-path issue plan/implement, ready-check, and merge — not milestone-admin. Treat Stage/Ship as follow-ups; run them only when the user requests that phase. Explicit commands still do admin. Use when the user asks about milestone

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

modernize

Assess and update an old PR against its current base and architecture. Use when the user says modernize, rebase this PR, or bring an old branch up to date; recommend rework or closure when a rebase would preserve obsolete behavior.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

observe-it

Add or improve observability — structured logs, metrics, traces, errors, analytics, dashboards, and (for generative) LLM traces/scores. Use when the user says "observe it", asks for instrumentation, telemetry, alerting hooks, Langfuse/evals online, or "how do we know this works in prod". Match signals to quality regime A/B/C; prefer existing vendors (OTel, Sentry, PostHog, Langfuse house default for LLM). Ask before emitting PII or paid-volume storms.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

pulls

Work GitHub PRs with create/open, update, critique, scope, review, status/checks, watch/monitor, babysit, merge, and close commands. Use when the user asks about PRs or invokes pulls. Watch observes; babysit fixes verified failures and waits without merging. A bare PR identifier or no args on a current-branch PR defaults to Integrate completion via merge-it; explicit commands and ready-for-human-merge requests keep their own finish line. Stage/Ship run only when requested.

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

recon

Scout the current work and recommend the next skill or action. Arguments: repo (whole-repo health), issue (deep implementation plan for an issue), milestone (milestone readiness and issue set). With no argument, read git logs and local branch state first to set scope, then suggest what to do next. Use when the user asks to recon, scout, assess, or \"what should I do next\". Knows DecisionNerd/dev-skills: agents, architect-it, idk-now, kiss, repos, issues, milestones, pulls, check-readiness, merg

1h installs
3
GitHub stars
0
Updated
Nov 4
decisionnerd
Community

refactor-it

Safely refactor code to improve structure, clarity, or testability without changing intended behavior. Use when the user says "refactor it", asks to clean up a module, extract helpers, reduce duplication, or prepare code for a feature — not for product behavior changes (use fix-it) or pure test adds (use test-it). Prefer small steps with tests green between steps.

1h installs
3
GitHub stars
0
Updated
Nov 4