Claude Code plugins
24 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 24 plugins that match these filters.
24 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 24 plugins that match these filters.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceOpenAPI specification generation, Mermaid diagram creation, tutorial writing, API reference documentation
Documentation generation, code explanation, and technical writing with automated doc generation and tutorial creation
Financial literacy for reading company accounts: a beginner's tutor for an uploaded annual report, an audited-boundary check on every headline figure, a profit-to-cash walk with the arithmetic shown, a same-definitions comparison of two companies, and a vocabulary explainer anchored to the document. Every figure carries a page reference and anything missing is marked not disclosed. Educational — not financial advice; decisions with real money belong with a regulated adviser.
Recommends relevant Claude Academy courses, tutorials, and use cases when users ask how to use Claude
A personal AI tutor based on Bloom's 2-sigma research: it generates a structured syllabus, teaches one adaptive lesson at a time, and tailors each next lesson to the learner's highlights and feedback. Bundles bloom-tutor plus six learn-* skills.
Author and maintain repository documentation: READMEs, AGENTS.md, llms.txt, Diataxis guides, component docs, tutorials, coding standards, tldr pages, and Markdown conversion or translation.
Diagnosis-first learning tutor skills: 零基础讲解、卡点诊断、解题引导、错题复盘、单词深挖、背诵抽测、学习计划。
Audits a website for compliance with Azerbaijan's Law on Personal Data No. 998-IIIQ and, where applicable, EU GDPR plus ePrivacy/cookie consent rules. Inventories the privacy documents present (privacy policy, cookie policy, cookie banner, consent flow, controller and DPO contact, data subject rights channel, cross-border transfer disclosures, AZ operator-registration references) and scores each against the applicable statutory requirements. Produces a dual-layer report: a plain-language traffic-light summary for business owners plus a clause-by-clause findings table with article-level citations for lawyers. Assessment-only, no drafting. Use whenever the user shares a URL or privacy/cookie policy text for an AZ-based or AZ-targeted site; also when the user mentions an .az domain, Law 998, the AZ State Register, ePrivacy, an Art. 27 EU representative, or asks "is my site GDPR compliant", "do I need to register as an operator in Azerbaijan", or "is our cookie banner lawful" even without
Reviews or drafts the agreement that pays an employee to settle their claims — and flags the statutory conditions that decide whether it actually binds them. Works under s.203 ERA 1996 for England & Wales. Flags apparent s.203 condition gaps for a solicitor to confirm (writing, specific complaints, independent adviser, identification, insurance, statement of conditions), drafts the substantive terms (sum, tax characterisation, confidentiality, references, restrictive covenants, indemnities), and surfaces enforceability risks. Does not rule on validity and is not legal advice. Use when the user says 'review this settlement agreement', 'draft a settlement agreement', 'compromise agreement' (old term), or asks whether an agreement is binding.
Audits a legal document against legal design principles. Scores the document on six pillars: language patterns (bureaucratese, archaisms, passive voice, nominalization), readability (Flesch Reading Ease and language-specific equivalents), structure and navigation, hidden conditions (material obligations buried away from their headings), statutory duplication (restating the law instead of citing it), and visual hierarchy where layout is available. Assessment-only; does not rewrite the document. Works on English, French, and German documents, inferring the applicable jurisdiction from the document's language and textual signals: governing-law clause, statute citations, party addresses. Use when a user shares a legal document (contract, NDA, T&C, privacy policy, internal policy) asking how good the drafting is from a legal design perspective, whether it is readable, whether it contains buried clauses or restates the law, or how it scores on Flesch / LIX / Amstad / Kandel-Moles readability
Adversarially stress-tests a legal text — a contract, statute, regulation, or judicial opinion — for interpretive ambiguity: it finds the seams where the people governed by it will later disagree about what it means and turns each into a concrete dispute scenario with both sides' arguments, the likely outcome, and a fix. Use it whenever someone wants to pressure-test, red-team, audit, or find weak spots, loopholes, gaps, ambiguities, or drafting problems in a legal document; whenever a drafter wants to tighten a contract, statute, regulation, or opinion before it issues; whenever a litigator wants to mine an opinion or contract for arguments; or whenever someone hands over a legal text and asks where it will be fought over or for issue-spotting. Trigger it for contract review, statutory-ambiguity analysis, judicial-opinion scope analysis, and drafting QA — even if the user never says "stress-test" or "ambiguity."
Day-to-day skills with memory: a morning briefing, a tutor that remembers what you got wrong, a retro that turns agent mistakes into one-line fixes, and animated explainer slides for teaching videos
Verifies UK case-law citations, pinpoint references and quotations against the official public register — The National Archives' Find Case Law — and statutory references against legislation.gov.uk, before a document that cites them is relied on, served or filed. Every check returns a graded verdict: VERIFIED, MISMATCH (the citation resolves to a different case — the classic AI miscitation), NOT ON REGISTER, OUTSIDE COVERAGE (the register cannot answer — absence proves nothing), or UNCHECKABLE (a law-report citation). The grading exists because there are two ways to get this wrong: citing a case that does not exist, and accusing a real case of not existing. Use when asked to check citations, verify a case exists, confirm a quotation is verbatim, check a pinpoint paragraph, audit a draft's authorities, screen a document for hallucinated cases, or check a statutory provision is in force. Not a substitute for reading the judgment: existence is not authority.
Guide for reading, interpreting, and applying statutes, regulations, and rules in legal and compliance contexts. Use when the user asks about (1) how to read and interpret statutes, regulations, or rules, (2) statutory interpretation methods and canons of construction, (3) understanding legislative intent, (4) applying statutes to specific legal situations, (5) extracting requirements from legal text, (6) distinguishing between different types of legal requirements, or (7) cross-jurisdictional compliance analysis.
Briefs statutes and legislative Acts using the MAPS + RULES framework: a system-level map of the whole Act (citation and text status, purpose, structure, scope, definitions) plus operational rule-modules for each operative provision (elements, legal effect, exceptions, procedure, consequences, forum, interaction rules). Works from statutory text supplied by the user and never invents statutory language. Use when briefing a statute, analyzing legislative text, mapping statutory architecture, extracting the elements of a provision, or applying a statute to facts. Triggers on "brief this statute", "analyze this Act", "map the statute", "apply [statute] to [scenario]", "what are the elements of [provision]", "statutory analysis", and on references to codified sections such as 42 U.S.C. or the Texas Health and Safety Code. Two modes: (A) text-only briefing for structural analysis, and (B) scenario-driven briefing that applies provisions to specific facts with verbatim quotation and pinpoint
Product requirements and prioritization, market and customer research, business model and pricing, and technical writing (READMEs, API docs, tutorials, runbooks, changelogs).
Apply distilled coding principles from 14 classic software books to code review, refactoring, design, and implementation decisions. Do not use for language- or framework-specific tutorials, tool manuals, or tasks already governed by a project's established conventions.
Teach a subject through source-grounded explanations, brief diagnostic tasks, practice, and adaptive feedback. Use when a learner asks to learn, understand, refresh, practice, or be tutored toward an observable goal. Do not use for a standalone factual lookup, doing the task on someone's behalf, life coaching, group-program design, or collecting research without teaching.
Generate on-brand YouTube thumbnails and in-video visuals (slides) using Higgsfield via reference images. Includes youtube-thumbnail-generate (creative ideation across variants, locked Ben face) and generate-visual (single slides or progressive-disclosure sequences for tutorial videos).
Record screen and generate narrated tutorial videos with AI voice-over.