1,594 boosters for "ai" — open source, verified from GitHub, ready to install
"name": "teams-skills", "name": "Microsoft", "url": "https://github.com/microsoft"
"name": "spec-driven-develop", "name": "zhu1090093659" "description": "Automates pre-development workflow for large-scale complex tasks"
Review the most recent commit (or the commit specified in ) in a single pass, using FXA-specific knowledge. Use Read and Grep to examine the changed files and their surrounding context. Look at imports, callers, and related types to understand the full picture before judging. Evaluate the diff throu
Browse once, cache the APIs, reuse them instantly. First call discovers and learns the site's APIs (~20-80s). Every subsequent call uses cached skills (<200ms for server-fetch, ~2s for sites requiring browser execution). When the task touches docs, install guidance, eval claims, landing-page copy, r
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>
"description": "Agent orchestration harness for Claude Code — campaign persistence, fleet coordination, intent routing", "name": "SethGammon" "homepage": "https://github.com/SethGammon/Citadel",
Refactor $ARGUMENTS to improve: 2. Maintainability 4. Modern Patterns
"version": "0.25.0", "description": "Datadog API CLI with 49 command groups, 300+ subcommands. Skills and domain agents for monitoring, logs, APM, security, and infrastructure.", "email": "support@datadoghq.com"
Our approach is pythonic, minimal and readable code. Follow these guidelines: 1. Use Vuetify components for UI (refer to vuetify.min.js) 2. Leverage Material Design Icons (refer to materialdesignicons.css)
"name": "research-companion", "description": "Strategic research thinking agents — idea evaluation, project triage, and structured brainstorming inspired by Carlini's research methodology", "name": "Andre Huang",
A debugging assistant that systematically analyzes errors, identifies root causes, and implements minimal fixes with verification for TypeScript and UI components. Ideal for developers working in Claude Code who need structured guidance on troubleshooting and fixing bugs.
Quoroom is an experimental open-source framework for building local AI agent systems with a Queen-Workers-Quorum architecture, designed for researchers and developers exploring multi-agent AI patterns with Claude and other LLMs.
The Portfolio Optimization skill applies mathematical optimization techniques to project portfolio selection and balancing. It maximizes portfolio value while respecting budget, resource, and strategic constraints, enabling data-driven investment decisions. 1. Annual Planning: Optimize project selec
Switch between Docker and Kubernetes backends for Kurtosis. After switching, restart the engine: When using Kubernetes:
1. Preserve custom rules from existing .gitignore 3. On auth error (401), retry with 4. Re-add preserved custom rules
Provides Flutter developers with structured guidance on integrating Firebase In-App Messaging, including setup, message triggering, privacy controls, and campaign testing to enhance user engagement.
This skill provides a philosophical framework and analytical methods for evaluating whether end users can "know" what value they can achieve through a product. It guides analysis from a value discovery perspective, rather than providing checklists. End users adopt products when they know what value
"name": "claude-dashboard", "version": "1.29.0", "description": "Unified status line for Claude Code with multi-CLI (Claude, Codex, Gemini, z.ai) usage monitoring, context, rate limits, and cost tracking",
This skill documents how to run the Parchi relay daemon, connect the browser extension as an agent, and use the CLI to drive browser automation. 1. Build everything: 2. Start the relay daemon (terminal A):
"name": "langchain-skills", "description": "Agent skills for building agents with LangChain, LangGraph, and Deep Agents", "name": "LangChain",
45 AI-powered skills for affiliate marketers. Each skill automates a specific workflow (content creation, program research, SEO, outreach, analytics, etc.) using live data from the Affitor API.
"description": "AI-native job queue for Bun — skills, MCP server (73 tools), custom agent, SQLite persistence, cron, priorities, retries, DLQ, webhooks", "name": "egeominotti" "homepage": "https://github.com/egeominotti/bunqueue",
A specialized AI skill for conducting 5S workplace organization audits with scoring, photo documentation, and sustainability tracking—enabling manufacturers and facilities managers to systematically assess and improve workplace organization.
1. Write Simple, Clear Code 3. Project Structure 4. Development Practice
