Claude Code plugins
74 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 74 plugins that match these filters.
74 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 74 plugins that match these filters.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceHow a team that works with agents commits and opens pull requests: /commit writes messages that explain why, /git-pr keeps PRs small and can never push to a protected branch, /worktree makes parallel branches the default. Adapts to your repo's existing conventions.
Build portable, first-person colored ASCII city engines and small GIS-derived city packs. Use when designing terrain-following walking, raycast character rendering, city-provider schemas, or reproducible public-GIS ingestion. Do not use for conventional 3D/WebGL games, multi-level interiors, general GIS analysis, or committing full-resolution GIS archives.
Prepare accountable executive decisions, decision support, briefings, information triage, calendar choices, and institutional memory. Use for chief of staff or CoS, executive operations, founder operations, operating rhythm, strategic attention, executive office, board materials, organizational sensing, team health, leadership transitions, gatekeeping, decision memos, executive briefing, strategic time, attention allocation, calendar triage, or meeting audits for a solo operator or organization. Do not use for generic personal assistance, employee surveillance, inferred commitments, automatic task mutation, meeting facilitation, org structure design, or business operating-process design; route to the owning specialist.
Use this skill to shape product or engineering work before committing time to it: set appetites instead of estimates, narrow raw ideas into bounded problems, sketch solutions at the right level of abstraction, de-risk rabbit holes, write pitches, bet with capped downside (circuit breaker), and govern builds with discovered scopes and scope hammering. Adapted from Basecamp's Shape Up and extended for human+AI-agent teams. Use when a raw idea, feature request, or "redesign X" grab-bag needs to become a bounded project before anyone builds; when planning how much work an idea is worth; or when delegated agent builds need budgets, kill criteria, and non-convergence rules. Do not use for discovering whether a problem is real (use product-discovery), for portfolio-level sequencing across quarters (product-roadmapping-and-portfolio), for formal specification after the bet is placed (spec-driven-development), or for task-level prioritization frameworks like RICE (product-methodology).
Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates, rollback and recovery planning, change-management and audit compliance (SOC 2, SOX, PCI), DORA metrics, and multi-team release coordination. Do not use for application feature implementation (backend-engineering/frontend-engineering), production incident root-cause debugging or on-call/SLO operations (systematic-debugging / site-reliability-engineering), security implementation or threat modeling (secure-software-engineering), or internal developer platform construction (platform-engineering).
Manage technical projects from initiation through delivery and closure: choose and tailor predictive, iterative, Scrum, flow-based, or hybrid approaches; coordinate teams and vendors; track milestones, risks, issues, dependencies, forecasts, scope changes, and recovery. Use when a team has no project manager, a TPM needs decision-ready analysis, a project is slipping, or commitments and handoffs need coordination. Use `technical-program-management` instead when multiple related projects, teams, vendors, shared capacity, or benefits must be coordinated toward one outcome. Adapt depth to the user's expertise. Do not use for a standalone coding task, product discovery or strategy, only writing an implementation plan, only diagnosing Kanban flow, operating a ticket tool, incident command, or a release go/no-go decision; route those to specialists.
Scaffold a new production application with the full agentic-AI guardrail canon baked in from commit #1: a uniform 7-gate interface (lint, typecheck, test, coverage, build, e2e, audit) on each stack's native runner, strict types, maximal static analysis, coverage thresholds with teeth, pre-commit hooks, hardened CI, supply-chain pinning, and an agent-ready AGENTS.md. Native adapters for Next.js, NestJS, Django, Go, Rust, and Spring Boot. Greenfield only.
Expert FinOps guidance for cloud, AI, SaaS and data-platform spend. Ask Claude how to reduce a bill, size a commitment, allocate shared costs or justify AI spend, and it answers with billing mechanics, decision rules and worked examples, not generic advice. Cloud: AWS, Azure, GCP, OCI, Kubernetes and on-premises or hybrid estates, including Savings Plans, Reserved Instances, Azure Hybrid Benefit and contract negotiation. AI: Anthropic, Bedrock, Azure OpenAI, Vertex AI, open-weight model APIs, AI coding tools, agent costs, self-hosted vs managed inference. Data platforms: Databricks, Snowflake, Microsoft Fabric. FinOps practice: allocation, showback and chargeback, forecasting, operating model, FOCUS multi-cloud cost data, tagging, anomalies, KPIs, workload onboarding, SaaS and IT asset management, GreenOps. Waste playbooks: 44 runbooks for waste patterns such as idle NAT gateways, orphaned disks, snapshot sprawl, unused reservations, oversized GPUs and coding-agent token waste. Each gi
Work in an OKF project: a knowledge base conformant with Google's Open Knowledge Format from commit one.
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits).
Composes Conventional Commits messages with gitmoji from the staged diff, with safety gates for protected branches, staged secrets, and pre-commit hooks.
version-controlRewrites and polishes Chinese or English prose, technical instructions, and product copy. Use when drafting, editing, localizing, or cutting AI tone. Not for code comments or commit messages.
Committee skills.
Hand a written brief to an ACP agent in its own git worktree and herdr workspace: dated doc, optional beads epic, handoff branch, launch via acp-run, then collect (commits, stray changes, the brief's checks) and close once merged. Use for: "hand this off", "create a handoff", "start it in its own worktree".
The questions someone will ask before they fund the work. SWOT, Five Forces, PESTLE, BCG, OKRs, a PRFAQ — each one ending in a committed document rather than a deck.
product-managementDesign and build complete, distinctive web experiences — award-level product pages, cinematic scroll-directed sites, and multi-screen products as one design system. Art direction is committed before any markup, assets come from local CLIs, and nothing ships until it passes the anti-slop and motion gates.
designConversational backend for a Hugo static blog — add / edit posts, manage categories, upload images, commit, push, auto-deploy. No CMS, no server.
Holistic state-of-the-project audit: unmerged branches, stalled PRs, failed GitHub Actions, stale builds, plan drift, unreleased commits, log errors. Read-only investigation → grouped checklist → fix only after confirmation.
A single skill that submits the commits on the current local branch as a new GitHub pull request: pushes the branch to the remote, opens the pull request with a clear title and a short prose body that explains what changed and why, and pings the repository owner exactly once — it ships work that already exists rather than producing new commits
productivity