review

Meta skills — authoring new skills, the OCKHAM minimal-entities discipline, and the WITTGENSTEIN clarity gate for specs & plans.

10 skills

Frontend Vue 3 skills — single-file components with Composition API and TypeScript, component architecture, BEM in scoped styles, Pinia stores, VueUse-first composables, Nuxt conventions, motion, testing.

9 skills

Frontend React skills — component structure, hooks registry, skeleton components, Storybook stories.

8 skills

Personal Salesforce skills — Apex test authoring standard and salesforce-dx MCP usage.

5 skills

Whose Turn, the Claude Code side of a local monitor of your Jira, GitHub, Linear and other sources: whose turn it is, what changed, your own to-dos, a summary at the start of each session, a hand-off from the monitor window into the session, a /whose-turn command that opens the window, and an MCP server for any agent. The monitor itself is the published whose-turn npm package; the plugin installs its latest version into the monitor's data directory on first start and runs it from there; each newer version is then announced in its window and at session start and installs only when the user says yes or clicks Update. Employer-specific values live in a workspace config on the machine, not in the plugin.

1 skill · 1 command · 1 MCP server · hooks

CERBERUS — the two-headed guard at the gate for a PUBLIC skills marketplace. A PostToolUse hook fires on every skill / reference / script / eval / manifest edit and reminds you to run BOTH heads before committing: cerberus:leak-check (outward — no real work identifier or secret escapes into the public marketplace) and cerberus:security-scan (inward — the eight-point consumer-safety checklist: prompt injection, exfiltration, secrets, dangerous commands, obfuscation, external fetches, credential access, privilege escalation, so nothing unsafe reaches whoever installs the skill). Before a push it also guards the commits themselves — their messages, authors and branch name, which no file check reads: a classic PreToolUse hook has a nested claude judge the outgoing commits and blocks a push that leaks or that it cannot judge, and on Claude Code 2.1.292 or newer a push-guard mod judges them in-process first; an older Claude Code gets a red notice at session start to update. The verdict cache is guarded best-effort, so the hook stops a forgotten check, not a deliberate forgery. Both are agent judgment passes, no denylist by design — a list of the real names to catch would itself be the leak; the intelligence lives in the agent, not a regex.

2 skills · hooks

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

5 skills + 35 modes + Material Passport pipeline. Includes v3.6.7 cross-model audit gate and v3.6.8 generator-evaluator contract.

5 skills · 16 commands · 4 agents · hooks

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills