🔌
Plugins
Loading...
Showing 30 of 27515 results
Skills for creating and refining Claude Code skills, rules, hooks, and subagents.
from involvex/involvex-claude-marketplace
from nathanvale/side-quest-marketplace
Cairn agent skills for Claude Code — authoring, review, maintenance, and collaboration. Markdown skills only; no runtime code.
FERPA-safe AI-assisted Canvas LMS toolkit. Includes agent specs (8) and pedagogical knowledge files (20+) covering course design audits, FERPA-safe LLM grading, Canvas sync, and the BYU-I Learning Model.
Full Captains Cabinet plugin: framework + work preset + 5 officers + 19 skills + 11 slash commands + 6 MCP servers.
Personal Cabinet variant — coaching-focused, lighter governance, Captain triplet only. Selects the personal preset via instance/config/active-preset at first run.
CAROL framework: ORACLE, COUNSELOR, MACHINIST primaries with Engineer/Pathfinder/Auditor/Librarian/Researcher secondaries, plus hooks and slash commands.
from ImproperSubset/hh-agentics
from tolo/coding-agent-toolkit
Portable scratch-notebook core: per-thread STATE.md handoffs + compiled INDEX dashboard, 3 skills + 2 hooks. Language-agnostic, no ticket system required.
from Lordjiggy/claude-code-marketplace
Know the project + own the owner relationship. At SessionStart, a compact proportional brief that gates substantive work on the project's Claude-facing docs: quality attributes (Lighthouse-aligned for web), a project map (file→responsibility index, for blast radius), recorded decisions/ADRs (the alignment anchor — don't reverse without consulting), a roadmap/backlog, stack notes, and the project's established conventions (reuse before create) — generating them from code/git when missing and going quiet once they're summarised in CLAUDE.md (claude-companion marker). Surfaces outcome memory — "scar tissue": files this project has REPEATEDLY had to FIX, derived from git history by the rework ratio (fix/revert commits over total touching a file), not raw churn — so the review loop treats debt magnets as high-risk (understand why they churn, cover them, prefer the smallest change, or simplify an over-built abstraction) before extending them; surfaced even in quiet mode (it's state, not policy), silent on a clean/new repo. Owns the non-technical owner loop: confirm intent in plain language → demonstrate the result back → recap. Adds an alignment floor — a bounded Stop hook (the outcome-time complement to the review loop's intent-time alignment): when a finished change plausibly bears on a recorded decision (a dependency manifest / config / migration changed, or a backtick-fenced decision token appears in the diff), it blocks once and puts the recorded decisions in front of the model — honor them, or, if the change reverses/contradicts one, surface that to the owner in plain language and confirm before it lands. Silent on routine edits and on projects with no recorded decisions; bounded (≤ CLAUDE_CHARTER_ALIGN_MAX blocks/session, never twice for the same tree) so it can't loop; disable with CLAUDE_CHARTER_ALIGN_GATE=0. /charter:align reconciles open/proposed work against recorded decisions + roadmap on demand (clean ≠ correct). Action-time consent for consequential/irreversible operations is enforced natively (settings.json auto mode + deny/ask rules), not a charter hook. MCP reachability probe: a second SessionStart hook checks that the MCP servers DECLARED for this project (merged read-only from ~/.claude.json, .mcp.json, and .claude/settings*.json) actually respond — briefly spawning each stdio server for the MCP initialize handshake and POSTing it to each http/sse endpoint, every probe hard-bounded by a per-server timeout and run in parallel — so the silent failure mode (a mis-installed/unreachable server whose tools just never appear) is surfaced to a non-technical owner in plain language; an HTTP auth challenge counts as reachable (not down), only a fresh start probes (not compact/resume), self-disables when no servers are declared, never blocks, and disables with CLAUDE_CHARTER_MCP_PROBE=0. Read-only over the project except for cache-only throttle state — it detects and the model authors the docs.
Control and inspect a live Chrome browser from your coding agent. Record performance traces, analyze network requests, check console messages with source-mapped stack traces, and automate browser actions with Puppeteer.
Test web application features in Chrome browser using DevTools MCP. Use proactively after implementing features or bug fixes.
Development hooks for validating CHT bash commands and formatting CHT configuration files