Plugins de Claude Code
10 plugins de marketplaces públicos de Claude Code. Cada uno agrupa skills, comandos de barra, agentes, hooks o MCP servers que se instalan juntos.
10 plugins de marketplaces públicos de Claude Code. Cada uno agrupa skills, comandos de barra, agentes, hooks o MCP servers que se instalan juntos.
Envía el repo con .claude-plugin/marketplace.json y listaremos cada plugin.
Enviar marketplace47 marketing skills across 8 pods: Content, SEO & AEO, CRO, Channels, Growth, Intelligence, Sales enablement, and X/Twitter growth. 62 Python tools, 89 reference docs.
Engineering discipline for AI coding agents: question the request, verify against current docs instead of memory, plan, build test-first on the cheapest capable model, review with a second model family, prove it before saying done
面向长期 AI 协作项目的知识、决策与验证治理:把 Agent 的一次性工作沉淀为可继承、可验证、可持续演进的项目能力。
A markdown brain that gives your AI coding tools judgment and rigor. Skills: init, build, debug, performance, qa, interview, learn, signature, persona, route, lint, clarify, deepen, double-check, deprecate, roadmap, assess, constitution, living-docs, specify, blueprint, breakdown, checklist, analyze, converge, prototype, explain, prompt, quarantine, report, handoff, levelup, help + agents: architect, code-reviewer, refactorer, tech-scout. Experimental (v0.33.2).
Football data analytics toolkit. Covers football provider docs, identity surfaces, and analytics workflows including Opta, StatsBomb, Wyscout, SportMonks, soccerdata, mplsoccer, databallpy, and free sources. Acquire, wrangle, compute, analyse, brainstorm visualisations, and review your work. Includes a searchable MCP docs server, Reep Register lookup routing, 11 skills, and 3 agents.
AI agent orchestration: agent messaging (AMP), identity (AID), canvas pages, memory, docs and code graph search, agent management and planning
Runs a substantial task through a mandatory built-in intake grill, then 10 gated stages (docs, brainstorm+decompose, spec, plan, subagent build, tests, lint/deploy, post-deploy, docs/wiki, acceptance). Every stage's doctrine is built into the skill — no companion plugin required — with typed auto/judgment/manual gates, a frozen requirement spine that closes with evidence, a work board and a verification ledger that outlive a run, an exposure line naming what shipped unconfirmed, a progress rail computed from the project's own config, a proportional short path for small changes, a loop guard whose ceilings stop and record a blocker, and stage-3 tracks for what a product does, how it sounds and how it looks. Two modes need no task: `checkup` (what is unverified) and `setup` (audit existing docs); a third, `waves`, takes the whole board and closes it in waves that each finish in one pass. Retro insights can publish upstream as issues, opt-in and redacted.
development22 engineering documentation skills covering the complete software lifecycle.
documentationAsks whether to publish freshly created HTML/Markdown reports, plans, and docs as Claude Code Artifacts or Pagecast Cloudflare Pages URLs.
Architecture reference generator: a docs/capstone/ index plus chapters stamped to commits, kept current by generate/sync, with doctor/review commands, a greenfield pipeline with a frontend-design stage, and a doc-grounded feature chain.