4,699 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
foundryxobotyi/cc-foundry1
ghost-securityghostsecurity/skills1
open-dashboardahpxex/open-dashboard1
kevmookevmoo/dash_skills1Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceThe full Open Dashboard skill catalogue — the `add-component` skill (a retriever over 35+ UI shapes: forms, lists & tables, kanban/calendar/tree/timeline, detail & pages, display & feedback, RBAC/auth/i18n/billing/search/realtime) plus the operation skills (scaffold-dashboard, add-backend, rebrand). The shapes assume the scaffold-dashboard base (TanStack Start + the platform layer) — run scaffold-dashboard first, then compose the shapes on top.
Dart & Flutter authoring, testing, and maintenance skills.
wjs-evaling-voicedrop-prompts
Core creation pipeline: onboard, create, fill, validate, test, package, publish — guided product creation with 20 structural quality patterns
Research and knowledge tools: scout domains before building, map expertise, explore marketplace, brainstorm approaches
Security audit for codebases — threat modeling, vulnerability detection, compliance checking, and hardening recommendations
Let your coding agent direct a cinematic launch video of your running web app. No LLM API key needed.
productivityHelp AI say clearly and get to the point.
productivityUse for Six Thinking Hats or de Bono's parallel thinking, or when a decision or idea needs facts, gut feel, risks, benefits and new options kept apart: "look at this from all sides", "full perspective check". Skip for plain factual questions or single-angle hot takes.
Use for critical thinking, or when the user wants a claim, plan or decision checked for weak spots: "is this right?", "what am I missing?", "poke holes", "sanity check", "devil's advocate", "red team this". Skip for execution-only tasks and wording edits.
Use for systems thinking, or when a change may ripple beyond its target: "what are the side effects?", "why does this keep coming back?", "how do these teams or services affect each other?". Maps loops, delays and leverage points. Skip for single-step fixes.
Use for creative thinking, or when the user wants many fresh options before choosing: "give me ideas", "brainstorm names", "other ways to do this", "think outside the box". Diverges first, then picks. Skip when one answer is wanted or the task is pure execution.
Use for strategic thinking, or when the user must choose a direction under constraints: "where should we focus?", "how do we win?", "roadmap for next year", "what should we not do?". Ends in explicit bets and risks. Skip for step-by-step implementation.
Use for analytical thinking, or when a question needs breaking down and evidence: "why did metric X drop?", "what drives this?", "break this down", "what data do we need?". Builds a tree, hypotheses and evidence, ends with an answer and key uncertainty. Skip for quick verdicts.
Use for lateral thinking, or when ideas feel stuck or incremental: "we've tried everything", "need a surprising angle", "break the pattern", "give me a wild idea that could work". Uses provocations and reframes. Skip for rule lookups or strict logical proofs.
Use for design thinking, or when a product or service problem needs user understanding before solutions: "what do users really need?", "how might we...", "plan a discovery sprint", "validate this concept". Skip when the spec is frozen or the task is code maintenance.
