Meta skills — authoring new skills, the OCKHAM minimal-entities discipline, and the WITTGENSTEIN clarity gate for specs & plans.
Plugin meta from marketplace bladeforge in aquivalabs/BladeForge. Commands read from the repo's manifest — 2 days ago.
lean-writingUse this skill to WRITE terse technical documents. Trigger when asked to write, draft, summarize, present, or update a spec, design doc, RFC, brainstorming/exploration summary, or a decision log of options considered — e.g. "write the spec for…", "draft a design doc…", "write up the options we consi
model-routingUse whenever the plan is to spawn, fan out, or parallelize agents \u2014 ANY multi-agent work, not just when models are mentioned. Triggers: \"spawn/kick off subagents\", \"a bunch of agents in parallel\", fleets that audit/comb/sweep/hunt across files, verify or skeptic stages, reviewer fan-outs, l
new-skillUse this skill to author a brand-new skill FROM SCRATCH \u2014 deciding its plugin/domain, folder name, file placement, and writing its SKILL.md, frontmatter, and initial metadata.yaml sidecar. Triggers for \"create/add/write a new skill for X\", \"where does the SKILL.md go\", \"what's the naming c
ockhamThe Razor. Invoke before creating ANY new entity — file, folder, module, class, function, component, hook, util, type, prop, variant, config key, abstraction layer, doc, or top-level category — in ANY language or stack. Not domain-specific. If you are about to bring a new thing into existence, OCKHA
reuse-firstUse before implementing any non-trivial piece of functionality in any stack — a drag-and-drop list, a tooltip or popover, a dialog, a date formatter, a form with validation, a debounce, a virtual list, a data table, a fetch cache, an animation, a parser — when the question is whether to write it or
skill-evalUse when you need to know whether a skill's `description` actually makes Claude reach for it — scoring an existing skill's trigger accuracy before shipping it, after editing its description, or when someone reports that a skill \"never triggers\" and you need to find out why. Also use to read a scor
solidSOLID is the design law for all code — SRP/OCP/LSP/ISP/DIP plus DRY, KISS, YAGNI. Activate at DESIGN time and whenever writing, editing, or reviewing code in ANY language or stack — ESPECIALLY when a class, function, hook, route, or method does several things (fetches + formats + writes, or auth + v
triageUse when you're about to attack a LARGE batch of items the same expensive way \u2014 a repo-wide sweep for dead code, unused exports, or bugs; a big multi-file diff to review; dozens of call sites to migrate; a fleet of skills, files, or docs to audit or read; every TODO to classify; hundreds of fai
update-skillUse when a skill ALREADY EXISTS and something about it needs changing: its body, its `description` or boundary wording, a missing `## Contract` or acceptance criteria, or a `metadata.yaml` sidecar that no longer matches what the skill does after its allowed-tools, bundled scripts or hooks changed. N
wittgensteinClarity gate for an already-written spec, plan, design doc/note, or RFC — a reviewer persona, not a writing guide. Activate to REVIEW or AUDIT such a doc (often under docs/superpowers/specs or docs/superpowers/plans) when checking whether a non-technical manager or reader could follow it; when it fe
Stack-agnostic pre-push review framework — eight reviewer agents (five on by default, plus skill, leak and security-scan for repos that publish skills), the /review orchestrator, and the secret-scan + attestation gate, all driven by a per-project .claude/review.config.json.
2 skills · 2 commands · 8 agents
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
Install the "Skill Author" editorial skill bundle for Claude Code.
6 skills
Connect Claude Code to 325+ business data sources via Windsor.ai. Query marketing, sales, CRM, ecommerce, finance, and analytics data from Google Ads, Meta, HubSpot, Salesforce, Shopify, Stripe, and hundreds more — directly from your terminal.
Technical SEO optimization including meta tags, keywords, structure, and featured snippets
4 agents
Cross-platform ad management for Google Ads, Meta Ads, TikTok Ads, and LinkedIn Ads. 91 tools for keyword research, campaign creation, performance analysis, and budget optimization.
15 skills · 5 commands · 1 agent · 1 MCP server
Founder-mode executive team plugin: 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff, General Counsel, Chief Data Officer, Chief AI Officer, Chief Customer Officer, VP of Engineering) with distinct cognitive voices, plus 21 /c-level-agents:* slash commands — forcing-question office hours (CFO/CMO/CPO/CRO/CTO/CISO/GC/CDO/CAIO/CCO/VPE reviews), strategic sprint pipeline (brief → boardroom → decide → execute → post-mortem), and meta routing (/c-level-agents:founder-mode auto-router, /cs-onboard, /c-level-agents:cross-eval multi-model consensus, /c-level-agents:freeze cooldown lock). Wraps the 33 c-level skills with cognitive gearing, persona voice, and artifact-driven handoffs. The business-domain answer to YC Garry Tan's gstack.
22 skills · 13 agents
Agent coordination and meta-programming - multi-agent orchestration, workflow automation, and safe refactor governance. Works best with other voltagent plugins installed.
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.