14 plugins from public Claude Code marketplaces. Each one bundles skills, slash commands, agents, hooks or MCP servers that install together.
Showing 14 plugins that match these filters.
agents-incagents-inc/skills1
magnus-agent-skillsmagnus919/agent-skills1Submit the repo with .claude-plugin/marketplace.json and we list every plugin.
Submit marketplaceThis skill maps disclosure strategy from a case summary, pleading, chronology, or early case theory: the document categories that will matter, likely custodians, adverse material, evidential gaps, search themes, and the risks worth confronting early.
Authoritative reference for Pi (@earendil-works/pi-coding-agent): install, configure, run, and extend. Use when the user asks about Pi CLI/flags/commands, providers/models/auth, settings/compaction/sessions, security/trust, extensions, skills, prompt templates, themes, packages, MCP, codemode, custom providers, TUI components, the SDK, RPC mode, or JSON streaming. Also use for Pi's design philosophy and opinionated choices (why minimal, 4 tools, YOLO, no MCP/plan mode/to-dos/sub-agents), Pi's internal monorepo architecture (the Chord typed host runtime (@earendil-works/chord), the durable agent harness (@earendil-works/pi-durable) and its Pico5 specification, telemetry, delta tracking), and the repository's build, development, and contribution rules. Also use for Pi Durable itself: what the experimental harness is, its versions, the runnable examples, and which blog demos 1.2.0 removed.
Authoritative reference and rules for developing for Obsidian — building TypeScript plugins (Plugin lifecycle, manifest.json, commands, settings, modals, views, ribbon/status bar), the Vault and Editor APIs, the event system, Markdown post-processing & code-block processors, CodeMirror 6 editor extensions, building CSS themes (CSS variables, theme.css/manifest), and submitting plugins/themes to the community directory. Use whenever the user asks to build, debug, or review an Obsidian plugin or theme, work with the Obsidian API (Vault/Editor/Workspace/Plugin), register commands/views/events, process Markdown, or release/submit to the Obsidian community.
Tamagui universal UI - styled(), tokens, themes, optimizing compiler, responsive media queries, animations, Sheet/Dialog components
Build, customize, and debug advanced Hugo CMS themes — template architecture, asset pipeline (CSS/JS/image processing), shortcodes and render hooks, page bundles, cover images, Hugo Modules, performance, SEO, and CI/CD. Use when working on a Hugo theme or site template layer. Do not use this skill for unrelated requests; route to the nearest named specialist.
Skills for CMS development across themes, plugins, admin tooling, media workflows, markdown rendering, and static export pipelines.
Create professional Marp presentation slides with 7 beautiful themes. Use when users request slide creation, presentations, or Marp documents.
Explore grouped customer feedback signals by impact and drill into a theme to guide product next steps.
Turn material, outlines, or talking points into click-driven 16:9 HTML slide decks for live presenting — cinematic, anti-AI aesthetic, 24 built-in themes, per-step speaker notes, and a presenter view (press P: speaker notes + live slide preview + timer in a separate window, synced via BroadcastChannel — share only the slide window to hide notes from the audience). Ships a Vite + React + TypeScript scaffold. Derived from ConardLi's garden-skills (MIT).
Use when the user asks about WordPress codebases (plugins, themes, block themes, Gutenberg blocks, WP core checkouts) and you need to quickly classify the repo and route to the correct workflow/skill (blocks, theme.json, REST API, WP-CLI, performance, security, testing, release packaging).
Use when developing WordPress block themes: theme.json (global settings/styles), templates and template parts, patterns, style variations, and Site Editor troubleshooting (style hierarchy, overrides, caching).
Use when configuring, running, or fixing PHPStan static analysis in WordPress projects (plugins/themes/sites): phpstan.neon setup, baselines, WordPress-specific typing, and handling third-party plugin classes.
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).
