35 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 35 plugins that match these filters.
claude-code-skillsalirezarezvani/claude-skills1
awesome-journal-skillsbrycewang-stanford/Awesome-Journal-Skills1
litestarlitestar-org/litestar-skills1
cc-arsenal-marketplacemgiovani/cc-arsenal1Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceInternal BizOps domain. v2.8.0 ships 7 skills: orchestrator + process-mapper (BPMN/bottleneck/cycle-time, Lean+TOC) + vendor-management (scorecard+SLA+3rd-party risk, NIST SP 800-161/ISO 27036) + capacity-planner (Erlang-C queueing math for ops teams, NOT engineering) + internal-comms (ADKAR+Kotter 8-step, NOT marketing) + knowledge-ops (SOP+runbook+KB hygiene with 5W2H, context: fork) + procurement-optimizer (UNSPSC spend categorization + supplier consolidation). Orchestrator uses context: fork to route inquiries via Matt Pocock grill discipline (one question per turn, recommended answer, canon-cited challenge). Every SKILL.md ships a Forcing-question library section. 18 stdlib Python tools, 24+ reference docs. Distinct from business-growth (external sales) and c-level-advisor (strategic).
Twelve-skill bundle covering the American Journal of Political Science (AJPS) manuscript lifecycle, with a dedicated skill for the journal's mandatory third-party verified replication package deposited to the AJPS Dataverse.
academic26 first-party Apple/Swift skills. Invoke explicitly with /apple-dev-skills:<skill>.
workflow12 first-party AI-agent collaboration & process skills. Invoke explicitly with /collaboration-skills:<skill>.
workflowOpinionated first-party agent skills, plugins, subagents, slash commands, and MCP servers for the Litestar framework ecosystem
developmentSpecialty skills: Browser automation (agent-browser), turning docs sites, PDFs, folders and YouTube videos into grounded agent skills (anything-to-skill), third-party skill discovery (find-skills), specification-driven skill creation with eval system and description optimization (create-skill v2.0), CLAUDE.md rule creation (create-rule), evidence-based improvement of existing skills (improve-skill), measured token-waste audits of AI coding setups (optimize-ai-setup), and model-tiered multi-agent orchestration (orchestrate)
Conduct AI governance, legal-risk, privacy, compliance, procurement, or vendor-risk reviews of internal AI use cases, AI product features, LLM workflows, or third-party AI vendors. The skill runs a structured intake process, identifies required documentation and missing evidence, maps the use case to AI governance frameworks and applicable legal domains, and produces a governance review with scorecards, findings, owners, remediation actions, and follow-up questions.
Pre-flight privilege and work-product check for legal AI prompts. Use when the user is about to send legal content to a third-party AI surface and wants to know whether the prompt risks blowing attorney-client privilege or work-product protection. Returns a SAFE/CAUTION/STOP band with cited factors, a discovery-impact line, and a redacted-safe rewrite.
An end-to-end method for drafting and finalising a complex, multi-pillar regulated fintech agreement — from intake to signature. Authored from a senior fintech lawyer's manual: a licensed payment-services provider engaging a counterparty across agent cash-in/cash-out, QR payments, wallet e-payments, and a marketplace, each with its own regulatory profile. Runs five phases and fourteen steps: regulatory mapping (activity-to-licence matrix, grey-zone classification gates), architecture (framework-plus-sub-agreement structure, ring-fenced marketplace), the regulatory–commercial balance (what flexes vs what cannot), core drafting (authority, float mechanics, hard-coded regulator caps, liability — all tracking control), execution-blocker triage, and a pre-signature check closing open blockers as conditions precedent. It refuses to invent licence-specific values or draft a representation as true without executed evidence. Use it to structure, draft, negotiate, or review any regulated payment
Guide to negotiating technology services agreements, professional services contracts, and commercial B2B transactions. Provides three-position frameworks (provider-favorable, balanced, client-favorable), deal-size tactics, objection handling templates, and concession roadmaps. Use when: (1) Developing negotiation strategies for SaaS, cloud, or managed services agreements, (2) Preparing position papers and fallback positions, (3) Responding to counterparty objections and demands, (4) Creating concession roadmaps that protect critical interests, (5) Assessing tactics based on deal value and leverage, or (6) Structuring balanced outcomes for liability, IP, payment, SLA, or warranty provisions.
Framework for assessing IT service providers, technology vendors, and third-party partners. Creates structured risk assessments across financial, operational, compliance, security, and reputational dimensions with regulatory checklists (GDPR, DORA, NIS2, SOX). Use when: (1) Evaluating new vendors or technology providers, (2) Conducting third-party risk assessments for procurement, (3) Performing critical vendor due diligence for regulatory compliance, (4) Creating vendor onboarding documentation, (5) Establishing ongoing vendor monitoring processes, (6) Assessing vendor concentration risk, or (7) Generating executive-level vendor risk reports.
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
Works out which documents you have to hand over to the other side in a civil case in England & Wales, and builds the formal list. The part it gets right that trips people up is which disclosure regime applies — Practice Direction 57AD (the Disclosure Pilot, now permanent in the Business and Property Courts, with its Models A–E) or standard disclosure under CPR Part 31 everywhere else. It picks the regime, chooses a Model per issue, structures the Disclosure Review Document, and drafts the disclosure certificate for the party to sign personally. Built for litigation juniors, in-house counsel, and small teams without a precedent bank. Use when the user says 'disclosure list', 'PD 57AD', 'Model C', 'extended disclosure', 'List of Documents', 'N265', or needs to work out what must be disclosed.
Analyzes legal disputes for mediation purposes — reviewing case materials (pleadings, contracts, correspondence, evidence), identifying contested issues, summarizing each party's position and interests, performing legal analysis of key issues, proposing mediation strategies or settlement directions, and preparing for mediation sessions. Use this skill whenever the user mentions mediation, dispute analysis, settlement, ADR, dispute resolution, party positions, caucus strategy, or asks to analyze a conflict between two or more parties with a resolution-oriented (rather than litigation-oriented) goal — including when they upload case files and ask for a structured breakdown of who wants what or how the case might settle, even when they don't explicitly say "mediation".
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.
Audit an AI agent skill before installing it. Use proactively whenever the user is about to add, install, enable, or evaluate an unfamiliar skill — including phrases like "audit this skill", "is this skill safe", "scan skill before install", "check skill for malicious code", "review this plugin", or any pre-install gate on an untrusted, third-party, or community-distributed skill bundle. Runs ten categories of static checks (code execution, network exfiltration, credential harvesting, persistence, prompt injection, supply-chain hooks, obfuscation, destructive filesystem ops, secrets, Trojan Source / homoglyphs) and emits a PASS / WARN / FAIL verdict.
Practitioner skill for EU Regulation 2023/2854 (Data Act). Covers Chapters II-VII (IoT data access, mandatory B2B sharing, unfair contract terms, public-sector exceptional need, cloud switching, third-country governmental access) and Chapter VIII (interoperability and smart contracts, gate-only). Use when the user asks about Data Act rights or obligations, drafts a Data Act notice or letter, reviews a data-sharing or cloud-switching contract under the Data Act, runs a Data Act gap analysis, or asks how the Data Act interacts with GDPR, the DMA, the Trade Secrets Directive, or sectoral law. Triggers include "Data Act", "Datengesetz", "Regulation (EU) 2023/2854", "Art. 4(1) request", "Art. 5(1) third-party request", "trade-secret handbrake", "cloud switching obligations", "Chapter VI", "Ch V exceptional need", and references to specific Data Act articles or recitals.
A working tool for lawyers advising on the EU Data Act (Regulation (EU) 2023/2854). Hand it the facts of a matter and it returns a classification memo, a drafting starter, a verbatim regulation lookup, an applied legal analysis, or a gap audit. Every output quotes verbatim from the bundled regulation and the European Commission's FAQ rather than paraphrasing from memory. Sixteen drafting templates cover what lawyers actually draft against: Art. 3(2) and 3(3) pre-contract notices, Art. 25 data-processing-service clauses, Art. 26, 28, and 29 public pages, the three-part trade-secret refusal pack, a safety and security restriction clause, and a third-party data-sharing request. Output goes to chat by default. A one-click Word export styled for client work is available after the chat answer, with a verified-as-of stamp and live EUR-Lex and FAQ links so currency is always visible on the page.
Expert DORA (Regulation (EU) 2022/2554 — Digital Operational Resilience Act) compliance advisor for EU financial entities. Use this skill whenever a user asks about DORA compliance, ICT risk management frameworks, ICT incident classification or reporting, threat-led penetration testing (TLPT), ICT third-party risk management, Register of Information, contractual provisions with ICT providers, ICT concentration risk, oversight of critical ICT third-party service providers (CTPPs), or any DORA RTS/ITS obligation.
Expert New Zealand Information Security Manual (NZISM) advisor for NZ government agencies and their supply chains. Use for NZISM control guidance, gap analysis, agency security obligations, classification framework (Unclassified through Top Secret), security risk management, system certification, and GCSB/NCSC NZ compliance. Triggers on: NZISM controls, NZ government security, GCSB compliance, agency cybersecurity obligations, NZ classification markings, Restricted/Confidential/Secret system scoping, agency security policies, third-party supplier security, Certification and Accreditation (C&A), and any question about NZ government information security requirements or the NZISM framework.
