Claude Code plugins
22 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 22 plugins that match these filters.
22 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 22 plugins that match these filters.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceTurn any domain folder of skills into a bounded agentic loop: a manifest builder inventories a domain's skills/tools/checks, a goal compiler turns a goal into a verifiable task plan (refusing vague goals with forcing questions), and a JSON-backed loop controller drives execute->verify->close with retry caps, controller-run verification (no verification theater), human escalation on exhausted budgets, and a close gate that refuses while any task is unverified or unwaived. Ships 3 stdlib Python tools, 18 committed per-domain harness manifests + JSON schema, 3 references citing the 2024-2026 agent-harness canon (Anthropic long-running harnesses, verifier's law, SWE-agent, Ralph loop, Cognition), harness-runner agent + /cs-harness command. Use when an agent or subagent should pick up a goal, define its tasks, complete and verify them, and close the loop.
Customer Success skills: Customer Health Scorecard, QBR Deck, Escalation Brief, Churn Analysis, Renewal Playbook, Customer Success Plan. Score health, build QBRs, write escalation briefs, plan renewals with commercial strategy and objection responses, and build joint success plans with milestones and mutual commitments.
Improves code targets — skills, plugins, or a branch's changes — through an autonomous review-and-fix workflow with a pluggable reviewer (any installed skill or agent), a cross-round findings ledger, oscillation escalation, and a mechanical scope guard.
Support & customer-ops skills: Support Macro, Help-Center Article, CSAT/NPS Analysis (with an NPS calculator), Support Runbook, Escalation Tree, and KB Audit. For frontline support, CX, and success teams.
Banking & lending skills: credit memos with covenant headroom, quarterly covenant compliance reviews, KYC/AML escalation write-ups, and portfolio risk briefs — credit and compliance judgment for analysts and RMs.
Scientific paper writing, source-traced review, and de-AI rewriting for top-tier journals (ApJ/MNRAS/PRD/JCAP-class) and NSF/NIH proposals. Ships 12 skills and 40 tools under one typed standard: scientific-integrity blockers that cannot be waived as style preferences, a zero-target L0 lexicon, ranked advisories, explicit measurement states so missing calibration never reads as clean, claim-first rewriting gated on hard scientific-fidelity eligibility, a mechanical length budget with a machine-built removal map and a required-shrink gate, corpus-calibrated salience-hierarchy, domain-register (with an exhaustive zero-hit vocabulary audit), collocation, and discourse-texture (given/new cohesion, epistemic hedging) axes, each judged against the field's own per-section distribution at the unit it was calibrated at, a residue axis that gates the trace an edit leaves, A-R review with narrative-spine and adversarial-escalation dimensions, registry-verified bibliographies (CrossRef, DataCite, a
writingAssess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.
Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.
Claude skill that turns Claude into a Connecticut-specific divorce planner — nine operating modes from pre-flight intake to post-judgment modification, modeled on Untangle.us's feature surface and grounded in C.G.S. Title 46b, Practice Book Chapter 25, and the 2026-08-01 CCSG schedule. Covers eligibility triage (nonadversarial under § 46b-44a vs standard), financial affidavit (JD-FM-6), child support (JD-FM-220 / CCSG-1 / 1A), alimony (§ 46b-82 fourteen factors), parenting plan (with GAL/AMC escalation under JD-FM-224), settlement agreement (JD-FM-172, TCJA-aware), filing packet (marshal 12-day rule, $360 + $50 fees, JD-FM-75 waiver), and post-judgment motion practice. Hard UPL gate: refuses non-CT, domestic violence (refers CTCADV 1-888-774-2900), hidden assets, courtroom advocacy. Heppner-aware: AI prompts are not privileged. First family-law skill in the Lawvable registry.
Approval cascade definition and tracking for multi-stakeholder document workflows. Internal review sequences, client approval workflows, regulatory review, overdue chasing with escalation logic, version control coordination, and cross-jurisdiction document dependencies.
End-to-end external local counsel lifecycle management for multi-jurisdiction legal matters. LC selection criteria and capability assessment, engagement setup and instruction design, performance monitoring and check-in cadence, scope enforcement, and relationship escalation.
Draft matter status reports from emails, call notes, and updates. Internal and client-facing formats, RAG logic, variance commentary, escalation flags. Use when asked to draft a status report, write a project update, summarise matter progress, prepare a client report, create a weekly or monthly update, convert emails into a status summary, or produce any kind of matter reporting. Also triggers when the user pastes email threads and asks what the status is, or needs to turn internal updates into client-facing reports.
Adjudicates whether a hit generated by sanctions, PEP, or adverse-media screening is a true positive, false positive, or requires human escalation. Use whenever a user presents a screening alert, a name match against a watchlist (OFAC SDN, EU consolidated list, UK OFSI, UN list, PEP list, adverse media hit, etc.), or asks to clear a screening hit / reduce false positives / determine whether a flagged name is actually the listed party. Use even when the user describes the task casually — "is this person actually on the sanctions list", "did we get a real match", "clear this alert", "I have a hit on X" — these are all screening-adjudication tasks. Produces a deterministic determination with full audit trail (structured JSON + human-readable narrative). Designed for use by compliance analysts and screening systems.
Human-in-the-loop (HITL) gate definitions for agent operations. Provides reusable YAML gates for destructive-action authorization, false-positive override, and recovery escalation. Loaded by agent loops and orchestrators that need bounded human checkpoints.
Determines whether a specific AI-agent action, output, recommendation, or proposed commitment remains admissible for execution or institutional reliance under current authority, delegated scope, evidence, facts, policy, risk, escalation, and revocation conditions. Use this Skill before an enterprise or regulated AI agent executes, updates records, triggers workflows, communicates externally, or before an institution relies on an agentic output in a way that creates legal, financial, operational, regulatory, customer, employee, patient, citizen, market, contractual, or reputational consequence.
Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. Use when evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review.
Reviews outside counsel invoices against billing guidelines, flags non-compliant entries by category, and produces the documents needed to approve, reduce, reject, and communicate those decisions. Covers the full invoice compliance workflow: line-item review through to formal firm escalation. Works with or without an e-billing platform. Where an e-billing system is in place, LEDES format and UTBMS coding are hard gates. Where there is no e-billing system, invoice submission by email is the channel and UTBMS coding is a best-efforts flag.
Operate an evaluated agent with tools and authority in production through a runtime control plane covering versioning, staged rollout, fallback, cost and latency budgets, tool health, human escalation, disablement, and trace-to-eval feedback. Do not use for building agents, designing evals, or general release, SRE, security, or platform engineering — those methods stay with their specialist skills.
Guide recurring human-relationship practices — success plans, health evidence, renewal and expansion signals, QBRs, handoffs, escalation, and closed-loop Voice of Customer. Do not use this skill for products without accounts, renewals, QBRs, or a customer-success team, including some internal tools, pure transactional products without recurring relationships, and public services without account-based engagement. Load only when the product context includes a recurring human relationship; decline or route away otherwise.
Route a product through its full lifecycle — discovery, strategy, portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules. Use when evaluating a new product idea, managing a product through its lifecycle, or connecting product phases that currently operate in isolation. Do not use for a single product task that is already owned by a specialist skill (load that skill directly); do not use for software delivery lifecycle work (route to neckbeard); do not use to duplicate product discovery, strategy, UX, experimentation, analytics, release, or delivery methods.