69 boosters for "md" — open source, verified from GitHub, ready to install
AGENTS.md Version 2 enables AI agents to autonomously interact with websites using browser automation, allowing developers to automate complex web tasks programmatically. It's ideal for developers building AI-powered automation tools and agents that need reliable web interaction capabilities.
"description": "Create and edit Obsidian vault files including Markdown, Bases, and Canvas. Use when working with .md, .base, or .canvas files in an Obsidian vault.", "name": "Steph Ango", "url": "https://stephango.com/"
"email": "tobi@lutke.com" "description": "Search and retrieve documents from local markdown files.", "email": "tobi@lutke.com"
You are an elite CLAUDE.md auditor and documentation integrity specialist. Your sole purpose is to ensure every file and file in the project accurately reflects the current codebase state. You work autonomously: discover, analyze, and fix documentation drift without manual guidance. You are method
This booster automates merging README.md files from multiple subdirectories into a root README.md for the TCP-IP-NetworkNote project. It's useful for maintaining a unified documentation index for large multi-chapter projects.
"name": "claude-reflect", "description": "Self-learning system for Claude Code that captures corrections and updates CLAUDE.md automatically", "name": "Bayram Annakov",
Automates the categorization and documentation of Neovim plugins in markdown-based plugin lists, helping maintainers of awesome-list repositories organize plugins by type and explain categorization decisions.
AGENTS.md provides a Python framework for building AI agents that execute complex, multi-step workflows with consistency using natural language definitions. Developers working with Claude can use this to create reusable agent SOPs that work across multiple platforms and convert to Anthropic Skills format.
"name": "spec-driven-develop", "name": "zhu1090093659" "description": "Automates pre-development workflow for large-scale complex tasks"
Use this agent when documentation in the `architecture/` directory needs to be updated or created for a specific file after implementing a feature, fix, refactor, or behavior change. Launch one instance of this agent per file that needs updating. This agent maintains the *contents* of architecture documentation files — it does not decide which files exist or how the directory is organized.\n\nExamples:\n\n- Example 1:\n Context: A developer just finished implementing OPA policy evaluation in the sandbox system.\n user: "I just finished implementing the OPA engine in crates/openshell-sandbox/src/opa.rs. Update architecture/sandbox.md to reflect the new policy evaluation flow."\n assistant: "I'll launch the arch-doc-writer agent to update the sandbox architecture documentation with the new OPA policy evaluation details."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/sandbox.md>\n\n- Example 2:\n Context: A refactor changed how the HTTP CONNECT proxy handles allowlists.\n user: "The proxy allowlist logic was refactored. Please update architecture/proxy.md."\n assistant: "Let me use the arch-doc-writer agent to synchronize the proxy documentation with the refactored allowlist logic."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/proxy.md>\n\n- Example 3:\n Context: After implementing a new CLI command, the assistant proactively updates docs.\n user: "Add a --rego-policy flag to the CLI."\n assistant: "Here is the implementation of the --rego-policy flag."\n <implementation complete>\n assistant: "Now let me launch the arch-doc-writer agent to update the CLI architecture documentation with the new flag."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/cli.md>\n\n- Example 4:\n Context: A user wants high-level overview documentation for a non-engineering audience.\n user: "Update architecture/overview.md with a non-engineer-friendly explanation of the sandbox system."\n assistant: "I'll launch the arch-doc-writer agent to create an accessible overview of the sandbox system for non-technical readers."\n <uses Task tool to launch arch-doc-writer with audience=non-engineer directive>\n\n- Example 5:\n Context: Multiple files need updating after a large feature lands.\n user: "I just landed the network namespace isolation feature. Update architecture/sandbox.md and architecture/networking.md."\n assistant: "I'll launch two arch-doc-writer agents — one for each file — to update the documentation in parallel."\n <uses Task tool to launch arch-doc-writer for architecture/sandbox.md>\n <uses Task tool to launch arch-doc-writer for architecture/networking.md>
"$schema": "https://anthropic.com/claude-code/marketplace.schema.json", "name": "claude-health", "description": "Configuration health audit skill for Claude Code. Audits CLAUDE.md, rules, skills, hooks, subagents, and verifiers with bounded data collection.",
mq is a jq-like CLI tool for querying and transforming Markdown files, with development guidelines covering Rust conventions, project structure, and multi-platform integrations (LSP, DAP, WASM, Python). Developers building Markdown processing pipelines or contributing to the mq project benefit from these structured instructions.
Helps SwiftUI developers integrate the Recap library for in-app release notes, configure display policies, and maintain Releases.md documentation. Essential for teams building apps with Recap-based feature announcements.
Draft PR content with the following additional instructions: $ARGUMENTS Create a PR draft in file based on the current branch changes. 1. Verify branch status:
Skyll enables agents to dynamically discover and retrieve skills at runtime. Instead of having all skills pre-loaded, agents can search for relevant skills on-demand and inject them into context. Get a specific skill: The API returns ranked skills with relevance scores (0-100):
Lint agent configurations before they break your workflow. Validates Skills, Hooks, MCP, Memory, Plugins across Claude Code, Cursor, GitHub Copilot, and Codex CLI. Invoke when user asks to: If not found, install:
Automatically extracts knowledge from Amp threads and synchronizes project documentation, keeping AGENTS.md and other docs up-to-date after epics and major work. Ideal for teams that need to maintain living documentation without manual overhead.
Automates creation of standardized research project structures with pre-configured folders, documentation templates, and guidelines. Ideal for researchers and teams starting new projects who need consistent organization and onboarding rules.
A Cursor IDE ruleset that enforces modern TypeScript, React, and Next.js best practices for building performant, maintainable web applications. Ideal for developers using Cursor who want consistent coding standards across their Next.js projects.
ring:dev-implementation automates code development using specialized agents and enforces test-driven development (TDD) workflows across projects. Development teams benefit from consistent implementation patterns and quality gates.
A plaintext-first docstring formatting specification for Python code that standardizes documentation style across projects. Developers writing or maintaining Python codebases benefit from consistent, readable documentation practices.
On every change, verify:
PSI is a structured Plan-Spec-Implement workflow that guides developers through documentation-first development with test-driven implementation. It benefits teams wanting disciplined, traceable development processes with clear artifact generation.
A zero-friction checkpoint tool that instantly saves session context, memory, and progress to files without prompts or delays—essential for Claude Code users managing multi-turn projects and persistent state.
