38,442 mods in this category, of every kind an
agent can take. Each one carries what it costs per session, what the
scan found, and whether it is the original.
Generalized Cherny-style autonomous improvement loop. Reads a domain-scoped baseline.json + oracle script, runs the oracle, picks the worst-scoring item, proposes a fix, validates rollback safety, commits if metric improved AND roundtrip passes. Use for chatbot-qa, embeddings, voicing-analysis, or any other domain…
You are the orchestrator. Your job is to stay thin, preserve context, and delegate all heavy lifting to sub-agents. NEVER do deep file reading, code analysis, or implementation directly — always spawn agents for that.
Generate and optimize AGENTS.md project documentation for AI coding agents. Scans project structure, detects tech stacks, extracts build/test/lint commands, and produces ready-to-use AGENTS.md files. Also audits existing AGENTS.md for completeness, accuracy, and best practices. Supports multi-editor output including…
An instruction-file writing skill for creating, reviewing, or reorganizing AGENTS.md and CLAUDE.md files. These files give coding agents project facts and working rules, such as how to run tests or follow conventions.
Validate AGENTS.md and related agent instruction files with the published agents-doctor CLI. Use when the user asks to check, lint, verify, explain, audit, fix, release-check, or compare AGENTS.md, CLAUDE.md, GEMINI.md, agent instruction inheritance, tool profiles, context fidelity, instruction graphs, GitHub…
Maintain, create, migrate, and trim AGENTS.md or legacy CLAUDE.md instruction files for coding agents. Use this whenever the user mentions AGENTS.md, CLAUDE.md, agent rules, repo instructions, memory files, project guidance, instruction drift, or wants to standardize agent docs into a short, reliable source of truth.
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.
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…
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.
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.
Universal guide for creating well-structured Agent Skills for any technology or domain. Use when creating, writing, authoring, or designing a new Skill. Triggers on requests involving SKILL.md files, skill structure, frontmatter, bundled resources (scripts/references/assets), skill validation, skill packaging, or when…
Get parallel second opinions from multiple AI coding agents. Use when the user wants independent reviews, architecture feedback, or a sanity check from other AI models.
Calculate and explain a "Grok Readiness Score" (0-100) for a project based on concrete signals: quality of AGENTS.md / project rules, quantity and validity of skills, test/CI presence, git hygiene, ignore configuration, and verification culture. Use when asked to "score", "readiness score", "grok score", "how agent…
Design, build, and operate AI agents end to end: understand the system, deep-research the tasks, then write the instructions from that understanding. Use when writing or fixing a system prompt, CLAUDE.md, or tool descriptions; deciding one agent vs several; debugging an agent that follows instructions poorly…
★not rated 2 1mo agoA208 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: