Skills, subagents, slash commands, hooks, settings, plugin bundles and MCP servers that install into Claude Code. 389,707 indexed, measured the same four ways as everything else here.
Push code, automatically run /commit if not yet committed, compute elapsed time and log work to Jira accurately. Handles all edge cases: no-ticket, no-state, re-push, multi-task, duplicate worklog, corrupt state, negative elapsed, wrong commit author.
Format the ad-hoc commands you run so the user reads their intent, steps, and blast radius before they execute — shell, python -c/node -e, jq, or SQL. Use whenever about to run a non-trivial command (multi-step, piped, looped, here-doc, or a dense inline snippet), or anything that writes, deletes, or overwrites state.
Gerencia o ciclo de vida completo de trilhas de trabalho (abertura com scaffolding, transição de blocos, fechamento e arquivamento em finalizadas/, propagação de conhecimento para a Wiki e auditoria de invariantes). Use ao criar, atualizar, passar de bloco, fechar ou auditar qualquer trilha.
Your pathfinder for navigating unknown codebases. Investigates with precision, implements surgically, and never assumes — if it doesn't know, it says so. Maintains a .notebook/ knowledge base that grows across sessions, turning every discovery into lasting intelligence. Summons available skills, MCPs, and docs when…
Calculate C1V1=C2V2 dilutions, serial dilutions with plate-based replicates, and budget-conscious volume planning that accounts for micropipette systematic error.
Drives the user's standard project-start ritual as one unified command. Writes three docs into the project's documents/ folder: (1) a dialogue-first spec.md, (2) an MVP-sliced living plan.md with 🤖/🧑 verification gates, (3) a design.md handed to a design AI. Invoke this whenever the user is starting a NEW project or…
Send and receive emails, and intercept verification/OTP codes for AI agents using the mails.dev service. Use this skill whenever an agent needs to: claim an @mails.dev mailbox, send an email, wait for a verification or OTP code to arrive, search an inbox for a specific message, or embed email functionality inside a…
One sentence saying what this skill produces and one sentence saying when to use it ("Use whenever asked to …"). Agents pick skills by this description alone — make the trigger unmistakable.
A review process for turning useful lessons from an AI-assisted coding session into proposed memory cards or development rules. It includes a user approval step before anything is saved.
Run the full pre-PR review per AGENTS.md §7 — gates, tagged diff walk, pessimistic meta-check, acceptance-criteria mapping, commit hygiene, rebase status, PR-description draft. Use when the human says "ship it", "ready to PR", "open the PR", "pre-PR check", or invokes /pre-pr.
Add a new tool adapter to agentsync — scaffolds internal/tools/ .go (a ToolMeta literal + render func), registers it, extends adopt.go for reverse mapping, adds a roundtrip test, regenerates the metadata golden, and updates README compatibility tables. Use when implementing one of the tools still open in TODO.md…
Full APIVR-Δ cycle reference — A(nalyze) → P(lan) → I(mplement) → V(erify) → Δ(Delta)/R(eflect). Use when the task is a non-trivial feature implementation in a brownfield codebase and you need the complete methodology reference: complexity routing, evidence-grounded planning rules, test-anchoring requirements, and…
Guide for creating effective Cursor commands. Use when creating new commands, updating existing commands, reviewing command quality, or when users request help with command design, organization, or best practices. Commands are simple slash-invoked workflows distinct from skills.
Set up or extend a "Hub-and-Spoke" agent documentation system in a repository — AGENTS.md as a table of contents pointing to spoke files (docs, agent instructions, runbooks, anything). Use this skill whenever the user wants to create or update AGENTS.md, add or restructure agent rules, migrate inline rules out of…
Document a repeatable process as a new skill or policy. Use when the owner says "make this repeatable", "document this process", "we should have a procedure for this", or when the same multi-step task has been done twice and will recur.
Run runtz DevSecOps security scans (SCA, SAST, host packages, container images, Kubernetes) and read runtz documentation. Use when the user wants to find vulnerable dependencies or packages, scan source code for secrets/weak crypto, audit a container image or Linux host for CVEs, check Kubernetes posture, or asks how…
Use when writing, modifying, reviewing, refactoring, or debugging code with Codex to reduce wrong assumptions, overengineering, unrelated diffs, and unverifiable work by applying Simon Stone's coding-agent guidelines.
Use when making any code change — adding features, fixing bugs, refactoring, updating modules, editing configuration, or changing any file in src/, tests/, wiki/, config/, or scripts/. Enforces the full post-change pipeline: wiki update → sync gate → tests → README → git push.
Configure the gleanwork agent baseline in a library or SDK repo — scaffold AGENTS.md, a CLAUDE.md pointer, and skills/, author the library's SKILL.md, and verify it in CI. Use when onboarding a gleanwork OSS repo to the agent setup, adding AGENTS.md or a skill to a repo, or writing/updating the SKILL.md that teaches a…
A skill that automatically adds directory-specific rules to a sub-agent before it works in that directory. These rules can be stored in files such as AGENTS.md or .hermes-rules.
Commit changes across the LiteStack meta-repo and its submodules. Use when the user asks to commit or push from the LiteStack root. It commits inside each changed submodule first, then records the updated submodule pointers in the meta-repo, and pushes according to the operating mode (template vs derived).
★not rated 2
changed 9d agoA65 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: