78 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 78 plugins that match these filters.
kheskillsHKTITAN/skills1
one-skill-to-rule-them-allrebelytics/one-skill-to-rule-them-all1
moss-skillsbrsbl/moss-skills1
fable-field-guideGreatMark/fable-field-guide-skills1Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceA skill for anyone needing legal documents translated into publication-ready English. Hand it a Word file in any language; get back an English .docx with formatting preserved, delivering notably higher quality than e.g. Legora’s DeepL tool. Unique features: * Skill has built-in English general lexicons and per-language sub-lexicons (phrasebooks) covering M&A, IP, IT/SaaS, finance, tax, litigation, employment and more. Full sub-lexicon coverage for 11 languages including Spanish, German, French and Chinese; others translate really well too. * Track changes read correctly when accepted/rejected, and typos are collapsed. * Definitions reordered alphabetically. * Headers, footers, footnotes and comments translated. * Translates to US English by default, UK English on request. * Quality gates throughout. * Takes minutes rather than seconds and is larger than simpler skills, but overall quality is higher. UK English default version here: https://lawve.ai/en/skills/legal-translation-uk-englis
Les LLM écrivent du juridique qui ressemble à du juridique sans en être. Formules creuses, attributions vagues, hedging systématique, latin décoratif : un praticien repère ces tics en trois lignes. Un juge aussi. Ce skill scanne 17 patterns typiques de l'écriture IA appliquée au droit français (conclusions, consultations, notes, mails, actes) et réécrit chaque passage pour retrouver le ton d'un avocat qui argumente, pas d'un modèle qui rédige. Le résultat : un texte engagé, précis, avec des références sourcées et une position claire. Pas un texte neutre qui "reste à disposition pour tout complément".
Helps a lawyer build and use a personalized Legal Guidance Vault — a local folder of structured, privilege-marked entries capturing legal guidance they've given, searchable later by topic, person, or product. Use this skill when the user says "set up my vault," "archive this meeting/email/thread/doc," "log the guidance I gave on [topic]," "save my notes from [meeting]," "what did I say about [topic]," "find the time I advised [person] on [topic]," or "search my vault for [topic]." Runs a setup interview to learn the user's tool stack (meeting notes, calendar, email, docs, messaging, vault location), then generates a customized vault prompt they can reuse in any future Claude session to start archiving and retrieving guidance.
RAID log methodology with decision extraction from emails and meeting notes. Use when asked to identify risks, log assumptions, track issues, extract decisions from correspondence, create or update a RAID log, escalate a risk to an issue, assess project risks, validate or challenge assumptions, or capture scope-relevant decisions. Also triggers when the user pastes email chains and asks what decisions were made, or needs to find buried decisions and untested assumptions in correspondence.
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.
Analyze any OFAC or OFSI enforcement action — by URL, pasted text, or uploaded document — and produce a structured root cause analysis as a formatted Excel (.xlsx) spreadsheet. Use this skill whenever a user names, links to, pastes, or uploads an OFAC or OFSI enforcement action and asks for any of the following: root cause analysis, compliance gaps, what went wrong, lessons learned, organizational self-assessment, or remediation planning. Also trigger when a user asks "analyze this enforcement action", "what were the root causes", "turn this into a checklist", or "how do I make sure this doesn't happen to us". Outputs a single-sheet .xlsx table with six columns: Root Cause | What Went Wrong | How It Went Wrong | What Could Have Stopped It | Is my organization immune to this? (Yes/No/Partial) | Notes.
Turn a lawyer's bounded expertise, workflow, review standard, or legal judgment pattern into a safe, inspectable legal AI skill. Use when a user provides legal memos, comments, checklists, negotiation notes, review habits, compliance playbooks, or professional feedback and wants a reusable Lawve-style skill. Do not impersonate the lawyer or claim to reproduce a person; distill only authorized, source-bounded capability.
Brains: answers from one source's public writing, talks or notes, with the source named. /khe-brain:emil-kowalski, /khe-brain:benji-taylor, /khe-brain:varun-mayya, /khe-brain:isb, /khe-brain:yc.
Turn-end guard for task-observer (experimental): notes a turn that used tools and wrote nothing to the observation log or checkpoints.log, and reminds the next turn to flush.
Skills for using Claude Code with mossnotes.app notes, packaged for reference use and customization.
Find your unknowns before, during, and after implementation: field-guide (router), blindspot-pass, design-directions, interview-me, reference-hunt, implementation-plan, implementation-notes, pitch-explainer, change-quiz
workflowTransforms reading-oriented prose into listening-optimized text for flat, neutral vocal delivery — TTS, podcasts, audiobooks, CLE audio. Carries a legal layer: case citations, section symbols, subsection lettering, Latin terms and footnotes are unspeakable as written, so a brief, opinion, statute, contract or memo needs them expanded, restructured or stripped before it can be listened to — and quoted authority is never rewritten. Use when converting written content for audio, preparing oral argument by ear, producing CLE or client-facing audio, or making a document listenable on a commute. Triggers on "make this listenable," "convert for audio," "optimize for reading aloud," "prepare for TTS," "make an audio version," "podcast script," "read this aloud." Supports English, French, Spanish, Italian, German and Portuguese; outputs plain text, ElevenLabs audio tags, or SSML for Amazon Polly, Google or Azure.
Condense a scholarly legal article by moving nonessential detail from the body into substantive footnotes while preserving every word and keeping the argument self-sufficient. Handles Markdown and Word (.docx), integrates moved material with existing notes, measures a user-specified relegation fraction (25% by default), and delivers a move-by-move memo. Use when asked to "push detail into footnotes," "relegate to footnotes," "footnote the caveats," "move the digressions down," or tighten a dense draft without deleting content. Word output requires file access plus document-conversion and rendering support; when those capabilities are unavailable, deliver Markdown and the memo or ask for a convertible source.
Rigorous multi-pass editor for law review articles, student notes, seminar papers and other legal scholarship. Runs six specialized passes — structure, substantive critique, Bluebook citations, grammar and clarity, fact-checking against sources, and a synthesizing memo — and delivers an editorial memo with issues prioritized as critical, substantial or minor and keyed to specific footnotes and paragraphs. Handles articles of any length, including 50,000-word pieces, by chunking on section boundaries. Reads .docx directly. Use when editing, critiquing, workshopping or pre-submission-reviewing academic legal writing. Triggers on "edit my article," "review this draft," "critique my note," "check my Bluebook citations," "is my argument sound," "read my law review piece," "workshop this paper," "pre-submission review." Chunking needs Python 3; fact-checking needs web search; both degrade gracefully without.
Turns dense legal documents, matter notes, and brainstorming dumps into clear, editable Mermaid diagrams to make strategizing and communicating clearer and faster. Use timelines and Gantt charts to uncover chronology gaps, flowcharts and decision trees to map litigation paths and negotiation possibilities, and entity relationship or class diagrams to clarify ownership, control, and corporate structure. Upload source files (.md, .docx, .pdf, .xlsx, or .pptx), paste text, or describe the issue you’re working on. /legal-diagram guides you through a simple interactive process to setup the skill and create timelines, Gantt charts, org charts, obligation checklists, litigation flowcharts, decision trees, corporate structure diagrams, and more.
Citable helps make your cite-checking more efficient and accurate. It transforms US court filings and drafts into structured tables that link every citation to pinpoint locations in the record, case law (CourtListener), statutes (Cornell LII), or treaties in a single click. Citable flags when a pincite cannot be located, potentially catching incorrect cites before your check begins. Check every citation from one table: each passage can be read alongside its citations, and clicking a citation opens the cited source. Adjust each citation’s status (check pending / confirmed / partial support / unsupported), and add notes from your review. Revised drafts: when the draft changes, citable rebuilds the table, flags the citations that changed, and carries your saved statuses and notes forward. Citable locates and links sources; the cite-checking judgment stays with the lawyer. It runs on your computer; nothing is stored in the browser or sent elsewhere.
Keep a large Obsidian vault tidy — file new notes into the best-fit folder and audit/reorganize existing structure, driven by a single source-of-truth map note (00_Index/Folder_Map.md) that lives inside the vault. Link-safe by design: all moves/renames go through the obsidian CLI so wikilinks auto-repair, never raw shell. Propose-then-confirm for bulk reorganizations.
Authoritative reference and rules for developing with Zotero — the Web API v3 (read/write requests, file upload, syncing, streaming, OAuth, item types & fields), the desktop client's internal JavaScript API, building Zotero plugins (7–10, incl. Zotero 10 migration notes), writing translators (web/import/export/search), and creating/editing CSL citation styles. Use whenever the user asks to query or write to a Zotero library via the API, build or debug a Zotero plugin, write a Zotero translator, work with citeproc-js / CSL styles, sync Zotero data programmatically, or script the Zotero client.
Screen + voice → bugs, ideas, notes and todos (review page; Markdown/CSV and hand-off .zip; your agent files them anywhere). 口喷鸡
Find which dependency APIs your code uses changed after your coding model's training cutoff, and write short AGENTS.md notes from the API diff, each with its source.
development
