SKILL RADAR · GITHUB
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
- 1,033
- repositories
- 142
- last synced
- Aug 31, 2026
riekeltreviewing-technical-prose
Use when reviewing, rewriting, or editing someone else's technical text, when writing a review report on a document, or as the final check before delivering any document. Encodes the severity mapping, the findings format, the what-not-to-flag list, and the delivery checklist. Use before any document ships, even when it looks fine.
- installs
- 412
- GitHub stars
- 15
- Updated
- Aug 30
riekeltwriting-runbooks
Use when writing operational documentation - runbooks, setup guides, release procedures, migration guides, deprecation guides, troubleshooting entries, or any ordered procedure someone will execute under time pressure. Encodes the runbook skeleton, the risk legend, the symptom-first troubleshooting format, and the migration-guide rules (mapping table, mandatory rollback, deprecation dates, built-in expiry). Use whenever someone will execute the text, even if it is called a "guide" or "setup notes".
- installs
- 412
- GitHub stars
- 15
- Updated
- Aug 30
riekeltdocumenting-legacy-codebases
Use when documenting an existing codebase whose documentation is missing, stale, or untrusted - an inherited system, a legacy application, a repo where the docs lie - or when regrounding a documentation tree against the code, or when someone asks what a system actually does. Encodes the survey-first inventory, the writer-side evidence hierarchy, depth-per-surface rules, the refactor test, dead-or-alive proofs, the quirks-and-findings split, the coverage ledger, the parallel campaign, and the docs-tree skeleton. Use whenever documentation must be reconstructed from the code rather than written alongside a change.
- installs
- 410
- GitHub stars
- 15
- Updated
- Aug 30
riekeltdiagramming-processes
Use when a business process, workflow, lifecycle, or interaction between systems needs a diagram - a flow that prose serializes badly, a state machine, a message sequence, an enterprise process map - or when drawing the process documentation of a legacy campaign. Encodes diagrams-as-source, the notation ladder from ArchiMate to PlantUML, the kind-per-question table, behavior-level participants, the diagram index, and the same-change maintenance rule. Use whenever a document needs a graph rather than more paragraphs, even if nobody says "PlantUML".
- installs
- 410
- GitHub stars
- 15
- Updated
- Aug 30
riekeltwriting-changelogs
Use when writing a changelog entry, release notes, or a "what shipped" summary after completing work. Encodes the entry shape, the handover template, and the honesty conventions. Use after shipping meaningful work, even if the user just says "summarize what we did".
- installs
- 410
- GitHub stars
- 15
- Updated
- Aug 30
riekeltwriting-issues
Use when writing or refining tracker items - epics, stories, tasks, bug reports, spikes, or acceptance criteria - or when turning a discussion, review finding, or plan into tickets. Encodes the survives-without-you test, the issue-type glossary, and the story and bug skeletons. Use whenever work is written into a tracker, even from a rough verbal dump.
- installs
- 410
- GitHub stars
- 15
- Updated
- Aug 30
riekeltwriting-postmortems
Use when writing a postmortem, incident report, or root-cause analysis after an outage, a defect that reached users, a data issue, or a near miss - or when turning an incident channel, alert log, or war-room thread into a durable document. Encodes the blameless framing, the evidence-only timeline, contributing factors, and owned action items. Use whenever something broke and the write-up must outlive the incident.
- installs
- 410
- GitHub stars
- 15
- Updated
- Aug 30
riekeltdocumenting-contracts
Use when documenting an HTTP API, message payloads, queue contracts, DTOs, file formats, or webhooks - or when writing the api-reference of a legacy campaign, or when callers keep asking what a field means or which errors an endpoint returns. Encodes the four detail levels, the DTO-first catalog, wire types with source anchors, the generated-spec one-home rule, and omitted-versus-null semantics. Use whenever a machine interface needs documenting for its callers, even if nobody says "API docs".
- installs
- 409
- GitHub stars
- 15
- Updated
- Aug 30
riekeltrecording-decisions
Use when a decision needs recording - an ADR, a decision log entry, or when someone asks to write down why something was chosen, rejected, or superseded. Encodes the ADR and decision-log formats. Use whenever a choice was made that would otherwise live only in chat, even if nobody says "ADR".
- installs
- 409
- GitHub stars
- 15
- Updated
- Aug 30
riekeltwriting-design-docs
Use when writing a proposal, RFC, design document, spec, or migration plan - anything that argues for a change, records a design, or asks readers for input on one. Encodes the proposal skeleton, the Why & What decision box, and the completeness checks. Use whenever a change needs arguing or scoping in writing, even if the user just says "write up the approach".
- installs
- 409
- GitHub stars
- 15
- Updated
- Aug 30
riekeltmulti-agent-review
Use when a spec or plan needs review before execution begins - "review my spec", "is this plan ready to execute", "check this before I build it", "second opinion on this plan" - and specifically before writing-plans (spec mode) or before subagent-driven-development (plan mode). Reviews specs and plans, not code. Panels six reviewers across two model tiers and three topics, invokes a reasoning-tier juror only when the tiers disagree, and gates the next workflow step with a fail-closed Blockers / Warnings / Observations verdict.
- installs
- 402
- GitHub stars
- 87
- Updated
- Aug 22
riekeltverifying-before-done
Use when about to say \"done\", \"fixed\", \"passing\", or \"shipped\" - or when reporting the outcome of any change. Encodes verification as the definition of done: drive the change at its surface, run the verify command, report faithfully, distrust green suites, own failing gates. Use before every completion claim, even when the change was small and obviously correct, which is when this is skipped.
- installs
- 402
- GitHub stars
- 1
- Updated
- Aug 30
riekeltadding-dependencies
Use when about to add, update, vet, or remove a dependency - a package, library, SDK, GitHub action, base image, or vendored code - or when a project's dependency posture needs declaring. Encodes the exhaust-what-you-have ladder, the vetting questions, and pin-and-prove updating. Use even for a tiny utility package: that is exactly how the tree grows.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekeltgrounding-before-coding
Use when starting any non-trivial change, investigating a bug, or working in unfamiliar code - before the first line is written. Also use for pure investigation with no change planned yet - \"dig into this\", \"figure out why\", \"sometimes the export is empty\", intermittent errors after a deploy. Encodes the ground-first discipline: map the real code and data, quote evidence, never guess conventions. Use whenever a change or a conclusion is about to be built from belief instead of from the tree, even under time pressure.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekeltguarding-architecture
Use when a change crosses module boundaries, adds a dependency direction between modules, touches a critical path, or conflicts with a stated principle - and when writing or updating architecture principles themselves. Encodes structural invariants as named, enforced contracts: statement, rationale, guard. Use whenever \"we'll just import it from there for now\" appears, which is how boundaries die.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekelthandling-failures
Use when writing or touching any error path, catch block, fallback, default value, retry, or degraded mode - in any language, any repo. Encodes the no-silent-swallows contract and the fail-loud discipline. Use whenever an exception is about to be caught, a null is about to get a default, or a failure could pass unnoticed, even if the goal is "just make it not crash".
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekeltkeeping-one-source-of-truth
Use when adding data, config, state, constants, an enum-like string, a cache, or anything that could exist in two places - or when two sources already disagree. Encodes the one-fact-one-source doctrine for code and data: derive rather than store, extend the owner, absorb duplicates. Use at the moment copying a value feels faster than referencing it.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekeltoperating-safely
Use when an action touches live systems, shared state, or things that do not come back - deleting, overwriting, restarting, killing processes, editing shared config, handling secrets, or working beside concurrent sessions. Encodes the destructive-op guards, secrets hygiene, and concurrent-session safety. Use before the destructive command, not after, even when the command looks routine.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekeltprincipal-engineering
Use when doing any non-trivial engineering work - implementing, debugging, refactoring, configuring, operating, or investigating why a system misbehaves - or any change where being wrong has a cost. Encodes the evidence-over-theory discipline, the hard safety rules, and the pre-change checkpoint. Use whenever code, data, or infrastructure is about to change or must be understood before it can, even if the task looks routine or is only "find out why". Foundation for the sibling skills.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekeltscoping-changes
Use when deciding how big a fix should be, when scope is drifting mid-task, when a plan is being quietly trimmed to fit, or when "while you're at it" appears in any form. Encodes size-to-trigger, decompose-not-descope, and drive-to-completion. Use whenever the work is about to grow past its cause or shrink below its promise.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekelttesting-changes
Use when deciding what tests a change needs - a feature, a bug fix, a refactor, any behavior change - or when reviewing whether a diff's tests are sufficient. Encodes tests-change-with-behavior, the bug-regression pattern, and assertion discrimination. Use whenever behavior changes and the test diff is empty, especially when the change is "too small to test".
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
riekeltwriting-unit-tests
Use when writing or refactoring unit tests - a new test file, added cases, a flaky test, an unreadable one. Encodes behavior-first testing: one behavior per test, names that state the claim, deterministic setup, mocks only at boundaries you do not own. Use whenever a test is being written, even a quick one, and whenever a test needs a sleep, a mock of your own code, or a copy of the implementation's math.
- installs
- 401
- GitHub stars
- 1
- Updated
- Aug 30
addyosmanifrontend-ui-engineering
Builds production-quality, accessible, responsive user-facing UIs. Use when building or modifying interfaces and pages, creating components, implementing layouts, meeting WCAG accessibility requirements, managing state, or when the output needs to look and feel production-quality rather than AI-generated.
- installs
- 384
- GitHub stars
- 91K
- Updated
- Aug 28
clerkclerk-backend-api
Clerk Backend REST API explorer and executor. Browse tags, inspect endpoint schemas, and execute authenticated requests. Use when listing users, managing organizations, or calling any Clerk API endpoint.
- installs
- 378
- GitHub stars
- 69
- Updated
- Aug 31