Claude Code plugins
8 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
8 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceOrganic LinkedIn presence, end to end, with LinkedIn's own rules enforced in code. Orchestrator (context: fork) gates every request against User Agreement §8.2 — refusing automation, scraping, engagement pods, bulk DMs, fake identity and fabricated proof, each with a compliant substitute — then routes to profile / strategy / content / engagement / analytics. Headline and whole-profile scoring with fixes ranked by points per hour; positioning brief with a mandatory exclusion list; cadence priced against real hours with a 90-minute floor; newsletter eligibility + six-month sustainability gate; post linter blocking on engagement bait and screen-reader-hostile Unicode pseudo-bold; repurposing with a reuse ledger; capped commenting roster and template-refusing outreach; analytics that test patterns against a seeded permutation null and refuse to conclude below 10 posts. 17 stdlib tools, 15 references with per-claim confidence levels. No credentials, no API calls, nothing auto-sent. Answers
Fix the cause, reuse what already works, and keep changes focused on a verified outcome.
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".
Capture, structure, and recycle lessons from active and closed legal matters. Three modes: in-flight capture (triggered by scope changes, risk events, status updates), mid-matter review (phase gates or quarterly), and matter close retrospective. Lessons are formatted for immediate reuse, not filed and forgotten.
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.
Create, explore, critique, and practice solarpunk across visual art and image prompts, fiction and worldbuilding, fashion, games, education, everyday living, adaptive reuse, ecological design, parklets, guerrilla gardening, urban and rural planning, community infrastructure, and hopeful collective futures. Use for solarpunk aesthetics, stories, values, or practical paths toward equitable ecological flourishing. Do not use for generic sustainability tasks with no solarpunk intent, certified engineering, jurisdiction-specific legal advice, or operating an image or infrastructure tool; pair with the relevant specialist.
Run Claude (or any capable LLM) as an autonomous senior engineer on any codebase — config-driven hooks enforcing discover-then-reuse, plus coordinator/succession/doc-sync skills and planner/builder/auditor agents. Frontend or backend, any language.
productivityIntercepts unclear prompts and forces restate-to-align with the user, then diagnose the root cause and reuse the domain's mature, established practices before proceeding