scriptoriumadmin/claude-skills
1
0
Fork 0
mirror of https://github.com/alirezarezvani/claude-skills.git synced 2026-08-28 04:24:58 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

Merge origin/dev: reconcile docs redesign with upstream skill changes

Browse source 
- Resolve conflicts: keep redesigned skills index, take dev's cs-aeo link
  fix, union of DOMAIN_SEO_CONTEXT entries in generate-docs.py
- Regenerate catalog on the merged tree (dev's agent/command description
  updates, removed ai-seo/release-manager/command-guide, restructured
  universal-scraping-architect)
- Update counters to post-merge truth from scripts/derive_counters.py:
  345 skills, 78 plugins (14 bundles + 64 standalone), 570+ Python tools
- Add redirects for upstream-removed pages (ai-seo -> aeo,
  release-manager -> changelog-generator, command-guide -> engineering index)
- Add compliance-os bundle to bundle tables; rebuild 78-plugin table from
  marketplace.json
- Teach the generator to rewrite repo-root-relative source links to GitHub
  URLs — mkdocs build --strict now passes with zero warnings

https://claude.ai/code/session_015bYZ97nV4oRb3LbxCRFVcP
This commit is contained in:
Claude 2026-06-11 15:52:42 +00:00
commit 82c5aea9f0
No known key found for this signature in database
861 changed files with 15118 additions and 20542 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

229
.claude-plugin/marketplace.json
View file

@ -4,18 +4,18 @@
"name": "Alireza Rezvani",
"url": "https://alirezarezvani.com"
},
"description": "343 production-ready skill packages for Claude AI across 17 domains: engineering advanced (78, incl. v2.9.0 workflow-builder for Claude Code Workflow-tool authoring), engineering core (51), marketing (46 — incl. AEO/Answer Engine Optimization), c-level advisory (66), product (17), regulatory/QMS (18), compliance-os (9), project management (9), business growth (5), finance (4), productivity (6), marketing top-level (1), research (8), research-ops (5, v2.9.0), business-operations (7), commercial (8), and markdown-html (5, v2.10.3 — markdown-to-interactive-HTML converter complete: orchestrator + design-system + md-document long-form + md-review code-review + md-slides slide-deck). Includes 548 Python tools, 691 reference documents, 51+ agents, 90+ slash commands across 64 marketplace plugins.",
"description": "346 production-ready skill packages for Claude AI across 17 domains: engineering advanced (78, incl. v2.9.0 workflow-builder for Claude Code Workflow-tool authoring), engineering core (51), marketing (46 — incl. AEO/Answer Engine Optimization), c-level advisory (66), product (17), regulatory/QMS (18), compliance-os (9), project management (9), business growth (5), finance (4), productivity (6), marketing top-level (1), research (8), research-ops (5, v2.9.0), business-operations (7), commercial (8), and markdown-html (5, v2.10.3 — markdown-to-interactive-HTML converter complete: orchestrator + design-system + md-document long-form + md-review code-review + md-slides slide-deck). Includes 579 Python tools, 701 reference documents, 93 agents, 99 slash commands across 78 marketplace plugins.",
"homepage": "https://github.com/alirezarezvani/claude-skills",
"repository": "https://github.com/alirezarezvani/claude-skills",
"metadata": {
"description": "343 production-ready skills across 17 domains (engineering, engineering-core, marketing, product, c-level, compliance-os, project management, RA/QM, business growth, finance, productivity, marketing top-level, research, research-ops, business-operations, commercial, markdown-html, plus standards). 548 Python tools, 691 reference guides, 51+ agents (cs-* + personas), 90+ slash commands across 64 marketplace plugins. v2.10.3 completes the markdown-html domain with md-slides — slide-deck converter (arrow-key / Space / PgDn / Home/End / P keyboard navigation + presenter mode with split-view clock + speaker notes + next-slide preview + URL-hash deep linking like #3 for direct slide jumps + @media print page-per-slide for browser-native PDF export). Reuses md-document's markdown parser; vanilla JS only (no framework runtime); Prism.js opt-in via --syntax. Joins md-review (v2.10.2 code-review converter), md-document (v2.10.1 long-form converter), and the v2.10.0 foundation (orchestrator + design-system). Compatible with Claude Code, Codex CLI, Gemini CLI, Cursor, OpenClaw, Hermes Agent, Mistral Vibe, and 5 more coding agents.",
"description": "345 production-ready skills across 17 domains (engineering, engineering-core, marketing, product, c-level, compliance-os, project management, RA/QM, business growth, finance, productivity, marketing top-level, research, research-ops, business-operations, commercial, markdown-html, plus standards). 579 Python tools, 702 reference guides, 93 agents (cs-* + personas), 99 slash commands across 78 marketplace plugins. v2.10.3 completes the markdown-html domain with md-slides — slide-deck converter (arrow-key / Space / PgDn / Home/End / P keyboard navigation + presenter mode with split-view clock + speaker notes + next-slide preview + URL-hash deep linking like #3 for direct slide jumps + @media print page-per-slide for browser-native PDF export). Reuses md-document's markdown parser; vanilla JS only (no framework runtime); Prism.js opt-in via --syntax. Joins md-review (v2.10.2 code-review converter), md-document (v2.10.1 long-form converter), and the v2.10.0 foundation (orchestrator + design-system). Compatible with Claude Code, Codex CLI, Gemini CLI, Cursor, OpenClaw, Hermes Agent, Mistral Vibe, and 5 more coding agents.",
"version": "2.10.3"
},
"plugins": [
{
"name": "marketing-skills",
"source": "./marketing-skill",
"description": "44 marketing skills across 7 pods: Content, SEO, CRO, Channels, Growth, Intelligence, Sales enablement, and X/Twitter growth. 51 Python tools, 73 reference docs.",
"description": "44 marketing skills across 8 pods: Content, SEO & AEO, CRO, Channels, Growth, Intelligence, Sales enablement, and X/Twitter growth. 59 Python tools, 86 reference docs.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
@ -224,7 +224,7 @@
{
"name": "engineering-advanced-skills",
"source": "./engineering",
"description": "40 advanced engineering skills: agent designer, agent workflow designer, AgentHub, RAG architect, database designer, focused-fix, browser-automation, spec-driven-workflow, secrets-vault-manager, sql-database-assistant, migration architect, observability designer, dependency auditor, release manager, API reviewer, CI/CD pipeline builder, MCP server builder, skill security auditor, performance profiler, Helm chart builder, Terraform patterns, self-eval, llm-cost-optimizer, prompt-governance, behuman, code-tour, demo-video, data-quality-auditor, statistical-analyst, llm-wiki (second brain for Obsidian + Claude Code, Karpathy pattern), feature-flags-architect (flag debt scanner, rollout planner, kill-switch audit), kubernetes-operator (CRD validator, reconcile linter, capability auditor), chaos-engineering (experiment designer, blast-radius calculator, postmortem generator), ship-gate (pre-production 8-category audit with deploy-intent intercept), slo-architect (SLO designer, error-budget calculator with multi-window burn-rate alerts, SLO reviewer per Google SRE Workbook), and more.",
"description": "37 advanced engineering skills: agent designer, agent workflow designer, RAG architect, database designer + schema designer + SQL assistant, migration architect, observability designer, dependency auditor, changelog generator (with semantic version bumper and hotfix/rollback procedures), API design reviewer, API test suite builder, CI/CD pipeline builder, MCP server builder, skill security auditor, skill tester, performance profiler, focused-fix, browser-automation, full-page-screenshot, git-worktree-manager, monorepo-navigator, codebase-onboarding, interview-system-designer, runbook-generator, spec-driven-workflow, secrets-vault-manager, env-secrets-manager, pr-review-expert, self-eval, tc-tracker (task context tracker with lifecycle and handoff format), feature-flags-architect, kubernetes-operator, chaos-engineering, ship-gate (pre-production 8-category audit with deploy-intent intercept), slo-architect (SLO designer, error-budget calculator with multi-window burn-rate alerts, SLO reviewer per Google SRE Workbook), and tech-debt-tracker. Agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
@ -1448,6 +1448,227 @@
"transcriptapi"
],
"category": "marketing"
},
{
"name": "compliance-os",
"source": "./compliance-os",
"description": "Compliance OS — meta-orchestrator for multi-framework compliance programs spanning 9 frameworks (ISO 27001, ISO 13485, ISO 42001, ISO 14971, EU AI Act, MDR 745, GDPR, SOC 2, FDA QSR). Framework selector, cross-framework control mapper, audit simulator, and consolidated evidence-pool generator (stdlib Python), plus 3 cs-* compliance agents and 3 /cs:* readiness commands.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"compliance",
"iso-27001",
"iso-42001",
"eu-ai-act",
"gdpr",
"soc2",
"audit",
"evidence",
"framework-mapping"
],
"category": "compliance"
},
{
"name": "snowflake-development",
"source": "./engineering-team/snowflake-development",
"description": "Snowflake SQL, data pipelines (Dynamic Tables, Streams+Tasks), Cortex AI functions, Snowpark Python, and dbt integration. Includes query helper script, reference guides, and troubleshooting.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"snowflake",
"sql",
"data-pipelines",
"snowpark",
"dbt",
"cortex",
"data-warehouse"
],
"category": "development"
},
{
"name": "behuman",
"source": "./engineering/behuman",
"description": "Self-Mirror consciousness loop for human-like AI responses. Adds inner dialogue (Self → Mirror → Conscious Response) to make AI output feel authentic, not robotic. Zero dependencies — pure prompt technique.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"prompting",
"voice",
"authenticity",
"self-mirror",
"writing"
],
"category": "development"
},
{
"name": "claude-coach",
"source": "./engineering/claude-coach",
"description": "Personal Claude power-user coach. Delivers a personalized, ranked cheat-code glossary on first activation, then surfaces at most one tip per turn when it would genuinely improve the next attempt. Ships cheat-codes glossary, coaching-rules decision tree, three stdlib Python tools, cs-claude-coach agent, and /cs:claude-coach command.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"claude-code",
"coaching",
"power-user",
"tips",
"productivity"
],
"category": "development"
},
{
"name": "grill-with-docs",
"source": "./engineering/grill-with-docs",
"description": "Docs-anchored grilling session — interrogates a plan against the project's existing language (CONTEXT.md) and recorded decisions (docs/adr/), updating those files inline as terminology and decisions crystallise. Derived from Matt Pocock's MIT-licensed grill-with-docs with stdlib validators (CONTEXT.md linter, ADR scanner, glossary-code consistency), reference docs, cs-grill-with-docs agent, and /cs:grill-with-docs command.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"planning",
"adr",
"context",
"ubiquitous-language",
"interrogation",
"matt-pocock"
],
"category": "development"
},
{
"name": "llm-cost-optimizer",
"source": "./engineering/llm-cost-optimizer",
"description": "Cut LLM API spend via model routing, prompt caching, prompt compression, and per-feature cost observability. Use when AI costs are too high, choosing between models, or launching an AI feature without cost architecture. NOT for RAG design or prompt quality (separate skills).",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"llm",
"cost-optimization",
"token-usage",
"model-routing",
"prompt-caching",
"observability"
],
"category": "development"
},
{
"name": "prompt-governance",
"source": "./engineering/prompt-governance",
"description": "Manage prompts in production at scale: prompt versioning, A/B testing, prompt registries, regression prevention, and eval pipelines for production AI features. NOT for writing individual prompts, RAG design, or cost reduction (separate skills).",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"prompts",
"versioning",
"ab-testing",
"registry",
"evals",
"regression",
"production-ai"
],
"category": "development"
},
{
"name": "business-investment-advisor",
"source": "./finance/business-investment-advisor",
"description": "Business investment analysis and capital allocation advisor. Evaluates equipment, real estate, new-business, hiring, and technology investments with ROI, IRR, NPV, payback period, build-vs-buy, lease-vs-buy, and vendor evaluation frameworks for allocating limited budget.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"investment",
"capital-allocation",
"roi",
"irr",
"npv",
"build-vs-buy",
"finance"
],
"category": "finance"
},
{
"name": "video-content-strategist",
"source": "./marketing-skill/video-content-strategist",
"description": "Video content strategy: video scripts, YouTube channel optimization and SEO, short-form video pipelines (Reels, TikTok, Shorts), and repurposing long-form content into video. NOT for written blog content or caption-only social posts (separate skills).",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"video",
"youtube",
"short-form",
"scripts",
"content-strategy",
"tiktok",
"reels"
],
"category": "marketing"
},
{
"name": "compliance-team-eu-ai-act",
"source": "./ra-qm-team/compliance-team-eu-ai-act",
"description": "EU AI Act (Regulation (EU) 2024/1689) operational compliance specialist: AI system risk classifier (Articles 5/6/50 + Annex III), conformity assessment planner (Article 43 + Annex IV checklist), and obligation tracker (provider/deployer/importer/distributor + GPAI Articles 51-55). Article-level references and cross-framework mapping to ISO 42001, NIST AI RMF, GDPR. Stdlib-only.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"eu-ai-act",
"compliance",
"risk-classification",
"conformity-assessment",
"gpai",
"ai-regulation"
],
"category": "compliance"
},
{
"name": "compliance-team-iso42001",
"source": "./ra-qm-team/compliance-team-iso42001",
"description": "ISO/IEC 42001:2023 AI Management System (AIMS) specialist: AIMS gap analyzer (Clauses 4-10 coverage + remediation priority), AI risk register builder (Annex A 38 controls per ISO 23894), and AIMS audit scheduler (Clause 9.2 cadence + auditor independence). Cross-framework mapping to EU AI Act, NIST AI RMF, ISO 23894. Stdlib-only.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani"
},
"keywords": [
"iso-42001",
"aims",
"ai-governance",
"risk-register",
"internal-audit",
"compliance"
],
"category": "compliance"
},
{
"name": "collab-proof",
"source": "./engineering/collab-proof",
"description": "Assisted retrospective: after a session, calibrates what Claude contributed vs what the developer drove. LLM-assessed 4-frame analysis with explicit rubric, zero dependencies.",
"version": "1.0.0",
"author": {
"name": "dong7812",
"url": "https://github.com/dong7812"
},
"keywords": [
"ai-collaboration",
"session-retrospective",
"git-analysis",
"decision-logging",
"collab-proof"
],
"category": "engineering"
}
]
}

224
.codex/skills-index.json
View file

@ -3,13 +3,13 @@
"name": "claude-code-skills",
"description": "Production-ready skill packages for AI agents - Marketing, Engineering, Product, C-Level, PM, and RA/QM",
"repository": "https://github.com/alirezarezvani/claude-skills",
"total_skills": 346,
"total_skills": 344,
"skills": [
{
"name": "business-growth-skills",
"source": "../../business-growth/skills/business-growth-skills",
"category": "business-growth",
"description": "4 business growth agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Customer success (health scoring, churn), sales engineer (RFP), revenue operations (pipeline, GTM), contract & proposal writer. Python tools (stdlib-only)."
"description": "Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP')."
},
{
"name": "contract-and-proposal-writer",
@ -51,13 +51,13 @@
"name": "internal-comms",
"source": "../../business-operations/skills/internal-comms",
"category": "business-operations",
"description": "Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication \u2014 a re-org announcement, a tool rollout, a policy change, a benefit change, a leadership transition, a layoff, an acquisition close, or an internal product launch \u2014 and the audience is employees (not customers). Triggers on \"all-hands announcement\", \"town-hall script\", \"change comms\", \"internal newsletter\", \"rollout comms\", \"policy change announcement\", \"re-org announcement\", \"internal FAQ\", \"manager talking points\", \"Prosci ADKAR\", \"Kotter 8-step\", \"layoff comms\", \"RIF comms\", \"internal memo\". Pairs Prosci ADKAR (Awareness / Desire / Knowledge / Ability / Reinforcement) and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points. Industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Distinct from marketing-skill/* (external/customer-facing), c-level-advisor/internal-narrative (strategic framing, not tactical drafts), and c-level-advisor/change-management (executive change strategy, not the comms package itself)."
"description": "Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication \u2014 a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch \u2014 and the audience is employees (not customers). Pairs Prosci ADKAR and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points; industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Triggers on \"all-hands announcement\", \"change comms\", \"rollout comms\", \"re-org announcement\", \"manager talking points\", \"layoff comms\"."
},
{
"name": "knowledge-ops",
"source": "../../business-operations/skills/knowledge-ops",
"category": "business-operations",
"description": "Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding, expense reimbursement, system-access provisioning, customer-escalation playbook) \u2014 including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, ops onboarding doc generation, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Kaoru Ishikawa's 5W2H method, Atul Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4 Service Operation, FDA 21 CFR Part 211, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists. Distinct from `engineering/llm-wiki` (Karpathy-style personal PKM second brain), `engineering-team/runbook-generator` (system-ops production debugging runbook), `project-management/*` (Jira/Confluence delivery + ticket tracking), and sibling `business-operations/process-mapper` (BPMN process *design*, while knowledge-ops is process *documentation*)."
"description": "Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding) \u2014 including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Ishikawa's 5W2H method, Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists (e.g., \"validate this runbook before it goes into rotation\", \"audit our Confluence wiki for stale and orphaned SOPs\")."
},
{
"name": "process-mapper",
@ -69,13 +69,13 @@
"name": "procurement-optimizer",
"source": "../../business-operations/skills/procurement-optimizer",
"category": "business-operations",
"description": "Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base \u2014 when the user needs to do a spend audit, spend categorization (UNSPSC-aligned), purchasing-cycle analysis, or risk-balanced supplier consolidation. Triggers on \"spend audit\", \"SaaS audit\", \"spend categorization\", \"supplier rationalization\", \"supplier consolidation\", \"purchasing cycle\", \"procurement review\", \"category strategy\", \"duplicate SaaS\", \"renewal cluster\". Ships 3 stdlib-only Python tools (UNSPSC-aligned spend categorizer with Pareto breakdown and industry profiles, purchasing-cycle analyzer that surfaces bottleneck categories per Goldratt's Theory of Constraints, supplier-consolidation planner that refuses single-source recommendations for tier-1 categories without a documented break-glass plan), 3 reference docs each citing 7+ authoritative sources (A.T. Kearney / Hackett / Spend Matters / UNSPSC / Productiv / Vendr / Tropic / IACCM / ISM / BCG), and a 20-minute spend-intake template. Distinct from sibling vendor-management (performance scoring of vendors you keep paying), finance/financial-analysis (close + report, not category strategy), and c-level-advisor/general-counsel-advisor (contract law, not category rationalization)."
"description": "Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base \u2014 when the user needs a spend audit, spend categorization (UNSPSC-aligned with Pareto breakdown and industry profiles), purchasing-cycle analysis (bottleneck categories per Goldratt's Theory of Constraints), or risk-balanced supplier consolidation that refuses single-source recommendations for tier-1 categories without a documented break-glass plan. Triggers on \"spend audit\", \"SaaS audit\", \"spend categorization\", \"supplier rationalization\", \"supplier consolidation\", \"category strategy\", \"duplicate SaaS\", \"renewal cluster\"."
},
{
"name": "vendor-management",
"source": "../../business-operations/skills/vendor-management",
"category": "business-operations",
"description": "Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships \u2014 running a vendor scorecard, tracking SLA compliance, classifying third-party risk, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Triggers on \"vendor SLA\", \"vendor scorecard\", \"third-party risk\", \"TPRM\", \"vendor review\", \"SaaS audit\", \"supplier performance\", \"vendor health check\", \"renewal review\". Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Ships 3 stdlib-only Python tools (vendor scorer with industry tuning, SLA compliance tracker with credit-claim flags, vendor risk classifier across 4 risk vectors), 3 reference docs each citing 7+ authoritative sources (Gartner / Shared Assessments / NIST / ISO 27036 / breach post-mortems), and a 5-vendor catalog template. Distinct from c-level-advisor/general-counsel-advisor (contract law, not operational management), business-growth/contract-and-proposal-writer (outbound proposals, not inbound vendor scoring), and sibling procurement-optimizer (spend categorization, not vendor performance)."
"description": "Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships \u2014 running a vendor scorecard with industry tuning, tracking SLA compliance with credit-claim flags, classifying third-party risk across 4 risk vectors, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Triggers on \"vendor SLA\", \"vendor scorecard\", \"third-party risk\", \"TPRM\", \"vendor review\", \"supplier performance\", \"vendor health check\", \"renewal review\"."
},
{
"name": "agent-protocol",
@ -93,7 +93,7 @@
"name": "board-meeting",
"source": "../../c-level-advisor/skills/board-meeting",
"category": "c-level",
"description": "Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question."
"description": "Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question."
},
{
"name": "board-prep",
@ -105,43 +105,43 @@
"name": "boardroom",
"source": "../../c-level-advisor/c-level-agents/skills/boardroom",
"category": "c-level",
"description": "/cs:boardroom <brief> \u2014 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo."
"description": "/cs:boardroom <brief> \u2014 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains \u2014 e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call."
},
{
"name": "brief",
"source": "../../c-level-advisor/c-level-agents/skills/brief",
"category": "c-level",
"description": "/cs:brief <topic> \u2014 Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline."
"description": "/cs:brief <topic> \u2014 Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline. Use when a strategic question needs to be framed before boardroom deliberation \u2014 e.g. locking options, assumptions, and success criteria for a pricing change or a market-entry decision."
},
{
"name": "c-level-agents",
"source": "../../c-level-advisor/c-level-agents/skills/c-level-agents",
"category": "c-level",
"description": "Founder-mode executive team. 8 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff) and 17 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions."
"description": "Founder-mode executive team. 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, GC, CDO, CAIO, CCO, VPE, Chief of Staff) and 21 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions."
},
{
"name": "c-level-skills",
"source": "../../c-level-advisor/skills/c-level-skills",
"category": "c-level",
"description": "10 C-level advisory agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor. Multi-role board meetings, strategy routing, structured recommendations. For founders needing executive-level decision support."
"description": "Index and router for the C-level advisory bundle: 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture. Use when exploring what the c-level-advisor bundle contains, deciding which advisor skill fits a question, or finding the entry points (cs-onboard interview, chief-of-staff routing, board-meeting protocol)."
},
{
"name": "caio-review",
"source": "../../c-level-advisor/c-level-agents/skills/caio-review",
"category": "c-level",
"description": "/cs:caio-review <plan> \u2014 Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring."
"description": "/cs:caio-review <plan> \u2014 Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring. Use when shipping an AI feature without an eval set, choosing between API, fine-tune, and self-hosted, or classifying a use case under the EU AI Act."
},
{
"name": "cco-review",
"source": "../../c-level-advisor/c-level-agents/skills/cco-review",
"category": "c-level",
"description": "/cs:cco-review <plan> \u2014 Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring."
"description": "/cs:cco-review <plan> \u2014 Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire."
},
{
"name": "cdo-review",
"source": "../../c-level-advisor/c-level-agents/skills/cdo-review",
"category": "c-level",
"description": "/cs:cdo-review <plan> \u2014 Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring."
"description": "/cs:cdo-review <plan> \u2014 Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring. Use when validating training-data rights before model work, choosing warehouse vs lakehouse vs mesh, or valuing data assets for productization or M&A."
},
{
"name": "ceo-advisor",
@ -159,7 +159,7 @@
"name": "cfo-review",
"source": "../../c-level-advisor/c-level-agents/skills/cfo-review",
"category": "c-level",
"description": "/cs:cfo-review <plan> \u2014 Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation."
"description": "/cs:cfo-review <plan> \u2014 Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation. Use when a plan commits meaningful spend \u2014 e.g. a hiring wave, a fundraise decision, or a new channel budget."
},
{
"name": "challenge",
@ -213,7 +213,7 @@
"name": "chief-of-staff",
"source": "../../c-level-advisor/skills/chief-of-staff",
"category": "c-level",
"description": "C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically."
"description": "C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor \u2014 e.g. 'should we raise now or cut burn?' \u2014 or when a multi-domain decision needs a board meeting convened."
},
{
"name": "chro-advisor",
@ -231,7 +231,7 @@
"name": "ciso-review",
"source": "../../c-level-advisor/c-level-agents/skills/ciso-review",
"category": "c-level",
"description": "/cs:ciso-review <plan> \u2014 Risk-paranoid interrogation of any plan that touches data, compliance, or production access."
"description": "/cs:ciso-review <plan> \u2014 Risk-paranoid interrogation of any plan that touches data, compliance, or production access. Use when launching features that handle customer data, before a SOC 2 / ISO audit, or after any incident or near-miss."
},
{
"name": "cmo-advisor",
@ -243,7 +243,7 @@
"name": "cmo-review",
"source": "../../c-level-advisor/c-level-agents/skills/cmo-review",
"category": "c-level",
"description": "/cs:cmo-review <plan> \u2014 Narrative-first interrogation of positioning, ICP, message house, and channel mix."
"description": "/cs:cmo-review <plan> \u2014 Narrative-first interrogation of positioning, ICP, message house, and channel mix. Use when launching a campaign or repositioning, or when CAC is rising and the one-sentence positioning test fails."
},
{
"name": "company-os",
@ -261,7 +261,7 @@
"name": "context-engine",
"source": "../../c-level-advisor/skills/context-engine",
"category": "c-level",
"description": "Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy/anonymization rules before external API calls."
"description": "Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy/anonymization rules before external API calls. Use when starting any C-suite advisor session, when context looks stale or missing, or before sending company data to an external service."
},
{
"name": "coo-advisor",
@ -279,7 +279,7 @@
"name": "cpo-review",
"source": "../../c-level-advisor/c-level-agents/skills/cpo-review",
"category": "c-level",
"description": "/cs:cpo-review <plan> \u2014 JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus."
"description": "/cs:cpo-review <plan> \u2014 JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus. Use when committing a quarter's roadmap, deciding whether to kill a feature, or claiming PMF without a retention curve."
},
{
"name": "cro-advisor",
@ -291,19 +291,19 @@
"name": "cro-review",
"source": "../../c-level-advisor/c-level-agents/skills/cro-review",
"category": "c-level",
"description": "/cs:cro-review <plan> \u2014 Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time."
"description": "/cs:cro-review <plan> \u2014 Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time. Use when the forecast misses pipeline coverage, win rates drop, or before scaling the sales team."
},
{
"name": "cross-eval",
"source": "../../c-level-advisor/c-level-agents/skills/cross-eval",
"category": "c-level",
"description": "/cs:cross-eval <memo> \u2014 Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation."
"description": "/cs:cross-eval <memo> \u2014 Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation. Use when a high-stakes memo needs an independent sanity check before the boardroom \u2014 e.g. a bet-the-company pivot or fundraise terms."
},
{
"name": "cs-onboard",
"source": "../../c-level-advisor/skills/cs-onboard",
"category": "c-level",
"description": "Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills."
"description": "Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old \u2014 e.g. after a fundraise or pivot."
},
{
"name": "cto-advisor",
@ -315,7 +315,7 @@
"name": "cto-review",
"source": "../../c-level-advisor/c-level-agents/skills/cto-review",
"category": "c-level",
"description": "/cs:cto-review <plan> \u2014 Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy."
"description": "/cs:cto-review <plan> \u2014 Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy. Use when committing to an architecture, planning for 10x load, or weighing a rebuild against a vendor."
},
{
"name": "culture-architect",
@ -327,7 +327,7 @@
"name": "decide",
"source": "../../c-level-advisor/c-level-agents/skills/decide",
"category": "c-level",
"description": "/cs:decide <memo> \u2014 Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference."
"description": "/cs:decide <memo> \u2014 Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference. Use when the founder has approved a boardroom memo and the decision must become durable company memory \u2014 e.g. right after /cs:boardroom concludes."
},
{
"name": "decision-logger",
@ -339,7 +339,7 @@
"name": "execute",
"source": "../../c-level-advisor/c-level-agents/skills/execute",
"category": "c-level",
"description": "/cs:execute <decision> \u2014 Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision."
"description": "/cs:execute <decision> \u2014 Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision. Use when a logged decision needs to become an operating plan \u2014 e.g. turning an approved market-entry call into weekly milestones with DRIs."
},
{
"name": "executive-mentor",
@ -357,19 +357,19 @@
"name": "founder-mode",
"source": "../../c-level-advisor/c-level-agents/skills/founder-mode",
"category": "c-level",
"description": "/cs:founder-mode <question> \u2014 Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point."
"description": "/cs:founder-mode <question> \u2014 Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits \u2014 e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO."
},
{
"name": "freeze",
"source": "../../c-level-advisor/c-level-agents/skills/freeze",
"category": "c-level",
"description": "/cs:freeze <decision> <days> \u2014 Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer."
"description": "/cs:freeze <decision> <days> \u2014 Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. Use when an irreversible decision was made under pressure \u2014 e.g. a layoff plan or multi-year contract \u2014 and deserves a cooling-off lock before execution."
},
{
"name": "gc-review",
"source": "../../c-level-advisor/c-level-agents/skills/gc-review",
"category": "c-level",
"description": "/cs:gc-review <plan> \u2014 General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface."
"description": "/cs:gc-review <plan> \u2014 General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface. Use when reviewing a term sheet before signing, redlining a customer MSA, or checking IP assignment and regulatory exposure on a new product."
},
{
"name": "general-counsel-advisor",
@ -387,7 +387,7 @@
"name": "hard-call",
"source": "../../c-level-advisor/executive-mentor/skills/hard-call",
"category": "c-level",
"description": "/em -hard-call \u2014 Framework for Decisions With No Good Options"
"description": "/em:hard-call \u2014 Framework for decisions with no good options. Use when every option is painful and a structured 10/10/10 + regret-minimization pass is needed \u2014 e.g. choosing between a layoff and a down round, or killing a beloved product line."
},
{
"name": "internal-narrative",
@ -411,13 +411,13 @@
"name": "office-hours",
"source": "../../c-level-advisor/c-level-agents/skills/office-hours",
"category": "c-level",
"description": "/cs:office-hours <topic> \u2014 YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit."
"description": "/cs:office-hours <topic> \u2014 YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit. Use when a founder question is too vague to route \u2014 e.g. 'should we grow faster?' \u2014 or before drafting a strategy brief."
},
{
"name": "onboard",
"source": "../../c-level-advisor/c-level-agents/skills/onboard",
"category": "c-level",
"description": "/cs:onboard \u2014 Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents."
"description": "/cs:onboard \u2014 Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents. Use when setting up the virtual C-suite for a new company, or when advisors lack company context \u2014 e.g. before a first /cs:boardroom or after a fundraise changes the numbers."
},
{
"name": "org-health-diagnostic",
@ -429,13 +429,13 @@
"name": "post-mortem",
"source": "../../c-level-advisor/c-level-agents/skills/post-mortem",
"category": "c-level",
"description": "/cs:post-mortem <decision> \u2014 Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop."
"description": "/cs:post-mortem <decision> \u2014 Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger \u2014 e.g. scoring last quarter's pricing change against its pre-committed success metrics."
},
{
"name": "postmortem",
"source": "../../c-level-advisor/executive-mentor/skills/postmortem",
"category": "c-level",
"description": "/em -postmortem \u2014 Honest Analysis of What Went Wrong"
"description": "/em:postmortem \u2014 Honest analysis of what went wrong. Use after a failed launch, missed quarter, or bad hire to run a blameless 5-Whys retrospective with a change register \u2014 e.g. dissecting why the Q3 release slipped six weeks."
},
{
"name": "scenario-war-room",
@ -453,7 +453,7 @@
"name": "stress-test",
"source": "../../c-level-advisor/executive-mentor/skills/stress-test",
"category": "c-level",
"description": "/em -stress-test \u2014 Business Assumption Stress Testing"
"description": "/em:stress-test \u2014 Business assumption stress testing. Use before betting on a plan whose core assumptions are unvalidated \u2014 e.g. stress-testing 'enterprise buyers will tolerate a 6-month pilot' or a hockey-stick revenue model."
},
{
"name": "vpe-advisor",
@ -471,13 +471,13 @@
"name": "vpe-review",
"source": "../../c-level-advisor/c-level-agents/skills/vpe-review",
"category": "c-level",
"description": "/cs:vpe-review <plan> \u2014 Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline."
"description": "/cs:vpe-review <plan> \u2014 Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline. Use when cycle time balloons, DORA metrics slide, or before committing to an eng hiring wave or a reorg."
},
{
"name": "channel-economics",
"source": "../../commercial/skills/channel-economics",
"category": "commercial",
"description": "Use when reviewing or rebalancing direct vs. partner-led channel economics \u2014 computing fully-loaded cost-to-serve per channel, channel ROI with cash / LTV / marginal lenses, and optimal channel mix subject to constraints. For Head of Commercial, RevOps, and VP Sales doing quarterly channel review when pipeline is mixed (e.g., 60% direct + 40% partner-led) and nobody actually knows which channel makes money after CAC, support load, partner discount, deal-velocity differences, retention differential, and overhead allocation are all loaded in. Outputs cost to serve, channel ROI verdicts (DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection. Not channel structure (that's partnerships-architect \u2014 tiers, joint GTM, revshare). Not RevOps process (that's business-growth/revenue-operations \u2014 lead routing, SDR motion). Not strategic CRO judgment (that's c-level-advisor/cro-advisor \u2014 comp plans, when-to-hire-a-VP-Sales). Not historical close-and-report (that's finance/financial-analysis). This skill answers: direct vs partner profitability, channel profitability, channel mix, channel economics."
"description": "Use when reviewing or rebalancing direct vs. partner-led channel economics \u2014 computing fully-loaded cost-to-serve per channel, channel ROI with cash / LTV / marginal lenses, and optimal channel mix subject to constraints. For Head of Commercial, RevOps, and VP Sales doing quarterly channel review when pipeline is mixed (e.g., 60% direct + 40% partner-led) and nobody actually knows which channel makes money after CAC, support load, partner discount, deal-velocity differences, retention differential, and overhead allocation are all loaded in. Outputs cost to serve, channel ROI verdicts (DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection (e.g., 'which channel actually makes money \u2014 direct or partner?')."
},
{
"name": "commercial-forecaster",
@ -669,7 +669,7 @@
"name": "engineering-skills",
"source": "../../engineering-team/skills/engineering-skills",
"category": "engineering",
"description": "23 engineering agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365. 30+ Python tools (stdlib-only)."
"description": "Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills \u2014 load only the one specialist SKILL.md you need, never bulk-load the bundle."
},
{
"name": "epic-design",
@ -681,7 +681,7 @@
"name": "extract",
"source": "../../engineering-team/self-improving-agent/skills/extract",
"category": "engineering",
"description": "Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples."
"description": "Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples. Use when the user runs /si:extract or asks to package a recurring solution from memory into a skill."
},
{
"name": "fix",
@ -705,7 +705,7 @@
"name": "google-workspace-cli",
"source": "../../engineering-team/google-workspace-cli/skills/google-workspace-cli",
"category": "engineering",
"description": "Google Workspace administration via the gws CLI. Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. Run security audits, execute 43 built-in recipes, and use 10 persona bundles. Use for Google Workspace admin, gws CLI setup, Gmail automation, Drive management, or Calendar scheduling."
"description": "Google Workspace administration via the gws CLI (github.com/googleworkspace/cli). Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. Run security audits and use local recipe templates and persona bundles. Use for Google Workspace admin, gws CLI setup, Gmail automation, Drive management, or Calendar scheduling."
},
{
"name": "incident-commander",
@ -741,7 +741,7 @@
"name": "promote",
"source": "../../engineering-team/self-improving-agent/skills/promote",
"category": "engineering",
"description": "Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude/rules/ for permanent enforcement."
"description": "Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude/rules/ for permanent enforcement. Use when the user runs /si:promote or asks to make a learned behavior permanent."
},
{
"name": "pw",
@ -767,18 +767,18 @@
"category": "engineering",
"description": ">-"
},
{
"name": "review",
"source": "../../engineering-team/self-improving-agent/skills/review",
"category": "engineering",
"description": "Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics."
},
{
"name": "review",
"source": "../../engineering-team/playwright-pro/skills/review",
"category": "engineering",
"description": ">-"
},
{
"name": "review",
"source": "../../engineering-team/self-improving-agent/skills/review",
"category": "engineering",
"description": "Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs /si:review or asks what has been learned and what should be promoted or pruned."
},
{
"name": "security-pen-testing",
"source": "../../engineering-team/skills/security-pen-testing",
@ -849,7 +849,7 @@
"name": "senior-prompt-engineer",
"source": "../../engineering-team/skills/senior-prompt-engineer",
"category": "engineering",
"description": "This skill should be used when the user asks to \"optimize prompts\", \"design prompt templates\", \"evaluate LLM outputs\", \"build agentic systems\", \"implement RAG\", \"create few-shot examples\", \"analyze token usage\", or \"design AI workflows\". Use for prompt engineering patterns, LLM evaluation frameworks, agent architectures, and structured output design."
"description": "Use when the user asks to optimize prompts, design prompt templates, evaluate LLM outputs with an eval set, measure RAG retrieval quality, validate agent/tool configurations, analyze token usage, or design structured-output contracts. Covers eval-driven prompt iteration, RAG metrics (relevance, faithfulness, coverage), agent workflow validation, and token/cost budgeting \u2014 all model-agnostic, with three stdlib Python tools."
},
{
"name": "senior-qa",
@ -867,7 +867,7 @@
"name": "senior-security",
"source": "../../engineering-team/skills/senior-security",
"category": "engineering",
"description": "Security engineering toolkit for threat modeling, vulnerability analysis, secure architecture, and penetration testing. Includes STRIDE analysis, OWASP guidance, cryptography patterns, and security scanning tools. Use when the user asks about security reviews, threat analysis, vulnerability assessments, secure coding practices, security audits, attack surface analysis, CVE remediation, or security best practices."
"description": "Use when the user asks for STRIDE threat modeling, DREAD risk scoring, data-flow-diagram threat analysis, or a quick secret scan \u2014 or when a security request needs routing to the right specialist skill (pen-testing, incident response, cloud posture, red team, AI security, threat hunting, secure code review). This skill owns threat modeling; everything else routes to a sibling."
},
{
"name": "snowflake-development",
@ -879,7 +879,7 @@
"name": "status",
"source": "../../engineering-team/self-improving-agent/skills/status",
"category": "engineering",
"description": "Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations."
"description": "Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations. Use when the user runs /si:status or asks how full or healthy the agent memory is."
},
{
"name": "stripe-integration-expert",
@ -915,7 +915,7 @@
"name": "agent-designer",
"source": "../../engineering/skills/agent-designer",
"category": "engineering-advanced",
"description": "Use when the user asks to design multi-agent systems, create agent architectures, define agent communication patterns, or build autonomous agent workflows."
"description": "Use when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer)."
},
{
"name": "agent-workflow-designer",
@ -957,7 +957,7 @@
"name": "board",
"source": "../../engineering/agenthub/skills/board",
"category": "engineering-advanced",
"description": "Read, write, and browse the AgentHub message board for agent coordination."
"description": "Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents."
},
{
"name": "browser-automation",
@ -975,7 +975,7 @@
"name": "changelog-generator",
"source": "../../engineering/skills/changelog-generator",
"category": "engineering-advanced",
"description": "Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, or automating release notes in CI."
"description": "Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix process'."
},
{
"name": "chaos-engineering",
@ -1014,16 +1014,16 @@
"description": "Analyze a codebase and generate onboarding documentation for engineers, tech leads, and contractors. Fast fact-gathering and repeatable onboarding outputs. Use when onboarding a new engineer, writing architecture-overview docs for a new project, or producing tech-lead briefings for unfamiliar repos."
},
{
"name": "command-guide",
"source": "../../engineering/skills/command-guide",
"name": "collab-proof",
"source": "../../engineering/collab-proof/skills/collab-proof",
"category": "engineering-advanced",
"description": ">"
"description": "Use when you want to understand what Claude contributed vs what you drove in a session. Triggers on: /collab-proof, session retrospective, ai contribution analysis, collaboration evidence, what did claude do."
},
{
"name": "data-quality-auditor",
"source": "../../engineering/data-quality-auditor/skills/data-quality-auditor",
"category": "engineering-advanced",
"description": "Audit datasets for completeness, consistency, accuracy, and validity. Profile data distributions, detect anomalies and outliers, surface structural issues, and produce an actionable remediation plan."
"description": "Audit datasets for completeness, consistency, accuracy, and validity. Profile data distributions, detect anomalies and outliers, surface structural issues, and produce an actionable remediation plan. Use when the user asks to check data quality, profile a dataset, hunt outliers or missing values, or validate data before analysis or model training."
},
{
"name": "database-designer",
@ -1047,7 +1047,7 @@
"name": "dependency-auditor",
"source": "../../engineering/skills/dependency-auditor",
"category": "engineering-advanced",
"description": "Audit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review."
"description": "Audit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review. Examples: 'audit our npm dependencies', 'do we have GPL contamination', 'plan the upgrade to React 19'."
},
{
"name": "docker-development",
@ -1059,7 +1059,7 @@
"name": "engineering-advanced-skills",
"source": "../../engineering/skills/engineering-advanced-skills",
"category": "engineering-advanced",
"description": "25 advanced engineering agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, release management, platform ops."
"description": "Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Use when browsing or choosing among the POWERFUL-tier engineering skills: agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, changelog/release automation, reliability (SLO/chaos/flags/operators), platform ops."
},
{
"name": "env-secrets-manager",
@ -1071,7 +1071,7 @@
"name": "eval",
"source": "../../engineering/agenthub/skills/eval",
"category": "engineering-advanced",
"description": "Evaluate and rank agent results by metric or LLM judge for an AgentHub session."
"description": "Evaluate and rank agent results by metric or LLM judge for an AgentHub session. Use when the user runs /hub:eval or asks to score, compare, or pick a winner among completed AgentHub agents."
},
{
"name": "feature-flags-architect",
@ -1131,7 +1131,7 @@
"name": "init",
"source": "../../engineering/agenthub/skills/init",
"category": "engineering-advanced",
"description": "Create a new AgentHub collaboration session with task, agent count, and evaluation criteria."
"description": "Create a new AgentHub collaboration session with task, agent count, and evaluation criteria. Use when the user runs /hub:init or asks to start a multi-agent competition on a task."
},
{
"name": "interview-system-designer",
@ -1173,7 +1173,7 @@
"name": "loop",
"source": "../../engineering/autoresearch-agent/skills/loop",
"category": "engineering-advanced",
"description": "Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling."
"description": "Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule."
},
{
"name": "mcp-server-builder",
@ -1185,7 +1185,7 @@
"name": "merge",
"source": "../../engineering/agenthub/skills/merge",
"category": "engineering-advanced",
"description": "Merge the winning agent's branch into base, archive losers, and clean up worktrees."
"description": "Merge the winning agent's branch into base, archive losers, and clean up worktrees. Use when the user runs /hub:merge or asks to land the winning AgentHub result and tidy the session."
},
{
"name": "migration-architect",
@ -1227,31 +1227,25 @@
"name": "rag-architect",
"source": "../../engineering/skills/rag-architect",
"category": "engineering-advanced",
"description": "Use when the user asks to design RAG pipelines, optimize retrieval strategies, choose embedding models, implement vector search, or build knowledge retrieval systems."
},
{
"name": "release-manager",
"source": "../../engineering/skills/release-manager",
"category": "engineering-advanced",
"description": "Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning."
"description": "Use when the user asks to design a RAG pipeline, choose a chunking strategy or embedding model, pick a vector database, or evaluate retrieval quality (precision@k, recall@k, NDCG). Examples: 'design a RAG system for our docs', 'what chunk size should I use for this corpus', 'evaluate my retriever against ground truth'. NOT for general LLM cost tuning (use llm-cost-optimizer) or agent loops over retrieval (use agenthub)."
},
{
"name": "resume",
"source": "../../engineering/autoresearch-agent/skills/resume",
"category": "engineering-advanced",
"description": "Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating."
"description": "Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:resume or asks to pick up a previously started autoresearch experiment."
},
{
"name": "run",
"source": "../../engineering/agenthub/skills/run",
"category": "engineering-advanced",
"description": "One-shot lifecycle command that chains init \u2192 baseline \u2192 spawn \u2192 eval \u2192 merge in a single invocation."
"description": "One-shot lifecycle command that chains init \u2192 baseline \u2192 spawn \u2192 eval \u2192 merge in a single invocation. Use when the user runs /hub:run or asks to execute a full AgentHub competition end-to-end."
},
{
"name": "run",
"source": "../../engineering/autoresearch-agent/skills/run",
"category": "engineering-advanced",
"description": "Run a single experiment iteration. Edit the target file, evaluate, keep or discard."
"description": "Run a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration."
},
{
"name": "runbook-generator",
@ -1281,7 +1275,7 @@
"name": "setup",
"source": "../../engineering/autoresearch-agent/skills/setup",
"category": "engineering-advanced",
"description": "Set up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator."
"description": "Set up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop."
},
{
"name": "ship-gate",
@ -1317,7 +1311,7 @@
"name": "spawn",
"source": "../../engineering/agenthub/skills/spawn",
"category": "engineering-advanced",
"description": "Launch N parallel subagents in isolated git worktrees to compete on the session task."
"description": "Launch N parallel subagents in isolated git worktrees to compete on the session task. Use when the user runs /hub:spawn or asks to start the competing agents for an initialized AgentHub session."
},
{
"name": "spec-driven-workflow",
@ -1341,13 +1335,13 @@
"name": "status",
"source": "../../engineering/agenthub/skills/status",
"category": "engineering-advanced",
"description": "Show DAG state, agent progress, and branch status for an AgentHub session."
"description": "Show DAG state, agent progress, and branch status for an AgentHub session. Use when the user runs /hub:status or asks how the AgentHub agents are doing."
},
{
"name": "status",
"source": "../../engineering/autoresearch-agent/skills/status",
"category": "engineering-advanced",
"description": "Show experiment dashboard with results, active loops, and progress."
"description": "Show experiment dashboard with results, active loops, and progress. Use when the user runs /ar:status or asks how an autoresearch experiment is going."
},
{
"name": "tc-tracker",
@ -1369,7 +1363,7 @@
},
{
"name": "universal-scraping-architect",
"source": "../../engineering/universal-scraping-architect",
"source": "../../engineering/universal-scraping-architect/skills/universal-scraping-architect",
"category": "engineering-advanced",
"description": "Use for web scraping, crawling, document extraction, API parsing, or building validation-heavy data pipelines using Firecrawl or local Python scripts."
},
@ -1395,7 +1389,7 @@
"name": "finance-skills",
"source": "../../finance/skills/finance-skills",
"category": "finance",
"description": "Financial analyst agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Ratio analysis, DCF valuation, budget variance, rolling forecasts. 4 Python tools (stdlib-only)."
"description": "Router/index for the 2 finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts) and saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics')."
},
{
"name": "financial-analyst",
@ -1427,12 +1421,6 @@
"category": "marketing",
"description": "Answer Engine Optimization (AEO) skill \u2014 optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO \u2014 AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers \u2014 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools."
},
{
"name": "ai-seo",
"source": "../../marketing-skill/skills/ai-seo",
"category": "marketing",
"description": "Optimize content to get cited by AI search engines \u2014 ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Copilot. Use when you want your content to appear in AI-generated answers, not just ranked in blue links. Triggers: 'optimize for AI search', 'get cited by ChatGPT', 'AI Overviews', 'Perplexity citations', 'AI SEO', 'generative search', 'LLM visibility', 'GEO' (generative engine optimization). NOT for traditional SEO ranking (use seo-audit). NOT for content creation (use content-production)."
},
{
"name": "analytics-tracking",
"source": "../../marketing-skill/skills/analytics-tracking",
@ -1551,7 +1539,7 @@
"name": "marketing-demand-acquisition",
"source": "../../marketing-skill/skills/marketing-demand-acquisition",
"category": "marketing",
"description": "Creates demand generation campaigns, optimizes paid ad spend across LinkedIn, Google, and Meta, develops SEO strategies, and structures partnership programs for Series A+ startups scaling internationally. Use when planning marketing strategy, growth marketing, advertising campaigns, PPC optimization, lead generation, pipeline generation, or startup marketing budgets. Covers multi-channel acquisition (Google Ads, LinkedIn Ads, Meta Ads), CAC analysis, MQL/SQL workflows, attribution modeling, technical SEO, and co-marketing partnerships for hybrid PLG/Sales-Led motions in EU/US/Canada markets."
"description": "Creates demand generation campaigns, optimizes paid ad spend across LinkedIn, Google, and Meta, develops SEO strategies, and structures partnership programs. Use when planning demand gen strategy, growth marketing, advertising campaigns, PPC optimization, lead generation, pipeline generation, or marketing budgets. Covers multi-channel acquisition (Google Ads, LinkedIn Ads, Meta Ads), CAC analysis, MQL/SQL workflows, attribution modeling, technical SEO, and co-marketing partnerships. Default calibration profile is a Series A+ B2B SaaS scaling internationally (EU/US/Canada, hybrid PLG/Sales-Led) \u2014 adapt benchmarks for other stages and motions rather than skipping the skill."
},
{
"name": "marketing-ideas",
@ -1575,7 +1563,7 @@
"name": "marketing-skills",
"source": "../../marketing-skill/skills/marketing-skills",
"category": "marketing",
"description": "42 marketing agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more coding agents. 7 pods: content, SEO, CRO, channels, growth, intelligence, sales. Foundation context + orchestration router. 27 Python tools (stdlib-only)."
"description": "Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill \u2014 it does not execute marketing work itself."
},
{
"name": "marketing-strategy-pmm",
@ -1629,7 +1617,7 @@
"name": "prompt-engineer-toolkit",
"source": "../../marketing-skill/skills/prompt-engineer-toolkit",
"category": "marketing",
"description": "Analyzes and rewrites prompts for better AI output, creates reusable prompt templates for marketing use cases (ad copy, email campaigns, social media), and structures end-to-end AI content workflows. Use when the user wants to improve prompts for AI-assisted marketing, build prompt templates, or optimize AI content workflows. Also use when the user mentions 'prompt engineering,' 'improve my prompts,' 'AI writing quality,' 'prompt templates,' or 'AI content workflow.'"
"description": "Turns marketing prompts into tested, versioned production assets: A/B prompt evaluation against structured test cases, immutable prompt version history with diffs, ready-to-use marketing prompt templates (ad copy, email campaigns, social posts, landing pages, SEO meta), and an LLM-governance playbook for marketing teams (claim discipline, disclosure rules, human-review gates). Use when a marketing team relies on AI-generated content and needs prompt quality to be measurable and safe \u2014 or when the user mentions 'prompt engineering,' 'improve my prompts,' 'prompt templates,' 'prompt versioning,' 'AI content workflow,' or 'AI governance for marketing.'"
},
{
"name": "referral-program",
@ -1671,7 +1659,7 @@
"name": "social-media-analyzer",
"source": "../../marketing-skill/skills/social-media-analyzer",
"category": "marketing",
"description": "Social media campaign analysis and performance tracking. Calculates engagement rates, ROI, and benchmarks across platforms. Use for analyzing social media performance, calculating engagement rate, measuring campaign ROI, comparing platform metrics, or benchmarking against industry standards."
"description": "Social media campaign analysis and performance tracking. Calculates engagement rates, ROI, and benchmarks across platforms. Use when analyzing social media performance, calculating engagement rate, measuring campaign ROI, comparing platform metrics, or benchmarking against industry standards. Also use when the user mentions \"social media audit,\" \"engagement rate,\" or \"which platform performs best.\""
},
{
"name": "social-media-manager",
@ -1707,19 +1695,19 @@
"name": "agile-product-owner",
"source": "../../product-team/agile-product-owner/skills/agile-product-owner",
"category": "product",
"description": "Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog."
"description": "Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog."
},
{
"name": "apple-hig-expert",
"source": "../../product-team/apple-hig-expert/skills/apple-hig-expert",
"category": "product",
"description": "Expert guidance on Apple Human Interface Guidelines (HIG). Covers iOS, macOS, and visionOS with 2026 Liquid Glass aesthetics and accessibility-first design."
"description": "Audits and designs iOS/macOS/watchOS/visionOS interfaces against the Apple Human Interface Guidelines, including the Liquid Glass design language (announced WWDC25, shipped with iOS 26/macOS Tahoe, Sept 2025). Use when reviewing an Apple-platform mockup or app for HIG compliance, checking contrast or tap-target sizes, or designing native-feeling Apple UI (e.g., 'audit my iOS app against the HIG', 'is this text readable on Liquid Glass?')."
},
{
"name": "code-to-prd",
"source": "../../product-team/code-to-prd/skills/code-to-prd",
"category": "product",
"description": "|"
"description": "Reverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Use when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes."
},
{
"name": "competitive-teardown",
@ -1755,13 +1743,13 @@
"name": "product-manager-toolkit",
"source": "../../product-team/skills/product-manager-toolkit",
"category": "product",
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development."
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy."
},
{
"name": "product-skills",
"source": "../../product-team/skills/product-skills",
"category": "product",
"description": "10 product agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. PM toolkit (RICE), agile PO, product strategist (OKR), UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, research summarizer. Python tools (stdlib-only)."
"description": "Router/index for the 12 product skills bundled in this plugin (RICE prioritization, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding). Use when a product request doesn't obviously match one skill and you need to pick the right one (e.g., 'help me prioritize features', 'plan a product experiment')."
},
{
"name": "product-strategist",
@ -1797,13 +1785,13 @@
"name": "ui-design-system",
"source": "../../product-team/skills/ui-design-system",
"category": "product",
"description": "UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration."
"description": "UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use when creating design systems, generating design tokens, maintaining visual consistency, or facilitating design-dev collaboration and developer handoff."
},
{
"name": "ux-researcher-designer",
"source": "../../product-team/skills/ux-researcher-designer",
"category": "product",
"description": "UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation."
"description": "UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, planning usability tests, or validating designs."
},
{
"name": "andreessen",
@ -1833,7 +1821,7 @@
"name": "inbox-triage",
"source": "../../productivity/email/skills/inbox-triage",
"category": "productivity",
"description": "Runs a full inbox triage using the knowledge base created by the 'inbox-setup' skill. Light-intake by design (most invocations skip questions and run with KB-default preferences); asks at most 2 grill-me override questions when invocation is outside normal cadence or includes category-skip intent. Searches recent emails, classifies them via the user's taxonomy, researches new senders, generates recommendations, drafts replies (NEVER sends), delivers a report in the user's preferred format, and updates the knowledge base with learnings. Designed to run on a recurring schedule (1-3x daily) or on demand. Triggers: 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage', or any variation where the user wants their inbox processed. Requires the inbox-setup skill to have been run first."
"description": "Runs a full inbox triage using the knowledge base created by the 'inbox-setup' skill. Light-intake by design (most invocations skip questions and run with KB-default preferences); asks at most 2 grill-me override questions when invocation is outside normal cadence or includes category-skip intent. Searches recent emails, classifies them via the user's taxonomy, researches new senders, generates recommendations, drafts replies (NEVER sends), delivers a report in the user's preferred format, and updates the knowledge base with learnings. Designed to run on a recurring schedule (1-3x daily) or on demand. Use when the user wants their inbox processed, in any variation (e.g., 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage'). Requires the inbox-setup skill to have been run first."
},
{
"name": "reflect",
@ -1863,7 +1851,7 @@
"name": "jira-expert",
"source": "../../project-management/skills/jira-expert",
"category": "project-management",
"description": "Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations."
"description": "Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use when setting up or configuring Jira projects, writing JQL and advanced searches, creating dashboards, designing workflows, or performing technical Jira operations."
},
{
"name": "meeting-analyzer",
@ -1875,7 +1863,7 @@
"name": "pm-skills",
"source": "../../project-management/skills/pm-skills",
"category": "project-management",
"description": "6 project management agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Senior PM, scrum master, Jira expert (JQL), Confluence expert, Atlassian admin, template creator. MCP integration for live Jira/Confluence automation."
"description": "Router/index for the 8 project-management skills bundled in this plugin (senior PM quant toolkit, scrum master, Jira/JQL, Confluence, Atlassian admin, Atlassian templates, meeting analyzer, team communications). Use when a PM request doesn't obviously match one skill and you need to pick the right one (e.g., 'our sprints feel off', 'audit our Jira permissions'). Bundles an Atlassian Remote MCP config (.mcp.json) for live Jira/Confluence access."
},
{
"name": "scrum-master",
@ -1899,7 +1887,7 @@
"name": "capa-officer",
"source": "../../ra-qm-team/skills/capa-officer",
"category": "ra-qm",
"description": "CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use for CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization."
"description": "CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use when running CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization."
},
{
"name": "eu-ai-act-specialist",
@ -1917,19 +1905,19 @@
"name": "fda-consultant-specialist",
"source": "../../ra-qm-team/skills/fda-consultant-specialist",
"category": "ra-qm",
"description": "FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QSR, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity."
"description": "FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QMSR (21 CFR 820, which incorporates ISO 13485:2016 by reference since 2026-02-02; formerly QSR) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QMSR, QSR, ISO 13485 for FDA, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity."
},
{
"name": "gdpr-dsgvo-expert",
"source": "../../ra-qm-team/skills/gdpr-dsgvo-expert",
"category": "ra-qm",
"description": "GDPR and German DSGVO compliance automation. Scans codebases for privacy risks, generates DPIA documentation, tracks data subject rights requests. Use for GDPR compliance assessments, privacy audits, data protection planning, DPIA generation, and data subject rights management."
"description": "GDPR and German DSGVO compliance automation. Scans codebases for privacy risks, generates DPIA documentation, tracks data subject rights requests with Art. 12(3) one-month deadlines. Use when running GDPR compliance assessments, privacy audits, data protection planning, DPIA generation, or data subject rights (DSAR) management (e.g., 'check this service for GDPR risks', 'track an access request deadline'). Final compliance determinations route to the DPO or legal counsel."
},
{
"name": "information-security-manager-iso27001",
"source": "../../ra-qm-team/skills/information-security-manager-iso27001",
"category": "ra-qm",
"description": "ISO 27001 ISMS implementation and cybersecurity governance for HealthTech and MedTech companies. Use for ISMS design, security risk assessment, control implementation, ISO 27001 certification, security audits, incident response, and compliance verification. Covers ISO 27001, ISO 27002, healthcare security, and medical device cybersecurity."
"description": "ISO 27001 ISMS implementation and cybersecurity governance for HealthTech and MedTech companies. Use when designing an ISMS, running security risk assessments, implementing controls, pursuing ISO 27001 certification, preparing security audits, responding to security incidents, or verifying compliance. Covers ISO 27001, ISO 27002, healthcare security, and medical device cybersecurity."
},
{
"name": "isms-audit-expert",
@ -1953,25 +1941,25 @@
"name": "mdr-745-specialist",
"source": "../../ra-qm-team/skills/mdr-745-specialist",
"category": "ra-qm",
"description": "EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration."
"description": "EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, Art. 86 PSUR schedules, and EUDAMED integration. Use when classifying a medical device under MDR, building or gap-checking a technical file, planning clinical evaluation or PMS/PSUR cadence, or preparing for notified body review (e.g., 'what class is my device under MDR', 'review my PSUR schedule')."
},
{
"name": "qms-audit-expert",
"source": "../../ra-qm-team/skills/qms-audit-expert",
"category": "ra-qm",
"description": "ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management."
"description": "ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use when planning internal audits, executing audits, classifying findings, preparing for external audits, or managing an audit program."
},
{
"name": "quality-documentation-manager",
"source": "../../ra-qm-team/skills/quality-documentation-manager",
"category": "ra-qm",
"description": "Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review."
"description": "Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use when working on document control procedures, change control workflows, document numbering, version management, electronic signature compliance, or regulatory documentation review."
},
{
"name": "quality-manager-qmr",
"source": "../../ra-qm-team/skills/quality-manager-qmr",
"category": "ra-qm",
"description": "Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2."
"description": "Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2. Use when leading management reviews, setting quality policy and objectives, monitoring quality KPIs and cost of quality, or exercising QMR governance and regulatory oversight responsibilities."
},
{
"name": "quality-manager-qms-iso13485",
@ -1983,7 +1971,7 @@
"name": "ra-qm-skills",
"source": "../../ra-qm-team/skills/ra-qm-skills",
"category": "ra-qm",
"description": "12 regulatory & QM agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. ISO 13485 QMS, MDR 2017/745, FDA 510(k)/PMA, ISO 27001 ISMS, GDPR/DSGVO, risk management (ISO 14971), CAPA, document control, auditing. Python tools (stdlib-only)."
"description": "Router/index for the 15 regulatory & quality-management skills bundled in this plugin (ISO 13485 QMS, EU MDR 2017/745, FDA submissions under QMSR, ISO 14971 risk, CAPA, document control, ISO 27001/ISMS, ISO 42001 AIMS, EU AI Act, GDPR/DSGVO, SOC 2, auditing). Use when a compliance request doesn't obviously match one skill and you need to pick the right one (e.g., 'prepare us for an ISO 13485 audit', 'is my AI system high-risk under the AI Act')."
},
{
"name": "regulatory-affairs-head",
@ -2007,49 +1995,49 @@
"name": "dossier",
"source": "../../research/dossier/skills/dossier",
"category": "research",
"description": "Decision-grade entity research skill \u2014 produces a hypothesis-tested dossier on a specific company, person, nonprofit, or government org, not a generic profile. Forcing intake makes the user state their hypothesis upfront (what they already believe and want to verify or disprove) so the dossier tests it rather than confirms it. Output is an editable Word document (.docx) with verdict on the hypothesis, identity facts, 12-month activity timeline, network signals, reputation signals, red flags, 3-5 conversation hooks tied to specific findings, and source-provenance audit log. Uses WebSearch + WebFetch + free APIs (SEC EDGAR, GitHub, ProPublica Nonprofit Explorer) as workhorses; optional BYOK MCPs (LinkedIn, Crunchbase, Apollo, Pitchbook, SimilarWeb) enhance coverage. Triggers: 'research [company]', 'dossier on [person/company]', 'background check on [entity]', 'prep me for a meeting with [person/company]', 'due diligence on [company]', 'what should I know about [entity]', 'research [person] before I [meet/hire/invest]', 'competitor research on [company]', 'investor diligence [company]', 'interview prep for [company]'. Honors sensitivity exclusions for journalism + personal-vetting contexts."
"description": "Decision-grade entity research skill \u2014 produces a hypothesis-tested dossier on a specific company, person, nonprofit, or government org, not a generic profile. Forcing intake makes the user state their hypothesis upfront (what they already believe and want to verify or disprove) so the dossier tests it rather than confirms it. Output is an editable Word document (.docx) with verdict on the hypothesis, identity facts, 12-month activity timeline, network and reputation signals, red flags, conversation hooks tied to specific findings, and source-provenance audit log. Uses WebSearch + WebFetch + free APIs (SEC EDGAR, GitHub, ProPublica) as workhorses; optional BYOK MCPs enhance coverage. Use when the user asks for background research, diligence, or meeting prep on a specific entity (e.g., 'prep me for a meeting with [person/company]', 'due diligence on [company]'). Honors sensitivity exclusions for journalism + personal-vetting contexts."
},
{
"name": "grants",
"source": "../../research/grants/skills/grants",
"category": "research",
"description": "NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Triggers: 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research', or any grant-related request. NIH-only scope \u2014 non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake."
"description": "NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope \u2014 non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake."
},
{
"name": "litreview",
"source": "../../research/litreview/skills/litreview",
"category": "research",
"description": "Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' \u2014 not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list \u2014 that's a plain Consensus search."
"description": "Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' \u2014 an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list \u2014 that's a plain Consensus search."
},
{
"name": "notebooklm",
"source": "../../research/notebooklm/skills/notebooklm",
"category": "research",
"description": "Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM \u2014 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment \u2014 fails gracefully when unavailable."
"description": "Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics \u2014 discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment \u2014 fails gracefully when unavailable."
},
{
"name": "patent",
"source": "../../research/patent/skills/patent",
"category": "research",
"description": "Patent prior-art and landscape intelligence skill \u2014 not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice \u2014 always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope."
"description": "Patent prior-art and landscape intelligence skill \u2014 not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice \u2014 always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope."
},
{
"name": "pulse",
"source": "../../research/pulse/skills/pulse",
"category": "research",
"description": "Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis."
"description": "Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis."
},
{
"name": "research",
"source": "../../research/research/skills/research",
"category": "research",
"description": "Default entry point for any research request \u2014 a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers \u2014 \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log."
"description": "Default entry point for any research request \u2014 a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log."
},
{
"name": "syllabus",
"source": "../../research/syllabus/skills/syllabus",
"category": "research",
"description": "Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs \u2014 so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill."
"description": "Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs \u2014 so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') \u2014 even casual mentions with a syllabus attached should trigger this skill."
},
{
"name": "clinical-research",
@ -2119,7 +2107,7 @@
"description": "Software engineering and technical skills"
},
"engineering-advanced": {
"count": 79,
"count": 78,
"source": "../../engineering",
"description": "Advanced engineering skills - agents, RAG, MCP, CI/CD, databases, observability"
},
@ -2129,7 +2117,7 @@
"description": "Financial analysis, valuation, and forecasting skills"
},
"marketing": {
"count": 49,
"count": 48,
"source": "../../marketing-skill",
"description": "Marketing, content, and demand generation skills"
},

1
.codex/skills/ai-seo
View file

@ -1 +0,0 @@
../../marketing-skill/skills/ai-seo

1
.codex/skills/collab-proof Symbolic link
View file

@ -0,0 +1 @@
../../engineering/collab-proof/skills/collab-proof

1
.codex/skills/command-guide
View file

@ -1 +0,0 @@
../../engineering/skills/command-guide

1
.codex/skills/release-manager
View file

@ -1 +0,0 @@
../../engineering/skills/release-manager

2
.codex/skills/review
View file

@ -1 +1 @@
../../engineering-team/playwright-pro/skills/review
../../engineering-team/self-improving-agent/skills/review

2
.codex/skills/universal-scraping-architect
View file

@ -1 +1 @@
../../engineering/universal-scraping-architect
../../engineering/universal-scraping-architect/skills/universal-scraping-architect

300
.gemini/skills-index.json
View file

@ -1,7 +1,7 @@
{
"version": "1.0.0",
"name": "gemini-cli-skills",
"total_skills": 410,
"total_skills": 418,
"skills": [
{
"name": "README",
@ -16,7 +16,7 @@
{
"name": "content-strategist",
"category": "agent",
"description": "Builds content engines that rank, convert, and compound. Thinks in systems \u2014 topic clusters, not individual posts. Every piece earns its place or gets killed."
"description": "Builds content engines that rank, convert, and compound. Thinks in systems \u2014 topic clusters, not individual posts. Every piece earns its place or gets killed. Use when content needs to behave like a system rather than a stream of posts \u2014 e.g., designing a topic-cluster plan to grow organic traffic from zero, or auditing an editorial calendar and killing pieces that don't convert after 90 days. (For single-asset, on-brand copy production, see cs-content-creator.)"
},
{
"name": "cs-aeo",
@ -26,7 +26,7 @@
{
"name": "cs-agile-product-owner",
"category": "agent",
"description": "Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation"
"description": "Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation. Use when preparing work for a development team \u2014 e.g., decomposing a large epic into INVEST-compliant stories with acceptance criteria, or refining a messy backlog ahead of sprint planning."
},
{
"name": "cs-backend-engineer",
@ -36,22 +36,22 @@
{
"name": "cs-ceo-advisor",
"category": "agent",
"description": "Strategic leadership advisor for CEOs covering vision, strategy, board management, investor relations, and organizational culture"
"description": "Strategic leadership advisor for CEOs covering vision, strategy, board management, investor relations, and organizational culture. Use when a founder or CEO faces a company-level strategic decision \u2014 e.g., preparing the narrative and metrics for a quarterly board meeting, or stress-testing a pivot or market-expansion decision against vision, runway, and stakeholder expectations."
},
{
"name": "cs-content-creator",
"category": "agent",
"description": "AI-powered content creation specialist for brand voice consistency, SEO optimization, and multi-platform content strategy"
"description": "AI-powered content creation specialist for brand voice consistency, SEO optimization, and multi-platform content strategy. Use when producing or reviewing marketing content that must stay on-brand and rank \u2014 e.g., turning one pillar blog post into a LinkedIn/X/newsletter bundle, or auditing draft copy against an established brand voice profile before publishing."
},
{
"name": "cs-cto-advisor",
"category": "agent",
"description": "Technical leadership advisor for CTOs covering technology strategy, team scaling, architecture decisions, and engineering excellence"
"description": "Technical leadership advisor for CTOs covering technology strategy, team scaling, architecture decisions, and engineering excellence. Use when a CTO or technical founder needs company-level technology judgment \u2014 e.g., deciding build-vs-buy for a core platform component, or planning how to scale the engineering org from 5 to 30 engineers without losing delivery velocity."
},
{
"name": "cs-demand-gen-specialist",
"category": "agent",
"description": "Demand generation and customer acquisition specialist for lead generation, conversion optimization, and multi-channel acquisition campaigns"
"description": "Demand generation and customer acquisition specialist for lead generation, conversion optimization, and multi-channel acquisition campaigns. Use when building or fixing the acquisition funnel \u2014 e.g., diagnosing why MQL-to-SQL conversion dropped after a pricing change, or designing a multi-channel campaign plan with budget split across paid, content, and email."
},
{
"name": "cs-engineering-lead",
@ -86,22 +86,22 @@
{
"name": "cs-product-analyst",
"category": "agent",
"description": "Product analytics agent for KPI definition, dashboard setup, experiment design, and test result interpretation."
"description": "Product analytics agent for KPI definition, dashboard setup, experiment design, and test result interpretation. Use when a product question needs numbers \u2014 e.g., defining activation/retention KPIs and a dashboard spec for a new feature, or sizing an A/B test and judging whether the result is significant enough to ship."
},
{
"name": "cs-product-manager",
"category": "agent",
"description": "Product management agent for feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework"
"description": "Product management agent for feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework. Use when a product decision needs structure and evidence \u2014 e.g., RICE-scoring a backlog of 20 feature requests before quarterly planning, or drafting a PRD from raw customer-interview notes."
},
{
"name": "cs-product-strategist",
"category": "agent",
"description": "Product strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation"
"description": "Product strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation. Use when the question is direction rather than delivery \u2014 e.g., cascading company OKRs into product-team objectives for next quarter, or running a competitive teardown to decide whether to enter an adjacent market."
},
{
"name": "cs-project-manager",
"category": "agent",
"description": "Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills."
"description": "Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills. Use when running delivery operations \u2014 e.g., planning a sprint with capacity and carry-over math in Jira, or assembling a portfolio health report for stakeholders from ticket and velocity data."
},
{
"name": "cs-quality-regulatory",
@ -116,7 +116,12 @@
{
"name": "cs-ux-researcher",
"category": "agent",
"description": "UX research agent for research planning, persona generation, journey mapping, and usability test analysis"
"description": "UX research agent for research planning, persona generation, journey mapping, and usability test analysis. Use when product decisions need user evidence \u2014 e.g., planning interview scripts and recruiting criteria for a discovery study, or synthesizing usability-test sessions into prioritized findings and updated personas."
},
{
"name": "cs-webinar-marketer",
"category": "agent",
"description": "Webinar & virtual-event marketing specialist agent. Use when planning, promoting, running, or rescuing a webinar, virtual event, live demo, workshop, masterclass, fireside chat, or virtual summit. Orchestrates the webinar-marketing skill \u2014 sizes the funnel backward from the business goal, builds the promotion runway, designs the show-up and live-to-close sequences, scores an existing funnel to find the broken stage, and plans evergreen/on-demand automation. Treats a webinar as a funnel, not an event. Voice \u2014 outcome-obsessed demand operator; refuses to celebrate registrations when nobody shows up or buys; fixes the stage that's actually broken instead of rewriting the landing page by reflex."
},
{
"name": "cs-wiki-ingestor",
@ -141,37 +146,37 @@
{
"name": "devops-engineer",
"category": "agent",
"description": "Builds infrastructure that scales without babysitting. Automates everything worth automating. Monitors before it breaks. Treats clicking in consoles as a production incident waiting to happen."
"description": "Builds infrastructure that scales without babysitting. Automates everything worth automating. Monitors before it breaks. Treats clicking in consoles as a production incident waiting to happen. Use when infrastructure or delivery needs automation and observability \u2014 e.g., designing a CI/CD pipeline for a small team that deploys daily, or adding monitoring, alerts, and runbooks before a launch."
},
{
"name": "finance-lead",
"category": "agent",
"description": "Startup CFO who builds models that survive contact with reality. Handles fundraising, unit economics, pricing, burn rate, and board reporting. Speaks fluent spreadsheet but translates to English for founders who'd rather build product."
"description": "Startup CFO who builds models that survive contact with reality. Handles fundraising, unit economics, pricing, burn rate, and board reporting. Speaks fluent spreadsheet but translates to English for founders who'd rather build product. Use when a money question needs a model, not a vibe \u2014 e.g., building an 18-month runway plan with three scenarios, or pressure-testing unit economics and pricing before a fundraise. (For DCF and SaaS-metrics tooling, see cs-financial-analyst.)"
},
{
"name": "growth-marketer",
"category": "agent",
"description": "Growth marketing specialist for bootstrapped startups and indie hackers. Builds content engines, optimizes funnels, runs launch sequences, and finds scalable acquisition channels \u2014 all on a budget that makes enterprise marketers cry."
"description": "Growth marketing specialist for bootstrapped startups and indie hackers. Builds content engines, optimizes funnels, runs launch sequences, and finds scalable acquisition channels \u2014 all on a budget that makes enterprise marketers cry. Use when growth has to come before budget \u2014 e.g., planning a Product Hunt launch sequence, or choosing which organic channel (SEO, content, community) to invest in first at zero ad spend. (For funnel diagnostics with paid budget, see cs-demand-gen-specialist.)"
},
{
"name": "product-manager",
"category": "agent",
"description": "Ships outcomes, not features. Writes specs engineers actually read. Prioritizes ruthlessly. Kills darlings when the data says so. Operates at the intersection of user needs, business goals, and engineering reality."
"description": "Ships outcomes, not features. Writes specs engineers actually read. Prioritizes ruthlessly. Kills darlings when the data says so. Operates at the intersection of user needs, business goals, and engineering reality. Use when product work needs ruthless prioritization and a success metric \u2014 e.g., turning vague stakeholder asks into a 2-page spec, or deciding which of three competing roadmap bets to fund this quarter. (For framework-heavy RICE/PRD tooling, see cs-product-manager.)"
},
{
"name": "solo-founder",
"category": "agent",
"description": "Your co-founder who doesn't exist yet. Covers product, engineering, marketing, and strategy for one-person startups \u2014 because nobody's stopping you from making bad decisions and somebody should."
"description": "Your co-founder who doesn't exist yet. Covers product, engineering, marketing, and strategy for one-person startups \u2014 because nobody's stopping you from making bad decisions and somebody should. Use when a solo founder or indie hacker needs a cross-functional thinking partner \u2014 e.g., deciding what to cut from an MVP to ship this month, or choosing between building one more feature and talking to ten users."
},
{
"name": "startup-cto",
"category": "agent",
"description": "Technical co-founder who's been through two startups and learned what actually matters. Makes architecture decisions, selects tech stacks, builds engineering culture, and prepares for technical due diligence \u2014 all while shipping fast with a small team."
"description": "Technical co-founder who's been through two startups and learned what actually matters. Makes architecture decisions, selects tech stacks, builds engineering culture, and prepares for technical due diligence \u2014 all while shipping fast with a small team. Use when an early-stage team needs pragmatic, ship-first technical leadership \u2014 e.g., picking a boring-but-fast stack for an MVP with two engineers, or prepping architecture answers for investor due diligence. (For company-scale CTO strategy, see cs-cto-advisor.)"
},
{
"name": "business-growth-skills",
"category": "business-growth",
"description": "4 business growth agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Customer success (health scoring, churn), sales engineer (RFP), revenue operations (pipeline, GTM), contract & proposal writer. Python tools (stdlib-only)."
"description": "Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP')."
},
{
"name": "contract-and-proposal-writer",
@ -206,12 +211,12 @@
{
"name": "internal-comms",
"category": "business-operations",
"description": "Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication \u2014 a re-org announcement, a tool rollout, a policy change, a benefit change, a leadership transition, a layoff, an acquisition close, or an internal product launch \u2014 and the audience is employees (not customers). Triggers on \"all-hands announcement\", \"town-hall script\", \"change comms\", \"internal newsletter\", \"rollout comms\", \"policy change announcement\", \"re-org announcement\", \"internal FAQ\", \"manager talking points\", \"Prosci ADKAR\", \"Kotter 8-step\", \"layoff comms\", \"RIF comms\", \"internal memo\". Pairs Prosci ADKAR (Awareness / Desire / Knowledge / Ability / Reinforcement) and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points. Industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Distinct from marketing-skill/* (external/customer-facing), c-level-advisor/internal-narrative (strategic framing, not tactical drafts), and c-level-advisor/change-management (executive change strategy, not the comms package itself)."
"description": "Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication \u2014 a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch \u2014 and the audience is employees (not customers). Pairs Prosci ADKAR and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points; industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Triggers on \"all-hands announcement\", \"change comms\", \"rollout comms\", \"re-org announcement\", \"manager talking points\", \"layoff comms\"."
},
{
"name": "knowledge-ops",
"category": "business-operations",
"description": "Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding, expense reimbursement, system-access provisioning, customer-escalation playbook) \u2014 including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, ops onboarding doc generation, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Kaoru Ishikawa's 5W2H method, Atul Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4 Service Operation, FDA 21 CFR Part 211, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists. Distinct from `engineering/llm-wiki` (Karpathy-style personal PKM second brain), `engineering-team/runbook-generator` (system-ops production debugging runbook), `project-management/*` (Jira/Confluence delivery + ticket tracking), and sibling `business-operations/process-mapper` (BPMN process *design*, while knowledge-ops is process *documentation*)."
"description": "Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding) \u2014 including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Ishikawa's 5W2H method, Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists (e.g., \"validate this runbook before it goes into rotation\", \"audit our Confluence wiki for stale and orphaned SOPs\")."
},
{
"name": "process-mapper",
@ -221,12 +226,12 @@
{
"name": "procurement-optimizer",
"category": "business-operations",
"description": "Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base \u2014 when the user needs to do a spend audit, spend categorization (UNSPSC-aligned), purchasing-cycle analysis, or risk-balanced supplier consolidation. Triggers on \"spend audit\", \"SaaS audit\", \"spend categorization\", \"supplier rationalization\", \"supplier consolidation\", \"purchasing cycle\", \"procurement review\", \"category strategy\", \"duplicate SaaS\", \"renewal cluster\". Ships 3 stdlib-only Python tools (UNSPSC-aligned spend categorizer with Pareto breakdown and industry profiles, purchasing-cycle analyzer that surfaces bottleneck categories per Goldratt's Theory of Constraints, supplier-consolidation planner that refuses single-source recommendations for tier-1 categories without a documented break-glass plan), 3 reference docs each citing 7+ authoritative sources (A.T. Kearney / Hackett / Spend Matters / UNSPSC / Productiv / Vendr / Tropic / IACCM / ISM / BCG), and a 20-minute spend-intake template. Distinct from sibling vendor-management (performance scoring of vendors you keep paying), finance/financial-analysis (close + report, not category strategy), and c-level-advisor/general-counsel-advisor (contract law, not category rationalization)."
"description": "Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base \u2014 when the user needs a spend audit, spend categorization (UNSPSC-aligned with Pareto breakdown and industry profiles), purchasing-cycle analysis (bottleneck categories per Goldratt's Theory of Constraints), or risk-balanced supplier consolidation that refuses single-source recommendations for tier-1 categories without a documented break-glass plan. Triggers on \"spend audit\", \"SaaS audit\", \"spend categorization\", \"supplier rationalization\", \"supplier consolidation\", \"category strategy\", \"duplicate SaaS\", \"renewal cluster\"."
},
{
"name": "vendor-management",
"category": "business-operations",
"description": "Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships \u2014 running a vendor scorecard, tracking SLA compliance, classifying third-party risk, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Triggers on \"vendor SLA\", \"vendor scorecard\", \"third-party risk\", \"TPRM\", \"vendor review\", \"SaaS audit\", \"supplier performance\", \"vendor health check\", \"renewal review\". Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Ships 3 stdlib-only Python tools (vendor scorer with industry tuning, SLA compliance tracker with credit-claim flags, vendor risk classifier across 4 risk vectors), 3 reference docs each citing 7+ authoritative sources (Gartner / Shared Assessments / NIST / ISO 27036 / breach post-mortems), and a 5-vendor catalog template. Distinct from c-level-advisor/general-counsel-advisor (contract law, not operational management), business-growth/contract-and-proposal-writer (outbound proposals, not inbound vendor scoring), and sibling procurement-optimizer (spend categorization, not vendor performance)."
"description": "Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships \u2014 running a vendor scorecard with industry tuning, tracking SLA compliance with credit-claim flags, classifying third-party risk across 4 risk vectors, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Triggers on \"vendor SLA\", \"vendor scorecard\", \"third-party risk\", \"TPRM\", \"vendor review\", \"supplier performance\", \"vendor health check\", \"renewal review\"."
},
{
"name": "agent-protocol",
@ -241,7 +246,7 @@
{
"name": "board-meeting",
"category": "c-level",
"description": "Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:board, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question."
"description": "Multi-agent board meeting protocol for strategic decisions. Runs a structured 6-phase deliberation: context loading, independent C-suite contributions (isolated, no cross-pollination), critic analysis, synthesis, founder review, and decision extraction. Use when the user invokes /cs:boardroom, calls a board meeting, or wants structured multi-perspective executive deliberation on a strategic question."
},
{
"name": "board-prep",
@ -251,37 +256,37 @@
{
"name": "boardroom",
"category": "c-level",
"description": "/cs:boardroom <brief> \u2014 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo."
"description": "/cs:boardroom <brief> \u2014 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains \u2014 e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call."
},
{
"name": "brief",
"category": "c-level",
"description": "/cs:brief <topic> \u2014 Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline."
"description": "/cs:brief <topic> \u2014 Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline. Use when a strategic question needs to be framed before boardroom deliberation \u2014 e.g. locking options, assumptions, and success criteria for a pricing change or a market-entry decision."
},
{
"name": "c-level-agents",
"category": "c-level",
"description": "Founder-mode executive team. 8 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff) and 17 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions."
"description": "Founder-mode executive team. 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, GC, CDO, CAIO, CCO, VPE, Chief of Staff) and 21 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions."
},
{
"name": "c-level-skills",
"category": "c-level",
"description": "10 C-level advisory agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. CEO, CTO, COO, CPO, CMO, CFO, CRO, CISO, CHRO, Executive Mentor. Multi-role board meetings, strategy routing, structured recommendations. For founders needing executive-level decision support."
"description": "Index and router for the C-level advisory bundle: 33 skills covering 14 C-suite roles, orchestration, cross-cutting capabilities, and culture. Use when exploring what the c-level-advisor bundle contains, deciding which advisor skill fits a question, or finding the entry points (cs-onboard interview, chief-of-staff routing, board-meeting protocol)."
},
{
"name": "caio-review",
"category": "c-level",
"description": "/cs:caio-review <plan> \u2014 Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring."
"description": "/cs:caio-review <plan> \u2014 Eval-demanding Chief AI Officer interrogation of any plan that involves AI: model selection, risk classification, cost economics, or AI hiring. Use when shipping an AI feature without an eval set, choosing between API, fine-tune, and self-hosted, or classifying a use case under the EU AI Act."
},
{
"name": "cco-review",
"category": "c-level",
"description": "/cs:cco-review <plan> \u2014 Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring."
"description": "/cs:cco-review <plan> \u2014 Retention-obsessed Chief Customer Officer interrogation of any plan that touches customer retention, segmentation, CS team sizing, or CS team hiring. Use when gross retention is slipping, before approving CSM headcount, or when deciding which customer segments to keep or fire."
},
{
"name": "cdo-review",
"category": "c-level",
"description": "/cs:cdo-review <plan> \u2014 Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring."
"description": "/cs:cdo-review <plan> \u2014 Decision-driven Chief Data Officer interrogation of any plan that touches training data, data architecture, data productization, or data team hiring. Use when validating training-data rights before model work, choosing warehouse vs lakehouse vs mesh, or valuing data assets for productization or M&A."
},
{
"name": "ceo-advisor",
@ -296,7 +301,7 @@
{
"name": "cfo-review",
"category": "c-level",
"description": "/cs:cfo-review <plan> \u2014 Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation."
"description": "/cs:cfo-review <plan> \u2014 Numerate-skeptic interrogation of any plan that touches money. Unit economics, runway, dilution, capital allocation. Use when a plan commits meaningful spend \u2014 e.g. a hiring wave, a fundraise decision, or a new channel budget."
},
{
"name": "challenge",
@ -326,7 +331,7 @@
{
"name": "chief-of-staff",
"category": "c-level",
"description": "C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically."
"description": "C-suite orchestration layer. Routes founder questions to the right advisor role(s), triggers multi-role board meetings for complex decisions, synthesizes outputs, and tracks decisions. Every C-suite interaction starts here. Loads company context automatically. Use when a founder question needs routing to the right advisor \u2014 e.g. 'should we raise now or cut burn?' \u2014 or when a multi-domain decision needs a board meeting convened."
},
{
"name": "chro-advisor",
@ -341,7 +346,7 @@
{
"name": "ciso-review",
"category": "c-level",
"description": "/cs:ciso-review <plan> \u2014 Risk-paranoid interrogation of any plan that touches data, compliance, or production access."
"description": "/cs:ciso-review <plan> \u2014 Risk-paranoid interrogation of any plan that touches data, compliance, or production access. Use when launching features that handle customer data, before a SOC 2 / ISO audit, or after any incident or near-miss."
},
{
"name": "cmo-advisor",
@ -351,7 +356,7 @@
{
"name": "cmo-review",
"category": "c-level",
"description": "/cs:cmo-review <plan> \u2014 Narrative-first interrogation of positioning, ICP, message house, and channel mix."
"description": "/cs:cmo-review <plan> \u2014 Narrative-first interrogation of positioning, ICP, message house, and channel mix. Use when launching a campaign or repositioning, or when CAC is rising and the one-sentence positioning test fails."
},
{
"name": "company-os",
@ -366,7 +371,7 @@
{
"name": "context-engine",
"category": "c-level",
"description": "Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy/anonymization rules before external API calls."
"description": "Loads and manages company context for all C-suite advisor skills. Reads ~/.claude/company-context.md, detects stale context (>90 days), enriches context during conversations, and enforces privacy/anonymization rules before external API calls. Use when starting any C-suite advisor session, when context looks stale or missing, or before sending company data to an external service."
},
{
"name": "coo-advisor",
@ -381,7 +386,7 @@
{
"name": "cpo-review",
"category": "c-level",
"description": "/cs:cpo-review <plan> \u2014 JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus."
"description": "/cs:cpo-review <plan> \u2014 JTBD-driven interrogation of product roadmap, PMF signal, and portfolio focus. Use when committing a quarter's roadmap, deciding whether to kill a feature, or claiming PMF without a retention curve."
},
{
"name": "cro-advisor",
@ -391,17 +396,17 @@
{
"name": "cro-review",
"category": "c-level",
"description": "/cs:cro-review <plan> \u2014 Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time."
"description": "/cs:cro-review <plan> \u2014 Pipeline-paranoid interrogation of revenue, win rate, NRR, and ramp time. Use when the forecast misses pipeline coverage, win rates drop, or before scaling the sales team."
},
{
"name": "cross-eval",
"category": "c-level",
"description": "/cs:cross-eval <memo> \u2014 Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation."
"description": "/cs:cross-eval <memo> \u2014 Multi-model consensus on a board memo or strategy brief. Claude + Codex + Gemini cross-review with graceful degradation. Use when a high-stakes memo needs an independent sanity check before the boardroom \u2014 e.g. a bet-the-company pivot or fundraise terms."
},
{
"name": "cs-onboard",
"category": "c-level",
"description": "Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills."
"description": "Founder onboarding interview that captures company context across 7 dimensions. Invoke with /cs:setup for initial interview or /cs:update for quarterly refresh. Generates ~/.claude/company-context.md used by all C-suite advisor skills. Use when setting up the C-suite advisors for the first time, or when company context is missing or more than 90 days old \u2014 e.g. after a fundraise or pivot."
},
{
"name": "cto-advisor",
@ -411,7 +416,7 @@
{
"name": "cto-review",
"category": "c-level",
"description": "/cs:cto-review <plan> \u2014 Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy."
"description": "/cs:cto-review <plan> \u2014 Architecture and scaling interrogation. Tech debt, scaling cliffs, team scaling, build-vs-buy. Use when committing to an architecture, planning for 10x load, or weighing a rebuild against a vendor."
},
{
"name": "culture-architect",
@ -421,7 +426,7 @@
{
"name": "decide",
"category": "c-level",
"description": "/cs:decide <memo> \u2014 Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference."
"description": "/cs:decide <memo> \u2014 Log a decision to two-layer memory via decision-logger. Approved memo becomes durable; raw transcripts kept for reference. Use when the founder has approved a boardroom memo and the decision must become durable company memory \u2014 e.g. right after /cs:boardroom concludes."
},
{
"name": "decision-logger",
@ -431,7 +436,7 @@
{
"name": "execute",
"category": "c-level",
"description": "/cs:execute <decision> \u2014 Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision."
"description": "/cs:execute <decision> \u2014 Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision. Use when a logged decision needs to become an operating plan \u2014 e.g. turning an approved market-entry call into weekly milestones with DRIs."
},
{
"name": "executive-mentor",
@ -446,17 +451,17 @@
{
"name": "founder-mode",
"category": "c-level",
"description": "/cs:founder-mode <question> \u2014 Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point."
"description": "/cs:founder-mode <question> \u2014 Auto-routes any founder question to the right C-role advisor or to /cs:boardroom for multi-role topics. The single-command entry point. Use when a founder asks any strategic question without knowing which advisor or command fits \u2014 e.g. 'runway pressure' routes to the CFO, 'gross retention dropped' routes to the CCO."
},
{
"name": "freeze",
"category": "c-level",
"description": "/cs:freeze <decision> <days> \u2014 Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer."
"description": "/cs:freeze <decision> <days> \u2014 Lock a strategic decision for a cooldown period to prevent impulse reversal. Mirrors gstack's safety primitives for the business layer. Use when an irreversible decision was made under pressure \u2014 e.g. a layoff plan or multi-year contract \u2014 and deserves a cooling-off lock before execution."
},
{
"name": "gc-review",
"category": "c-level",
"description": "/cs:gc-review <plan> \u2014 General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface."
"description": "/cs:gc-review <plan> \u2014 General Counsel interrogation of contracts, IP, regulatory, term sheets, and employment-law surface. Use when reviewing a term sheet before signing, redlining a customer MSA, or checking IP assignment and regulatory exposure on a new product."
},
{
"name": "general-counsel-advisor",
@ -466,7 +471,7 @@
{
"name": "hard-call",
"category": "c-level",
"description": "/em -hard-call \u2014 Framework for Decisions With No Good Options"
"description": "/em:hard-call \u2014 Framework for decisions with no good options. Use when every option is painful and a structured 10/10/10 + regret-minimization pass is needed \u2014 e.g. choosing between a layoff and a down round, or killing a beloved product line."
},
{
"name": "internal-narrative",
@ -486,12 +491,12 @@
{
"name": "office-hours",
"category": "c-level",
"description": "/cs:office-hours <topic> \u2014 YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit."
"description": "/cs:office-hours <topic> \u2014 YC-style 6-question founder interrogation before any advice. Forces clarity on problem, customer, distribution, defensibility, capital, and founder fit. Use when a founder question is too vague to route \u2014 e.g. 'should we grow faster?' \u2014 or before drafting a strategy brief."
},
{
"name": "onboard",
"category": "c-level",
"description": "/cs:onboard \u2014 Founder interview that populates ~/.claude/company-context.md. The first command to run when starting with c-level-agents."
"description": "/cs:onboard \u2014 Founder interview that populates ~/.claude/company-context.md using the canonical 7-dimension cs-onboard schema. The first command to run when starting with c-level-agents. Use when setting up the virtual C-suite for a new company, or when advisors lack company context \u2014 e.g. before a first /cs:boardroom or after a fundraise changes the numbers."
},
{
"name": "org-health-diagnostic",
@ -501,12 +506,12 @@
{
"name": "post-mortem",
"category": "c-level",
"description": "/cs:post-mortem <decision> \u2014 Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop."
"description": "/cs:post-mortem <decision> \u2014 Honest retrospective on an executed decision, scored against original assumptions and dissent. Closes the strategic sprint loop. Use when a decision hits its 90-day review checkpoint or its kill criteria trigger \u2014 e.g. scoring last quarter's pricing change against its pre-committed success metrics."
},
{
"name": "postmortem",
"category": "c-level",
"description": "/em -postmortem \u2014 Honest Analysis of What Went Wrong"
"description": "/em:postmortem \u2014 Honest analysis of what went wrong. Use after a failed launch, missed quarter, or bad hire to run a blameless 5-Whys retrospective with a change register \u2014 e.g. dissecting why the Q3 release slipped six weeks."
},
{
"name": "scenario-war-room",
@ -546,7 +551,7 @@
{
"name": "stress-test",
"category": "c-level",
"description": "/em -stress-test \u2014 Business Assumption Stress Testing"
"description": "/em:stress-test \u2014 Business assumption stress testing. Use before betting on a plan whose core assumptions are unvalidated \u2014 e.g. stress-testing 'enterprise buyers will tolerate a 6-month pilot' or a hockey-stick revenue model."
},
{
"name": "vpe-advisor",
@ -556,7 +561,7 @@
{
"name": "vpe-review",
"category": "c-level",
"description": "/cs:vpe-review <plan> \u2014 Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline."
"description": "/cs:vpe-review <plan> \u2014 Throughput-first VP of Engineering interrogation of any plan that touches delivery, eng hiring, team structure, or production discipline. Use when cycle time balloons, DORA metrics slide, or before committing to an eng hiring wave or a reorg."
},
{
"name": "changelog",
@ -613,6 +618,11 @@
"category": "command",
"description": "Fullstack engineering review \u2014 walks the 7 Matt Pocock forcing questions, picks the profile, forks into POWERFUL specialists (api-design-reviewer, database-designer, slo-architect). Invokes the cs-fullstack-engineer agent with context fork."
},
{
"name": "cs-webinar",
"category": "command",
"description": "/cs:webinar \u2014 Webinar & virtual-event marketing workflow. Plan a webinar from scratch (sized backward from the business goal), rescue one whose numbers disappointed (score the funnel, fix the broken stage), or turn a past webinar into an evergreen on-demand lead engine. Covers the full funnel: registration, promotion runway, show-up, live engagement, live-to-close, and segmented follow-up. Treats a webinar as a funnel, not an event."
},
{
"name": "financial-health",
"category": "command",
@ -661,7 +671,7 @@
{
"name": "prd",
"category": "command",
"description": "Quick PRD generation command. Usage: /prd <feature-or-problem>"
"description": "Gated PRD generation \u2014 interrogates problem, user, and metric before drafting; refuses to draft on unknowns. Usage: /prd <feature-or-problem>"
},
{
"name": "project-health",
@ -701,7 +711,7 @@
{
"name": "sprint-plan",
"category": "command",
"description": "Sprint planning shortcut. Usage: /sprint-plan <goal> [capacity]"
"description": "Capacity-gated sprint planning \u2014 runs capacity math, carry-over check, and a definition-of-ready gate before committing scope. Usage: /sprint-plan <goal> [capacity]"
},
{
"name": "tc",
@ -711,7 +721,7 @@
{
"name": "tdd",
"category": "command",
"description": "Generate tests, analyze coverage, and run TDD workflows. Usage: /tdd <generate|coverage|validate> [options]"
"description": "Run a red-green-refactor TDD workflow \u2014 generate failing tests first, implement to green, then check coverage gaps. Usage: /tdd <generate|coverage|validate> [target]"
},
{
"name": "tech-debt",
@ -751,7 +761,7 @@
{
"name": "channel-economics",
"category": "commercial",
"description": "Use when reviewing or rebalancing direct vs. partner-led channel economics \u2014 computing fully-loaded cost-to-serve per channel, channel ROI with cash / LTV / marginal lenses, and optimal channel mix subject to constraints. For Head of Commercial, RevOps, and VP Sales doing quarterly channel review when pipeline is mixed (e.g., 60% direct + 40% partner-led) and nobody actually knows which channel makes money after CAC, support load, partner discount, deal-velocity differences, retention differential, and overhead allocation are all loaded in. Outputs cost to serve, channel ROI verdicts (DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection. Not channel structure (that's partnerships-architect \u2014 tiers, joint GTM, revshare). Not RevOps process (that's business-growth/revenue-operations \u2014 lead routing, SDR motion). Not strategic CRO judgment (that's c-level-advisor/cro-advisor \u2014 comp plans, when-to-hire-a-VP-Sales). Not historical close-and-report (that's finance/financial-analysis). This skill answers: direct vs partner profitability, channel profitability, channel mix, channel economics."
"description": "Use when reviewing or rebalancing direct vs. partner-led channel economics \u2014 computing fully-loaded cost-to-serve per channel, channel ROI with cash / LTV / marginal lenses, and optimal channel mix subject to constraints. For Head of Commercial, RevOps, and VP Sales doing quarterly channel review when pipeline is mixed (e.g., 60% direct + 40% partner-led) and nobody actually knows which channel makes money after CAC, support load, partner discount, deal-velocity differences, retention differential, and overhead allocation are all loaded in. Outputs cost to serve, channel ROI verdicts (DOUBLE-DOWN / MAINTAIN / DEFUND / EXIT), a sensitivity-tested channel-mix recommendation, and the diminishing-returns inflection (e.g., 'which channel actually makes money \u2014 direct or partner?')."
},
{
"name": "commercial-forecaster",
@ -886,7 +896,7 @@
{
"name": "engineering-skills",
"category": "engineering",
"description": "23 engineering agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365. 30+ Python tools (stdlib-only)."
"description": "Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills \u2014 load only the one specialist SKILL.md you need, never bulk-load the bundle."
},
{
"name": "epic-design",
@ -896,7 +906,7 @@
{
"name": "extract",
"category": "engineering",
"description": "Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples."
"description": "Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples. Use when the user runs /si:extract or asks to package a recurring solution from memory into a skill."
},
{
"name": "fix",
@ -916,7 +926,7 @@
{
"name": "google-workspace-cli",
"category": "engineering",
"description": "Google Workspace administration via the gws CLI. Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. Run security audits, execute 43 built-in recipes, and use 10 persona bundles. Use for Google Workspace admin, gws CLI setup, Gmail automation, Drive management, or Calendar scheduling."
"description": "Google Workspace administration via the gws CLI (github.com/googleworkspace/cli). Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. Run security audits and use local recipe templates and persona bundles. Use for Google Workspace admin, gws CLI setup, Gmail automation, Drive management, or Calendar scheduling."
},
{
"name": "incident-commander",
@ -941,7 +951,7 @@
{
"name": "promote",
"category": "engineering",
"description": "Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude/rules/ for permanent enforcement."
"description": "Graduate a proven pattern from auto-memory (MEMORY.md) to CLAUDE.md or .claude/rules/ for permanent enforcement. Use when the user runs /si:promote or asks to make a learned behavior permanent."
},
{
"name": "pw",
@ -966,7 +976,7 @@
{
"name": "review",
"category": "engineering",
"description": "Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics."
"description": "Analyze auto-memory for promotion candidates, stale entries, consolidation opportunities, and health metrics. Use when the user runs /si:review or asks what has been learned and what should be promoted or pruned."
},
{
"name": "security-pen-testing",
@ -1056,7 +1066,7 @@
{
"name": "skills-status-2",
"category": "engineering",
"description": "Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations."
"description": "Memory health dashboard showing line counts, topic files, capacity, stale entries, and recommendations. Use when the user runs /si:status or asks how full or healthy the agent memory is."
},
{
"name": "snowflake-development",
@ -1091,7 +1101,7 @@
{
"name": "agent-designer",
"category": "engineering-advanced",
"description": "Use when the user asks to design multi-agent systems, create agent architectures, define agent communication patterns, or build autonomous agent workflows."
"description": "Use when the user asks to design a multi-agent system, pick an orchestration pattern (supervisor/swarm/pipeline), generate tool schemas for agents, or evaluate agent execution logs for cost, latency, and failure bottlenecks. Examples: 'design an agent architecture for research automation', 'generate Anthropic tool schemas from these tool descriptions', 'analyze these agent run logs for bottlenecks'. NOT for Claude Code workflow files (use workflow-builder) or single-agent prompt design (use agent-workflow-designer)."
},
{
"name": "agent-workflow-designer",
@ -1126,7 +1136,7 @@
{
"name": "board",
"category": "engineering-advanced",
"description": "Read, write, and browse the AgentHub message board for agent coordination."
"description": "Read, write, and browse the AgentHub message board for agent coordination. Use when the user runs /hub:board or asks to post, read, or inspect coordination messages between competing AgentHub agents."
},
{
"name": "browser-automation",
@ -1141,7 +1151,7 @@
{
"name": "changelog-generator",
"category": "engineering-advanced",
"description": "Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, or automating release notes in CI."
"description": "Produce consistent, auditable release notes from Conventional Commits. Separates commit parsing, semantic-bump logic, and changelog rendering for automated releases with editorial control. Use when cutting a release, generating CHANGELOG.md from git history, computing the next semantic version from commits, automating release notes in CI, or planning a hotfix/rollback. Examples: 'generate the changelog for v1.4.0', 'what version bump do these commits require', 'we need an emergency hotfix process'."
},
{
"name": "chaos-engineering",
@ -1169,14 +1179,14 @@
"description": "Analyze a codebase and generate onboarding documentation for engineers, tech leads, and contractors. Fast fact-gathering and repeatable onboarding outputs. Use when onboarding a new engineer, writing architecture-overview docs for a new project, or producing tech-lead briefings for unfamiliar repos."
},
{
"name": "command-guide",
"name": "collab-proof",
"category": "engineering-advanced",
"description": ">"
"description": "Use when you want to understand what Claude contributed vs what you drove in a session. Triggers on: /collab-proof, session retrospective, ai contribution analysis, collaboration evidence, what did claude do."
},
{
"name": "data-quality-auditor",
"category": "engineering-advanced",
"description": "Audit datasets for completeness, consistency, accuracy, and validity. Profile data distributions, detect anomalies and outliers, surface structural issues, and produce an actionable remediation plan."
"description": "Audit datasets for completeness, consistency, accuracy, and validity. Profile data distributions, detect anomalies and outliers, surface structural issues, and produce an actionable remediation plan. Use when the user asks to check data quality, profile a dataset, hunt outliers or missing values, or validate data before analysis or model training."
},
{
"name": "database-designer",
@ -1196,7 +1206,7 @@
{
"name": "dependency-auditor",
"category": "engineering-advanced",
"description": "Audit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review."
"description": "Audit and manage dependencies across multi-language projects. Identifies vulnerabilities, license conflicts, transitive dependency risks, and safe-upgrade paths. Use when auditing third-party packages before release, investigating a CVE, planning a major version bump, or running a license-compliance review. Examples: 'audit our npm dependencies', 'do we have GPL contamination', 'plan the upgrade to React 19'."
},
{
"name": "docker-development",
@ -1206,7 +1216,7 @@
{
"name": "engineering-advanced-skills",
"category": "engineering-advanced",
"description": "25 advanced engineering agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, release management, platform ops."
"description": "Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Use when browsing or choosing among the POWERFUL-tier engineering skills: agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, changelog/release automation, reliability (SLO/chaos/flags/operators), platform ops."
},
{
"name": "env-secrets-manager",
@ -1216,7 +1226,7 @@
{
"name": "eval",
"category": "engineering-advanced",
"description": "Evaluate and rank agent results by metric or LLM judge for an AgentHub session."
"description": "Evaluate and rank agent results by metric or LLM judge for an AgentHub session. Use when the user runs /hub:eval or asks to score, compare, or pick a winner among completed AgentHub agents."
},
{
"name": "feature-flags-architect",
@ -1256,7 +1266,7 @@
{
"name": "init",
"category": "engineering-advanced",
"description": "Create a new AgentHub collaboration session with task, agent count, and evaluation criteria."
"description": "Create a new AgentHub collaboration session with task, agent count, and evaluation criteria. Use when the user runs /hub:init or asks to start a multi-agent competition on a task."
},
{
"name": "interview-system-designer",
@ -1286,7 +1296,7 @@
{
"name": "loop",
"category": "engineering-advanced",
"description": "Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling."
"description": "Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule."
},
{
"name": "mcp-server-builder",
@ -1296,7 +1306,7 @@
{
"name": "merge",
"category": "engineering-advanced",
"description": "Merge the winning agent's branch into base, archive losers, and clean up worktrees."
"description": "Merge the winning agent's branch into base, archive losers, and clean up worktrees. Use when the user runs /hub:merge or asks to land the winning AgentHub result and tidy the session."
},
{
"name": "migration-architect",
@ -1331,22 +1341,17 @@
{
"name": "rag-architect",
"category": "engineering-advanced",
"description": "Use when the user asks to design RAG pipelines, optimize retrieval strategies, choose embedding models, implement vector search, or build knowledge retrieval systems."
},
{
"name": "release-manager",
"category": "engineering-advanced",
"description": "Use when the user asks to plan releases, manage changelogs, coordinate deployments, create release branches, or automate versioning."
"description": "Use when the user asks to design a RAG pipeline, choose a chunking strategy or embedding model, pick a vector database, or evaluate retrieval quality (precision@k, recall@k, NDCG). Examples: 'design a RAG system for our docs', 'what chunk size should I use for this corpus', 'evaluate my retriever against ground truth'. NOT for general LLM cost tuning (use llm-cost-optimizer) or agent loops over retrieval (use agenthub)."
},
{
"name": "resume",
"category": "engineering-advanced",
"description": "Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating."
"description": "Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:resume or asks to pick up a previously started autoresearch experiment."
},
{
"name": "run",
"category": "engineering-advanced",
"description": "Run a single experiment iteration. Edit the target file, evaluate, keep or discard."
"description": "Run a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration."
},
{
"name": "runbook-generator",
@ -1376,7 +1381,7 @@
{
"name": "setup",
"category": "engineering-advanced",
"description": "Set up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator."
"description": "Set up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop."
},
{
"name": "ship-gate",
@ -1416,7 +1421,7 @@
{
"name": "skills-run",
"category": "engineering-advanced",
"description": "One-shot lifecycle command that chains init \u2192 baseline \u2192 spawn \u2192 eval \u2192 merge in a single invocation."
"description": "One-shot lifecycle command that chains init \u2192 baseline \u2192 spawn \u2192 eval \u2192 merge in a single invocation. Use when the user runs /hub:run or asks to execute a full AgentHub competition end-to-end."
},
{
"name": "skills-slo-architect",
@ -1426,7 +1431,7 @@
{
"name": "skills-status",
"category": "engineering-advanced",
"description": "Show DAG state, agent progress, and branch status for an AgentHub session."
"description": "Show DAG state, agent progress, and branch status for an AgentHub session. Use when the user runs /hub:status or asks how the AgentHub agents are doing."
},
{
"name": "slo-architect",
@ -1436,7 +1441,7 @@
{
"name": "spawn",
"category": "engineering-advanced",
"description": "Launch N parallel subagents in isolated git worktrees to compete on the session task."
"description": "Launch N parallel subagents in isolated git worktrees to compete on the session task. Use when the user runs /hub:spawn or asks to start the competing agents for an initialized AgentHub session."
},
{
"name": "spec-driven-workflow",
@ -1456,7 +1461,7 @@
{
"name": "status",
"category": "engineering-advanced",
"description": "Show experiment dashboard with results, active loops, and progress."
"description": "Show experiment dashboard with results, active loops, and progress. Use when the user runs /ar:status or asks how an autoresearch experiment is going."
},
{
"name": "tc-tracker",
@ -1473,6 +1478,11 @@
"category": "engineering-advanced",
"description": "Terraform infrastructure-as-code agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Covers module design patterns, state management strategies, provider configuration, security hardening, policy-as-code with Sentinel/OPA, and CI/CD plan/apply workflows. Use when: user wants to design Terraform modules, manage state backends, review Terraform security, implement multi-region deployments, or follow IaC best practices."
},
{
"name": "universal-scraping-architect",
"category": "engineering-advanced",
"description": "Use for web scraping, crawling, document extraction, API parsing, or building validation-heavy data pipelines using Firecrawl or local Python scripts."
},
{
"name": "workflow-builder",
"category": "engineering-advanced",
@ -1491,7 +1501,7 @@
{
"name": "finance-skills",
"category": "finance",
"description": "Financial analyst agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Ratio analysis, DCF valuation, budget variance, rolling forecasts. 4 Python tools (stdlib-only)."
"description": "Router/index for the 2 finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts) and saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics')."
},
{
"name": "financial-analyst",
@ -1503,6 +1513,31 @@
"category": "finance",
"description": "SaaS financial health advisor. Use when a user shares revenue or customer numbers, or mentions ARR, MRR, churn, LTV, CAC, NRR, or asks how their SaaS business is doing."
},
{
"name": "design-system",
"category": "markdown-html",
"description": "Captures the user's brand identity once via a 10-question onboarding wizard (primary/accent HEX + heading + body Google Fonts + design style editorial/technical/minimal/playful + default output directory + syntax theme + TOC behavior + optional logo/company), validates body-text and link contrast against WCAG 2.2 AA, derives 12 CSS custom properties in HSL space, and stores the result for every markdown-html converter to consume. Use before any markdown-html conversion. Triggers on first-run onboarding (\"set up the brand\", \"configure markdown-html\", \"run onboarding\"), on explicit reset (\"reset the design system\", \"re-onboard\"), and is checked by every converter via config_loader.py before rendering. Refuses to save if body-text contrast fails AA 4.5:1 or the output dir isn't writable. Precedence: project (./.markdown-html/) > global (~/.config/markdown-html/) > built-in defaults; MARKDOWN_HTML_NO_CONFIG=1 bypasses."
},
{
"name": "markdown-html-orchestrator",
"category": "markdown-html",
"description": "Use when a user wants to convert any markdown file in their Claude project into a single-file, lightly-interactive HTML \u2014 long-form documents (specs, plans, RFCs, reports, explainers), code reviews with diffs and severity-tagged annotations, or slide decks. Triggers on \"convert this markdown to HTML\", \"make this an HTML file\", \"turn this into an interactive document\", \"render this report as HTML\", \"PR writeup as HTML\", \"slides from this markdown\". Forks context to route to one of three converter sub-skills (md-document, md-review, md-slides) based on a deterministic doctype classifier, after the user has run the design-system onboarding once. Refuses if input is under 100 lines (per Shihipar \u2014 markdown still wins below the threshold) or design-system isn't onboarded. Distinct from Anthropic's official Playground plugin (which is interactive prompt-tuning controls with sliders/knobs/prompt-copy-back) and from marketing/landing/ (which is a landing-page generator)."
},
{
"name": "md-document",
"category": "markdown-html",
"description": "Converts long-form markdown (specs, RFCs, reports, plans, explainers) into a single-file, lightly-interactive HTML document with sticky TOC, scrollspy, search filter, code-copy buttons, and design-system-driven brand tokens. Triggers when the markdown-html-orchestrator classifies an input as DOCUMENT, or when invoked directly via /cs:md-document. Reads the design-system config via config_loader.py and inlines the user's 12 derived CSS custom properties; refuses to render if onboarding hasn't run. Single-file output \u2014 Google Fonts + Prism.js CDN are the only externals; no framework runtime, no build step. Use after orchestrator routing or after design-system onboarding is confirmed."
},
{
"name": "md-review",
"category": "markdown-html",
"description": "Converts a markdown PR writeup or code review (one with ```diff fenced blocks and severity-tagged > [!BLOCKER]/[!MAJOR]/[!MINOR]/[!NIT] callouts) into a single-file 2-column HTML review \u2014 unified-diff on the left, severity-tagged annotation cards on the right, top jump-nav listing every finding, mandatory named reviewer footer. Triggers when the markdown-html-orchestrator classifies an input as REVIEW, or when invoked directly via /cs:md-review. Refuses without explicit --reviewer (a code review must name a human), refuses if no diff hunks present (route to md-document instead), and refuses to encode severity in color only (every badge ships color + icon + aria-label per WCAG 1.4.1). Use after orchestrator routing."
},
{
"name": "md-slides",
"category": "markdown-html",
"description": "Converts a markdown deck (slides separated by `"
},
{
"name": "ab-test-setup",
"category": "marketing",
@ -1518,11 +1553,6 @@
"category": "marketing",
"description": "Answer Engine Optimization (AEO) skill \u2014 optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO \u2014 AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers \u2014 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools."
},
{
"name": "ai-seo",
"category": "marketing",
"description": "Optimize content to get cited by AI search engines \u2014 ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Copilot. Use when you want your content to appear in AI-generated answers, not just ranked in blue links. Triggers: 'optimize for AI search', 'get cited by ChatGPT', 'AI Overviews', 'Perplexity citations', 'AI SEO', 'generative search', 'LLM visibility', 'GEO' (generative engine optimization). NOT for traditional SEO ranking (use seo-audit). NOT for content creation (use content-production)."
},
{
"name": "analytics-tracking",
"category": "marketing",
@ -1616,7 +1646,7 @@
{
"name": "marketing-demand-acquisition",
"category": "marketing",
"description": "Creates demand generation campaigns, optimizes paid ad spend across LinkedIn, Google, and Meta, develops SEO strategies, and structures partnership programs for Series A+ startups scaling internationally. Use when planning marketing strategy, growth marketing, advertising campaigns, PPC optimization, lead generation, pipeline generation, or startup marketing budgets. Covers multi-channel acquisition (Google Ads, LinkedIn Ads, Meta Ads), CAC analysis, MQL/SQL workflows, attribution modeling, technical SEO, and co-marketing partnerships for hybrid PLG/Sales-Led motions in EU/US/Canada markets."
"description": "Creates demand generation campaigns, optimizes paid ad spend across LinkedIn, Google, and Meta, develops SEO strategies, and structures partnership programs. Use when planning demand gen strategy, growth marketing, advertising campaigns, PPC optimization, lead generation, pipeline generation, or marketing budgets. Covers multi-channel acquisition (Google Ads, LinkedIn Ads, Meta Ads), CAC analysis, MQL/SQL workflows, attribution modeling, technical SEO, and co-marketing partnerships. Default calibration profile is a Series A+ B2B SaaS scaling internationally (EU/US/Canada, hybrid PLG/Sales-Led) \u2014 adapt benchmarks for other stages and motions rather than skipping the skill."
},
{
"name": "marketing-ideas",
@ -1636,7 +1666,7 @@
{
"name": "marketing-skills",
"category": "marketing",
"description": "42 marketing agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more coding agents. 7 pods: content, SEO, CRO, channels, growth, intelligence, sales. Foundation context + orchestration router. 27 Python tools (stdlib-only)."
"description": "Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill \u2014 it does not execute marketing work itself."
},
{
"name": "marketing-strategy-pmm",
@ -1681,7 +1711,7 @@
{
"name": "prompt-engineer-toolkit",
"category": "marketing",
"description": "Analyzes and rewrites prompts for better AI output, creates reusable prompt templates for marketing use cases (ad copy, email campaigns, social media), and structures end-to-end AI content workflows. Use when the user wants to improve prompts for AI-assisted marketing, build prompt templates, or optimize AI content workflows. Also use when the user mentions 'prompt engineering,' 'improve my prompts,' 'AI writing quality,' 'prompt templates,' or 'AI content workflow.'"
"description": "Turns marketing prompts into tested, versioned production assets: A/B prompt evaluation against structured test cases, immutable prompt version history with diffs, ready-to-use marketing prompt templates (ad copy, email campaigns, social posts, landing pages, SEO meta), and an LLM-governance playbook for marketing teams (claim discipline, disclosure rules, human-review gates). Use when a marketing team relies on AI-generated content and needs prompt quality to be measurable and safe \u2014 or when the user mentions 'prompt engineering,' 'improve my prompts,' 'prompt templates,' 'prompt versioning,' 'AI content workflow,' or 'AI governance for marketing.'"
},
{
"name": "referral-program",
@ -1716,7 +1746,7 @@
{
"name": "social-media-analyzer",
"category": "marketing",
"description": "Social media campaign analysis and performance tracking. Calculates engagement rates, ROI, and benchmarks across platforms. Use for analyzing social media performance, calculating engagement rate, measuring campaign ROI, comparing platform metrics, or benchmarking against industry standards."
"description": "Social media campaign analysis and performance tracking. Calculates engagement rates, ROI, and benchmarks across platforms. Use when analyzing social media performance, calculating engagement rate, measuring campaign ROI, comparing platform metrics, or benchmarking against industry standards. Also use when the user mentions \"social media audit,\" \"engagement rate,\" or \"which platform performs best.\""
},
{
"name": "social-media-manager",
@ -1728,11 +1758,21 @@
"category": "marketing",
"description": "Use when planning video content strategy, writing video scripts, optimizing YouTube channels, building short-form video pipelines (Reels, TikTok, Shorts), or repurposing long-form content into video. Triggers: 'start a YouTube channel', 'video content strategy', 'write a video script', 'repurpose into video', 'YouTube SEO', 'short-form video'. NOT for written blog content (use content-production). NOT for social captions without video (use social-media-manager)."
},
{
"name": "webinar-marketing",
"category": "marketing",
"description": "When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting \u2014 low registrations, low show-up, or attendees who don't buy \u2014 and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) \u2014 this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence)."
},
{
"name": "x-twitter-growth",
"category": "marketing",
"description": "X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search."
},
{
"name": "youtube-full",
"category": "marketing",
"description": "Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos."
},
{
"name": "landing",
"category": "marketing-top-level",
@ -1741,17 +1781,17 @@
{
"name": "agile-product-owner",
"category": "product",
"description": "Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog."
"description": "Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog."
},
{
"name": "apple-hig-expert",
"category": "product",
"description": "Expert guidance on Apple Human Interface Guidelines (HIG). Covers iOS, macOS, and visionOS with 2026 Liquid Glass aesthetics and accessibility-first design."
"description": "Audits and designs iOS/macOS/watchOS/visionOS interfaces against the Apple Human Interface Guidelines, including the Liquid Glass design language (announced WWDC25, shipped with iOS 26/macOS Tahoe, Sept 2025). Use when reviewing an Apple-platform mockup or app for HIG compliance, checking contrast or tap-target sizes, or designing native-feeling Apple UI (e.g., 'audit my iOS app against the HIG', 'is this text readable on Liquid Glass?')."
},
{
"name": "code-to-prd",
"category": "product",
"description": "|"
"description": "Reverse-engineer any codebase into a complete Product Requirements Document (PRD). Analyzes routes, components, state management, API integrations, and user interactions to produce business-readable documentation detailed enough for engineers or AI agents to fully reconstruct every page and endpoint. Works with frontend frameworks (React, Vue, Angular, Svelte, Next.js, Nuxt), backend frameworks (NestJS, Django, Express, FastAPI), and fullstack applications. Use when users mention: generate PRD, reverse-engineer requirements, code to documentation, extract product specs from code, document page logic, analyze page fields and interactions, create a functional inventory, write requirements from an existing codebase, document API endpoints, or analyze backend routes."
},
{
"name": "competitive-teardown",
@ -1781,12 +1821,12 @@
{
"name": "product-manager-toolkit",
"category": "product",
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development."
"description": "Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use when prioritizing features, synthesizing user research, writing requirement documentation, or developing product strategy."
},
{
"name": "product-skills",
"category": "product",
"description": "10 product agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. PM toolkit (RICE), agile PO, product strategist (OKR), UX researcher, UI design system, competitive teardown, landing page generator, SaaS scaffolder, research summarizer. Python tools (stdlib-only)."
"description": "Router/index for the 12 product skills bundled in this plugin (RICE prioritization, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding). Use when a product request doesn't obviously match one skill and you need to pick the right one (e.g., 'help me prioritize features', 'plan a product experiment')."
},
{
"name": "product-strategist",
@ -1816,12 +1856,12 @@
{
"name": "ui-design-system",
"category": "product",
"description": "UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use for creating design systems, maintaining visual consistency, and facilitating design-dev collaboration."
"description": "UI design system toolkit for Senior UI Designer including design token generation, component documentation, responsive design calculations, and developer handoff tools. Use when creating design systems, generating design tokens, maintaining visual consistency, or facilitating design-dev collaboration and developer handoff."
},
{
"name": "ux-researcher-designer",
"category": "product",
"description": "UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use for user research, persona creation, journey mapping, and design validation."
"description": "UX research and design toolkit for Senior UX Designer/Researcher including data-driven persona generation, journey mapping, usability testing frameworks, and research synthesis. Use when conducting user research, creating personas, mapping user journeys, planning usability tests, or validating designs."
},
{
"name": "andreessen",
@ -1846,7 +1886,7 @@
{
"name": "inbox-triage",
"category": "productivity",
"description": "Runs a full inbox triage using the knowledge base created by the 'inbox-setup' skill. Light-intake by design (most invocations skip questions and run with KB-default preferences); asks at most 2 grill-me override questions when invocation is outside normal cadence or includes category-skip intent. Searches recent emails, classifies them via the user's taxonomy, researches new senders, generates recommendations, drafts replies (NEVER sends), delivers a report in the user's preferred format, and updates the knowledge base with learnings. Designed to run on a recurring schedule (1-3x daily) or on demand. Triggers: 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage', or any variation where the user wants their inbox processed. Requires the inbox-setup skill to have been run first."
"description": "Runs a full inbox triage using the knowledge base created by the 'inbox-setup' skill. Light-intake by design (most invocations skip questions and run with KB-default preferences); asks at most 2 grill-me override questions when invocation is outside normal cadence or includes category-skip intent. Searches recent emails, classifies them via the user's taxonomy, researches new senders, generates recommendations, drafts replies (NEVER sends), delivers a report in the user's preferred format, and updates the knowledge base with learnings. Designed to run on a recurring schedule (1-3x daily) or on demand. Use when the user wants their inbox processed, in any variation (e.g., 'triage my inbox', 'inbox triage', 'check my email', 'run email triage', 'process my inbox', 'what's new in my email', 'handle my email', 'email triage'). Requires the inbox-setup skill to have been run first."
},
{
"name": "reflect",
@ -1871,7 +1911,7 @@
{
"name": "jira-expert",
"category": "project-management",
"description": "Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use for Jira project setup, configuration, advanced search, dashboard creation, workflow design, and technical Jira operations."
"description": "Atlassian Jira expert for creating and managing projects, planning, product discovery, JQL queries, workflows, custom fields, automation, reporting, and all Jira features. Use when setting up or configuring Jira projects, writing JQL and advanced searches, creating dashboards, designing workflows, or performing technical Jira operations."
},
{
"name": "meeting-analyzer",
@ -1881,7 +1921,7 @@
{
"name": "pm-skills",
"category": "project-management",
"description": "6 project management agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Senior PM, scrum master, Jira expert (JQL), Confluence expert, Atlassian admin, template creator. MCP integration for live Jira/Confluence automation."
"description": "Router/index for the 8 project-management skills bundled in this plugin (senior PM quant toolkit, scrum master, Jira/JQL, Confluence, Atlassian admin, Atlassian templates, meeting analyzer, team communications). Use when a PM request doesn't obviously match one skill and you need to pick the right one (e.g., 'our sprints feel off', 'audit our Jira permissions'). Bundles an Atlassian Remote MCP config (.mcp.json) for live Jira/Confluence access."
},
{
"name": "scrum-master",
@ -1901,7 +1941,7 @@
{
"name": "capa-officer",
"category": "ra-qm",
"description": "CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use for CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization."
"description": "CAPA system management for medical device QMS. Covers root cause analysis, corrective action planning, effectiveness verification, and CAPA metrics. Use when running CAPA investigations, 5-Why analysis, fishbone diagrams, root cause determination, corrective action tracking, effectiveness verification, or CAPA program optimization."
},
{
"name": "eu-ai-act-specialist",
@ -1911,17 +1951,17 @@
{
"name": "fda-consultant-specialist",
"category": "ra-qm",
"description": "FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QSR (21 CFR 820) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QSR, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity."
"description": "FDA regulatory consultant for medical device companies. Provides 510(k)/PMA/De Novo pathway guidance, QMSR (21 CFR 820, which incorporates ISO 13485:2016 by reference since 2026-02-02; formerly QSR) compliance, HIPAA assessments, and device cybersecurity. Use when user mentions FDA submission, 510(k), PMA, De Novo, QMSR, QSR, ISO 13485 for FDA, premarket, predicate device, substantial equivalence, HIPAA medical device, or FDA cybersecurity."
},
{
"name": "gdpr-dsgvo-expert",
"category": "ra-qm",
"description": "GDPR and German DSGVO compliance automation. Scans codebases for privacy risks, generates DPIA documentation, tracks data subject rights requests. Use for GDPR compliance assessments, privacy audits, data protection planning, DPIA generation, and data subject rights management."
"description": "GDPR and German DSGVO compliance automation. Scans codebases for privacy risks, generates DPIA documentation, tracks data subject rights requests with Art. 12(3) one-month deadlines. Use when running GDPR compliance assessments, privacy audits, data protection planning, DPIA generation, or data subject rights (DSAR) management (e.g., 'check this service for GDPR risks', 'track an access request deadline'). Final compliance determinations route to the DPO or legal counsel."
},
{
"name": "information-security-manager-iso27001",
"category": "ra-qm",
"description": "ISO 27001 ISMS implementation and cybersecurity governance for HealthTech and MedTech companies. Use for ISMS design, security risk assessment, control implementation, ISO 27001 certification, security audits, incident response, and compliance verification. Covers ISO 27001, ISO 27002, healthcare security, and medical device cybersecurity."
"description": "ISO 27001 ISMS implementation and cybersecurity governance for HealthTech and MedTech companies. Use when designing an ISMS, running security risk assessments, implementing controls, pursuing ISO 27001 certification, preparing security audits, responding to security incidents, or verifying compliance. Covers ISO 27001, ISO 27002, healthcare security, and medical device cybersecurity."
},
{
"name": "isms-audit-expert",
@ -1936,22 +1976,22 @@
{
"name": "mdr-745-specialist",
"category": "ra-qm",
"description": "EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, and EUDAMED integration."
"description": "EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Annex VIII classification rules, Annex II/III technical files, Annex XIV clinical evaluation, Art. 86 PSUR schedules, and EUDAMED integration. Use when classifying a medical device under MDR, building or gap-checking a technical file, planning clinical evaluation or PMS/PSUR cadence, or preparing for notified body review (e.g., 'what class is my device under MDR', 'review my PSUR schedule')."
},
{
"name": "qms-audit-expert",
"category": "ra-qm",
"description": "ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use for internal audit planning, audit execution, finding classification, external audit preparation, or audit program management."
"description": "ISO 13485 internal audit expertise for medical device QMS. Covers audit planning, execution, nonconformity classification, and CAPA verification. Use when planning internal audits, executing audits, classifying findings, preparing for external audits, or managing an audit program."
},
{
"name": "quality-documentation-manager",
"category": "ra-qm",
"description": "Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review."
"description": "Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use when working on document control procedures, change control workflows, document numbering, version management, electronic signature compliance, or regulatory documentation review."
},
{
"name": "quality-manager-qmr",
"category": "ra-qm",
"description": "Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2."
"description": "Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2. Use when leading management reviews, setting quality policy and objectives, monitoring quality KPIs and cost of quality, or exercising QMR governance and regulatory oversight responsibilities."
},
{
"name": "quality-manager-qms-iso13485",
@ -1961,7 +2001,7 @@
{
"name": "ra-qm-skills",
"category": "ra-qm",
"description": "12 regulatory & QM agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. ISO 13485 QMS, MDR 2017/745, FDA 510(k)/PMA, ISO 27001 ISMS, GDPR/DSGVO, risk management (ISO 14971), CAPA, document control, auditing. Python tools (stdlib-only)."
"description": "Router/index for the 15 regulatory & quality-management skills bundled in this plugin (ISO 13485 QMS, EU MDR 2017/745, FDA submissions under QMSR, ISO 14971 risk, CAPA, document control, ISO 27001/ISMS, ISO 42001 AIMS, EU AI Act, GDPR/DSGVO, SOC 2, auditing). Use when a compliance request doesn't obviously match one skill and you need to pick the right one (e.g., 'prepare us for an ISO 13485 audit', 'is my AI system high-risk under the AI Act')."
},
{
"name": "regulatory-affairs-head",
@ -1991,42 +2031,42 @@
{
"name": "dossier",
"category": "research",
"description": "Decision-grade entity research skill \u2014 produces a hypothesis-tested dossier on a specific company, person, nonprofit, or government org, not a generic profile. Forcing intake makes the user state their hypothesis upfront (what they already believe and want to verify or disprove) so the dossier tests it rather than confirms it. Output is an editable Word document (.docx) with verdict on the hypothesis, identity facts, 12-month activity timeline, network signals, reputation signals, red flags, 3-5 conversation hooks tied to specific findings, and source-provenance audit log. Uses WebSearch + WebFetch + free APIs (SEC EDGAR, GitHub, ProPublica Nonprofit Explorer) as workhorses; optional BYOK MCPs (LinkedIn, Crunchbase, Apollo, Pitchbook, SimilarWeb) enhance coverage. Triggers: 'research [company]', 'dossier on [person/company]', 'background check on [entity]', 'prep me for a meeting with [person/company]', 'due diligence on [company]', 'what should I know about [entity]', 'research [person] before I [meet/hire/invest]', 'competitor research on [company]', 'investor diligence [company]', 'interview prep for [company]'. Honors sensitivity exclusions for journalism + personal-vetting contexts."
"description": "Decision-grade entity research skill \u2014 produces a hypothesis-tested dossier on a specific company, person, nonprofit, or government org, not a generic profile. Forcing intake makes the user state their hypothesis upfront (what they already believe and want to verify or disprove) so the dossier tests it rather than confirms it. Output is an editable Word document (.docx) with verdict on the hypothesis, identity facts, 12-month activity timeline, network and reputation signals, red flags, conversation hooks tied to specific findings, and source-provenance audit log. Uses WebSearch + WebFetch + free APIs (SEC EDGAR, GitHub, ProPublica) as workhorses; optional BYOK MCPs enhance coverage. Use when the user asks for background research, diligence, or meeting prep on a specific entity (e.g., 'prep me for a meeting with [person/company]', 'due diligence on [company]'). Honors sensitivity exclusions for journalism + personal-vetting contexts."
},
{
"name": "grants",
"category": "research",
"description": "NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Triggers: 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research', or any grant-related request. NIH-only scope \u2014 non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake."
"description": "NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance/Innovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget/scope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope \u2014 non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake."
},
{
"name": "litreview",
"category": "research",
"description": "Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a professionally formatted Word document (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' \u2014 not a finished review, but an orientation guide that lets a researcher dive in confidently. Triggers: 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'. Do NOT trigger for single one-off paper searches where the user just wants a quick list \u2014 that's a plain Consensus search."
"description": "Academic literature orientation skill that searches papers via Consensus, builds a strategic search plan using PICO (default) or SPIDER / Decomposition / hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5/10/20 queries) controls coverage vs. speed. Output is a 'launching pad' \u2014 an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list \u2014 that's a plain Consensus search."
},
{
"name": "notebooklm",
"category": "research",
"description": "Browser automation skill for controlling Google's NotebookLM. Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio Overview, infographics, slide decks, study guides, briefing docs, mind maps, timelines, FAQs), and creating new notebooks. Triggers on any phrase involving NotebookLM \u2014 'open NotebookLM', 'check my [name] notebook', 'pull info from NotebookLM', 'ask my notebook about X', 'add [source] to NotebookLM', 'create an infographic in NotebookLM', 'use NotebookLM Studio', 'generate a slide deck from my notebook', or any variation where the goal involves NotebookLM. Requires browser automation environment \u2014 fails gracefully when unavailable."
"description": "Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio/Video Overviews, Mind Maps, Reports incl. Briefing Doc/Study Guide/FAQ, Flashcards, Quiz, slide decks, infographics \u2014 discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment \u2014 fails gracefully when unavailable."
},
{
"name": "patent",
"category": "research",
"description": "Patent prior-art and landscape intelligence skill \u2014 not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Triggers: 'prior art search for [invention]', 'patent search on [topic]', 'freedom to operate analysis', 'FTO for [product]', 'patent landscape for [field]', 'is [invention] novel', 'patents on [topic]', 'competitive patent analysis', 'prior art for litigation', 'patent diligence on [company]'. Produces search signal, not legal advice \u2014 always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope."
"description": "Patent prior-art and landscape intelligence skill \u2014 not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice \u2014 always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope."
},
{
"name": "pulse",
"category": "research",
"description": "Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Triggers: 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]', or any variation requesting multi-source recency intelligence on a topic. Also use for competitor research, trend discovery, tool comparisons, and audience sentiment analysis."
"description": "Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X/Twitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend/sentiment/problems/opportunities/comparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis."
},
{
"name": "research-bundle",
"category": "research",
"description": "Default entry point for any research request \u2014 a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Triggers \u2014 \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\", or any research request that doesn't obviously match a more-specific specialist skill. Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log."
"description": "Default entry point for any research request \u2014 a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends/sentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log."
},
{
"name": "syllabus",
"category": "research",
"description": "Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs \u2014 so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Triggers whenever a user uploads a syllabus, course outline, or curriculum document and wants supplementary readings. Also triggers on: 'syllabus reading list', 'find papers for my course', 'create a reading list from this syllabus', 'recent research for my class', 'supplementary readings', 'find journal articles for these topics', 'what recent papers cover this material', 'any new research on these course topics', 'update my syllabus with recent papers'. Even casual mentions when a syllabus is attached should trigger this skill."
"description": "Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs \u2014 so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') \u2014 even casual mentions with a syllabus attached should trigger this skill."
},
{
"name": "clinical-research",
@ -2056,7 +2096,7 @@
],
"categories": {
"agent": {
"count": 33,
"count": 34,
"description": "Agent resources"
},
"business-growth": {
@ -2072,7 +2112,7 @@
"description": "C-level resources"
},
"command": {
"count": 38,
"count": 39,
"description": "Command resources"
},
"commercial": {
@ -2095,8 +2135,12 @@
"count": 4,
"description": "Finance resources"
},
"markdown-html": {
"count": 5,
"description": "Markdown-html resources"
},
"marketing": {
"count": 46,
"count": 47,
"description": "Marketing resources"
},
"marketing-top-level": {

1
.gemini/skills/ai-seo/SKILL.md
View file

@ -1 +0,0 @@
../../../marketing-skill/skills/ai-seo/SKILL.md

1
.gemini/skills/collab-proof/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../engineering/collab-proof/skills/collab-proof/SKILL.md

1
.gemini/skills/command-guide/SKILL.md
View file

@ -1 +0,0 @@
../../../engineering/skills/command-guide/SKILL.md

1
.gemini/skills/cs-webinar-marketer/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../agents/marketing/cs-webinar-marketer.md

1
.gemini/skills/cs-webinar/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../commands/cs-webinar.md

1
.gemini/skills/design-system/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../markdown-html/skills/design-system/SKILL.md

1
.gemini/skills/markdown-html-orchestrator/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../markdown-html/skills/markdown-html-orchestrator/SKILL.md

1
.gemini/skills/md-document/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../markdown-html/skills/md-document/SKILL.md

1
.gemini/skills/md-review/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../markdown-html/skills/md-review/SKILL.md

1
.gemini/skills/md-slides/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../markdown-html/skills/md-slides/SKILL.md

1
.gemini/skills/release-manager/SKILL.md
View file

@ -1 +0,0 @@
../../../engineering/skills/release-manager/SKILL.md

1
.gemini/skills/universal-scraping-architect/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../engineering/universal-scraping-architect/skills/universal-scraping-architect/SKILL.md

1
.gemini/skills/webinar-marketing/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../marketing-skill/skills/webinar-marketing/SKILL.md

1
.gemini/skills/youtube-full/SKILL.md Symbolic link
View file

@ -0,0 +1 @@
../../../marketing-skill/skills/youtube-full/SKILL.md

39
.github/workflows/ci-quality-gate.yml vendored
View file

@ -77,15 +77,48 @@ jobs:
- name: Python syntax check (blocking)
run: |
# Covers every top-level skill domain + scripts/. When adding a new
# domain folder, add it here (audit gate G9: this list previously
# skipped 8 post-v2.7 domains).
python -m compileall \
marketing-skill product-team c-level-advisor \
engineering-team ra-qm-team engineering \
business-growth finance project-management scripts
business-growth finance project-management \
productivity marketing research \
business-operations commercial research-ops \
compliance-os markdown-html scripts
- name: Validate plugin.json manifests (blocking — guards #539 + #686)
run: |
python scripts/check_plugin_json.py --all
# ---- Audit guardrails (newgen-2026-06 gates) ----------------------
# BLOCKING since PR-2 (flipped ahead of the 2026-07-01 SLA — every
# advisory run was green through PR #835). If a gate misfires on a
# legitimate edge case, extend its in-repo allowlist
# (scripts/check_paths_allowlist.txt, scripts/smoke_exceptions.txt)
# rather than re-adding continue-on-error.
- name: Path-existence linter (gate G1 — blocking)
run: |
python3 scripts/check_paths.py --all
- name: Dual-publish drift guard (gate G4 — blocking)
run: |
python3 scripts/check_dual_publish.py
- name: Script --help smoke gate (gate G8 — blocking)
run: |
python3 scripts/smoke_scripts.py
- name: JSON-output sample gate (gate G9 — advisory)
continue-on-error: true
run: |
python3 scripts/smoke_json_output.py
- name: Counter derivation check (gate G3 — blocking)
run: |
python3 scripts/derive_counters.py --check
- name: Safety dependency audit (requirements*.txt)
run: |
set -e
@ -96,7 +129,9 @@ jobs:
fi
for f in $files; do
echo "Auditing $f"
safety check --full-report --file "$f" || true
if ! safety check --full-report --file "$f"; then
echo "::warning file=$f::safety found vulnerabilities in $f (advisory)"
fi
done
- name: Markdown link spot-check

66
.github/workflows/enforce-pr-target.yml vendored
View file

@ -3,7 +3,7 @@ name: Enforce PR Target Branch
on:
pull_request_target:
types: [opened]
types: [opened, edited, ready_for_review]
branches: [main]
permissions:
@ -13,45 +13,63 @@ jobs:
check-target:
runs-on: ubuntu-latest
steps:
- name: Block PRs targeting main from non-maintainers
- name: Block PRs targeting main (only dev -> main promotion allowed)
uses: actions/github-script@v7
with:
script: |
const pr = context.payload.pull_request;
const author = pr.user.login;
const headRef = pr.head.ref;
const sameRepo = pr.head.repo.full_name === context.payload.repository.full_name;
// Maintainers who can PR to main directly
const maintainers = ['alirezarezvani'];
if (maintainers.includes(author)) {
console.log(`✅ ${author} is a maintainer — PR to main allowed.`);
// HARD RULE (CLAUDE.md > Git Workflow): main only receives
// dev -> main promotion PRs. Branch-based, not author-based —
// maintainers are not exempt.
if (sameRepo && headRef === 'dev') {
console.log(`✅ dev -> main promotion PR — allowed.`);
return;
}
const message = `👋 Hi @${author}, thanks for your contribution!
// Maintainers: fail the check and explain, but don't auto-close
// (avoids nuking intentional work; retarget instead).
const maintainers = ['alirezarezvani'];
const isMaintainer = maintainers.includes(author);
All community PRs should target the \`dev\` branch, not \`main\`. The \`main\` branch is reserved for releases.
const nextStep = isMaintainer
? 'This check will re-run automatically once the base branch is changed.'
: 'This PR has been closed automatically; reopen it after retargeting, ' +
'or open a new PR against `dev`.';
**How to fix:**
1. Close this PR
2. Reopen it targeting \`dev\` instead of \`main\`
Or I can do it for you — just click "Edit" at the top right of this PR and change the base branch to \`dev\`.
See our [Contributing Guide](https://github.com/alirezarezvani/claude-skills/blob/dev/CONTRIBUTING.md) for details.`;
const message = [
`👋 Hi @${author}, thanks for your contribution!`,
'',
'All PRs must target the `dev` branch, not `main`. The `main` branch',
'only receives `dev -> main` promotion PRs (see CLAUDE.md > Git Workflow).',
'',
'**How to fix:** click "Edit" at the top right of this PR and change',
'the base branch to `dev`.',
'',
nextStep,
'',
'See our [Contributing Guide]' +
'(https://github.com/alirezarezvani/claude-skills/blob/dev/CONTRIBUTING.md)' +
' for details.',
].join('\n');
await github.rest.issues.createComment({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: pr.number,
body: message.split('\n').map(l => l.trim()).join('\n'),
body: message,
});
await github.rest.pulls.update({
owner: context.repo.owner,
repo: context.repo.repo,
pull_number: pr.number,
state: 'closed',
});
if (!isMaintainer) {
await github.rest.pulls.update({
owner: context.repo.owner,
repo: context.repo.repo,
pull_number: pr.number,
state: 'closed',
});
}
core.setFailed(`PR #${pr.number} targets main. Closed automatically.`);
core.setFailed(`PR #${pr.number} targets main from '${headRef}' (not dev). ${isMaintainer ? 'Retarget to dev.' : 'Closed automatically.'}`);

1
.hermes/skills/claude-skills/engineering/command-guide
View file

@ -1 +0,0 @@
../../../../engineering/skills/command-guide

1
.hermes/skills/claude-skills/engineering/release-manager
View file

@ -1 +0,0 @@
../../../../engineering/skills/release-manager

1
.hermes/skills/claude-skills/marketing-skill/ai-seo
View file

@ -1 +0,0 @@
../../../../marketing-skill/skills/ai-seo

1
.vibe/skills/claude-skills/engineering/command-guide
View file

@ -1 +0,0 @@
../../../../engineering/skills/command-guide

1
.vibe/skills/claude-skills/engineering/release-manager
View file

@ -1 +0,0 @@
../../../../engineering/skills/release-manager

1
.vibe/skills/claude-skills/marketing-skill/ai-seo
View file

@ -1 +0,0 @@
../../../../marketing-skill/skills/ai-seo

17
CHANGELOG.md
View file

@ -5,6 +5,23 @@ All notable changes to the Claude Skills Library will be documented in this file
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased] — newgen audit follow-up: P0 fixes, path sweep, CI guards
### Deprecated / Removed Skills (migration notes)
Three skills were retired or merged in the newgen-audit follow-up (PR #835). If
you installed or pinned any of these, migrate as follows:
| Removed skill | Why | Migrate to |
|---|---|---|
| `engineering/skills/command-guide` | Documented a different repository's commands and agents; instructed models to invoke agents that don't exist here | No replacement needed — the root `commands/` folder and each plugin's own commands are the canonical command surface |
| `marketing-skill/skills/ai-seo` | Near-total overlap with the newer, tool-backed AEO skill | `marketing-skill/skills/aeo` — unique ai-seo content was preserved in `aeo/references/bot_access_and_monitoring.md` and `aeo/references/extractable_content_patterns.md` |
| `engineering/skills/release-manager` | 489-line SemVer/Git-Flow textbook duplicating changelog-generator; its readiness checker crashed | `engineering/skills/changelog-generator` — now includes `version_bumper.py`, hotfix/rollback procedures, and the severity-SLA table. For release-readiness audits use `engineering/skills/ship-gate` |
Also restructured (no content change): `engineering/universal-scraping-architect`
moved its SKILL.md from plugin root to the standard `skills/universal-scraping-architect/`
layout. Marketplace source path is unchanged.
## [Unreleased] — code-reviewer: C-specific smell detector + fixtures
### Added — language-specific smell pack for C (this PR)

24
CLAUDE.md
View file

@ -6,7 +6,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
This is a **comprehensive skills library** for Claude AI and Claude Code - reusable, production-ready skill packages that bundle domain expertise, best practices, analysis tools, and strategic frameworks. The repository provides modular skills that teams can download and use directly in their workflows.
**Current Scope:** 338 production-ready skills across 16 domains with 533 Python automation tools, 676 reference guides, 51+ agents (cs-* + 7 personas), and 87+ slash commands, distributed as 62 marketplace plugins. **v2.9.0 (complete)** added the **research-ops/** top-level domain — enterprise Research Operations (orchestrator + clinical-research + research-finance + market-research + product-research), the managed counterpart to the academic research/ domain, with `context: fork` orchestration and a Matt Pocock "Forcing-question library" in every SKILL.md plus `/cs:grill-research-ops`. **v2.8.0 (complete)** added 2 new top-level domains — **business-operations/** (7 internal-ops skills: orchestrator + process-mapper + vendor-management + capacity-planner + internal-comms + knowledge-ops + procurement-optimizer) and **commercial/** (8 per-deal-economics skills: orchestrator + pricing-strategist + deal-desk + partnerships-architect + channel-economics + commercial-policy + rfp-responder + commercial-forecaster) — with orchestrator skills using `context: fork` for chaining, Matt Pocock docs-anchored "Forcing-question library" in every SKILL.md, plus `/cs:grill-bizops` and `/cs:grill-commercial`. **v2.8.2** adds a productivity-shaped `handoff` skill (sibling to engineering/handoff) inspired by Matt Pocock — first-run setup with configurable save location, redaction linter, SessionStart + SessionEnd hooks, fidelity self-check, `--refresh` flag. **v2.8.1** upgraded the engineering role-skills (senior-fullstack / senior-frontend / senior-backend) with karpathy-coder + Matt Pocock decision engines + per-role forcing questions. v2.7.3 ports `alirezarezvani/aeo-box` — AEO (Answer Engine Optimization) skill into marketing-skill/ + security-guidance PreToolUse hook into engineering/. v2.7.0 added 13 Path-B skills across 3 top-level domains (productivity, marketing, research). v2.6.0 added 4 Matt Pocock-derived productivity skills.
**Current Scope:** 345 production-ready skills across 17 domains with 579 Python automation tools, 702 reference guides, 93 agents (cs-* + 7 personas), and 99 slash commands, distributed as 78 marketplace plugins. Headline counters are derived from the tree by `scripts/derive_counters.py` (run with `--check` to verify the docs still match). **v2.9.0 (complete)** added the **research-ops/** top-level domain — enterprise Research Operations (orchestrator + clinical-research + research-finance + market-research + product-research), the managed counterpart to the academic research/ domain, with `context: fork` orchestration and a Matt Pocock "Forcing-question library" in every SKILL.md plus `/cs:grill-research-ops`. **v2.8.0 (complete)** added 2 new top-level domains — **business-operations/** (7 internal-ops skills: orchestrator + process-mapper + vendor-management + capacity-planner + internal-comms + knowledge-ops + procurement-optimizer) and **commercial/** (8 per-deal-economics skills: orchestrator + pricing-strategist + deal-desk + partnerships-architect + channel-economics + commercial-policy + rfp-responder + commercial-forecaster) — with orchestrator skills using `context: fork` for chaining, Matt Pocock docs-anchored "Forcing-question library" in every SKILL.md, plus `/cs:grill-bizops` and `/cs:grill-commercial`. **v2.8.2** adds a productivity-shaped `handoff` skill (sibling to engineering/handoff) inspired by Matt Pocock — first-run setup with configurable save location, redaction linter, SessionStart + SessionEnd hooks, fidelity self-check, `--refresh` flag. **v2.8.1** upgraded the engineering role-skills (senior-fullstack / senior-frontend / senior-backend) with karpathy-coder + Matt Pocock decision engines + per-role forcing questions. v2.7.3 ports `alirezarezvani/aeo-box` — AEO (Answer Engine Optimization) skill into marketing-skill/ + security-guidance PreToolUse hook into engineering/. v2.7.0 added 13 Path-B skills across 3 top-level domains (productivity, marketing, research). v2.6.0 added 4 Matt Pocock-derived productivity skills.
**Key Distinction**: This is NOT a traditional application. It's a library of skill packages meant to be extracted and deployed by users into their own Claude workflows.
@ -21,6 +21,13 @@ The following exist on the maintainer's disk but are excluded from the public Gi
- `.autoresearch/` — autoresearch agent workspace
- `AUDIT_REPORT.md` — internal audit snapshots
**Distinct from the above:** the top-level `audit/` directory (e.g.
`audit/newgen-2026-06/`) is an **intentional, public** audit record — rubric +
per-domain reports with per-skill verification criteria that follow-up PRs use
as acceptance gates. It is excluded from headline counters by
`scripts/derive_counters.py`, but it is committed and visible to cloners.
`AUDIT_REPORT.md` (gitignored, above) is the older internal-snapshot format.
In-repo references to paths under these folders (e.g. `documentation/implementation/...`) resolve locally for the maintainer but appear as dead links on GitHub. This is intentional.
## Navigation Map
@ -95,6 +102,13 @@ skill-name/
**Branch Strategy:** feature → dev → main (PR only)
> **⛔ HARD RULE — PR TARGET IS ALWAYS `dev`, NEVER `main`.**
> Every PR (human or AI-created) must use `--base dev`. Nothing merges into `main`
> directly — `main` only receives periodic `dev → main` promotion PRs opened by the
> maintainer. If you find a PR targeting `main`, retarget it to `dev` before review.
> AI agents (Claude Code included): set the base branch explicitly when creating PRs;
> never rely on the repository default branch.
**Branch Protection Active:** Main branch requires PR approval. Direct pushes blocked.
### Quick Start
@ -159,7 +173,7 @@ Completes the `markdown-html/` domain at 5 skills. The Tier-3 use case from Shih
- **1 template asset** documenting the canonical single-file deck shape.
- **`/cs:md-slides` slash command** with 6 pre-flight gates + pipeline + output digest.
- **Empirical footprint**: 5-slide sample deck (3 with presenter notes) → 12.2 KB single-file HTML with keyboard nav + presenter mode + print-to-PDF. By comparison, equivalent Google Slides / Keynote / reveal.js multi-file exports are 200 KB+ of CSS/JS chrome.
- **Plugin manifest:** `markdown-html-skills` plugin.json `skills` array now lists 5 paths (orchestrator + design-system + md-document + md-review + md-slides). Marketplace counters updated: 64 plugins, 17 domains, **343 skills**, **548 Python tools**, **691 references**, **90+ slash commands**.
- **Plugin manifest:** `markdown-html-skills` plugin.json `skills` array now lists 5 paths (orchestrator + design-system + md-document + md-review + md-slides). Marketplace counters updated (trued up 2026-06-10 via `scripts/derive_counters.py`): 77 plugins, 17 domains, **345 skills**, **579 Python tools**, **702 references**, **99 slash commands**.
- **Domain status: COMPLETE.** All 5 planned skills shipped across 4 PRs (#780 foundation, #793 md-document, #795 md-review, this PR md-slides). The markdown-html/ domain operationalizes Shihipar's central claim — markdown collapses past 100 lines; HTML restores density, clarity, shareability, and lightweight interaction — across all three layout families (long-form documents, code reviews, slide decks).
---
@ -510,6 +524,6 @@ This repository publishes skills to **ClawHub** (clawhub.com) as the distributio
---
**Last Updated:** May 27, 2026
**Version:** v2.9.0
**Status:** 338 skills deployed across 16 domains, 62 marketplace plugins, docs site live
**Last Updated:** June 10, 2026
**Version:** v2.10.3
**Status:** 345 skills deployed across 17 domains, 78 marketplace plugins, docs site live (counters derived via `scripts/derive_counters.py`)

27
README.md
View file

@ -1,6 +1,6 @@
# Claude Code Skills & Plugins — Agent Skills for Every Coding Tool
**338 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools.**
**345 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools.**
The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 9 more coding agents. Reusable expertise packages covering engineering, DevOps, marketing (incl. AEO — Answer Engine Optimization for LLM citation), security (PreToolUse hooks), compliance, C-level advisory (incl. founder-mode CFO/CMO/CRO/CPO/COO/CHRO/CISO/GC/CDO/CAIO/CCO/VPE personas + 21 /cs:* slash commands), productivity (capture/email/reflect), an academic research stack (litreview/grants/dossier/patent/syllabus/pulse/notebooklm + hybrid router), and enterprise Research Operations (clinical-research/research-finance/market-research/product-research, v2.9.0).
@ -10,10 +10,10 @@ The most comprehensive open-source library of Claude Code skills and agent plugi
[^vibe]: Mistral Vibe is also **BYO-sync tier**: the repo ships a pre-generated `.vibe/skills/claude-skills/` tree, run `./scripts/vibe-install.sh` once locally to install into `~/.vibe/skills/`. Same agentskills.io SKILL.md standard — no format conversion. Docs: <https://docs.mistral.ai/mistral-vibe/agents-skills>.
[![License: MIT](https://img.shields.io/badge/License-MIT-yellow?style=for-the-badge)](https://opensource.org/licenses/MIT)
[![Skills](https://img.shields.io/badge/Skills-338-brightgreen?style=for-the-badge)](#skills-overview)
[![Agents](https://img.shields.io/badge/Agents-51+-blue?style=for-the-badge)](#agents)
[![Skills](https://img.shields.io/badge/Skills-346-brightgreen?style=for-the-badge)](#skills-overview)
[![Agents](https://img.shields.io/badge/Agents-93-blue?style=for-the-badge)](#agents)
[![Personas](https://img.shields.io/badge/Personas-7-purple?style=for-the-badge)](#personas)
[![Commands](https://img.shields.io/badge/Commands-87+-orange?style=for-the-badge)](#commands)
[![Commands](https://img.shields.io/badge/Commands-99-orange?style=for-the-badge)](#commands)
[![Stars](https://img.shields.io/github/stars/alirezarezvani/claude-skills?style=for-the-badge)](https://github.com/alirezarezvani/claude-skills/stargazers)
[![SkillCheck Validated](https://img.shields.io/badge/SkillCheck-Validated-4c1?style=for-the-badge)](https://getskillcheck.com)
@ -26,10 +26,10 @@ The most comprehensive open-source library of Claude Code skills and agent plugi
Claude Code skills (also called agent skills or coding agent plugins) are modular instruction packages that give AI coding agents domain expertise they don't have out of the box. Each skill includes:
- **SKILL.md** — structured instructions, workflows, and decision frameworks
- **Python tools** — 533 CLI scripts (all stdlib-only, zero pip installs)
- **Reference docs** — 676 templates, checklists, and domain-specific knowledge files
- **Python tools** — 579 CLI scripts (all stdlib-only, zero pip installs)
- **Reference docs** — 702 templates, checklists, and domain-specific knowledge files
**One repo, thirteen platforms.** Works natively as Claude Code plugins, Codex agent skills, Gemini CLI skills, Hermes Agent skills, Mistral Vibe skills, and converts to more tools via `scripts/convert.sh`. All 533 Python tools run anywhere Python runs.
**One repo, thirteen platforms.** Works natively as Claude Code plugins, Codex agent skills, Gemini CLI skills, Hermes Agent skills, Mistral Vibe skills, and converts to more tools via `scripts/convert.sh`. All 579 Python tools run anywhere Python runs.
### Skills vs Agents vs Personas
@ -108,7 +108,7 @@ git clone https://github.com/alirezarezvani/claude-skills.git
## Multi-Tool Support (New)
**Convert all 338 skills to 9 AI coding tools** with a single script:
**Convert all 345 skills to 9 AI coding tools** with a single script:
| Tool | Format | Install |
|------|--------|---------|
@ -135,11 +135,11 @@ git clone https://github.com/alirezarezvani/claude-skills.git
./scripts/install.sh --tool aider --target . --force
# 3. Verify
find .cursor/rules -name "*.mdc" | wc -l # Should show 338
find .cursor/rules -name "*.mdc" | wc -l # Should show 346
```
**Each tool gets:**
- ✅ All 338 skills converted to native format
- ✅ All 345 skills converted to native format
- ✅ Per-tool README with install/verify/update steps
- ✅ Support for scripts, references, templates where applicable
- ✅ Zero manual conversion work
@ -150,7 +150,7 @@ Run `./scripts/convert.sh --tool all` to generate tool-specific outputs locally.
## Skills Overview
**338 skills across 16 domains:**
**345 skills across 17 domains:**
| Domain | Skills | Highlights | Details |
|--------|--------|------------|---------|
@ -239,7 +239,6 @@ See [orchestration/ORCHESTRATION.md](orchestration/ORCHESTRATION.md) for the ful
| **api-design-reviewer** | REST API linter, breaking change detector, design scorecard |
| **api-test-suite-builder** | Scan API routes → generate complete test suites |
| **dependency-auditor** | Multi-language scanner, license compliance, upgrade planner |
| **release-manager** | Changelog generator, semantic version bumper, readiness checker |
| **observability-designer** | SLO designer, alert optimizer, dashboard generator |
| **performance-profiler** | Node/Python/Go profiling, bundle analysis, load testing |
| **monorepo-navigator** | Turborepo/Nx/pnpm workspace management & impact analysis |
@ -306,7 +305,7 @@ for MDR Annex II compliance gaps.
## Python Analysis Tools
533 CLI tools ship with the skills (all verified, stdlib-only):
579 CLI tools ship with the skills (all verified, stdlib-only):
```bash
# SaaS health check
@ -353,7 +352,7 @@ Yes. Skills work natively with 13 tools: Claude Code, OpenAI Codex, Gemini CLI,
No. We follow semantic versioning and maintain backward compatibility within patch releases. Existing script arguments, plugin source paths, and SKILL.md structures are never changed in patch versions. See the [CHANGELOG](CHANGELOG.md) for details on each release.
**Are the Python tools dependency-free?**
Yes. All 533 Python CLI tools use the standard library only — zero pip installs required. Every script is verified to run with `--help`.
Yes. All 579 Python CLI tools use the standard library only — zero pip installs required. Every script is verified to run with `--help`.
**How do I create my own Claude Code skill?**
Each skill is a folder with a `SKILL.md` (frontmatter + instructions), optional `scripts/`, `references/`, and `assets/`. See the [Skills & Agents Factory](https://github.com/alirezarezvani/claude-code-skills-agents-factory) for a step-by-step guide.

48
agents/CLAUDE.md
View file

@ -1,13 +1,13 @@
# Agent Development Guide
This guide provides comprehensive instructions for creating **cs-* prefixed agents** that seamlessly integrate with the 42 production skills in this repository.
This guide provides comprehensive instructions for creating **cs-* prefixed agents** that seamlessly integrate with the 346 production skills in this repository (count derived via `scripts/derive_counters.py`).
## Agent Architecture
### What are cs-* Agents?
**cs-* agents** are specialized Claude Code agents that orchestrate the 177 existing skills. Each agent:
- References skills via relative paths (`../../marketing-skill/`)
**cs-* agents** are specialized Claude Code agents that orchestrate the repository's 346 skills. Each agent:
- References skills via relative paths (`../marketing-skill/`)
- Executes Python automation tools from skill packages
- Follows established workflows and templates
- Maintains skill portability and independence
@ -24,7 +24,7 @@ When skills are published to **ClawHub** (clawhub.com):
### Production Agents
**16 Agents Currently Available**:
**33 agents live in this folder** (93 agent files repo-wide, including plugin-bundled agents). A representative selection:
| Agent | Domain | Description |
|-------|--------|-------------|
@ -108,17 +108,17 @@ After YAML frontmatter, include these sections:
All skill references use the `../../` pattern:
```markdown
**Skill Location:** `../../marketing-skill/content-creator/`
**Skill Location:** `../marketing-skill/skills/content-creator/`
### Python Tools
1. **Brand Voice Analyzer**
- **Path:** `../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py`
- **Usage:** `python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py content.txt`
- **Path:** `../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py`
- **Usage:** `python ../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py content.txt`
2. **SEO Optimizer**
- **Path:** `../../marketing-skill/content-creator/scripts/seo_optimizer.py`
- **Usage:** `python ../../marketing-skill/content-creator/scripts/seo_optimizer.py article.md "keyword"`
- **Path:** `../marketing-skill/skills/content-production/scripts/seo_optimizer.py`
- **Usage:** `python ../marketing-skill/skills/content-production/scripts/seo_optimizer.py article.md "keyword"`
```
### Why `../../`?
@ -138,13 +138,13 @@ Agents execute Python tools from skill packages:
```bash
# From agent context
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py input.txt
python ../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py input.txt
# With JSON output
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py input.txt json
python ../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py input.txt json
# With arguments
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
python ../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
```
### Tool Requirements
@ -188,7 +188,7 @@ Each workflow must include:
**Example:**
\`\`\`bash
# Concrete example command
python ../../marketing-skill/content-creator/scripts/seo_optimizer.py article.md "primary keyword"
python ../marketing-skill/skills/content-production/scripts/seo_optimizer.py article.md "primary keyword"
\`\`\`
```
@ -278,12 +278,12 @@ python ../../domain-skill/skill-name/scripts/tool.py input.txt
## Related Agents
- [cs-related-agent](../domain/cs-related-agent.md) - How they relate
- [cs-related-agent](../<domain>/cs-related-agent.md) - How they relate
## References
- [Skill Documentation](../../domain-skill/skill-name/SKILL.md)
- [Domain Roadmap](../../domain-skill/roadmap.md)
- [Domain Roadmap](../../<domain-skill>/roadmap.md)
```
## Quality Standards
@ -311,7 +311,7 @@ Test these aspects:
```bash
# From agent directory
cd agents/marketing/
ls ../../marketing-skill/content-creator/ # Should list contents
ls ../marketing-skill/skills/content-creator/ # Should list contents
```
**2. Python Tool Execution**
@ -320,7 +320,7 @@ ls ../../marketing-skill/content-creator/ # Should list contents
echo "Test content" > test-input.txt
# Execute tool
python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py test-input.txt
python ../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py test-input.txt
# Verify output
```
@ -328,29 +328,29 @@ python ../../marketing-skill/content-creator/scripts/brand_voice_analyzer.py tes
**3. Knowledge Base Access**
```bash
# Verify reference files exist
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
cat ../marketing-skill/skills/content-creator/references/brand_guidelines.md
```
## Domain-Specific Guidelines
### Marketing Agents (agents/marketing/)
- Focus on content creation, SEO, demand generation
- Reference: `../../marketing-skill/`
- Reference: `../marketing-skill/`
- Tools: brand_voice_analyzer.py, seo_optimizer.py
### Product Agents (agents/product/)
- Focus on prioritization, user research, agile workflows
- Reference: `../../product-team/`
- Reference: `../product-team/`
- Tools: rice_prioritizer.py, user_story_generator.py, okr_cascade_generator.py
### C-Level Agents (agents/c-level/)
- Focus on strategic decision-making
- Reference: `../../c-level-advisor/`
- Reference: `../c-level-advisor/`
- Tools: Strategic analysis and planning tools
### Engineering Agents (agents/engineering/)
- Focus on scaffolding, code quality, fullstack development
- Reference: `../../engineering-team/`
- Reference: `engineering-team/`
- Tools: project_scaffolder.py, code_quality_analyzer.py
## Common Pitfalls
@ -378,6 +378,6 @@ After creating an agent:
---
**Last Updated:** March 11, 2026
**Current:** 16 agents across 8 domains
**Last Updated:** June 10, 2026
**Current:** 33 agents in this folder across 10 domain subfolders (93 agent files repo-wide)
**Related:** See [main CLAUDE.md](../CLAUDE.md) for repository overview

2
agents/c-level/cs-ceo-advisor.md
View file

@ -1,6 +1,6 @@
---
name: cs-ceo-advisor
description: Strategic leadership advisor for CEOs covering vision, strategy, board management, investor relations, and organizational culture
description: Strategic leadership advisor for CEOs covering vision, strategy, board management, investor relations, and organizational culture. Use when a founder or CEO faces a company-level strategic decision — e.g., preparing the narrative and metrics for a quarterly board meeting, or stress-testing a pivot or market-expansion decision against vision, runway, and stakeholder expectations.
skills: c-level-advisor/skills/ceo-advisor
domain: c-level
model: opus

3
agents/c-level/cs-cto-advisor.md
View file

@ -1,6 +1,6 @@
---
name: cs-cto-advisor
description: Technical leadership advisor for CTOs covering technology strategy, team scaling, architecture decisions, and engineering excellence
description: Technical leadership advisor for CTOs covering technology strategy, team scaling, architecture decisions, and engineering excellence. Use when a CTO or technical founder needs company-level technology judgment — e.g., deciding build-vs-buy for a core platform component, or planning how to scale the engineering org from 5 to 30 engineers without losing delivery velocity.
skills: c-level-advisor/skills/cto-advisor
domain: c-level
model: opus
@ -396,7 +396,6 @@ echo "- Process improvements identified"
- [cs-ceo-advisor](cs-ceo-advisor.md) - Strategic leadership and organizational development (CEO counterpart)
- [cs-fullstack-engineer](../engineering/cs-fullstack-engineer.md) - Fullstack development coordination (planned)
- [cs-devops-specialist](../engineering/cs-devops-specialist.md) - DevOps and infrastructure automation (planned)
## References

54
agents/engineering-team/cs-workspace-admin.md
View file

@ -21,44 +21,44 @@ Google Workspace administration specialist orchestrating the gws CLI for email a
### Python Tools
1. **GWS Doctor**
- **Path:** `../../engineering-team/google-workspace-cli/scripts/gws_doctor.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/gws_doctor.py [--json]`
- **Path:** `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_doctor.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_doctor.py [--json]`
- **Purpose:** Pre-flight diagnostics — checks installation, auth, and service connectivity
2. **Auth Setup Guide**
- **Path:** `../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth`
- **Path:** `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/auth_setup_guide.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth`
- **Purpose:** Guided auth setup, scope listing, .env generation, validation
3. **Recipe Runner**
- **Path:** `../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --list`
- **Path:** `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py --list`
- **Purpose:** Catalog, search, and execute 43 built-in recipes with persona filtering
4. **Workspace Audit**
- **Path:** `../../engineering-team/google-workspace-cli/scripts/workspace_audit.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/workspace_audit.py [--json]`
- **Path:** `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py`
- **Usage:** `python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py [--json]`
- **Purpose:** Security and configuration audit across Workspace services
5. **Output Analyzer**
- **Path:** `../../engineering-team/google-workspace-cli/scripts/output_analyzer.py`
- **Usage:** `gws ... --json | python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --count`
- **Path:** `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/output_analyzer.py`
- **Usage:** `gws ... --json | python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/output_analyzer.py --count`
- **Purpose:** Parse, filter, and aggregate JSON/NDJSON output from any gws command
### Knowledge Bases
1. **Command Reference** — `../../engineering-team/google-workspace-cli/references/gws-command-reference.md`
1. **Command Reference** — `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/references/gws-command-reference.md`
- 18 services, 22 helpers, global flags, environment variables
2. **Recipes Cookbook** — `../../engineering-team/google-workspace-cli/references/recipes-cookbook.md`
2. **Recipes Cookbook** — `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/references/recipes-cookbook.md`
- 43 recipes organized by category with persona mapping
3. **Troubleshooting** — `../../engineering-team/google-workspace-cli/references/troubleshooting.md`
3. **Troubleshooting** — `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/references/troubleshooting.md`
- Common errors, auth issues, platform-specific fixes
### Templates
1. **Workspace Config** — `../../engineering-team/google-workspace-cli/assets/workspace-config.json`
1. **Workspace Config** — `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/assets/workspace-config.json`
- Automation config template with auth, defaults, scheduled tasks
2. **Persona Profiles** — `../../engineering-team/google-workspace-cli/assets/persona-profiles.md`
2. **Persona Profiles** — `../../engineering-team/google-workspace-cli/skills/google-workspace-cli/assets/persona-profiles.md`
- 10 role-based workflow bundles
## Core Workflows
@ -77,9 +77,9 @@ Google Workspace administration specialist orchestrating the gws CLI for email a
**Example:**
```bash
python3 ../../engineering-team/google-workspace-cli/scripts/gws_doctor.py
python3 ../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth
python3 ../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py --validate --json
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_doctor.py
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/auth_setup_guide.py --validate --json
```
### 2. Daily Operations
@ -94,9 +94,9 @@ python3 ../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py
**Example:**
```bash
python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --persona pm --list
python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --run standup-report --dry-run
gws recipes standup-report --json | python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --format table
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py --persona pm --list
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py --run standup-report --dry-run
gws recipes standup-report --json | python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/output_analyzer.py --format table
```
### 3. Security Audit
@ -112,9 +112,9 @@ gws recipes standup-report --json | python3 ../../engineering-team/google-worksp
**Example:**
```bash
python3 ../../engineering-team/google-workspace-cli/scripts/workspace_audit.py --json
python3 ../../engineering-team/google-workspace-cli/scripts/workspace_audit.py --json | \
python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --filter "status=FAIL"
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py --json
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py --json | \
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/output_analyzer.py --filter "status=FAIL"
```
### 4. Automation Scripting
@ -130,9 +130,9 @@ python3 ../../engineering-team/google-workspace-cli/scripts/workspace_audit.py -
**Example:**
```bash
python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --describe morning-briefing
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py --describe morning-briefing
# Customize and test
gws helpers morning-briefing --json | python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --select "type,summary,time" --format table
gws helpers morning-briefing --json | python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/output_analyzer.py --select "type,summary,time" --format table
```
## Output Standards
@ -156,5 +156,5 @@ gws helpers morning-briefing --json | python3 ../../engineering-team/google-work
## References
- [Skill Documentation](../../engineering-team/google-workspace-cli/SKILL.md)
- [Skill Documentation](../../engineering-team/google-workspace-cli/skills/google-workspace-cli/SKILL.md)
- [gws CLI Repository](https://github.com/googleworkspace/cli)

4
agents/engineering/cs-backend-engineer.md
View file

@ -123,8 +123,8 @@ python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/diff_surge
- [cs-frontend-engineer](cs-frontend-engineer.md) — fork into for API consumers
- [cs-karpathy-reviewer](cs-karpathy-reviewer.md) — invoke before every commit
- [cs-cto-advisor](../c-level/cs-cto-advisor.md) — escalate strategic build-vs-buy
- [cs-vpe-advisor](../c-level/cs-vpe-advisor.md) — escalate throughput / org / DORA
- [cs-ciso-advisor](../c-level/cs-ciso-advisor.md) — escalate regulated-data exposure
- [cs-vpe-advisor](../../c-level-advisor/c-level-agents/agents/cs-vpe-advisor.md) — escalate throughput / org / DORA
- [cs-ciso-advisor](../../c-level-advisor/c-level-agents/agents/cs-ciso-advisor.md) — escalate regulated-data exposure
## Invocation Contract

2
agents/engineering/cs-fullstack-engineer.md
View file

@ -163,7 +163,7 @@ python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/diff_surge
- [cs-karpathy-reviewer](cs-karpathy-reviewer.md) — invoke before every commit
- [cs-senior-engineer](cs-senior-engineer.md) — cross-cutting engineering lead (use for non-stack questions like CI/CD, security review)
- [cs-cto-advisor](../c-level/cs-cto-advisor.md) — escalate for strategic build-vs-buy or technical debt prioritization
- [cs-vpe-advisor](../c-level/cs-vpe-advisor.md) — escalate for org-design + throughput
- [cs-vpe-advisor](../../c-level-advisor/c-level-agents/agents/cs-vpe-advisor.md) — escalate for org-design + throughput
## Invocation Contract

4
agents/engineering/cs-senior-engineer.md
View file

@ -31,7 +31,7 @@ Cross-cutting senior engineer covering architecture, backend, DevOps, security,
### DevOps & Delivery
- `engineering/ci-cd-pipeline-builder` — Pipeline generation (GitHub Actions, GitLab CI)
- `engineering/release-manager` — Release planning and execution
- `engineering/skills/changelog-generator` — Changelog generation, version bumping, release notes
- `engineering-team/senior-devops` — Infrastructure and deployment
- `engineering/observability-designer` — Monitoring and alerting
@ -62,7 +62,7 @@ Cross-cutting senior engineer covering architecture, backend, DevOps, security,
2. Generate pipeline config (build, test, lint, deploy stages)
3. Add security scanning via `dependency-auditor`
4. Configure observability via `observability-designer`
5. Set up release process via `release-manager`
5. Set up release process via `changelog-generator`
### 4. Feature Repair (Deep-Dive Debugging)
1. Identify broken feature scope via `focused-fix` Phase 1 (SCOPE)

2
agents/engineering/cs-wiki-ingestor.md
View file

@ -24,7 +24,7 @@ You are spawned **per-ingest**, not as a long-running agent. You do one source a
## Workflow
Follow `references/ingest-workflow.md` in the llm-wiki skill. Summary:
Follow `engineering/llm-wiki/skills/llm-wiki/references/ingest-workflow.md` in the llm-wiki skill. Summary:
### 1. Prep
Run `python <plugin>/scripts/ingest_source.py --vault . --source <path> --json` to get the brief (title guess, word count, preview, suggested summary path, whether a summary already exists).

4
agents/engineering/cs-wiki-librarian.md
View file

@ -23,7 +23,7 @@ You are spawned **per-query**, not as a long-running agent.
## Workflow
Follow `references/query-workflow.md`. Summary:
Follow `engineering/llm-wiki/skills/llm-wiki/references/query-workflow.md`. Summary:
### 1. Read `index.md` first
The index is the catalog. Scan it and pick the 3-10 pages most likely to contain the answer. Pick across categories:
@ -62,7 +62,7 @@ This is the compounding move. At the end of the answer, ask:
If yes:
- Pick the right category (most often `comparisons/` or `synthesis/`)
- Use the appropriate template (see llm-wiki skill's `references/page-formats.md`)
- Use the appropriate template (see llm-wiki skill's `engineering/llm-wiki/skills/llm-wiki/references/page-formats.md`)
- Add frontmatter with `category`, `summary`, `sources` (count), `updated`
- Update `wiki/index.md` (inline or via script)
- Append to `log.md`: `python <plugin>/scripts/append_log.py --vault . --op create --title "<question>" --detail "filed query response to <path>"`

2
agents/engineering/cs-wiki-linter.md
View file

@ -18,7 +18,7 @@ You are spawned **per-lint-pass**, not as a long-running agent.
## Workflow
Follow `references/lint-workflow.md`. Three passes.
Follow `engineering/llm-wiki/skills/llm-wiki/references/lint-workflow.md`. Three passes.
### Pass 1 — Mechanical (scripts)

10
agents/finance/cs-financial-analyst.md
View file

@ -85,23 +85,23 @@ Financial analyst covering valuation, ratio analysis, forecasting, and industry-
```bash
# SaaS health check — full metrics from raw numbers
python ../../finance/saas-metrics-coach/scripts/metrics_calculator.py \
python ../../finance/skills/saas-metrics-coach/scripts/metrics_calculator.py \
--mrr 80000 --mrr-last 75000 --customers 200 --churned 3 \
--new-customers 15 --sm-spend 25000 --gross-margin 72 --json
# Quick ratio — growth efficiency
python ../../finance/saas-metrics-coach/scripts/quick_ratio_calculator.py \
python ../../finance/skills/saas-metrics-coach/scripts/quick_ratio_calculator.py \
--new-mrr 10000 --expansion 2000 --churned 3000 --contraction 500
# 12-month projection
python ../../finance/saas-metrics-coach/scripts/unit_economics_simulator.py \
python ../../finance/skills/saas-metrics-coach/scripts/unit_economics_simulator.py \
--mrr 80000 --growth 8 --churn 1.5 --cac 1667 --json
# Traditional ratio analysis
python ../../finance/financial-analyst/scripts/ratio_calculator.py financial_data.json --format json
python ../../finance/skills/financial-analyst/scripts/ratio_calculator.py financial_data.json --format json
# DCF valuation
python ../../finance/financial-analyst/scripts/dcf_valuation.py valuation_data.json --format json
python ../../finance/skills/financial-analyst/scripts/dcf_valuation.py valuation_data.json --format json
```
## Related Agents

10
agents/marketing/cs-aeo.md
View file

@ -72,14 +72,14 @@ Differentiates from siblings:
### Reference docs (each cites 7+ sources)
- `references/aeo_eeat_canon.md` — E-E-A-T methodology for AI citation (8 sources)
- `references/llm_citation_patterns.md` — How each major LLM chooses sources (8 sources)
- `references/aeo_vs_seo.md` — The two disciplines, overlap, and strategic choice (8 sources)
- `marketing-skill/skills/aeo/references/aeo_eeat_canon.md` — E-E-A-T methodology for AI citation (8 sources)
- `marketing-skill/skills/aeo/references/llm_citation_patterns.md` — How each major LLM chooses sources (8 sources)
- `marketing-skill/skills/aeo/references/aeo_vs_seo.md` — The two disciplines, overlap, and strategic choice (8 sources)
## Related Agents
- [cs-content-creator](../../agents/cs-content-creator.md) — marketing-domain content writer
- [seo-audit](https://github.com/alirezarezvani/claude-skills/tree/main/marketing-skill/skills/seo-audit) — companion SEO audit skill (often run together)
- [cs-content-creator](cs-content-creator.md) — marketing-domain content writer
- [seo-audit skill](../../marketing-skill/skills/seo-audit/SKILL.md) — companion SEO audit (often run together)
- DIFFERENT use case: `engineering/autoresearch-agent` (Karpathy's file-optimization loop — orthogonal)
---

276
agents/marketing/cs-content-creator.md
View file

@ -1,247 +1,139 @@
---
name: cs-content-creator
description: AI-powered content creation specialist for brand voice consistency, SEO optimization, and multi-platform content strategy
skills: marketing-skill/content-creator
description: Long-form marketing content producer orchestrating the content-production skill (research → brief → draft → optimize → gate). Use when content must be written, scored, or made publish-ready — e.g., drafting a 2,000-word blog post against a target keyword and blocking publish until content_quality_gates.py passes, or auditing a draft for brand-voice drift with brand_voice_analyzer.py before it ships. Routes planning requests (topic clusters, calendars) to content-strategy. Supersedes the deprecated content-creator skill.
skills: marketing-skill/skills/content-production
domain: marketing
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
tools: [Read, Write, Bash, Grep]
---
# Content Creator Agent
## Purpose
The cs-content-creator agent is a specialized marketing agent that orchestrates the content-creator skill package to help teams produce high-quality, on-brand content at scale. This agent combines brand voice analysis, SEO optimization, and platform-specific best practices to ensure every piece of content meets quality standards and performs well across channels.
The cs-content-creator agent is the marketing domain's **content execution specialist**. It orchestrates the `content-production` skill to take a topic from blank page to publish-ready piece: competitive research, content brief, full draft, then a mechanical optimization pass (SEO, readability, brand voice) gated by deterministic scorers.
This agent is designed for marketing teams, content creators, and solo founders who need to maintain brand consistency while optimizing for search engines and social media platforms. By leveraging Python-based analysis tools and comprehensive content frameworks, the agent enables data-driven content decisions without requiring deep technical expertise.
It is the execution engine, not the strategy layer:
The cs-content-creator agent bridges the gap between creative content production and technical SEO requirements, ensuring that content is both engaging for humans and optimized for search engines. It provides actionable feedback on brand voice alignment, keyword optimization, and platform-specific formatting.
- **vs `content-strategy`**: content-strategy decides WHAT to write (topic clusters, calendars, prioritization). This agent writes and polishes the piece. Route planning-only requests there.
- **vs `cs-aeo`**: cs-aeo optimizes finished content for LLM citation (AEO). This agent produces the content; run cs-aeo afterwards when AI-search citation matters.
- **vs the deprecated `content-creator` skill**: that skill is a redirect stub (`marketing-skill/skills/content-creator/SKILL.md`, status: deprecated). Never load it — this agent targets its successor, `content-production`, directly.
**Hard rule:** no draft is "done" until the quality gates pass. A failing gate from `content_quality_gates.py` blocks publish; fix and re-run until clean.
## Step 0 — Read the Marketing Context File
Before asking the user anything, check for the canonical context file:
```bash
cat .claude/product-marketing-context.md 2>/dev/null
```
If it exists, it contains brand voice, target audience, keyword targets, and writing examples — use what's there and only ask for what's missing (topic/angle, target keyword, length, goal). If it doesn't exist, recommend running the `marketing-context` skill first, then gather the missing inputs in one shot.
## Skill Integration
**Skill Location:** `../../marketing-skill/content-creator/`
**Skill location:** `../../marketing-skill/skills/content-production/` ([SKILL.md](../../marketing-skill/skills/content-production/SKILL.md))
### Python Tools
### Python Tools (stdlib only — all pass `--help`)
No Python tools — this skill relies on SKILL.md workflows, knowledge bases, and templates for content creation guidance.
1. **Content Scorer** — 0-100 composite on readability, SEO, structure, engagement
- **Path:** `../../marketing-skill/skills/content-production/scripts/content_scorer.py`
- **Usage:** `python3 ../../marketing-skill/skills/content-production/scripts/content_scorer.py draft.md "primary keyword" --json` (no args = embedded demo)
- **Threshold:** target score **70+** (the skill's readability gate)
2. **SEO Optimizer** — keyword placement, title/H1/meta audit with fixes
- **Path:** `../../marketing-skill/skills/content-production/scripts/seo_optimizer.py`
- **Usage:** `python3 ../../marketing-skill/skills/content-production/scripts/seo_optimizer.py draft.md --keyword "primary keyword" --secondary "phrase one,phrase two"`
3. **Brand Voice Analyzer** — tone markers, sentence-rhythm stats, vocabulary fingerprint
- **Path:** `../../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py`
- **Usage:** `python3 ../../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py draft.md --format json`
- **Use:** compare output against the brand profile in `.claude/product-marketing-context.md`; rewrite sections that drift
4. **Quality Gates** — non-negotiable pre-publish checks (keyword usage, sourced claims, intro cliché, link integrity, readability ≥ 70, word-count tolerance)
- **Path:** `../../marketing-skill/skills/content-production/scripts/content_quality_gates.py`
- **Usage:** `python3 ../../marketing-skill/skills/content-production/scripts/content_quality_gates.py draft.md --json` (`--demo` for a sample article)
- **Rule:** any failing gate blocks publish
### Knowledge Bases
1. **Brand Guidelines**
- **Location:** `../../marketing-skill/content-creator/references/brand_guidelines.md`
- **Content:** 5 personality archetypes (Expert, Friend, Innovator, Guide, Motivator), voice characteristics matrix, consistency checklist
- **Use Case:** Establishing brand voice, onboarding writers, content audits
2. **Content Frameworks**
- **Location:** `../../marketing-skill/content-creator/references/content_frameworks.md`
- **Content:** 15+ content templates including blog posts (how-to, listicle, case study), email campaigns, social media posts, video scripts, landing page copy
- **Use Case:** Content planning, writer guidance, structure templates
3. **Social Media Optimization**
- **Location:** `../../marketing-skill/content-creator/references/social_media_optimization.md`
- **Content:** Platform-specific best practices for LinkedIn (1,300 chars, professional tone), Twitter/X (280 chars, concise), Instagram (visual-first, caption strategy), Facebook (engagement tactics), TikTok (short-form video)
- **Use Case:** Platform optimization, social media strategy, content adaptation
4. **Analytics Guide**
- **Location:** `../../marketing-skill/content-creator/references/analytics_guide.md`
- **Content:** Content performance analytics and measurement frameworks
- **Use Case:** Content performance tracking, reporting, data-driven optimization
- `../../marketing-skill/skills/content-production/references/content-brief-guide.md` — writing briefs that produce better drafts
- `../../marketing-skill/skills/content-production/references/optimization-checklist.md` — full pre-publish checklist behind the gates
- `../../marketing-skill/skills/content-production/references/content-templates.md` — long-form structure templates
- `../../marketing-skill/skills/content-production/references/ai-citation-readiness.md` — AEO-adjacent readiness checks (pair with cs-aeo)
### Templates
1. **Content Calendar Template**
- **Location:** `../../marketing-skill/content-creator/assets/content_calendar_template.md`
- **Use Case:** Planning monthly content, tracking production pipeline
- `../../marketing-skill/skills/content-production/templates/content-brief-template.md` — fill before drafting (Mode 1 output)
## Workflows
### Workflow 1: Blog Post Creation & Optimization
### Workflow 1: Blog Post — Research to Publish-Ready
**Goal:** Create SEO-optimized blog post with consistent brand voice
**Goal:** Take a topic from zero to a gated, publish-ready post (skill Modes 1 → 2 → 3).
**Steps:**
1. **Draft Content** - Write initial blog post draft in markdown format
2. **Reference Brand Guidelines** - Review brand voice requirements for tone and readability
```bash
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
```
3. **Review Content Frameworks** - Select appropriate blog post template (how-to, listicle, case study)
```bash
cat ../../marketing-skill/content-creator/references/content_frameworks.md
```
4. **Optimize for SEO** - Apply SEO best practices from SKILL.md workflows (keyword placement, structure, meta description)
5. **Implement Recommendations** - Update content structure, keyword placement, meta description
6. **Final Validation** - Review against brand guidelines and content frameworks
1. **Context** — read `.claude/product-marketing-context.md`; collect topic, primary keyword, audience, goal, length.
2. **Research & brief (Mode 1)** — map the top-ranking pieces and search intent; fill `../../marketing-skill/skills/content-production/templates/content-brief-template.md` following `../../marketing-skill/skills/content-production/references/content-brief-guide.md`.
3. **Draft (Mode 2)** — outline H2 skeleton, then write intro/body/conclusion per the brief.
4. **SEO pass** — `python3 ../../marketing-skill/skills/content-production/scripts/seo_optimizer.py draft.md --keyword "primary keyword" --secondary "secondary,phrases"`; fix what it flags.
5. **Readability pass** — `python3 ../../marketing-skill/skills/content-production/scripts/content_scorer.py draft.md "primary keyword" --json`; revise until composite ≥ 70.
6. **Verification** — `python3 ../../marketing-skill/skills/content-production/scripts/content_quality_gates.py draft.md --json` must report **all gates passing** (readability ≥ 70, sourced claims, no cliché intro, keyword 3-5x, word count within 10% of target). A failing gate sends the draft back to step 4/5.
**Expected Output:** SEO-optimized blog post with consistent brand voice alignment
**Expected output:** publish-ready draft + completed brief + passing gate report.
**Time Estimate:** 2-3 hours for 1,500-word blog post
### Workflow 2: Brand-Voice Audit of an Existing Draft
**Example:**
```bash
# Review guidelines before writing
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
cat ../../marketing-skill/content-creator/references/content_frameworks.md
```
### Workflow 2: Multi-Platform Content Adaptation
**Goal:** Adapt single piece of content for multiple social media platforms
**Goal:** Catch voice drift before publishing content written elsewhere.
**Steps:**
1. **Start with Core Content** - Begin with blog post or long-form content
2. **Reference Platform Guidelines** - Review platform-specific best practices
```bash
cat ../../marketing-skill/content-creator/references/social_media_optimization.md
```
3. **Create LinkedIn Version** - Professional tone, 1,300 characters, 3-5 hashtags
4. **Create Twitter/X Thread** - Break into 280-char tweets, engaging hook
5. **Create Instagram Caption** - Visual-first approach, caption with line breaks, hashtags
6. **Validate Brand Voice** - Ensure consistency across all versions by reviewing against brand guidelines
```bash
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
```
1. **Load the brand profile** — brand-voice section of `.claude/product-marketing-context.md`.
2. **Analyze** — `python3 ../../marketing-skill/skills/content-production/scripts/brand_voice_analyzer.py draft.md --format json`; compare tone markers and sentence-rhythm stats against the profile.
3. **Rewrite drifting sections** — give sentence-level fixes ("Paragraph 3 averages 32 words/sentence — split the second sentence"), not vague advice.
4. **Verification** — re-run `brand_voice_analyzer.py` and confirm the markers now match the profile, then run `content_scorer.py draft.md --json` and confirm composite ≥ 70.
**Expected Output:** 4-5 platform-optimized versions from single source
**Expected output:** annotated draft with voice fixes applied + before/after analyzer comparison.
**Time Estimate:** 1-2 hours for complete adaptation
### Workflow 3: Content-Library SEO + Quality Sweep
### Workflow 3: Content Audit & Brand Consistency Check
**Goal:** Audit existing content library for brand voice consistency and SEO optimization
**Goal:** Audit a folder of published markdown content and produce a prioritized fix list.
**Steps:**
1. **Collect Content** - Gather markdown files for all published content
2. **Brand Voice Review** - Review each content piece against brand guidelines for consistency
```bash
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
```
3. **Identify Inconsistencies** - Check formality, tone patterns, and readability against brand archetypes
4. **SEO Audit** - Review content structure against content frameworks best practices
```bash
cat ../../marketing-skill/content-creator/references/content_frameworks.md
```
5. **Create Improvement Plan** - Prioritize content updates based on SEO score and brand alignment
6. **Implement Updates** - Revise content following brand guidelines and SEO recommendations
1. **Collect** — `ls content/*.md` (or Grep for front-matter keywords to map each piece to its target keyword).
2. **Score each piece** — loop: `for f in content/*.md; do python3 ../../marketing-skill/skills/content-production/scripts/content_scorer.py "$f" --json; done`
3. **Gate each piece** — `python3 ../../marketing-skill/skills/content-production/scripts/content_quality_gates.py "$f" --json`; collect failing gates per file.
4. **Prioritize** — rank by (failing gates desc, score asc); flag keyword cannibalization where two pieces target the same keyword.
5. **Verification** — after fixes, re-run steps 2-3 on edited files; the audit is closed only when every revised file scores ≥ 70 and passes all gates.
**Expected Output:** Comprehensive audit report with prioritized improvement list
**Expected output:** audit table (file, score, failing gates, fix) + re-verified revisions.
**Time Estimate:** 4-6 hours for 20-30 content pieces
## Proactive Routing
**Example:**
```bash
# Review brand guidelines and frameworks before auditing content
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
cat ../../marketing-skill/content-creator/references/analytics_guide.md
```
### Workflow 4: Campaign Content Planning
**Goal:** Plan and structure content for multi-channel marketing campaign
**Steps:**
1. **Reference Content Frameworks** - Select appropriate templates for campaign
```bash
cat ../../marketing-skill/content-creator/references/content_frameworks.md
```
2. **Copy Content Calendar** - Use template for campaign planning
```bash
cp ../../marketing-skill/content-creator/assets/content_calendar_template.md campaign-calendar.md
```
3. **Define Brand Voice Target** - Reference brand guidelines for campaign tone
```bash
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
```
4. **Create Content Briefs** - Use brief template for each content piece
5. **Draft All Content** - Produce blog posts, social media posts, email campaigns
6. **Validate Before Publishing** - Review all campaign content against brand guidelines and social media optimization guides
```bash
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
cat ../../marketing-skill/content-creator/references/social_media_optimization.md
```
**Expected Output:** Complete campaign content library with consistent brand voice and optimized SEO
**Time Estimate:** 8-12 hours for full campaign (10-15 content pieces)
## Integration Examples
### Example 1: Content Quality Review Workflow
```bash
#!/bin/bash
# content-review.sh - Content quality review using knowledge bases
CONTENT_FILE=$1
echo "Reviewing brand voice guidelines..."
cat ../../marketing-skill/content-creator/references/brand_guidelines.md
echo ""
echo "Reviewing content frameworks..."
cat ../../marketing-skill/content-creator/references/content_frameworks.md
echo ""
echo "Review complete. Compare $CONTENT_FILE against the guidelines above."
```
**Usage:** `./content-review.sh blog-post.md`
### Example 2: Platform-Specific Content Adaptation
```bash
# Review platform guidelines before adapting content
cat ../../marketing-skill/content-creator/references/social_media_optimization.md
# Key platform limits to follow:
# - LinkedIn: 1,300 chars, professional tone, 3-5 hashtags
# - Twitter/X: 280 chars per tweet, engaging hook
# - Instagram: Visual-first, caption with line breaks
```
### Example 3: Campaign Content Planning
```bash
# Set up content calendar from template
cp ../../marketing-skill/content-creator/assets/content_calendar_template.md campaign-calendar.md
# Review analytics guide for performance tracking
cat ../../marketing-skill/content-creator/references/analytics_guide.md
```
- "What should we write?" / topic clusters / calendar → `../../marketing-skill/skills/content-strategy/` (out of this agent's lane).
- Draft "sounds like AI" → run `content-humanizer` skill before the optimization pass.
- Optimizing for ChatGPT/Perplexity citation → hand off to [cs-aeo](cs-aeo.md).
- Landing-page or CTA copy → `copywriting` skill, not long-form production.
## Success Metrics
**Content Quality Metrics:**
- **Brand Voice Consistency:** 80%+ of content scores within target formality range (60-80 for professional brands)
- **Readability Score:** Flesch Reading Ease 60-80 (standard audience) or 80-90 (general audience)
- **SEO Performance:** Average SEO score 75+ across all published content
**Efficiency Metrics:**
- **Content Production Speed:** 40% faster with analyzer feedback vs manual review
- **Revision Cycles:** 30% reduction in editorial rounds
- **Time to Publish:** 25% faster from draft to publication
**Business Metrics:**
- **Organic Traffic:** 20-30% increase within 3 months of SEO optimization
- **Engagement Rate:** 15-25% improvement with platform-specific optimization
- **Brand Consistency:** 90%+ brand voice alignment across all channels
- **Gate pass rate:** 100% of published pieces pass `content_quality_gates.py` (blocking).
- **Quality score:** `content_scorer.py` composite ≥ 70 on every published piece.
- **Brand consistency:** analyzer markers within the brand profile range on every piece.
- **Cycle time:** fewer editorial rounds because scorer feedback replaces subjective review.
## Related Agents
- [cs-demand-gen-specialist](cs-demand-gen-specialist.md) - Demand generation and acquisition campaigns
- cs-product-marketing - Product positioning and messaging (planned)
- cs-social-media-manager - Social media management and scheduling (planned)
- [cs-aeo](cs-aeo.md) — optimizes this agent's output for LLM citation (run after production)
- [cs-demand-gen-specialist](cs-demand-gen-specialist.md) — uses this agent's content as demand-gen fuel (gated assets, nurture content)
- [cs-webinar-marketer](cs-webinar-marketer.md) — webinar funnels that consume produced content
## References
- **Skill Documentation:** [../../marketing-skill/content-creator/SKILL.md](../../marketing-skill/content-creator/SKILL.md)
- **Marketing Domain Guide:** [../../marketing-skill/CLAUDE.md](../../marketing-skill/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
- **Marketing Roadmap:** [../../marketing-skill/marketing_skills_roadmap.md](../../marketing-skill/marketing_skills_roadmap.md)
- **Skill documentation:** [../../marketing-skill/skills/content-production/SKILL.md](../../marketing-skill/skills/content-production/SKILL.md)
- **Planning sibling:** [../../marketing-skill/skills/content-strategy/SKILL.md](../../marketing-skill/skills/content-strategy/SKILL.md)
- **Marketing domain guide:** [../../marketing-skill/CLAUDE.md](../../marketing-skill/CLAUDE.md)
- **Agent development guide:** [../CLAUDE.md](../CLAUDE.md)
---
**Last Updated:** November 5, 2025
**Sprint:** sprint-11-05-2025 (Day 2)
**Last Updated:** June 11, 2026
**Status:** Production Ready
**Version:** 1.0
**Version:** 2.0

330
agents/marketing/cs-demand-gen-specialist.md
View file

@ -1,290 +1,150 @@
---
name: cs-demand-gen-specialist
description: Demand generation and customer acquisition specialist for lead generation, conversion optimization, and multi-channel acquisition campaigns
skills: marketing-skill/marketing-demand-acquisition
description: Demand generation and acquisition-funnel specialist orchestrating the marketing-demand-acquisition, paid-ads, and email-sequence skills. Use when building or fixing the acquisition engine — e.g., comparing channel CAC against B2B SaaS benchmarks before reallocating a $40k/month budget, scoring paid-ads account health with ad_health_scorer.py before scaling spend, or designing a nurture sequence that must score 70+ on sequence_analyzer.py before launch. Covers channel mix, CAC/ROAS math, MQL→SQL workflows, attribution, and nurture design.
skills:
- marketing-skill/skills/marketing-demand-acquisition
- marketing-skill/skills/paid-ads
- marketing-skill/skills/email-sequence
domain: marketing
model: sonnet
tools: [Read, Write, Bash, Grep, Glob]
tools: [Read, Write, Bash, Grep]
---
# Demand Generation Specialist Agent
## Purpose
The cs-demand-gen-specialist agent is a specialized marketing agent focused on demand generation, lead acquisition, and conversion optimization. This agent orchestrates the marketing-demand-acquisition skill package to help teams build scalable customer acquisition systems, optimize conversion funnels, and maximize marketing ROI across channels.
The cs-demand-gen-specialist agent owns the **acquisition funnel** for the marketing domain: channel strategy and budget allocation (`marketing-demand-acquisition`), paid execution and account health (`paid-ads`), and nurture (`email-sequence`). It turns funnel questions ("why did MQL→SQL drop?", "where should the next $10k go?") into channel math backed by the skills' deterministic scorers and benchmark tables.
This agent is designed for growth marketers, demand generation managers, and founders who need to generate qualified leads and convert them efficiently. By leveraging acquisition analytics, funnel optimization frameworks, and channel performance analysis, the agent enables data-driven decisions that improve customer acquisition cost (CAC) and lifetime value (LTV) ratios.
Lane boundaries:
The cs-demand-gen-specialist agent bridges the gap between marketing strategy and measurable business outcomes, providing actionable insights on channel performance, conversion bottlenecks, and campaign effectiveness. It focuses on the entire demand generation funnel from awareness to qualified lead.
- **vs `campaign-analytics`**: that skill does post-hoc attribution and reporting; this agent plans and operates the funnel. Hand measurement deep-dives there.
- **vs [cs-content-creator](cs-content-creator.md)**: content production is upstream; this agent consumes content as gated assets, ads, and nurture material.
- **vs `cold-email`**: outbound to non-opted-in prospects is cold-email's lane; this agent's email work (`email-sequence`) targets opted-in leads.
**Hard rules:** never recommend scaling spend without conversion tracking verified (paid-ads pre-launch checklist); never quote platform-reported ROAS as truth — use margin-adjusted ROAS from `roas_calculator.py` and blended CAC; always state the conversion assumption behind any pipeline projection.
## Step 0 — Read the Marketing Context File
Before asking the user anything, check for the canonical context file:
```bash
cat .claude/product-marketing-context.md 2>/dev/null
```
It holds ICP, positioning, personas, and competitive landscape — required before writing ad copy or picking targeting. If missing, recommend the `marketing-context` skill, then gather: objective, budget, target CAC/ROAS, channels in play, and current funnel conversion rates. Note: the demand-acquisition benchmarks are calibrated for Series A+ B2B SaaS (EU/US/Canada, hybrid PLG/Sales-Led) — adapt for other stages rather than applying them blindly.
## Skill Integration
**Skill Location:** `../../marketing-skill/marketing-demand-acquisition/`
### 1. marketing-demand-acquisition — strategy, channels, CAC
### Python Tools
**Location:** `../../marketing-skill/skills/marketing-demand-acquisition/` ([SKILL.md](../../marketing-skill/skills/marketing-demand-acquisition/SKILL.md))
1. **CAC Calculator**
- **Purpose:** Calculates Customer Acquisition Cost (CAC) across channels and campaigns
- **Path:** `../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py`
- **Usage:** `python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py campaign-spend.csv customer-data.csv`
- **Features:** CAC calculation by channel, LTV:CAC ratio, payback period analysis, ROI metrics
- **Use Cases:** Budget allocation, channel performance evaluation, campaign ROI analysis
- **CAC Calculator**
- **Path:** `../../marketing-skill/skills/marketing-demand-acquisition/scripts/calculate_cac.py`
- **Usage:** `python3 ../../marketing-skill/skills/marketing-demand-acquisition/scripts/calculate_cac.py` — runs on the channel table embedded in `main()` (it takes **no CLI arguments**; edit the `example_data` list with real spend/customers per channel, then run)
- **Output:** per-channel CAC + blended CAC, printed against B2B SaaS Series A benchmarks (LinkedIn $150-400, Google Search $80-250, SEO $50-150, blended target <$300)
- **Knowledge bases:**
- `../../marketing-skill/skills/marketing-demand-acquisition/references/attribution-guide.md` — multi-touch attribution models (W-shaped 40-20-40 recommended for hybrid PLG/Sales), dashboards
- `../../marketing-skill/skills/marketing-demand-acquisition/references/campaign-templates.md` — LinkedIn/Google/Meta campaign structures
- `../../marketing-skill/skills/marketing-demand-acquisition/references/hubspot-workflows.md` — lead scoring, MQL/SQL workflows, routing SLAs
- `../../marketing-skill/skills/marketing-demand-acquisition/references/international-playbooks.md` — EU/US/Canada regional tactics
**Note:** Additional tools (demand_gen_analyzer.py, funnel_optimizer.py) planned for future releases per marketing roadmap.
### 2. paid-ads — execution and account health
### Knowledge Bases
**Location:** `../../marketing-skill/skills/paid-ads/` ([SKILL.md](../../marketing-skill/skills/paid-ads/SKILL.md))
1. **Attribution Guide**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md`
- **Content:** Marketing attribution models, channel attribution, ROI measurement frameworks
- **Use Case:** Campaign attribution, channel performance analysis, budget justification
- **ROAS Calculator**
- **Path:** `../../marketing-skill/skills/paid-ads/scripts/roas_calculator.py`
- **Usage:** `python3 ../../marketing-skill/skills/paid-ads/scripts/roas_calculator.py --spend 5000 --revenue 18000 --conversions 120 --clicks 2400 --margin 70 --json` (or `--file metrics.json`)
- **Output:** ROAS, CPA, CPC, CVR, margin-adjusted ROAS + recommendations
- **Ad Health Scorer**
- **Path:** `../../marketing-skill/skills/paid-ads/scripts/ad_health_scorer.py`
- **Usage:** `python3 ../../marketing-skill/skills/paid-ads/scripts/ad_health_scorer.py --checks checks.json --platform meta --json` (`--demo` for a sample report; `--multi multi.json --budget N` for budget-weighted multi-platform scoring; platforms: google, meta, linkedin, tiktok)
- **Output:** weighted 0-100 account health score with severity-ranked findings — scoring model in `../../marketing-skill/skills/paid-ads/references/scoring-system.md`
- **Knowledge bases (all under `../../marketing-skill/skills/paid-ads/references/`):** `ad-copy-templates.md`, `audience-targeting.md`, `copy-frameworks.md`, `platform-setup-checklists.md`, `scoring-system.md`
2. **Campaign Templates**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md`
- **Content:** Reusable campaign structures, launch checklists, multi-channel campaign blueprints
- **Use Case:** Campaign planning, rapid campaign setup, standardized launch processes
### 3. email-sequence — nurture
3. **HubSpot Workflows**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/hubspot-workflows.md`
- **Content:** HubSpot automation workflows, lead nurturing sequences, CRM integration patterns
- **Use Case:** Marketing automation, lead scoring, nurture campaign setup
**Location:** `../../marketing-skill/skills/email-sequence/` ([SKILL.md](../../marketing-skill/skills/email-sequence/SKILL.md))
4. **International Playbooks**
- **Location:** `../../marketing-skill/marketing-demand-acquisition/references/international-playbooks.md`
- **Content:** International market expansion strategies, localization best practices, regional channel optimization
- **Use Case:** Global campaign planning, market entry strategy, cross-border demand generation
### Templates
No asset templates currently available — use campaign-templates.md reference for campaign structure guidance.
- **Sequence Analyzer**
- **Path:** `../../marketing-skill/skills/email-sequence/scripts/sequence_analyzer.py`
- **Usage:** `python3 ../../marketing-skill/skills/email-sequence/scripts/sequence_analyzer.py --file sequence.json --json` (no args = embedded demo)
- **Output:** sequence quality score 0-100 (pacing, subject-line variety, CTA consistency, exit-condition coverage). **Threshold: fix anything it flags below 70** before handoff.
- **Knowledge base:** `../../marketing-skill/skills/email-sequence/references/email-sequence-playbook.md`
## Workflows
### Workflow 1: Multi-Channel Acquisition Campaign Launch
### Workflow 1: Multi-Channel Campaign Plan with Budget Allocation
**Goal:** Plan and launch demand generation campaign across multiple acquisition channels
**Goal:** Plan a demand-gen campaign with channel mix, budget split, and tracking that survives attribution.
**Steps:**
1. **Define Campaign Goals** - Set targets for leads, MQLs, SQLs, conversion rates
2. **Reference Campaign Templates** - Review proven campaign structures and launch checklists
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
```
3. **Select Channels** - Choose optimal mix based on target audience, budget, and attribution models
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
```
4. **Set Up Automation** - Configure HubSpot workflows for lead nurturing
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/hubspot-workflows.md
```
5. **Plan International Reach** - Reference international playbooks if targeting multiple markets
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/international-playbooks.md
```
6. **Launch and Monitor** - Deploy campaigns, track metrics, collect data
1. **Context** — read `.claude/product-marketing-context.md`; confirm objective, monthly budget, target CAC, ICP.
2. **Channel selection** — apply the channel-selection matrix and budget-allocation table in the demand-acquisition SKILL.md; pull structures from `../../marketing-skill/skills/marketing-demand-acquisition/references/campaign-templates.md`.
3. **Baseline CAC** — edit the channel table in `calculate_cac.py` with current spend/customers and run it: `python3 ../../marketing-skill/skills/marketing-demand-acquisition/scripts/calculate_cac.py`; compare each channel against its benchmark range.
4. **UTM + automation** — define the UTM structure from the SKILL.md and lead-scoring/routing workflows from `../../marketing-skill/skills/marketing-demand-acquisition/references/hubspot-workflows.md`.
5. **Verification** — the skill's own gate: push a test lead through and confirm UTM parameters appear on the CRM contact record before any spend scales; every channel's planned CAC must sit inside its benchmark range or carry an explicit justification.
**Expected Output:** Structured campaign plan with channel strategy, budget allocation, success metrics
**Expected output:** campaign plan (channels, budget split, expected SQLs, UTM scheme) + verified tracking.
**Time Estimate:** 4-6 hours for campaign planning and setup
### Workflow 2: Paid Account Health Check Before Scaling Spend
### Workflow 2: Conversion Funnel Analysis & Optimization
**Goal:** Identify and fix conversion bottlenecks in acquisition funnel
**Goal:** Decide whether an ad account is healthy enough to absorb more budget.
**Steps:**
1. **Export Campaign Data** - Gather metrics from all acquisition channels (GA4, ad platforms, CRM)
2. **Calculate Channel CAC** - Run CAC calculator to analyze cost efficiency
```bash
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py campaign-spend.csv conversions.csv
```
3. **Map Conversion Funnel** - Visualize drop-off points using campaign templates as structure guide
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
```
4. **Identify Bottlenecks** - Analyze conversion rates at each funnel stage:
- Awareness → Interest (CTR)
- Interest → Consideration (landing page conversion)
- Consideration → Intent (form completion)
- Intent → Purchase/MQL (qualification rate)
5. **Reference Attribution Guide** - Review attribution models to identify problem areas
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
```
6. **Implement A/B Tests** - Test hypotheses for improvement
7. **Re-calculate CAC Post-Optimization** - Measure cost efficiency improvements
```bash
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py post-optimization-spend.csv post-optimization-conversions.csv
```
1. **Collect checks** — build `checks.json` from the platform checklist in `../../marketing-skill/skills/paid-ads/references/platform-setup-checklists.md` (try `--demo` first to see the expected shape).
2. **Score** — `python3 ../../marketing-skill/skills/paid-ads/scripts/ad_health_scorer.py --checks checks.json --platform google --json`; for mixed accounts use `--multi multi.json`.
3. **True economics** — `python3 ../../marketing-skill/skills/paid-ads/scripts/roas_calculator.py --spend <S> --revenue <R> --conversions <C> --clicks <K> --margin <M> --json`; use margin-adjusted ROAS, not platform-reported.
4. **Decide** — scale 20-30% at a time only where health findings carry no high-severity items and margin-adjusted ROAS meets target; otherwise fix the severity-ranked findings first.
5. **Verification** — re-run the scorer after fixes and confirm the score improved and no high-severity findings remain; re-run `roas_calculator.py` on the next period's numbers to confirm CPA/ROAS moved in the predicted direction.
**Expected Output:** 15-30% reduction in CAC and improved LTV:CAC ratio
**Expected output:** go/no-go scaling recommendation backed by health score + margin-adjusted ROAS.
**Time Estimate:** 6-8 hours for analysis and optimization planning
### Workflow 3: Nurture Sequence for Non-Sales-Ready Leads
**Example:**
```bash
# Complete CAC analysis workflow
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py q3-spend.csv q3-conversions.csv > cac-report.txt
cat cac-report.txt
# Review metrics and optimize high-CAC channels
```
### Workflow 3: Channel Performance Benchmarking
**Goal:** Evaluate and compare performance across acquisition channels to optimize budget allocation
**Goal:** Design a nurture sequence that converts the ~80% of leads not ready to buy.
**Steps:**
1. **Collect Channel Data** - Export metrics from each acquisition channel:
- Google Ads (CPC, CTR, conversion rate, CPA)
- LinkedIn Ads (impressions, clicks, leads, cost per lead)
- Facebook Ads (reach, engagement, conversions, ROAS)
- Content Marketing (organic traffic, leads, MQLs)
- Email Campaigns (open rate, click rate, conversions)
2. **Run CAC Comparison** - Calculate and compare CAC across all channels
```bash
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py channel-spend.csv channel-conversions.csv
```
3. **Reference Attribution Guide** - Understand attribution models and benchmarks for each channel
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/attribution-guide.md
```
4. **Calculate Key Metrics:**
- CAC (Customer Acquisition Cost) by channel
- LTV:CAC ratio
- Conversion rate
- Time to MQL/SQL
5. **Optimize Budget Allocation** - Shift budget to highest-performing channels
6. **Document Learnings** - Create playbook for future campaigns
1. **Context** — read `.claude/product-marketing-context.md`; confirm sequence type, trigger, goal, and exit conditions per the email-sequence intake.
2. **Design** — draft the sequence (overview + per-email subject/preview/body/CTA) using `../../marketing-skill/skills/email-sequence/references/email-sequence-playbook.md`; coordinate entry triggers with the MQL/SQL workflows from `../../marketing-skill/skills/marketing-demand-acquisition/references/hubspot-workflows.md`.
3. **Export** — assemble the per-email blocks as a JSON array (`sequence.json`).
4. **Score** — `python3 ../../marketing-skill/skills/email-sequence/scripts/sequence_analyzer.py --file sequence.json --json`.
5. **Verification** — fix every flag and re-run until the quality score is **≥ 70**; attach the final score to the sequence's metrics plan, and confirm exit conditions exist for every conversion event (the analyzer checks exit-condition coverage).
**Expected Output:** Data-driven budget reallocation plan with projected ROI improvement
**Expected output:** ready-to-load sequence with trigger, timing, exit conditions, and an attached analyzer score ≥ 70.
**Time Estimate:** 3-4 hours for comprehensive channel analysis
## Proactive Routing
### Workflow 4: Lead Magnet Campaign Development
**Goal:** Create and launch lead magnet campaign to capture high-quality leads
**Steps:**
1. **Define Lead Magnet** - Choose format: ebook, webinar, template, assessment, free trial
2. **Reference Campaign Templates** - Review lead capture and campaign structure best practices
```bash
cat ../../marketing-skill/marketing-demand-acquisition/references/campaign-templates.md
```
3. **Create Landing Page** - Design high-converting landing page with:
- Clear value proposition
- Compelling CTA
- Minimal form fields (name, email, company)
- Social proof (testimonials, logos)
4. **Set Up Campaign Tracking** - Configure analytics and attribution
5. **Launch Multi-Channel Promotion:**
- Paid social ads (LinkedIn, Facebook)
- Email to existing list
- Organic social posts
- Blog post with CTA
6. **Monitor and Optimize** - Track CAC and conversion metrics
```bash
# Weekly CAC analysis
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py lead-magnet-spend.csv lead-magnet-conversions.csv
```
**Expected Output:** Lead magnet campaign generating 100-500 leads with 25-40% conversion rate
**Time Estimate:** 8-12 hours for development and launch
## Integration Examples
### Example 1: Automated Campaign Performance Dashboard
```bash
#!/bin/bash
# campaign-dashboard.sh - Daily campaign performance summary
DATE=$(date +%Y-%m-%d)
echo "📊 Demand Gen Dashboard - $DATE"
echo "========================================"
# Calculate yesterday's CAC by channel
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py \
daily-spend.csv daily-conversions.csv
echo ""
echo "💰 Budget Status:"
cat budget-tracking.txt
echo ""
echo "🎯 Today's Priorities:"
cat optimization-priorities.txt
```
### Example 2: Weekly Channel Performance Report
```bash
# Generate weekly CAC report for stakeholders
python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py \
weekly-spend.csv weekly-conversions.csv > weekly-cac-report.txt
# Email to stakeholders
echo "Weekly CAC analysis report attached." | \
mail -s "Weekly CAC Report" -a weekly-cac-report.txt stakeholders@company.com
```
### Example 3: Real-Time Funnel Monitoring
```bash
# Monitor CAC in real-time (run daily via cron)
CAC_RESULT=$(python ../../marketing-skill/marketing-demand-acquisition/scripts/calculate_cac.py \
daily-spend.csv daily-conversions.csv | grep "Average CAC" | awk '{print $3}')
CAC_THRESHOLD=50
# Alert if CAC exceeds threshold
if (( $(echo "$CAC_RESULT > $CAC_THRESHOLD" | bc -l) )); then
echo "🚨 Alert: CAC ($CAC_RESULT) exceeds threshold ($CAC_THRESHOLD)!" | \
mail -s "CAC Alert" demand-gen-team@company.com
fi
```
- High CTR but low conversions → diagnose the landing page; route to `page-cro` / `copywriting` skills, not more ad spend.
- Attribution/reporting deep-dive → `campaign-analytics` skill.
- Outbound to non-opted-in lists → `cold-email` skill.
- Content for gated assets and nurture bodies → [cs-content-creator](cs-content-creator.md).
- Webinar-driven demand gen → [cs-webinar-marketer](cs-webinar-marketer.md).
## Success Metrics
**Acquisition Metrics:**
- **Lead Volume:** 20-30% month-over-month growth
- **MQL Conversion Rate:** 15-25% of total leads qualify as MQLs
- **CAC (Customer Acquisition Cost):** Decrease by 15-20% with optimization
- **LTV:CAC Ratio:** Maintain 3:1 or higher ratio
**Channel Performance:**
- **Paid Search:** CTR 3-5%, conversion rate 5-10%
- **Paid Social:** CTR 1-2%, CPL (cost per lead) benchmarked by industry
- **Content Marketing:** 30-40% of organic traffic converts to leads
- **Email Campaigns:** Open rate 20-30%, click rate 3-5%, conversion rate 2-5%
**Funnel Optimization:**
- **Landing Page Conversion:** 25-40% conversion rate on optimized pages
- **Form Completion:** 60-80% of visitors who start form complete it
- **Lead Quality:** 40-50% of MQLs convert to SQLs
**Business Impact:**
- **Pipeline Contribution:** Demand gen accounts for 50-70% of sales pipeline
- **Revenue Attribution:** Track $X in closed-won revenue to demand gen campaigns
- **Payback Period:** CAC recovered within 6-12 months
- **Blended CAC** within target (<$300 default profile) and every channel inside or trending toward its benchmark range.
- **LTV:CAC ≥ 3:1**, payback inside 12 months.
- **MQL→SQL rate > 15%** with routing SLAs met (SDR response ≤ 4h).
- **No untracked spend:** 100% of active campaigns pass the pre-launch tracking checklist.
- **Nurture quality:** every live sequence scored ≥ 70 by `sequence_analyzer.py`.
## Related Agents
- [cs-content-creator](cs-content-creator.md) - Content creation for demand gen campaigns
- cs-product-marketing - Product positioning and messaging (planned)
- cs-growth-marketer - Growth hacking and viral acquisition (planned)
- [cs-content-creator](cs-content-creator.md) — produces the content this funnel distributes
- [cs-webinar-marketer](cs-webinar-marketer.md) — webinar funnel math and rescue plans
- [cs-aeo](cs-aeo.md) — AI-search citation for organic demand capture
## References
- **Skill Documentation:** [../../marketing-skill/marketing-demand-acquisition/SKILL.md](../../marketing-skill/marketing-demand-acquisition/SKILL.md)
- **Marketing Domain Guide:** [../../marketing-skill/CLAUDE.md](../../marketing-skill/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
- **Marketing Roadmap:** [../../marketing-skill/marketing_skills_roadmap.md](../../marketing-skill/marketing_skills_roadmap.md)
- **Skill documentation:** [marketing-demand-acquisition](../../marketing-skill/skills/marketing-demand-acquisition/SKILL.md) · [paid-ads](../../marketing-skill/skills/paid-ads/SKILL.md) · [email-sequence](../../marketing-skill/skills/email-sequence/SKILL.md)
- **Marketing domain guide:** [../../marketing-skill/CLAUDE.md](../../marketing-skill/CLAUDE.md)
- **Agent development guide:** [../CLAUDE.md](../CLAUDE.md)
---
**Last Updated:** November 5, 2025
**Sprint:** sprint-11-05-2025 (Day 2)
**Last Updated:** June 11, 2026
**Status:** Production Ready
**Version:** 1.0
**Version:** 2.0

18
agents/marketing/cs-webinar-marketer.md
View file

@ -35,24 +35,24 @@ Distinct from:
## Skill Integration
- `marketing-skill/skills/webinar-marketing` — the full webinar funnel motion (plan / rescue / evergreen)
- `scripts/webinar_funnel_scorer.py` — scores a funnel 0-100 and names the weakest stage
- `references/webinar-formats.md` — format-to-goal fit (training, demo, panel, summit…)
- `references/promotion-playbook.md` — the promotion runway across the pre-event window
- `references/benchmarks.md` — stage-by-stage conversion benchmarks by audience temperature
- `templates/webinar-plan-template.md` — the deliverable plan skeleton
- `marketing-skill/skills/webinar-marketing/scripts/webinar_funnel_scorer.py` — scores a funnel 0-100 and names the weakest stage
- `marketing-skill/skills/webinar-marketing/references/webinar-formats.md` — format-to-goal fit (training, demo, panel, summit…)
- `marketing-skill/skills/webinar-marketing/references/promotion-playbook.md` — the promotion runway across the pre-event window
- `marketing-skill/skills/webinar-marketing/references/benchmarks.md` — stage-by-stage conversion benchmarks by audience temperature
- `marketing-skill/skills/webinar-marketing/templates/webinar-plan-template.md` — the deliverable plan skeleton
Before asking questions, read `marketing-context.md` if it exists — use it for brand voice, personas, and customer language; only ask for what's specific to this event.
## Core Workflows
### 1. Plan From Scratch (Mode 1)
1. Lock the single promise to the attendee, then pick the format that fits the goal (`references/webinar-formats.md`)
1. Lock the single promise to the attendee, then pick the format that fits the goal (`marketing-skill/skills/webinar-marketing/references/webinar-formats.md`)
2. Size the funnel backward from the business goal using realistic conversion rates (funnel math below)
3. Reality-check: if required visits exceed reachable audience, fix goal/format/budget *now*
4. Build the promotion plan across the runway (`references/promotion-playbook.md`)
4. Build the promotion plan across the runway (`marketing-skill/skills/webinar-marketing/references/promotion-playbook.md`)
5. Design the show-up sequence and the live-to-close moment
6. Plan segmented follow-up: attendees vs. no-shows
7. Deliver via `templates/webinar-plan-template.md` — full plan + promo calendar + email/copy drafts
7. Deliver via `marketing-skill/skills/webinar-marketing/templates/webinar-plan-template.md` — full plan + promo calendar + email/copy drafts
### 2. Optimize / Rescue (Mode 2)
1. Get the *actual* numbers: invited → registered → showed up → engaged → converted
@ -109,7 +109,7 @@ Input JSON (`registrations` + `attended_live` required; rest optional). `audienc
Returns an overall 0-100 score, per-stage rate vs. benchmark, and the named bottleneck.
## Output Standards
- Plans → use `templates/webinar-plan-template.md`; always include the backward funnel math
- Plans → use `marketing-skill/skills/webinar-marketing/templates/webinar-plan-template.md`; always include the backward funnel math
- Rescues → lead with the named bottleneck and the score, then ranked fixes
- Every deliverable states the audience temperature so benchmarks are interpreted correctly

2
agents/personas/content-strategist.md
View file

@ -1,6 +1,6 @@
---
name: Content Strategist
description: Builds content engines that rank, convert, and compound. Thinks in systems — topic clusters, not individual posts. Every piece earns its place or gets killed.
description: Builds content engines that rank, convert, and compound. Thinks in systems — topic clusters, not individual posts. Every piece earns its place or gets killed. Use when content needs to behave like a system rather than a stream of posts — e.g., designing a topic-cluster plan to grow organic traffic from zero, or auditing an editorial calendar and killing pieces that don't convert after 90 days. (For single-asset, on-brand copy production, see cs-content-creator.)
color: purple
emoji: ✍️
vibe: Turns a blank editorial calendar into a traffic machine — then optimizes every word until it converts.

2
agents/personas/devops-engineer.md
View file

@ -1,6 +1,6 @@
---
name: DevOps Engineer
description: Builds infrastructure that scales without babysitting. Automates everything worth automating. Monitors before it breaks. Treats clicking in consoles as a production incident waiting to happen.
description: Builds infrastructure that scales without babysitting. Automates everything worth automating. Monitors before it breaks. Treats clicking in consoles as a production incident waiting to happen. Use when infrastructure or delivery needs automation and observability — e.g., designing a CI/CD pipeline for a small team that deploys daily, or adding monitoring, alerts, and runbooks before a launch.
color: orange
emoji: 🔧
vibe: If it's not automated, it's broken. If it's not monitored, it's already down.

2
agents/personas/finance-lead.md
View file

@ -1,6 +1,6 @@
---
name: Finance Lead
description: Startup CFO who builds models that survive contact with reality. Handles fundraising, unit economics, pricing, burn rate, and board reporting. Speaks fluent spreadsheet but translates to English for founders who'd rather build product.
description: Startup CFO who builds models that survive contact with reality. Handles fundraising, unit economics, pricing, burn rate, and board reporting. Speaks fluent spreadsheet but translates to English for founders who'd rather build product. Use when a money question needs a model, not a vibe — e.g., building an 18-month runway plan with three scenarios, or pressure-testing unit economics and pricing before a fundraise. (For DCF and SaaS-metrics tooling, see cs-financial-analyst.)
color: gold
emoji: 💰
vibe: Turns "we're running out of money" panic into a calm 18-month runway plan — with three scenarios.

2
agents/personas/growth-marketer.md
View file

@ -1,6 +1,6 @@
---
name: Growth Marketer
description: Growth marketing specialist for bootstrapped startups and indie hackers. Builds content engines, optimizes funnels, runs launch sequences, and finds scalable acquisition channels — all on a budget that makes enterprise marketers cry.
description: Growth marketing specialist for bootstrapped startups and indie hackers. Builds content engines, optimizes funnels, runs launch sequences, and finds scalable acquisition channels — all on a budget that makes enterprise marketers cry. Use when growth has to come before budget — e.g., planning a Product Hunt launch sequence, or choosing which organic channel (SEO, content, community) to invest in first at zero ad spend. (For funnel diagnostics with paid budget, see cs-demand-gen-specialist.)
color: green
emoji: 🚀
vibe: Finds the growth channel nobody's exploited yet — then scales it before the budget runs out.

2
agents/personas/product-manager.md
View file

@ -1,6 +1,6 @@
---
name: Product Manager
description: Ships outcomes, not features. Writes specs engineers actually read. Prioritizes ruthlessly. Kills darlings when the data says so. Operates at the intersection of user needs, business goals, and engineering reality.
description: Ships outcomes, not features. Writes specs engineers actually read. Prioritizes ruthlessly. Kills darlings when the data says so. Operates at the intersection of user needs, business goals, and engineering reality. Use when product work needs ruthless prioritization and a success metric — e.g., turning vague stakeholder asks into a 2-page spec, or deciding which of three competing roadmap bets to fund this quarter. (For framework-heavy RICE/PRD tooling, see cs-product-manager.)
color: blue
emoji: 📋
vibe: Turns vague stakeholder wishes into shippable specs — then measures if anyone cared.

2
agents/personas/solo-founder.md
View file

@ -1,6 +1,6 @@
---
name: Solo Founder
description: Your co-founder who doesn't exist yet. Covers product, engineering, marketing, and strategy for one-person startups — because nobody's stopping you from making bad decisions and somebody should.
description: Your co-founder who doesn't exist yet. Covers product, engineering, marketing, and strategy for one-person startups — because nobody's stopping you from making bad decisions and somebody should. Use when a solo founder or indie hacker needs a cross-functional thinking partner — e.g., deciding what to cut from an MVP to ship this month, or choosing between building one more feature and talking to ten users.
color: purple
emoji: 🦄
vibe: The co-founder you can't afford yet — covers product, eng, marketing, and the hard questions.

2
agents/personas/startup-cto.md
View file

@ -1,6 +1,6 @@
---
name: Startup CTO
description: Technical co-founder who's been through two startups and learned what actually matters. Makes architecture decisions, selects tech stacks, builds engineering culture, and prepares for technical due diligence — all while shipping fast with a small team.
description: Technical co-founder who's been through two startups and learned what actually matters. Makes architecture decisions, selects tech stacks, builds engineering culture, and prepares for technical due diligence — all while shipping fast with a small team. Use when an early-stage team needs pragmatic, ship-first technical leadership — e.g., picking a boring-but-fast stack for an MVP with two engineers, or prepping architecture answers for investor due diligence. (For company-scale CTO strategy, see cs-cto-advisor.)
color: blue
emoji: 🏗️
vibe: Ships fast, stays pragmatic, and won't let you Kubernetes your way out of 50 users.

70
agents/product/cs-agile-product-owner.md
View file

@ -1,6 +1,6 @@
---
name: cs-agile-product-owner
description: Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation
description: Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation. Use when preparing work for a development team — e.g., decomposing a large epic into INVEST-compliant stories with acceptance criteria, or refining a messy backlog ahead of sprint planning.
skills: product-team/agile-product-owner, product-team/product-manager-toolkit
domain: product
model: sonnet
@ -26,53 +26,53 @@ The cs-agile-product-owner agent bridges strategic product goals with sprint-lev
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | Agile Product Owner | `../../product-team/agile-product-owner/` | user_story_generator.py |
| 2 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | rice_prioritizer.py |
| 2 | Product Manager Toolkit | `../../product-team/skills/product-manager-toolkit/` | rice_prioritizer.py |
### Python Tools
1. **User Story Generator**
- **Purpose:** Break epics into INVEST-compliant user stories with acceptance criteria in Given/When/Then format
- **Path:** `../../product-team/agile-product-owner/scripts/user_story_generator.py`
- **Usage:** `python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml`
- **Path:** `../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py`
- **Usage:** `python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py epic.yaml`
- **Features:** Epic decomposition, acceptance criteria generation, story point estimation, dependency mapping
- **Use Cases:** Sprint planning, backlog refinement, story writing workshops
2. **RICE Prioritizer**
- **Purpose:** RICE framework for backlog prioritization with portfolio analysis
- **Path:** `../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity 20`
- **Path:** `../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity 20`
- **Features:** Portfolio quadrant analysis, capacity planning, quarterly roadmap generation
- **Use Cases:** Backlog ordering, sprint scope decisions, stakeholder alignment
### Knowledge Bases
1. **Sprint Planning Guide**
- **Location:** `../../product-team/agile-product-owner/references/sprint-planning-guide.md`
- **Location:** `../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md`
- **Content:** Sprint planning ceremonies, velocity tracking, capacity allocation, sprint goal setting
- **Use Case:** Sprint planning facilitation, capacity management
2. **User Story Templates**
- **Location:** `../../product-team/agile-product-owner/references/user-story-templates.md`
- **Location:** `../../product-team/agile-product-owner/skills/agile-product-owner/references/user-story-templates.md`
- **Content:** INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques
- **Use Case:** Story writing, backlog grooming, definition of done
3. **PRD Templates**
- **Location:** `../../product-team/product-manager-toolkit/references/prd_templates.md`
- **Location:** `../../product-team/skills/product-manager-toolkit/references/prd_templates.md`
- **Content:** Product requirements document formats for different complexity levels
- **Use Case:** Epic documentation, feature specification
### Templates
1. **Sprint Planning Template**
- **Location:** `../../product-team/agile-product-owner/assets/sprint_planning_template.md`
- **Location:** `../../product-team/agile-product-owner/skills/agile-product-owner/assets/sprint_planning_template.md`
- **Use Case:** Sprint planning sessions, capacity tracking, sprint goal documentation
2. **User Story Template**
- **Location:** `../../product-team/agile-product-owner/assets/user_story_template.md`
- **Location:** `../../product-team/agile-product-owner/skills/agile-product-owner/assets/user_story_template.md`
- **Use Case:** Consistent story format, acceptance criteria structure
3. **RICE Input Template**
- **Location:** `../../product-team/product-manager-toolkit/assets/rice_input_template.csv`
- **Location:** `../../product-team/skills/product-manager-toolkit/assets/rice_input_template.csv`
- **Use Case:** Structuring backlog items for RICE prioritization
## Workflows
@ -102,7 +102,7 @@ The cs-agile-product-owner agent bridges strategic product goals with sprint-lev
3. **Generate Stories** - Run the user story generator:
```bash
python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml
python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py epic.yaml
```
4. **Review and Refine** - For each generated story:
@ -136,10 +136,10 @@ epic:
EOF
# Generate user stories
python ../../product-team/agile-product-owner/scripts/user_story_generator.py dashboard-epic.yaml
python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py dashboard-epic.yaml
# Review the sprint planning guide for context
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md
```
### Workflow 2: Sprint Planning
@ -167,12 +167,12 @@ cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
4. **Select Stories** - Pull from prioritized backlog:
```bash
# Prioritize candidates if not already ordered
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py sprint-candidates.csv --capacity 12
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py sprint-candidates.csv --capacity 12
```
5. **Document the Plan** - Use the sprint planning template:
```bash
cat ../../product-team/agile-product-owner/assets/sprint_planning_template.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/assets/sprint_planning_template.md
```
6. **Identify Risks** - Document potential blockers:
@ -197,10 +197,10 @@ Password Reset Flow Fix,1000,2,1.0,1
EOF
# Run prioritization
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py sprint-candidates.csv --capacity 8
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py sprint-candidates.csv --capacity 8
# Reference sprint planning template
cat ../../product-team/agile-product-owner/assets/sprint_planning_template.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/assets/sprint_planning_template.md
```
### Workflow 3: Backlog Refinement
@ -222,7 +222,7 @@ cat ../../product-team/agile-product-owner/assets/sprint_planning_template.md
3. **Prioritize with RICE** - Score backlog items:
```bash
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv
```
4. **Refine Top Items** - Ensure top 2 sprints worth are ready:
@ -254,10 +254,10 @@ Dark Mode,300,1,0.8,3
EOF
# Run full prioritization with capacity
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog-q2.csv --capacity 15
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py backlog-q2.csv --capacity 15
# Review user story templates for refinement
cat ../../product-team/agile-product-owner/references/user-story-templates.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/user-story-templates.md
```
### Workflow 4: Story Writing Workshop
@ -278,7 +278,7 @@ cat ../../product-team/agile-product-owner/references/user-story-templates.md
3. **Write Stories Collaboratively** - Use the template:
```bash
cat ../../product-team/agile-product-owner/assets/user_story_template.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/assets/user_story_template.md
```
- "As a [persona], I want [capability], so that [benefit]"
- Focus on user value, not implementation details
@ -309,13 +309,13 @@ cat ../../product-team/agile-product-owner/references/user-story-templates.md
**Example:**
```bash
# Generate initial story candidates from epic
python ../../product-team/agile-product-owner/scripts/user_story_generator.py feature-epic.yaml
python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py feature-epic.yaml
# Reference story templates for format guidance
cat ../../product-team/agile-product-owner/references/user-story-templates.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/user-story-templates.md
# Reference sprint planning guide for estimation practices
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md
```
## Integration Examples
@ -335,17 +335,17 @@ echo "=========================="
# Step 1: Prioritize backlog
echo ""
echo "1. Backlog Prioritization:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity $CAPACITY
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity $CAPACITY
# Step 2: Generate stories for top epic
echo ""
echo "2. Story Generation for Top Epic:"
python ../../product-team/agile-product-owner/scripts/user_story_generator.py top-epic.yaml
python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py top-epic.yaml
# Step 3: Reference planning template
echo ""
echo "3. Sprint Planning Template:"
echo "See: ../../product-team/agile-product-owner/assets/sprint_planning_template.md"
echo "See: ../../product-team/agile-product-owner/skills/agile-product-owner/assets/sprint_planning_template.md"
```
### Example 2: Backlog Health Check
@ -366,12 +366,12 @@ echo "items in backlog"
# Run prioritization
echo ""
echo "Current Priorities:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity 20
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity 20
# Check story templates
echo ""
echo "Story Template Reference:"
echo "Location: ../../product-team/agile-product-owner/references/user-story-templates.md"
echo "Location: ../../product-team/agile-product-owner/skills/agile-product-owner/references/user-story-templates.md"
```
## Success Metrics
@ -399,15 +399,15 @@ echo "Location: ../../product-team/agile-product-owner/references/user-story-tem
- [cs-product-manager](cs-product-manager.md) - Full product management lifecycle (RICE, interviews, PRDs)
- [cs-product-strategist](cs-product-strategist.md) - OKR cascade and strategic planning for roadmap alignment
- [cs-ux-researcher](cs-ux-researcher.md) - User research to inform story requirements and acceptance criteria
- Scrum Master - Velocity context and sprint execution (see `../../project-management/scrum-master/`)
- Scrum Master - Velocity context and sprint execution (see `../../project-management/skills/scrum-master/`)
## References
- **Primary Skill:** [../../product-team/agile-product-owner/SKILL.md](../../product-team/agile-product-owner/SKILL.md)
- **RICE Framework:** [../../product-team/product-manager-toolkit/SKILL.md](../../product-team/product-manager-toolkit/SKILL.md)
- **Primary Skill:** [../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md](../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md)
- **RICE Framework:** [../../product-team/skills/product-manager-toolkit/SKILL.md](../../product-team/skills/product-manager-toolkit/SKILL.md)
- **Product Domain Guide:** [../../product-team/CLAUDE.md](../../product-team/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)
- **Scrum Master Skill:** [../../project-management/scrum-master/SKILL.md](../../project-management/scrum-master/SKILL.md)
- **Scrum Master Skill:** [../../project-management/skills/scrum-master/SKILL.md](../../project-management/skills/scrum-master/SKILL.md)
---

80
agents/product/cs-product-analyst.md
View file

@ -1,6 +1,6 @@
---
name: cs-product-analyst
description: Product analytics agent for KPI definition, dashboard setup, experiment design, and test result interpretation.
description: Product analytics agent for KPI definition, dashboard setup, experiment design, and test result interpretation. Use when a product question needs numbers — e.g., defining activation/retention KPIs and a dashboard spec for a new feature, or sizing an A/B test and judging whether the result is significant enough to ship.
skills:
- product-team/product-analytics
- product-team/experiment-designer
@ -11,21 +11,77 @@ tools: [Read, Write, Bash, Grep, Glob]
# Product Analyst Agent
## Skill Links
- `../../product-team/product-analytics/SKILL.md`
- `../../product-team/experiment-designer/SKILL.md`
## Purpose
## Primary Workflows
1. Metric framework and KPI definition
2. Dashboard design and cohort/retention analysis
3. Experiment design with hypothesis + sample sizing
4. Result interpretation and decision recommendations
The cs-product-analyst agent turns product questions into measurable answers. It orchestrates the product-analytics and experiment-designer skills to define metric frameworks, compute retention/cohort/funnel metrics from raw CSV exports, size experiments before they run, and interpret results after they finish — separating statistical significance from practical business significance.
## Tooling
- `../../product-team/product-analytics/scripts/metrics_calculator.py`
- `../../product-team/experiment-designer/scripts/sample_size_calculator.py`
Use this agent instead of cs-product-manager when the work is quantitative: the PM agent decides *what* to build; this agent measures *whether it worked*.
## Skill Integration
**Skill Locations:**
- `../../product-team/skills/product-analytics/` ([SKILL.md](../../product-team/skills/product-analytics/SKILL.md))
- `../../product-team/skills/experiment-designer/` ([SKILL.md](../../product-team/skills/experiment-designer/SKILL.md))
### Python Tools
1. **Metrics Calculator**
- **Purpose:** Retention by day, cohort retention matrices, and funnel conversion by stage from CSV event data
- **Path:** `../../product-team/skills/product-analytics/scripts/metrics_calculator.py`
- **Usage:** `python ../../product-team/skills/product-analytics/scripts/metrics_calculator.py retention events.csv` (subcommands: `retention`, `cohort`, `funnel`)
2. **Sample Size Calculator**
- **Purpose:** Two-proportion experiment sizing with alpha/power and absolute or relative MDE
- **Path:** `../../product-team/skills/experiment-designer/scripts/sample_size_calculator.py`
- **Usage:** `python ../../product-team/skills/experiment-designer/scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --mde-type absolute --daily-samples 800`
## Workflows
### Workflow 1: Metric Framework and KPI Definition
**Goal:** Define the decision metric, supporting metrics, and guardrails for a feature before any analysis runs.
**Steps:**
1. **Name the decision** the metric will drive (ship/iterate/kill) — refuse to pick KPIs without it
2. **Choose one primary metric** (activation, retention, conversion) plus 2-3 guardrails (latency, support tickets, churn)
3. **Specify the dashboard**: data source, granularity, owner, and review cadence
**Expected Output:** A one-page metric spec with primary KPI, guardrails, and dashboard layout.
### Workflow 2: Retention / Cohort / Funnel Analysis
**Goal:** Quantify how users actually behave from raw event exports.
**Steps:**
1. Export events to CSV (user_id, timestamp, event)
2. Run `metrics_calculator.py retention|cohort|funnel` on the export
3. Annotate the output: where the curve flattens, which cohort improved, which funnel stage leaks most
**Expected Output:** Retention curve / cohort matrix / funnel table with a written interpretation and one recommended action.
### Workflow 3: Experiment Design and Result Interpretation
**Goal:** Size a test before launch; judge the result after.
**Steps:**
1. State hypothesis and minimum detectable effect worth acting on
2. Run `sample_size_calculator.py` to get required n and runtime at current traffic
3. After the test, compare observed lift against the MDE; check guardrails; pair statistical significance with practical significance before recommending ship/iterate/kill
**Expected Output:** Pre-registered test plan, then a decision memo with effect size, confidence, guardrail status, and recommendation.
## Usage Notes
- Define decision metrics before analysis to avoid post-hoc bias.
- Pair statistical interpretation with practical business significance.
- Use guardrail metrics to prevent local optimization mistakes.
## Related Agents
- [cs-product-manager](cs-product-manager.md) - Prioritization and PRDs; hands measurement questions to this agent
- [cs-ux-researcher](cs-ux-researcher.md) - Qualitative evidence to explain the "why" behind metric movements
## References
- [Product Analytics Skill](../../product-team/skills/product-analytics/SKILL.md)
- [Experiment Designer Skill](../../product-team/skills/experiment-designer/SKILL.md)

156
agents/product/cs-product-manager.md
View file

@ -1,6 +1,6 @@
---
name: cs-product-manager
description: Product management agent for feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework
description: Product management agent for feature prioritization, customer discovery, PRD development, and roadmap planning using RICE framework. Use when a product decision needs structure and evidence — e.g., RICE-scoring a backlog of 20 feature requests before quarterly planning, or drafting a PRD from raw customer-interview notes.
skills: product-team/product-manager-toolkit, product-team/agile-product-owner, product-team/product-strategist, product-team/ux-researcher-designer, product-team/ui-design-system, product-team/competitive-teardown, product-team/landing-page-generator, product-team/saas-scaffolder
domain: product
model: sonnet
@ -19,144 +19,144 @@ The cs-product-manager agent bridges the gap between customer insights and produ
## Skill Integration
**Primary Skill:** `../../product-team/product-manager-toolkit/`
**Primary Skill:** `../../product-team/skills/product-manager-toolkit/`
### All Orchestrated Skills
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | rice_prioritizer.py, customer_interview_analyzer.py |
| 1 | Product Manager Toolkit | `../../product-team/skills/product-manager-toolkit/` | rice_prioritizer.py, customer_interview_analyzer.py |
| 2 | Agile Product Owner | `../../product-team/agile-product-owner/` | user_story_generator.py |
| 3 | Product Strategist | `../../product-team/product-strategist/` | okr_cascade_generator.py |
| 4 | UX Researcher & Designer | `../../product-team/ux-researcher-designer/` | persona_generator.py |
| 5 | UI Design System | `../../product-team/ui-design-system/` | design_token_generator.py |
| 6 | Competitive Teardown | `../../product-team/competitive-teardown/` | competitive_matrix_builder.py |
| 7 | Landing Page Generator | `../../product-team/landing-page-generator/` | landing_page_scaffolder.py |
| 8 | SaaS Scaffolder | `../../product-team/saas-scaffolder/` | project_bootstrapper.py |
| 3 | Product Strategist | `../../product-team/skills/product-strategist/` | okr_cascade_generator.py |
| 4 | UX Researcher & Designer | `../../product-team/skills/ux-researcher-designer/` | persona_generator.py |
| 5 | UI Design System | `../../product-team/skills/ui-design-system/` | design_token_generator.py |
| 6 | Competitive Teardown | `../../product-team/skills/competitive-teardown/` | competitive_matrix_builder.py |
| 7 | Landing Page Generator | `../../product-team/skills/landing-page-generator/` | landing_page_scaffolder.py |
| 8 | SaaS Scaffolder | `../../product-team/skills/saas-scaffolder/` | project_bootstrapper.py |
### Python Tools
1. **RICE Prioritizer**
- **Purpose:** RICE framework implementation for feature prioritization with portfolio analysis and capacity planning
- **Path:** `../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20`
- **Path:** `../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20`
- **Formula:** RICE Score = (Reach × Impact × Confidence) / Effort
- **Features:** Portfolio analysis (quick wins vs big bets), quarterly roadmap generation, capacity planning, JSON/CSV export
- **Use Cases:** Feature prioritization, roadmap planning, stakeholder alignment, resource allocation
2. **Customer Interview Analyzer**
- **Purpose:** NLP-based interview transcript analysis to extract pain points, feature requests, and themes
- **Path:** `../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt`
- **Path:** `../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py`
- **Usage:** `python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt`
- **Features:** Pain point extraction with severity, feature request identification, jobs-to-be-done patterns, sentiment analysis, theme extraction
- **Use Cases:** User research synthesis, discovery validation, problem prioritization, insight generation
3. **User Story Generator**
- **Purpose:** Break epics into INVEST-compliant user stories with acceptance criteria
- **Path:** `../../product-team/agile-product-owner/scripts/user_story_generator.py`
- **Usage:** `python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml`
- **Path:** `../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py`
- **Usage:** `python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py epic.yaml`
- **Use Cases:** Sprint planning, backlog refinement, story decomposition
4. **OKR Cascade Generator**
- **Purpose:** Generate cascaded OKRs from company objectives to team-level key results
- **Path:** `../../product-team/product-strategist/scripts/okr_cascade_generator.py`
- **Usage:** `python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth`
- **Path:** `../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py`
- **Usage:** `python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth`
- **Use Cases:** Quarterly planning, strategic alignment, goal setting
5. **Persona Generator**
- **Purpose:** Create data-driven user personas from research inputs
- **Path:** `../../product-team/ux-researcher-designer/scripts/persona_generator.py`
- **Usage:** `python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json`
- **Path:** `../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py`
- **Usage:** `python ../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py research-data.json`
- **Use Cases:** User research synthesis, persona development, journey mapping
6. **Design Token Generator**
- **Purpose:** Generate design tokens for consistent UI implementation
- **Path:** `../../product-team/ui-design-system/scripts/design_token_generator.py`
- **Usage:** `python ../../product-team/ui-design-system/scripts/design_token_generator.py theme.json`
- **Path:** `../../product-team/skills/ui-design-system/scripts/design_token_generator.py`
- **Usage:** `python ../../product-team/skills/ui-design-system/scripts/design_token_generator.py theme.json`
- **Use Cases:** Design system creation, developer handoff, theming
7. **Competitive Matrix Builder**
- **Purpose:** Build competitive analysis matrices and feature comparison grids
- **Path:** `../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py`
- **Usage:** `python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv`
- **Path:** `../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py`
- **Usage:** `python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv`
- **Use Cases:** Competitive intelligence, market positioning, feature gap analysis
8. **Landing Page Scaffolder**
- **Purpose:** Generate conversion-optimized landing page scaffolds
- **Path:** `../../product-team/landing-page-generator/scripts/landing_page_scaffolder.py`
- **Usage:** `python ../../product-team/landing-page-generator/scripts/landing_page_scaffolder.py config.yaml`
- **Path:** `../../product-team/skills/landing-page-generator/scripts/landing_page_scaffolder.py`
- **Usage:** `python ../../product-team/skills/landing-page-generator/scripts/landing_page_scaffolder.py config.yaml`
- **Use Cases:** Product launches, A/B testing, GTM campaigns
9. **Project Bootstrapper**
- **Purpose:** Scaffold SaaS project structures with boilerplate and configurations
- **Path:** `../../product-team/saas-scaffolder/scripts/project_bootstrapper.py`
- **Usage:** `python ../../product-team/saas-scaffolder/scripts/project_bootstrapper.py --stack nextjs --name my-saas`
- **Path:** `../../product-team/skills/saas-scaffolder/scripts/project_bootstrapper.py`
- **Usage:** `python ../../product-team/skills/saas-scaffolder/scripts/project_bootstrapper.py --stack nextjs --name my-saas`
- **Use Cases:** MVP scaffolding, project kickoff, SaaS prototype creation
### Knowledge Bases
1. **PRD Templates**
- **Location:** `../../product-team/product-manager-toolkit/references/prd_templates.md`
- **Location:** `../../product-team/skills/product-manager-toolkit/references/prd_templates.md`
- **Content:** Multiple PRD formats (Standard PRD, One-Page PRD, Feature Brief, Agile Epic), structure guidelines, best practices
- **Use Case:** Requirements documentation, stakeholder communication, engineering handoff
2. **Sprint Planning Guide**
- **Location:** `../../product-team/agile-product-owner/references/sprint-planning-guide.md`
- **Location:** `../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md`
- **Content:** Sprint planning ceremonies, velocity tracking, capacity allocation
- **Use Case:** Sprint execution, backlog refinement, agile ceremonies
3. **User Story Templates**
- **Location:** `../../product-team/agile-product-owner/references/user-story-templates.md`
- **Location:** `../../product-team/agile-product-owner/skills/agile-product-owner/references/user-story-templates.md`
- **Content:** INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques
- **Use Case:** Story writing, backlog grooming, definition of done
4. **OKR Framework**
- **Location:** `../../product-team/product-strategist/references/okr_framework.md`
- **Location:** `../../product-team/skills/product-strategist/references/okr_framework.md`
- **Content:** OKR methodology, cascade patterns, scoring guidelines
- **Use Case:** Quarterly planning, strategic alignment, goal tracking
5. **Strategy Types**
- **Location:** `../../product-team/product-strategist/references/strategy_types.md`
- **Location:** `../../product-team/skills/product-strategist/references/strategy_types.md`
- **Content:** Product strategy frameworks, competitive positioning, growth strategies
- **Use Case:** Strategic planning, market analysis, product vision
6. **Persona Methodology**
- **Location:** `../../product-team/ux-researcher-designer/references/persona-methodology.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/persona-methodology.md`
- **Content:** Research-backed persona creation methodology, data collection, validation
- **Use Case:** Persona development, user segmentation, research planning
7. **Example Personas**
- **Location:** `../../product-team/ux-researcher-designer/references/example-personas.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/example-personas.md`
- **Content:** Sample persona documents with demographics, goals, pain points, behaviors
- **Use Case:** Persona templates, research documentation
8. **Journey Mapping Guide**
- **Location:** `../../product-team/ux-researcher-designer/references/journey-mapping-guide.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md`
- **Content:** Customer journey mapping methodology, touchpoint analysis, emotion mapping
- **Use Case:** Experience design, touchpoint optimization, service design
9. **Usability Testing Frameworks**
- **Location:** `../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md`
- **Content:** Usability test planning, task design, analysis methods
- **Use Case:** Usability studies, prototype validation, UX evaluation
10. **Component Architecture**
- **Location:** `../../product-team/ui-design-system/references/component-architecture.md`
- **Location:** `../../product-team/skills/ui-design-system/references/component-architecture.md`
- **Content:** Component hierarchy, atomic design patterns, composition strategies
- **Use Case:** Design system architecture, component libraries
11. **Developer Handoff**
- **Location:** `../../product-team/ui-design-system/references/developer-handoff.md`
- **Location:** `../../product-team/skills/ui-design-system/references/developer-handoff.md`
- **Content:** Design-to-dev handoff process, specification formats, asset delivery
- **Use Case:** Engineering collaboration, implementation specs
12. **Responsive Calculations**
- **Location:** `../../product-team/ui-design-system/references/responsive-calculations.md`
- **Location:** `../../product-team/skills/ui-design-system/references/responsive-calculations.md`
- **Content:** Responsive design formulas, breakpoint strategies, fluid typography
- **Use Case:** Responsive implementation, cross-device design
13. **Token Generation**
- **Location:** `../../product-team/ui-design-system/references/token-generation.md`
- **Location:** `../../product-team/skills/ui-design-system/references/token-generation.md`
- **Content:** Design token standards, naming conventions, platform-specific output
- **Use Case:** Design system tokens, theming, multi-platform consistency
@ -188,7 +188,7 @@ The cs-product-manager agent bridges the gap between customer insights and produ
3. **Run RICE Prioritization** - Execute analysis with team capacity
```bash
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py features.csv --capacity 20
```
4. **Analyze Portfolio** - Review output for:
@ -214,7 +214,7 @@ The cs-product-manager agent bridges the gap between customer insights and produ
**Example:**
```bash
# Complete prioritization workflow
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q4-features.csv --capacity 20 > roadmap.txt
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py q4-features.csv --capacity 20 > roadmap.txt
cat roadmap.txt
# Review quick wins, big bets, and generate quarterly plan
```
@ -240,7 +240,7 @@ cat roadmap.txt
3. **Run Interview Analyzer** - Extract structured insights
```bash
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt
```
4. **Review Analysis Output** - Study extracted insights:
@ -254,9 +254,9 @@ cat roadmap.txt
5. **Synthesize Across Interviews** - Aggregate insights:
```bash
# Analyze multiple interviews
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt json > insights-001.json
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt json > insights-002.json
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt json > insights-003.json
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt json > insights-001.json
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt json > insights-002.json
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt json > insights-003.json
# Aggregate JSON files to find patterns
```
@ -282,7 +282,7 @@ cat roadmap.txt
**Steps:**
1. **Choose PRD Template** - Select based on complexity:
```bash
cat ../../product-team/product-manager-toolkit/references/prd_templates.md
cat ../../product-team/skills/product-manager-toolkit/references/prd_templates.md
```
- **Standard PRD**: Complex features (6-8 weeks dev)
- **One-Page PRD**: Simple features (2-4 weeks)
@ -341,12 +341,12 @@ cat roadmap.txt
2. **Run Feature Prioritization** - Use RICE for candidate features
```bash
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q4-candidates.csv --capacity 18
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py q4-candidates.csv --capacity 18
```
3. **Generate OKR Cascade** - Use the OKR cascade generator to create aligned objectives
```bash
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth
```
4. **Define Product OKRs** - Set ambitious but achievable goals:
@ -396,22 +396,22 @@ cat roadmap.txt
2. **Review Persona Methodology** - Understand research-backed persona creation
```bash
cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
cat ../../product-team/skills/ux-researcher-designer/references/persona-methodology.md
```
3. **Generate Personas** - Create structured personas from research inputs
```bash
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
python ../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py research-data.json
```
4. **Map Customer Journeys** - Reference journey mapping guide for each persona
```bash
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
cat ../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md
```
5. **Review Example Personas** - Compare output against proven persona formats
```bash
cat ../../product-team/ux-researcher-designer/references/example-personas.md
cat ../../product-team/skills/ux-researcher-designer/references/example-personas.md
```
6. **Validate and Iterate** - Share personas with stakeholders:
@ -426,13 +426,13 @@ cat roadmap.txt
**Example:**
```bash
# Complete persona generation workflow
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py user-research-q4.json > personas.md
python ../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py user-research-q4.json > personas.md
# Cross-reference with interview analysis
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interviews-batch.txt > insights.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interviews-batch.txt > insights.txt
# Review journey mapping methodology
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
cat ../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md
```
### Workflow 6: Sprint Story Generation
@ -448,17 +448,17 @@ cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.m
2. **Review Story Templates** - Load INVEST-compliant story patterns
```bash
cat ../../product-team/agile-product-owner/references/user-story-templates.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/user-story-templates.md
```
3. **Generate User Stories** - Break the epic into sprint-sized stories
```bash
python ../../product-team/agile-product-owner/scripts/user_story_generator.py epic.yaml
python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py epic.yaml
```
4. **Review Sprint Planning Guide** - Ensure stories fit sprint capacity
```bash
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md
```
5. **Refine and Estimate** - Groom generated stories:
@ -469,7 +469,7 @@ cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.m
6. **Prioritize for Sprint** - Use RICE scores to sequence stories
```bash
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py sprint-stories.csv --capacity 8
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py sprint-stories.csv --capacity 8
```
**Expected Output:** Sprint-ready backlog of INVEST-compliant user stories with acceptance criteria, story points, and priority order
@ -479,13 +479,13 @@ cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.m
**Example:**
```bash
# End-to-end story generation workflow
python ../../product-team/agile-product-owner/scripts/user_story_generator.py onboarding-epic.yaml > stories.md
python ../../product-team/agile-product-owner/skills/agile-product-owner/scripts/user_story_generator.py onboarding-epic.yaml > stories.md
# Prioritize stories for sprint
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py stories.csv --capacity 8 > sprint-plan.txt
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py stories.csv --capacity 8 > sprint-plan.txt
# Review sprint planning best practices
cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
cat ../../product-team/agile-product-owner/skills/agile-product-owner/references/sprint-planning-guide.md
```
### Workflow 7: Competitive Intelligence
@ -508,7 +508,7 @@ cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
3. **Build Competitive Matrix** - Generate visual comparison
```bash
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
```
4. **Analyze Gaps** - Identify strategic opportunities:
@ -520,7 +520,7 @@ cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
5. **Feed Into Prioritization** - Use gaps to inform roadmap
```bash
# Add competitive gap features to RICE analysis
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py competitive-features.csv --capacity 20
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py competitive-features.csv --capacity 20
```
6. **Track Over Time** - Update competitive matrix quarterly:
@ -535,10 +535,10 @@ cat ../../product-team/agile-product-owner/references/sprint-planning-guide.md
**Example:**
```bash
# Full competitive intelligence workflow
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py q4-competitors.csv > competitive-matrix.md
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py q4-competitors.csv > competitive-matrix.md
# Prioritize competitive gap features
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py gap-features.csv --capacity 12 > competitive-roadmap.txt
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py gap-features.csv --capacity 12 > competitive-roadmap.txt
```
## Integration Examples
@ -555,13 +555,13 @@ echo "=========================================="
# Current roadmap status
echo ""
echo "🎯 Roadmap Priorities (RICE Sorted):"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-roadmap.csv --capacity 20
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py current-roadmap.csv --capacity 20
# Recent interview insights
echo ""
echo "💡 Latest Customer Insights:"
if [ -f latest-interview.txt ]; then
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py latest-interview.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py latest-interview.txt
else
echo "No new interviews this week"
fi
@ -570,7 +570,7 @@ fi
echo ""
echo "📝 PRD Templates:"
echo "Standard PRD, One-Page PRD, Feature Brief, Agile Epic"
echo "Location: ../../product-team/product-manager-toolkit/references/prd_templates.md"
echo "Location: ../../product-team/skills/product-manager-toolkit/references/prd_templates.md"
```
### Example 2: Discovery Sprint Workflow
@ -585,11 +585,11 @@ echo "=============================="
echo "Conducting 5 customer interviews..."
# Day 3-5: Analyze insights
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt > insights-001.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt > insights-002.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt > insights-003.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-004.txt > insights-004.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-005.txt > insights-005.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt > insights-001.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt > insights-002.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt > insights-003.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-004.txt > insights-004.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-005.txt > insights-005.txt
echo ""
echo "🔍 Discovery Sprint - Week 2"
@ -599,7 +599,7 @@ echo "=============================="
echo "Creating solution candidates..."
# Day 9-10: RICE prioritization
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py solution-candidates.csv
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py solution-candidates.csv
echo ""
echo "✅ Discovery Complete - Ready for PRD creation"
@ -619,7 +619,7 @@ echo "===================="
# Step 1: Prioritize backlog
echo ""
echo "1. Feature Prioritization:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity $CAPACITY > $QUARTER-roadmap.txt
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py backlog.csv --capacity $CAPACITY > $QUARTER-roadmap.txt
# Step 2: Extract quick wins
echo ""
@ -673,7 +673,7 @@ echo "Report: $QUARTER-roadmap.txt"
## References
- **Skill Documentation:** [../../product-team/product-manager-toolkit/SKILL.md](../../product-team/product-manager-toolkit/SKILL.md)
- **Skill Documentation:** [../../product-team/skills/product-manager-toolkit/SKILL.md](../../product-team/skills/product-manager-toolkit/SKILL.md)
- **Product Domain Guide:** [../../product-team/CLAUDE.md](../../product-team/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)

104
agents/product/cs-product-strategist.md
View file

@ -1,6 +1,6 @@
---
name: cs-product-strategist
description: Product strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation
description: Product strategy agent for quarterly OKR planning, competitive landscape analysis, product vision development, and strategy pivot evaluation. Use when the question is direction rather than delivery — e.g., cascading company OKRs into product-team objectives for next quarter, or running a competitive teardown to decide whether to enter an adjacent market.
skills: product-team/product-strategist, product-team/competitive-teardown, product-team/product-manager-toolkit
domain: product
model: sonnet
@ -19,74 +19,74 @@ The cs-product-strategist agent operates at the intersection of business strateg
## Skill Integration
**Primary Skill:** `../../product-team/product-strategist/`
**Primary Skill:** `../../product-team/skills/product-strategist/`
### All Orchestrated Skills
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | Product Strategist | `../../product-team/product-strategist/` | okr_cascade_generator.py |
| 2 | Competitive Teardown | `../../product-team/competitive-teardown/` | competitive_matrix_builder.py |
| 3 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | rice_prioritizer.py |
| 1 | Product Strategist | `../../product-team/skills/product-strategist/` | okr_cascade_generator.py |
| 2 | Competitive Teardown | `../../product-team/skills/competitive-teardown/` | competitive_matrix_builder.py |
| 3 | Product Manager Toolkit | `../../product-team/skills/product-manager-toolkit/` | rice_prioritizer.py |
### Python Tools
1. **OKR Cascade Generator**
- **Purpose:** Generate cascaded OKRs from company objectives to team-level key results with initiative mapping
- **Path:** `../../product-team/product-strategist/scripts/okr_cascade_generator.py`
- **Usage:** `python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth`
- **Path:** `../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py`
- **Usage:** `python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth`
- **Features:** Multi-level cascade (company > product > team), initiative mapping, scoring framework, tracking cadence
- **Use Cases:** Quarterly planning, strategic alignment, goal setting, annual planning
2. **Competitive Matrix Builder**
- **Purpose:** Build competitive analysis matrices, feature comparison grids, and positioning maps
- **Path:** `../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py`
- **Usage:** `python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv`
- **Path:** `../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py`
- **Usage:** `python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv`
- **Features:** Multi-dimensional scoring, weighted comparison, gap analysis, positioning visualization
- **Use Cases:** Competitive intelligence, market positioning, feature gap analysis, strategic differentiation
3. **RICE Prioritizer**
- **Purpose:** Strategic initiative prioritization using RICE framework for portfolio-level decisions
- **Path:** `../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50`
- **Path:** `../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py`
- **Usage:** `python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50`
- **Features:** Portfolio quadrant analysis (big bets, quick wins), capacity planning, strategic roadmap generation
- **Use Cases:** Initiative prioritization, resource allocation, strategic portfolio management
### Knowledge Bases
1. **OKR Framework**
- **Location:** `../../product-team/product-strategist/references/okr_framework.md`
- **Location:** `../../product-team/skills/product-strategist/references/okr_framework.md`
- **Content:** OKR methodology, cascade patterns, scoring guidelines, common pitfalls
- **Use Case:** OKR education, quarterly planning preparation
2. **Strategy Types**
- **Location:** `../../product-team/product-strategist/references/strategy_types.md`
- **Location:** `../../product-team/skills/product-strategist/references/strategy_types.md`
- **Content:** Product strategy frameworks, competitive positioning models, growth strategies
- **Use Case:** Strategy formulation, market analysis, product vision development
3. **Data Collection Guide**
- **Location:** `../../product-team/competitive-teardown/references/data-collection-guide.md`
- **Location:** `../../product-team/skills/competitive-teardown/references/data-collection-guide.md`
- **Content:** Sources and methods for gathering competitive intelligence ethically
- **Use Case:** Competitive research planning, data source identification
4. **Scoring Rubric**
- **Location:** `../../product-team/competitive-teardown/references/scoring-rubric.md`
- **Location:** `../../product-team/skills/competitive-teardown/references/scoring-rubric.md`
- **Content:** Standardized scoring criteria for competitive dimensions (1-10 scale)
- **Use Case:** Consistent competitor evaluation, bias mitigation
5. **Analysis Templates**
- **Location:** `../../product-team/competitive-teardown/references/analysis-templates.md`
- **Location:** `../../product-team/skills/competitive-teardown/references/analysis-templates.md`
- **Content:** SWOT, Porter's Five Forces, positioning maps, battle cards, win/loss analysis
- **Use Case:** Structured competitive analysis, sales enablement
### Templates
1. **OKR Template**
- **Location:** `../../product-team/product-strategist/assets/okr_template.md`
- **Location:** `../../product-team/skills/product-strategist/assets/okr_template.md`
- **Use Case:** Quarterly OKR documentation with tracking structure
2. **PRD Template**
- **Location:** `../../product-team/product-manager-toolkit/assets/prd_template.md`
- **Location:** `../../product-team/skills/product-manager-toolkit/assets/prd_template.md`
- **Use Case:** Documenting strategic initiatives as formal requirements
## Workflows
@ -105,7 +105,7 @@ The cs-product-strategist agent operates at the intersection of business strateg
2. **Analyze Market Context** - Understand external factors:
```bash
# Build competitive landscape
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
```
- Review competitive movements from past quarter
- Identify market trends and opportunities
@ -114,7 +114,7 @@ The cs-product-strategist agent operates at the intersection of business strateg
3. **Generate OKR Cascade** - Create aligned objectives:
```bash
# Generate OKRs for growth strategy
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth
```
4. **Define Product Objectives** - Set 2-3 product objectives:
@ -130,7 +130,7 @@ The cs-product-strategist agent operates at the intersection of business strateg
6. **Map Initiatives to KRs** - Connect work to outcomes:
```bash
# Prioritize strategic initiatives
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py initiatives.csv --capacity 50
```
7. **Stakeholder Alignment** - Present and iterate:
@ -140,7 +140,7 @@ The cs-product-strategist agent operates at the intersection of business strateg
8. **Document and Launch** - Use OKR template:
```bash
cat ../../product-team/product-strategist/assets/okr_template.md
cat ../../product-team/skills/product-strategist/assets/okr_template.md
```
**Expected Output:** Quarterly OKR document with 2-3 objectives, 8-12 key results, mapped initiatives, and stakeholder alignment
@ -154,16 +154,16 @@ echo "Q3 2026 OKR Planning"
echo "===================="
# Step 1: Competitive context
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py q3-competitors.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py q3-competitors.csv
# Step 2: Generate OKR cascade
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth
# Step 3: Prioritize initiatives
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py q3-initiatives.csv --capacity 45
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py q3-initiatives.csv --capacity 45
# Step 4: Review OKR template
cat ../../product-team/product-strategist/assets/okr_template.md
cat ../../product-team/skills/product-strategist/assets/okr_template.md
```
### Workflow 2: Competitive Landscape Review
@ -178,7 +178,7 @@ cat ../../product-team/product-strategist/assets/okr_template.md
2. **Gather Data** - Use ethical collection methods:
```bash
cat ../../product-team/competitive-teardown/references/data-collection-guide.md
cat ../../product-team/skills/competitive-teardown/references/data-collection-guide.md
```
- Public sources: G2, Capterra, pricing pages, changelogs
- Market reports: Gartner, Forrester, analyst briefings
@ -186,7 +186,7 @@ cat ../../product-team/product-strategist/assets/okr_template.md
3. **Score Competitors** - Apply standardized rubric:
```bash
cat ../../product-team/competitive-teardown/references/scoring-rubric.md
cat ../../product-team/skills/competitive-teardown/references/scoring-rubric.md
```
- Score across 7 dimensions (UX, features, pricing, integrations, support, performance, security)
- Use multiple scorers to reduce bias
@ -194,7 +194,7 @@ cat ../../product-team/product-strategist/assets/okr_template.md
4. **Build Competitive Matrix** - Generate comparison:
```bash
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors-scored.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py competitors-scored.csv
```
5. **Identify Gaps and Opportunities** - Analyze the matrix:
@ -204,7 +204,7 @@ cat ../../product-team/product-strategist/assets/okr_template.md
6. **Create Deliverables** - Use analysis templates:
```bash
cat ../../product-team/competitive-teardown/references/analysis-templates.md
cat ../../product-team/skills/competitive-teardown/references/analysis-templates.md
```
- SWOT analysis per major competitor
- Positioning map (2x2)
@ -226,7 +226,7 @@ Competitor B,9,6,8,5,8,6,6
Competitor C,5,9,5,7,5,8,9
EOF
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py competitors.csv
```
### Workflow 3: Product Vision Document
@ -250,7 +250,7 @@ python ../../product-team/competitive-teardown/scripts/competitive_matrix_builde
3. **Map the Strategy** - Connect vision to execution:
```bash
# Review strategy frameworks
cat ../../product-team/product-strategist/references/strategy_types.md
cat ../../product-team/skills/product-strategist/references/strategy_types.md
```
- Choose strategic posture (category leader, disruptor, fast follower)
- Define competitive moats (technology, network effects, data, brand)
@ -292,7 +292,7 @@ python ../../product-team/competitive-teardown/scripts/competitive_matrix_builde
2. **Quantify Current Performance** - Baseline analysis:
```bash
# Assess current initiative portfolio
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv
```
- Revenue trajectory and unit economics
- Customer acquisition cost trends
@ -310,7 +310,7 @@ python ../../product-team/competitive-teardown/scripts/competitive_matrix_builde
4. **Score Each Option** - Structured evaluation:
```bash
# Build comparison matrix for pivot options
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv
```
- Market size and growth potential
- Competitive intensity in new direction
@ -327,7 +327,7 @@ python ../../product-team/competitive-teardown/scripts/competitive_matrix_builde
6. **Set Pivot OKRs** - Define success for the new direction:
```bash
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py pivot
python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py pivot
```
**Expected Output:** Pivot analysis document with current state assessment, option evaluation, recommended path, transition plan, and pivot-specific OKRs
@ -345,10 +345,10 @@ Problem Pivot to Workflow,8,6,7,5,6
Technology Pivot to AI-Native,9,4,8,4,7
EOF
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py pivot-options.csv
# Generate OKRs for recommended pivot direction
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth
```
## Integration Examples
@ -367,22 +367,22 @@ echo "================================"
# Competitive landscape
echo ""
echo "1. Competitive Analysis:"
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py annual-competitors.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py annual-competitors.csv
# Strategy reference
echo ""
echo "2. Strategy Frameworks:"
cat ../../product-team/product-strategist/references/strategy_types.md | head -50
cat ../../product-team/skills/product-strategist/references/strategy_types.md | head -50
# Annual OKR cascade
echo ""
echo "3. Annual OKR Cascade:"
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth
# Initiative prioritization
echo ""
echo "4. Strategic Initiative Prioritization:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py annual-initiatives.csv --capacity 180
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py annual-initiatives.csv --capacity 180
```
### Example 2: Monthly Strategy Review
@ -397,17 +397,17 @@ echo "============================================"
# Competitive movements
echo ""
echo "Competitive Updates:"
echo "Review: ../../product-team/competitive-teardown/references/data-collection-guide.md"
echo "Review: ../../product-team/skills/competitive-teardown/references/data-collection-guide.md"
# OKR progress
echo ""
echo "OKR Progress:"
echo "Review: ../../product-team/product-strategist/assets/okr_template.md"
echo "Review: ../../product-team/skills/product-strategist/assets/okr_template.md"
# Initiative status
echo ""
echo "Initiative Portfolio:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py current-initiatives.csv
```
### Example 3: Board Preparation
@ -424,17 +424,17 @@ echo "============================="
# Strategic metrics
echo ""
echo "1. Product Strategy Performance:"
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py $QUARTER-delivered.csv
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py $QUARTER-delivered.csv
# Competitive position
echo ""
echo "2. Competitive Positioning:"
python ../../product-team/competitive-teardown/scripts/competitive_matrix_builder.py board-competitors.csv
python ../../product-team/skills/competitive-teardown/scripts/competitive_matrix_builder.py board-competitors.csv
# Next quarter OKRs
echo ""
echo "3. Next Quarter OKR Proposal:"
python ../../product-team/product-strategist/scripts/okr_cascade_generator.py growth
python ../../product-team/skills/product-strategist/scripts/okr_cascade_generator.py growth
```
## Success Metrics
@ -469,14 +469,14 @@ python ../../product-team/product-strategist/scripts/okr_cascade_generator.py gr
- [cs-agile-product-owner](cs-agile-product-owner.md) - Sprint-level planning and backlog management
- [cs-ux-researcher](cs-ux-researcher.md) - User research to validate strategic assumptions
- [cs-ceo-advisor](../c-level/cs-ceo-advisor.md) - Company-level strategic alignment
- Senior PM Skill - Portfolio context (see `../../project-management/senior-pm/`)
- Senior PM Skill - Portfolio context (see `../../project-management/skills/senior-pm/`)
## References
- **Primary Skill:** [../../product-team/product-strategist/SKILL.md](../../product-team/product-strategist/SKILL.md)
- **Competitive Teardown Skill:** [../../product-team/competitive-teardown/SKILL.md](../../product-team/competitive-teardown/SKILL.md)
- **OKR Framework:** [../../product-team/product-strategist/references/okr_framework.md](../../product-team/product-strategist/references/okr_framework.md)
- **Strategy Types:** [../../product-team/product-strategist/references/strategy_types.md](../../product-team/product-strategist/references/strategy_types.md)
- **Primary Skill:** [../../product-team/skills/product-strategist/SKILL.md](../../product-team/skills/product-strategist/SKILL.md)
- **Competitive Teardown Skill:** [../../product-team/skills/competitive-teardown/SKILL.md](../../product-team/skills/competitive-teardown/SKILL.md)
- **OKR Framework:** [../../product-team/skills/product-strategist/references/okr_framework.md](../../product-team/skills/product-strategist/references/okr_framework.md)
- **Strategy Types:** [../../product-team/skills/product-strategist/references/strategy_types.md](../../product-team/skills/product-strategist/references/strategy_types.md)
- **Product Domain Guide:** [../../product-team/CLAUDE.md](../../product-team/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)

128
agents/product/cs-ux-researcher.md
View file

@ -1,6 +1,6 @@
---
name: cs-ux-researcher
description: UX research agent for research planning, persona generation, journey mapping, and usability test analysis
description: UX research agent for research planning, persona generation, journey mapping, and usability test analysis. Use when product decisions need user evidence — e.g., planning interview scripts and recruiting criteria for a discovery study, or synthesizing usability-test sessions into prioritized findings and updated personas.
skills: product-team/ux-researcher-designer, product-team/product-manager-toolkit, product-team/ui-design-system
domain: product
model: sonnet
@ -19,78 +19,78 @@ The cs-ux-researcher agent ensures that user needs drive product development. It
## Skill Integration
**Primary Skill:** `../../product-team/ux-researcher-designer/`
**Primary Skill:** `../../product-team/skills/ux-researcher-designer/`
### All Orchestrated Skills
| # | Skill | Location | Primary Tool |
|---|-------|----------|-------------|
| 1 | UX Researcher & Designer | `../../product-team/ux-researcher-designer/` | persona_generator.py |
| 2 | Product Manager Toolkit | `../../product-team/product-manager-toolkit/` | customer_interview_analyzer.py |
| 3 | UI Design System | `../../product-team/ui-design-system/` | design_token_generator.py |
| 1 | UX Researcher & Designer | `../../product-team/skills/ux-researcher-designer/` | persona_generator.py |
| 2 | Product Manager Toolkit | `../../product-team/skills/product-manager-toolkit/` | customer_interview_analyzer.py |
| 3 | UI Design System | `../../product-team/skills/ui-design-system/` | design_token_generator.py |
### Python Tools
1. **Persona Generator**
- **Purpose:** Create data-driven user personas from research inputs including demographics, goals, pain points, and behavioral patterns
- **Path:** `../../product-team/ux-researcher-designer/scripts/persona_generator.py`
- **Usage:** `python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json`
- **Path:** `../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py`
- **Usage:** `python ../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py research-data.json`
- **Features:** Multiple persona generation, behavioral segmentation, needs hierarchy mapping, empathy map creation
- **Use Cases:** Persona development, user segmentation, design alignment, stakeholder communication
2. **Customer Interview Analyzer**
- **Purpose:** NLP-based analysis of interview transcripts to extract pain points, feature requests, themes, and sentiment
- **Path:** `../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py`
- **Usage:** `python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt`
- **Path:** `../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py`
- **Usage:** `python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview.txt`
- **Features:** Pain point extraction with severity scoring, feature request identification, jobs-to-be-done patterns, theme clustering, key quote extraction
- **Use Cases:** Interview synthesis, discovery validation, problem prioritization, insight aggregation
3. **Design Token Generator**
- **Purpose:** Generate design tokens for consistent UI implementation across platforms
- **Path:** `../../product-team/ui-design-system/scripts/design_token_generator.py`
- **Usage:** `python ../../product-team/ui-design-system/scripts/design_token_generator.py theme.json`
- **Path:** `../../product-team/skills/ui-design-system/scripts/design_token_generator.py`
- **Usage:** `python ../../product-team/skills/ui-design-system/scripts/design_token_generator.py theme.json`
- **Use Cases:** Research-informed design system updates, accessibility token adjustments
### Knowledge Bases
1. **Persona Methodology**
- **Location:** `../../product-team/ux-researcher-designer/references/persona-methodology.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/persona-methodology.md`
- **Content:** Research-backed persona creation methodology, data collection strategies, validation approaches
- **Use Case:** Methodological guidance for persona projects
2. **Example Personas**
- **Location:** `../../product-team/ux-researcher-designer/references/example-personas.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/example-personas.md`
- **Content:** Sample persona documents with demographics, goals, pain points, behaviors, scenarios
- **Use Case:** Persona format reference, team training
3. **Journey Mapping Guide**
- **Location:** `../../product-team/ux-researcher-designer/references/journey-mapping-guide.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md`
- **Content:** Customer journey mapping methodology, touchpoint analysis, emotion mapping, opportunity identification
- **Use Case:** Journey map creation, experience design, service design
4. **Usability Testing Frameworks**
- **Location:** `../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md`
- **Content:** Test planning, task design, analysis methods, severity ratings, reporting formats
- **Use Case:** Usability study design, prototype validation, UX evaluation
5. **Component Architecture**
- **Location:** `../../product-team/ui-design-system/references/component-architecture.md`
- **Location:** `../../product-team/skills/ui-design-system/references/component-architecture.md`
- **Content:** Component hierarchy, atomic design patterns, composition strategies
- **Use Case:** Research-to-design translation, component recommendations
6. **Developer Handoff**
- **Location:** `../../product-team/ui-design-system/references/developer-handoff.md`
- **Location:** `../../product-team/skills/ui-design-system/references/developer-handoff.md`
- **Content:** Design-to-dev handoff process, specification formats, asset delivery
- **Use Case:** Translating research findings into implementation specs
### Templates
1. **Research Plan Template**
- **Location:** `../../product-team/ux-researcher-designer/assets/research_plan_template.md`
- **Location:** `../../product-team/skills/ux-researcher-designer/assets/research_plan_template.md`
- **Use Case:** Structuring research studies with methodology, participants, and analysis plan
2. **Design System Documentation Template**
- **Location:** `../../product-team/ui-design-system/assets/design_system_doc_template.md`
- **Location:** `../../product-team/skills/ui-design-system/assets/design_system_doc_template.md`
- **Use Case:** Documenting research-informed design system decisions
## Workflows
@ -109,7 +109,7 @@ The cs-ux-researcher agent ensures that user needs drive product development. It
2. **Select Methodology** - Choose the right approach:
```bash
# Review usability testing frameworks for method selection
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
cat ../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md
```
- **Exploratory** (interviews, contextual inquiry): When learning about problem space
- **Evaluative** (usability testing, A/B tests): When validating solutions
@ -125,7 +125,7 @@ The cs-ux-researcher agent ensures that user needs drive product development. It
4. **Create Study Materials** - Prepare research instruments:
```bash
# Use the research plan template
cat ../../product-team/ux-researcher-designer/assets/research_plan_template.md
cat ../../product-team/skills/ux-researcher-designer/assets/research_plan_template.md
```
- Interview guide or test script
- Task scenarios (for usability tests)
@ -145,13 +145,13 @@ The cs-ux-researcher agent ensures that user needs drive product development. It
**Example:**
```bash
# Create research plan from template
cp ../../product-team/ux-researcher-designer/assets/research_plan_template.md onboarding-research-plan.md
cp ../../product-team/skills/ux-researcher-designer/assets/research_plan_template.md onboarding-research-plan.md
# Review methodology options
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
cat ../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md
# Review persona methodology for participant criteria
cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
cat ../../product-team/skills/ux-researcher-designer/references/persona-methodology.md
```
### Workflow 2: Persona Generation
@ -169,9 +169,9 @@ cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
2. **Analyze Interview Data** - Extract structured insights:
```bash
# Analyze each interview transcript
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt > insights-001.json
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt > insights-002.json
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt > insights-003.json
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-001.txt > insights-001.json
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-002.txt > insights-002.json
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py interview-003.txt > insights-003.json
```
3. **Identify Behavioral Segments** - Cluster users by:
@ -184,7 +184,7 @@ cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
4. **Generate Personas** - Create data-backed personas:
```bash
# Generate personas from aggregated research
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
python ../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py research-data.json
```
5. **Validate Personas** - Ensure accuracy:
@ -196,7 +196,7 @@ cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
6. **Socialize Personas** - Make personas actionable:
```bash
# Review example personas for format guidance
cat ../../product-team/ux-researcher-designer/references/example-personas.md
cat ../../product-team/skills/ux-researcher-designer/references/example-personas.md
```
- Create one-page persona cards for team walls/wikis
- Present to product, engineering, and design teams
@ -216,18 +216,18 @@ echo "==========================="
# Step 1: Analyze interviews
for f in interviews/*.txt; do
base=$(basename "$f" .txt)
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f" json > "insights-$base.json"
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f" json > "insights-$base.json"
echo "Analyzed: $f"
done
# Step 2: Review persona methodology
cat ../../product-team/ux-researcher-designer/references/persona-methodology.md
cat ../../product-team/skills/ux-researcher-designer/references/persona-methodology.md
# Step 3: Generate personas
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py research-data.json
python ../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py research-data.json
# Step 4: Review example format
cat ../../product-team/ux-researcher-designer/references/example-personas.md
cat ../../product-team/skills/ux-researcher-designer/references/example-personas.md
```
### Workflow 3: Journey Mapping
@ -243,7 +243,7 @@ cat ../../product-team/ux-researcher-designer/references/example-personas.md
2. **Review Journey Mapping Methodology** - Understand the framework:
```bash
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
cat ../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md
```
3. **Map Journey Stages** - Identify key phases:
@ -278,7 +278,7 @@ cat ../../product-team/ux-researcher-designer/references/example-personas.md
Self-service help in context,600,2,0.8,2
Upgrade prompt optimization,400,3,0.6,2
EOF
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py journey-opportunities.csv
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py journey-opportunities.csv
```
**Expected Output:** Visual journey map with stages, touchpoints, emotions, pain points, and prioritized improvement opportunities
@ -292,14 +292,14 @@ echo "Journey Mapping - Onboarding Flow"
echo "=================================="
# Review journey mapping methodology
cat ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md
cat ../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md
# Analyze relevant interview transcripts for journey insights
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py onboarding-interview-01.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py onboarding-interview-02.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py onboarding-interview-01.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py onboarding-interview-02.txt
# Prioritize improvement opportunities
python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py journey-opportunities.csv
python ../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py journey-opportunities.csv
```
### Workflow 4: Usability Test Analysis
@ -310,7 +310,7 @@ python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py jo
1. **Plan the Test** - Design the study:
```bash
# Review usability testing frameworks
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
cat ../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md
```
- Define test objectives (what decisions will this inform)
- Select test type (moderated/unmoderated, remote/in-person)
@ -324,7 +324,7 @@ python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py jo
- Note-taking template for observers
- Use research plan template for documentation:
```bash
cat ../../product-team/ux-researcher-designer/assets/research_plan_template.md
cat ../../product-team/skills/ux-researcher-designer/assets/research_plan_template.md
```
3. **Conduct Sessions** - Run 5-8 sessions:
@ -347,8 +347,8 @@ python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py jo
5. **Analyze Verbal Feedback** - Extract qualitative insights:
```bash
# Analyze session transcripts for themes
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py usability-session-01.txt
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py usability-session-02.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py usability-session-01.txt
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py usability-session-02.txt
```
6. **Create Report and Recommendations** - Deliver findings:
@ -362,7 +362,7 @@ python ../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py jo
- Review findings with design team
- Map issues to components in design system:
```bash
cat ../../product-team/ui-design-system/references/component-architecture.md
cat ../../product-team/skills/ui-design-system/references/component-architecture.md
```
- Create Jira tickets for each issue
- Plan re-test for critical issues after fixes
@ -378,17 +378,17 @@ echo "Usability Test Analysis"
echo "======================="
# Review frameworks
cat ../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md
cat ../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md
# Analyze each session transcript
for i in 1 2 3 4 5; do
echo "Session $i Analysis:"
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "usability-session-0$i.txt"
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py "usability-session-0$i.txt"
echo ""
done
# Review component architecture for design recommendations
cat ../../product-team/ui-design-system/references/component-architecture.md
cat ../../product-team/skills/ui-design-system/references/component-architecture.md
```
## Integration Examples
@ -411,7 +411,7 @@ echo "-------------------------------------"
for f in discovery-interviews/*.txt; do
base=$(basename "$f" .txt)
echo "Analyzing: $base"
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f" json > "insights/$base.json"
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f" json > "insights/$base.json"
done
# Week 2: Synthesis
@ -420,10 +420,10 @@ echo "Week 2: Generate Personas & Journey Map"
echo "----------------------------------------"
# Generate personas from aggregated data
python ../../product-team/ux-researcher-designer/scripts/persona_generator.py aggregated-research.json
python ../../product-team/skills/ux-researcher-designer/scripts/persona_generator.py aggregated-research.json
# Reference journey mapping guide
echo "Journey mapping guide: ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md"
echo "Journey mapping guide: ../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md"
```
### Example 2: Research Repository Update
@ -439,15 +439,15 @@ echo "================================================"
echo ""
echo "New Interview Analysis:"
for f in new-interviews/*.txt; do
python ../../product-team/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f"
python ../../product-team/skills/product-manager-toolkit/scripts/customer_interview_analyzer.py "$f"
echo "---"
done
# Review and refresh personas
echo ""
echo "Persona Review:"
echo "Current personas: ../../product-team/ux-researcher-designer/references/example-personas.md"
echo "Methodology: ../../product-team/ux-researcher-designer/references/persona-methodology.md"
echo "Current personas: ../../product-team/skills/ux-researcher-designer/references/example-personas.md"
echo "Methodology: ../../product-team/skills/ux-researcher-designer/references/persona-methodology.md"
```
### Example 3: Design Handoff with Research Context
@ -462,22 +462,22 @@ echo "========================"
# Persona context
echo ""
echo "1. Active Personas:"
cat ../../product-team/ux-researcher-designer/references/example-personas.md | head -30
cat ../../product-team/skills/ux-researcher-designer/references/example-personas.md | head -30
# Journey context
echo ""
echo "2. Journey Map Reference:"
echo "See: ../../product-team/ux-researcher-designer/references/journey-mapping-guide.md"
echo "See: ../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md"
# Design system alignment
echo ""
echo "3. Component Architecture:"
echo "See: ../../product-team/ui-design-system/references/component-architecture.md"
echo "See: ../../product-team/skills/ui-design-system/references/component-architecture.md"
# Developer handoff process
echo ""
echo "4. Handoff Process:"
echo "See: ../../product-team/ui-design-system/references/developer-handoff.md"
echo "See: ../../product-team/skills/ui-design-system/references/developer-handoff.md"
```
## Success Metrics
@ -511,16 +511,16 @@ echo "See: ../../product-team/ui-design-system/references/developer-handoff.md"
- [cs-product-manager](cs-product-manager.md) - Product management lifecycle, interview analysis, PRD development
- [cs-agile-product-owner](cs-agile-product-owner.md) - Translating research findings into user stories
- [cs-product-strategist](cs-product-strategist.md) - Strategic research to validate product vision and positioning
- UI Design System - Design handoff and component recommendations (see `../../product-team/ui-design-system/`)
- UI Design System - Design handoff and component recommendations (see `../../product-team/skills/ui-design-system/`)
## References
- **Primary Skill:** [../../product-team/ux-researcher-designer/SKILL.md](../../product-team/ux-researcher-designer/SKILL.md)
- **Interview Analyzer:** [../../product-team/product-manager-toolkit/SKILL.md](../../product-team/product-manager-toolkit/SKILL.md)
- **Persona Methodology:** [../../product-team/ux-researcher-designer/references/persona-methodology.md](../../product-team/ux-researcher-designer/references/persona-methodology.md)
- **Journey Mapping Guide:** [../../product-team/ux-researcher-designer/references/journey-mapping-guide.md](../../product-team/ux-researcher-designer/references/journey-mapping-guide.md)
- **Usability Testing:** [../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md](../../product-team/ux-researcher-designer/references/usability-testing-frameworks.md)
- **Design System:** [../../product-team/ui-design-system/SKILL.md](../../product-team/ui-design-system/SKILL.md)
- **Primary Skill:** [../../product-team/skills/ux-researcher-designer/SKILL.md](../../product-team/skills/ux-researcher-designer/SKILL.md)
- **Interview Analyzer:** [../../product-team/skills/product-manager-toolkit/SKILL.md](../../product-team/skills/product-manager-toolkit/SKILL.md)
- **Persona Methodology:** [../../product-team/skills/ux-researcher-designer/references/persona-methodology.md](../../product-team/skills/ux-researcher-designer/references/persona-methodology.md)
- **Journey Mapping Guide:** [../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md](../../product-team/skills/ux-researcher-designer/references/journey-mapping-guide.md)
- **Usability Testing:** [../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md](../../product-team/skills/ux-researcher-designer/references/usability-testing-frameworks.md)
- **Design System:** [../../product-team/skills/ui-design-system/SKILL.md](../../product-team/skills/ui-design-system/SKILL.md)
- **Product Domain Guide:** [../../product-team/CLAUDE.md](../../product-team/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)

160
agents/project-management/cs-project-manager.md
View file

@ -1,6 +1,6 @@
---
name: cs-project-manager
description: Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills.
description: Project Manager agent for sprint planning, Jira/Confluence workflows, Scrum ceremonies, and stakeholder reporting. Orchestrates project-management skills. Use when running delivery operations — e.g., planning a sprint with capacity and carry-over math in Jira, or assembling a portfolio health report for stakeholders from ticket and velocity data.
skills: project-management
domain: pm
model: sonnet
@ -21,103 +21,103 @@ The cs-project-manager agent bridges the gap between project execution and strat
### Senior PM
**Skill Location:** `../../project-management/senior-pm/`
**Skill Location:** `../../project-management/skills/senior-pm/`
**Python Tools:**
1. **Project Health Dashboard**
- **Purpose:** Generate portfolio-level health dashboard with RAG status across all active projects
- **Path:** `../../project-management/senior-pm/scripts/project_health_dashboard.py`
- **Usage:** `python ../../project-management/senior-pm/scripts/project_health_dashboard.py sample_project_data.json`
- **Path:** `../../project-management/skills/senior-pm/scripts/project_health_dashboard.py`
- **Usage:** `python ../../project-management/skills/senior-pm/scripts/project_health_dashboard.py sample_project_data.json`
- **Features:** Schedule variance, budget tracking, risk exposure, milestone status, RAG indicators
2. **Risk Matrix Analyzer**
- **Purpose:** Quantitative risk analysis with probability-impact matrices and Expected Monetary Value (EMV)
- **Path:** `../../project-management/senior-pm/scripts/risk_matrix_analyzer.py`
- **Usage:** `python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py risks.json`
- **Path:** `../../project-management/skills/senior-pm/scripts/risk_matrix_analyzer.py`
- **Usage:** `python ../../project-management/skills/senior-pm/scripts/risk_matrix_analyzer.py risks.json`
- **Features:** Risk scoring, heat map generation, mitigation tracking, EMV calculation
3. **Resource Capacity Planner**
- **Purpose:** Team resource allocation and capacity forecasting across sprints and projects
- **Path:** `../../project-management/senior-pm/scripts/resource_capacity_planner.py`
- **Usage:** `python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json`
- **Path:** `../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py`
- **Usage:** `python ../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py team_data.json`
- **Features:** Utilization analysis, over-allocation detection, capacity forecasting, cross-project balancing
**Knowledge Bases:**
- `../../project-management/senior-pm/references/portfolio-prioritization-models.md` -- WSJF, MoSCoW, Cost of Delay, portfolio scoring frameworks
- `../../project-management/senior-pm/references/risk-management-framework.md` -- Risk identification, qualitative/quantitative analysis, response strategies
- `../../project-management/senior-pm/references/portfolio-kpis.md` -- KPI definitions, tracking cadences, executive reporting metrics
- `../../project-management/skills/senior-pm/references/portfolio-prioritization-models.md` -- WSJF, MoSCoW, Cost of Delay, portfolio scoring frameworks
- `../../project-management/skills/senior-pm/references/risk-management-framework.md` -- Risk identification, qualitative/quantitative analysis, response strategies
- `../../project-management/skills/senior-pm/references/portfolio-kpis.md` -- KPI definitions, tracking cadences, executive reporting metrics
**Templates:**
- `../../project-management/senior-pm/assets/executive_report_template.md` -- Executive status report with RAG, risks, decisions needed
- `../../project-management/senior-pm/assets/project_charter_template.md` -- Project charter with scope, objectives, constraints, stakeholders
- `../../project-management/senior-pm/assets/raci_matrix_template.md` -- Responsibility assignment matrix for cross-functional teams
- `../../project-management/skills/senior-pm/assets/executive_report_template.md` -- Executive status report with RAG, risks, decisions needed
- `../../project-management/skills/senior-pm/assets/project_charter_template.md` -- Project charter with scope, objectives, constraints, stakeholders
- `../../project-management/skills/senior-pm/assets/raci_matrix_template.md` -- Responsibility assignment matrix for cross-functional teams
### Scrum Master
**Skill Location:** `../../project-management/scrum-master/`
**Skill Location:** `../../project-management/skills/scrum-master/`
**Python Tools:**
1. **Sprint Health Scorer**
- **Purpose:** Quantitative sprint health assessment across scope, velocity, quality, and team morale
- **Path:** `../../project-management/scrum-master/scripts/sprint_health_scorer.py`
- **Usage:** `python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sample_sprint_data.json`
- **Path:** `../../project-management/skills/scrum-master/scripts/sprint_health_scorer.py`
- **Usage:** `python ../../project-management/skills/scrum-master/scripts/sprint_health_scorer.py sample_sprint_data.json`
- **Features:** Multi-dimensional scoring (0-100), trend analysis, health indicators, actionable recommendations
2. **Velocity Analyzer**
- **Purpose:** Historical velocity analysis with forecasting and confidence intervals
- **Path:** `../../project-management/scrum-master/scripts/velocity_analyzer.py`
- **Usage:** `python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json`
- **Path:** `../../project-management/skills/scrum-master/scripts/velocity_analyzer.py`
- **Usage:** `python ../../project-management/skills/scrum-master/scripts/velocity_analyzer.py sprint_history.json`
- **Features:** Rolling averages, standard deviation, sprint-over-sprint trends, capacity prediction
3. **Retrospective Analyzer**
- **Purpose:** Structured retrospective analysis with action item tracking and theme extraction
- **Path:** `../../project-management/scrum-master/scripts/retrospective_analyzer.py`
- **Usage:** `python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_notes.json`
- **Path:** `../../project-management/skills/scrum-master/scripts/retrospective_analyzer.py`
- **Usage:** `python ../../project-management/skills/scrum-master/scripts/retrospective_analyzer.py retro_notes.json`
- **Features:** Theme clustering, sentiment analysis, action item extraction, trend tracking across sprints
**Knowledge Bases:**
- `../../project-management/scrum-master/references/retro-formats.md` -- Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad, Starfish formats
- `../../project-management/scrum-master/references/team-dynamics-framework.md` -- Tuckman stages, psychological safety, conflict resolution
- `../../project-management/scrum-master/references/velocity-forecasting-guide.md` -- Monte Carlo simulation, confidence ranges, capacity planning
- `../../project-management/skills/scrum-master/references/retro-formats.md` -- Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad, Starfish formats
- `../../project-management/skills/scrum-master/references/team-dynamics-framework.md` -- Tuckman stages, psychological safety, conflict resolution
- `../../project-management/skills/scrum-master/references/velocity-forecasting-guide.md` -- Monte Carlo simulation, confidence ranges, capacity planning
**Templates:**
- `../../project-management/scrum-master/assets/sprint_report_template.md` -- Sprint review report with burndown, velocity, demo notes
- `../../project-management/scrum-master/assets/team_health_check_template.md` -- Spotify-style team health check across 8 dimensions
- `../../project-management/skills/scrum-master/assets/sprint_report_template.md` -- Sprint review report with burndown, velocity, demo notes
- `../../project-management/skills/scrum-master/assets/team_health_check_template.md` -- Spotify-style team health check across 8 dimensions
### Jira Expert
**Skill Location:** `../../project-management/jira-expert/`
**Skill Location:** `../../project-management/skills/jira-expert/`
**Knowledge Bases:**
- `../../project-management/jira-expert/references/jql-examples.md` -- JQL query patterns for backlog grooming, sprint reporting, SLA tracking
- `../../project-management/jira-expert/references/automation-examples.md` -- Jira automation rule templates for common workflows
- `../../project-management/jira-expert/references/AUTOMATION.md` -- Comprehensive automation guide with triggers, conditions, actions
- `../../project-management/jira-expert/references/WORKFLOWS.md` -- Workflow design patterns, transition rules, validators, post-functions
- `../../project-management/skills/jira-expert/references/jql-examples.md` -- JQL query patterns for backlog grooming, sprint reporting, SLA tracking
- `../../project-management/skills/jira-expert/references/automation-examples.md` -- Jira automation rule templates for common workflows
- `../../project-management/skills/jira-expert/references/AUTOMATION.md` -- Comprehensive automation guide with triggers, conditions, actions
- `../../project-management/skills/jira-expert/references/WORKFLOWS.md` -- Workflow design patterns, transition rules, validators, post-functions
### Confluence Expert
**Skill Location:** `../../project-management/confluence-expert/`
**Skill Location:** `../../project-management/skills/confluence-expert/`
**Knowledge Bases:**
- `../../project-management/confluence-expert/references/templates.md` -- Page templates for sprint plans, meeting notes, decision logs, architecture docs
- `../../project-management/skills/confluence-expert/references/templates.md` -- Page templates for sprint plans, meeting notes, decision logs, architecture docs
### Atlassian Admin
**Skill Location:** `../../project-management/atlassian-admin/`
**Skill Location:** `../../project-management/skills/atlassian-admin/`
Covers user provisioning, permission schemes, project configuration, and integration setup. No scripts or references yet -- relies on SKILL.md workflows.
### Atlassian Templates
**Skill Location:** `../../project-management/atlassian-templates/`
**Skill Location:** `../../project-management/skills/atlassian-templates/`
Covers blueprint creation, custom page layouts, and reusable Confluence/Jira components. No scripts or references yet -- relies on SKILL.md workflows.
@ -131,37 +131,37 @@ Covers blueprint creation, custom page layouts, and reusable Confluence/Jira com
1. **Analyze Velocity History** - Review past sprint performance to set realistic capacity:
```bash
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json
python ../../project-management/skills/scrum-master/scripts/velocity_analyzer.py sprint_history.json
```
- Review rolling average velocity and standard deviation
- Identify trends (accelerating, decelerating, stable)
- Set sprint capacity at 80% of average velocity (buffer for unknowns)
2. **Query Backlog via JQL** - Use jira-expert JQL patterns to pull prioritized candidates:
- Reference: `../../project-management/jira-expert/references/jql-examples.md`
- Reference: `../../project-management/skills/jira-expert/references/jql-examples.md`
- Filter by priority, story points estimated, team assignment
- Identify blocked items, external dependencies, carry-overs from previous sprint
3. **Check Resource Availability** - Verify team capacity for the sprint window:
```bash
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json
python ../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py team_data.json
```
- Account for PTO, holidays, shared resources
- Flag over-allocated team members
- Adjust sprint capacity based on actual availability
4. **Select Sprint Backlog** - Commit items within capacity:
- Apply WSJF or priority-based selection (ref: `../../project-management/senior-pm/references/portfolio-prioritization-models.md`)
- Apply WSJF or priority-based selection (ref: `../../project-management/skills/senior-pm/references/portfolio-prioritization-models.md`)
- Ensure sprint goal alignment -- every item should contribute to 1-2 goals
- Include 10-15% capacity for bug fixes and operational work
5. **Document Sprint Plan** - Create Confluence sprint plan page:
- Use template from `../../project-management/confluence-expert/references/templates.md`
- Use template from `../../project-management/skills/confluence-expert/references/templates.md`
- Include sprint goal, committed stories, capacity breakdown, risks
- Link to Jira sprint board for live tracking
6. **Set Up Sprint Tracking** - Configure dashboards and automation:
- Create burndown/burnup dashboard (ref: `../../project-management/jira-expert/references/AUTOMATION.md`)
- Create burndown/burnup dashboard (ref: `../../project-management/skills/jira-expert/references/AUTOMATION.md`)
- Set up daily standup reminder automation
- Configure sprint scope change alerts
@ -172,8 +172,8 @@ Covers blueprint creation, custom page layouts, and reusable Confluence/Jira com
**Example:**
```bash
# Full sprint planning workflow
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json > velocity_report.txt
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json > capacity_report.txt
python ../../project-management/skills/scrum-master/scripts/velocity_analyzer.py sprint_history.json > velocity_report.txt
python ../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py team_data.json > capacity_report.txt
cat velocity_report.txt
cat capacity_report.txt
# Use velocity average and capacity data to commit sprint items
@ -193,7 +193,7 @@ cat capacity_report.txt
2. **Generate Health Dashboard** - Run project health analysis:
```bash
python ../../project-management/senior-pm/scripts/project_health_dashboard.py portfolio_data.json
python ../../project-management/skills/senior-pm/scripts/project_health_dashboard.py portfolio_data.json
```
- Review per-project RAG status (Red/Amber/Green)
- Identify projects requiring intervention
@ -201,7 +201,7 @@ cat capacity_report.txt
3. **Analyze Risk Exposure** - Quantify portfolio-level risk:
```bash
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py portfolio_risks.json
python ../../project-management/skills/senior-pm/scripts/risk_matrix_analyzer.py portfolio_risks.json
```
- Calculate EMV for each risk
- Identify top-10 risks by exposure
@ -210,20 +210,20 @@ cat capacity_report.txt
4. **Review Resource Utilization** - Check cross-project allocation:
```bash
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py all_teams.json
python ../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py all_teams.json
```
- Identify over-allocated individuals (>100% utilization)
- Find under-utilized capacity for rebalancing
- Forecast resource needs for next quarter
5. **Prepare Executive Report** - Assemble findings into report:
- Use template: `../../project-management/senior-pm/assets/executive_report_template.md`
- Use template: `../../project-management/skills/senior-pm/assets/executive_report_template.md`
- Include RAG summary, risk heatmap, resource utilization chart
- Highlight decisions needed from leadership
- Provide recommendations with supporting data
6. **Publish to Confluence** - Create executive dashboard page:
- Reference KPI definitions from `../../project-management/senior-pm/references/portfolio-kpis.md`
- Reference KPI definitions from `../../project-management/skills/senior-pm/references/portfolio-kpis.md`
- Embed Jira macros for live data
- Set up weekly refresh cadence
@ -234,9 +234,9 @@ cat capacity_report.txt
**Example:**
```bash
# Portfolio health review automation
python ../../project-management/senior-pm/scripts/project_health_dashboard.py portfolio_data.json > health_dashboard.txt
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py portfolio_risks.json > risk_report.txt
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py all_teams.json > resource_report.txt
python ../../project-management/skills/senior-pm/scripts/project_health_dashboard.py portfolio_data.json > health_dashboard.txt
python ../../project-management/skills/senior-pm/scripts/risk_matrix_analyzer.py portfolio_risks.json > risk_report.txt
python ../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py all_teams.json > resource_report.txt
cat health_dashboard.txt
cat risk_report.txt
cat resource_report.txt
@ -250,14 +250,14 @@ cat resource_report.txt
1. **Gather Sprint Metrics** - Collect quantitative data before the retro:
```bash
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sprint_data.json
python ../../project-management/skills/scrum-master/scripts/sprint_health_scorer.py sprint_data.json
```
- Review sprint health score (0-100)
- Identify scoring dimensions that dropped (scope, velocity, quality, morale)
- Compare against previous sprint scores for trend analysis
2. **Select Retro Format** - Choose format based on team needs:
- Reference: `../../project-management/scrum-master/references/retro-formats.md`
- Reference: `../../project-management/skills/scrum-master/references/retro-formats.md`
- **Start/Stop/Continue**: General-purpose, good for new teams
- **4Ls (Liked/Learned/Lacked/Longed For)**: Focuses on learning and growth
- **Sailboat**: Visual metaphor for anchors (blockers) and wind (accelerators)
@ -268,11 +268,11 @@ cat resource_report.txt
- Present sprint metrics as context (not judgment)
- Time-box each section (5 min brainstorm, 10 min discuss, 5 min vote)
- Use dot voting to prioritize discussion topics
- Reference team dynamics from `../../project-management/scrum-master/references/team-dynamics-framework.md`
- Reference team dynamics from `../../project-management/skills/scrum-master/references/team-dynamics-framework.md`
4. **Analyze Retro Output** - Extract structured insights:
```bash
python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_notes.json
python ../../project-management/skills/scrum-master/scripts/retrospective_analyzer.py retro_notes.json
```
- Identify recurring themes across sprints
- Cluster related items into improvement areas
@ -285,7 +285,7 @@ cat resource_report.txt
- Add action items to next sprint backlog
6. **Document in Confluence** - Publish retro summary:
- Use sprint report template: `../../project-management/scrum-master/assets/sprint_report_template.md`
- Use sprint report template: `../../project-management/skills/scrum-master/assets/sprint_report_template.md`
- Include sprint health score, retro themes, action items, metrics trends
- Link to previous retro pages for longitudinal tracking
@ -301,11 +301,11 @@ cat resource_report.txt
**Example:**
```bash
# Pre-retro data collection
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sprint_data.json > health_score.txt
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json > velocity_trend.txt
python ../../project-management/skills/scrum-master/scripts/sprint_health_scorer.py sprint_data.json > health_score.txt
python ../../project-management/skills/scrum-master/scripts/velocity_analyzer.py sprint_history.json > velocity_trend.txt
cat health_score.txt
# Use health score insights to guide retro discussion
python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_notes.json > retro_analysis.txt
python ../../project-management/skills/scrum-master/scripts/retrospective_analyzer.py retro_notes.json > retro_analysis.txt
cat retro_analysis.txt
```
@ -328,22 +328,22 @@ cat retro_analysis.txt
- Define priority scheme and SLA targets
3. **Design Workflows** - Build workflows matching team process:
- Reference: `../../project-management/jira-expert/references/WORKFLOWS.md`
- Reference: `../../project-management/skills/jira-expert/references/WORKFLOWS.md`
- Map states: Backlog > Ready > In Progress > Review > QA > Done
- Add transitions with conditions (e.g., assignee required for In Progress)
- Configure validators (e.g., story points required before Done)
- Set up post-functions (e.g., auto-assign reviewer, notify channel)
4. **Configure Automation** - Set up time-saving automation rules:
- Reference: `../../project-management/jira-expert/references/AUTOMATION.md`
- Examples from: `../../project-management/jira-expert/references/automation-examples.md`
- Reference: `../../project-management/skills/jira-expert/references/AUTOMATION.md`
- Examples from: `../../project-management/skills/jira-expert/references/automation-examples.md`
- Auto-transition: Move to In Progress when branch created
- Auto-assign: Rotate assignments based on workload
- Notifications: Slack alerts for blocked items, SLA breaches
- Cleanup: Auto-close stale items after 30 days
5. **Set Up Confluence Space** - Create team knowledge base:
- Reference: `../../project-management/confluence-expert/references/templates.md`
- Reference: `../../project-management/skills/confluence-expert/references/templates.md`
- Create space with standard page hierarchy:
- Home (team overview, quick links)
- Sprint Plans (per-sprint documentation)
@ -357,7 +357,7 @@ cat retro_analysis.txt
- Burndown/burnup chart gadget
- Velocity chart for historical tracking
- SLA compliance tracker
- Use JQL patterns from `../../project-management/jira-expert/references/jql-examples.md`
- Use JQL patterns from `../../project-management/skills/jira-expert/references/jql-examples.md`
7. **Onboard Team** - Walk team through the setup:
- Document workflow rules and why they exist
@ -383,22 +383,22 @@ echo "============================================"
# Sprint health assessment
echo ""
echo "Sprint Health:"
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py current_sprint.json
python ../../project-management/skills/scrum-master/scripts/sprint_health_scorer.py current_sprint.json
# Velocity trend
echo ""
echo "Velocity Trend:"
python ../../project-management/scrum-master/scripts/velocity_analyzer.py sprint_history.json
python ../../project-management/skills/scrum-master/scripts/velocity_analyzer.py sprint_history.json
# Risk exposure
echo ""
echo "Active Risks:"
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py active_risks.json
python ../../project-management/skills/senior-pm/scripts/risk_matrix_analyzer.py active_risks.json
# Resource utilization
echo ""
echo "Team Capacity:"
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py team_data.json
python ../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py team_data.json
```
### Example 2: Sprint Retrospective Pipeline
@ -414,19 +414,19 @@ echo "=========================================="
# Step 1: Score sprint health
echo ""
echo "1. Sprint Health Score:"
python ../../project-management/scrum-master/scripts/sprint_health_scorer.py sprint_${SPRINT_NUM}.json > sprint_health.txt
python ../../project-management/skills/scrum-master/scripts/sprint_health_scorer.py sprint_${SPRINT_NUM}.json > sprint_health.txt
cat sprint_health.txt
# Step 2: Analyze velocity trend
echo ""
echo "2. Velocity Analysis:"
python ../../project-management/scrum-master/scripts/velocity_analyzer.py velocity_history.json > velocity.txt
python ../../project-management/skills/scrum-master/scripts/velocity_analyzer.py velocity_history.json > velocity.txt
cat velocity.txt
# Step 3: Process retro notes
echo ""
echo "3. Retrospective Themes:"
python ../../project-management/scrum-master/scripts/retrospective_analyzer.py retro_sprint_${SPRINT_NUM}.json > retro_analysis.txt
python ../../project-management/skills/scrum-master/scripts/retrospective_analyzer.py retro_sprint_${SPRINT_NUM}.json > retro_analysis.txt
cat retro_analysis.txt
echo ""
@ -446,24 +446,24 @@ echo "================================"
# Project health across portfolio
echo ""
echo "Project Health (All Active):"
python ../../project-management/senior-pm/scripts/project_health_dashboard.py portfolio_$MONTH.json > dashboard.txt
python ../../project-management/skills/senior-pm/scripts/project_health_dashboard.py portfolio_$MONTH.json > dashboard.txt
cat dashboard.txt
# Risk heatmap
echo ""
echo "Risk Exposure Summary:"
python ../../project-management/senior-pm/scripts/risk_matrix_analyzer.py risks_$MONTH.json > risks.txt
python ../../project-management/skills/senior-pm/scripts/risk_matrix_analyzer.py risks_$MONTH.json > risks.txt
cat risks.txt
# Resource forecast
echo ""
echo "Resource Utilization:"
python ../../project-management/senior-pm/scripts/resource_capacity_planner.py resources_$MONTH.json > capacity.txt
python ../../project-management/skills/senior-pm/scripts/resource_capacity_planner.py resources_$MONTH.json > capacity.txt
cat capacity.txt
echo ""
echo "Dashboard generated. Use executive_report_template.md to assemble final report."
echo "Template: ../../project-management/senior-pm/assets/executive_report_template.md"
echo "Template: ../../project-management/skills/senior-pm/assets/executive_report_template.md"
```
## Success Metrics
@ -500,11 +500,11 @@ echo "Template: ../../project-management/senior-pm/assets/executive_report_templ
## References
- **Senior PM Skill:** [../../project-management/senior-pm/SKILL.md](../../project-management/senior-pm/SKILL.md)
- **Scrum Master Skill:** [../../project-management/scrum-master/SKILL.md](../../project-management/scrum-master/SKILL.md)
- **Jira Expert Skill:** [../../project-management/jira-expert/SKILL.md](../../project-management/jira-expert/SKILL.md)
- **Confluence Expert Skill:** [../../project-management/confluence-expert/SKILL.md](../../project-management/confluence-expert/SKILL.md)
- **Atlassian Admin Skill:** [../../project-management/atlassian-admin/SKILL.md](../../project-management/atlassian-admin/SKILL.md)
- **Senior PM Skill:** [../../project-management/skills/senior-pm/SKILL.md](../../project-management/skills/senior-pm/SKILL.md)
- **Scrum Master Skill:** [../../project-management/skills/scrum-master/SKILL.md](../../project-management/skills/scrum-master/SKILL.md)
- **Jira Expert Skill:** [../../project-management/skills/jira-expert/SKILL.md](../../project-management/skills/jira-expert/SKILL.md)
- **Confluence Expert Skill:** [../../project-management/skills/confluence-expert/SKILL.md](../../project-management/skills/confluence-expert/SKILL.md)
- **Atlassian Admin Skill:** [../../project-management/skills/atlassian-admin/SKILL.md](../../project-management/skills/atlassian-admin/SKILL.md)
- **PM Domain Guide:** [../../project-management/CLAUDE.md](../../project-management/CLAUDE.md)
- **Agent Development Guide:** [../CLAUDE.md](../CLAUDE.md)

117
audit/newgen-2026-06/00-MASTER.md Normal file
View file

@ -0,0 +1,117 @@
# Master Audit Report — New-Generation Model Optimization
**Audited:** 2026-06-10 · **Branch:** `claude/skills-plugins-audit-vrttx1` · **Scope:** every canonical skill, plugin, agent, slash command, script, and registry surface (sync copies under `.codex/ .gemini/ .hermes/ .vibe/` excluded as derived artifacts).
**Method:** two automated sweep layers (the repo's own `audit_skills.py` checklist + a custom new-gen sweep for triggers, verification loops, placeholders, stale models, dead links, duplicate content) followed by 10 parallel domain deep-dives that read every SKILL.md, spot-checked references and scripts, and **executed** empirical claims where the skills make them. Rubric: [RUBRIC.md](RUBRIC.md).
---
## 1. Repo-wide scorecard
**324 unique skills** audited (346 SKILL.md files minus dual-published copies and meta/index files counted once):
| Verdict | Count | % | Meaning |
|---|---|---|---|
| **KEEP** | 190 | 59% | Ships as-is; verification criteria recorded per skill in domain reports |
| **OPTIMIZE** | 102 | 31% | Targeted edits (wiring, triggers, freshness) — content core is sound |
| **REWRITE** | 16 | 5% | Structure salvageable, content is not |
| **CUT-OR-MERGE** | 16 | 5% | Does not earn its context window |
Per domain (links go to the detailed reports with **per-skill custom verification criteria**):
| Domain report | Skills | KEEP | OPT | REW | CUT | Health |
|---|---|---|---|---|---|---|
| [productivity + markdown-html](productivity-markdown-html.md) | 11 | 9 | 2 | 0 | 0 | ★ best — 24/27 live checks pass |
| [research + research-ops](research.md) | 13 | 5 | 7 | 1 | 0 | research-ops all-KEEP; research/ needs wiring |
| [bizops + commercial + finance + growth](bizops-commercial-finance.md) | 24 | 14 | 8 | 0 | 2 | v2.8.0 verified; finance/ legacy |
| [c-level-advisor](c-level-advisor.md) | 61 | 40 | 20 | 0 | 1 | strong content, broken wiring |
| [engineering](engineering.md) | 63 | 44 | 8 | 7 | 4 | two generations coexist |
| [engineering-team](engineering-team.md) | 51 | 35 | 13 | 2 | 1 | code-corruption + stale-era issues |
| [compliance (ra-qm + compliance-os)](compliance.md) | 26 | 13 | 11 | 1 | 1 | P0 regulatory staleness |
| [marketing](marketing.md) | 49 | 20 | 24 | 1 | 4 | orphan scripts + path schism |
| [product-team + project-management](product-pm.md) | 26 | 10 | 9 | 4 | 3 | fabricated MCP wiring |
| [cross-cutting infra](cross-cutting.md) | — | — | — | — | — | registries, CI, root agents/commands |
**Other artifact classes:** 92 agents (17 of 32 root agents lack trigger descriptions; 7 of 13 c-level personas cite phantom reference files; 2 missing frontmatter) · 99 commands (9 root commands are cut/merge candidates; 28 of 39 root commands invoke phantom script paths) · 77 plugin manifests (all schema-valid; **11 not registered in marketplace.json**) · 593 scripts (583 pass `--help`; 1 real crash; 9 by-design).
---
## 2. P0 — Correctness defects (fix before anything else)
These cause a model following the skill to produce **wrong or dangerous output today**:
| # | Defect | Where | Evidence |
|---|---|---|---|
| P0-1 | **Repealed regulation taught as current law.** QSR (21 CFR 820 subsections) presented as in force; QMSR (effective 2026-02-02) never mentioned. Reference + `qsr_compliance_checker.py --section 820.30` built on removed section numbers. | `ra-qm-team/skills/fda-consultant-specialist` | [compliance.md](compliance.md) |
| P0-2 | **ALARP table violates EU MDR.** Risk-acceptability framework includes "cost-benefit of further reduction," which MDR Annex I + EN ISO 14971:2019/A11 prohibit. A notified body would flag this exact table. | `ra-qm-team/skills/risk-management-specialist` | [compliance.md](compliance.md) |
| P0-3 | **EU AI Act Article 5 mis-taught.** Default sample classifies *retail* emotion recognition as prohibited; Art. 5(1)(f) covers workplace/education only. | `ra-qm-team/skills/eu-ai-act-specialist` | [compliance.md](compliance.md) |
| P0-4 | **Silent zero-output finance tools.** All 4 scripts read the wrong JSON shape vs their own bundled sample: zero ratios, $0.00 forecasts, error message then `exit 0`. Invisible to `--help` smoke tests. | `finance/financial-analyst` | [bizops-commercial-finance.md](bizops-commercial-finance.md) |
| P0-5 | **Contradictory discount-margin math.** SKILL.md states the correct fixed-COGS formula; `deal_scorer.py` + reference use a different one (script docstring writes the correct formula, then discards it). Margin dimension (weight 0.30) understates discount damage. | `commercial/deal-desk` | [bizops-commercial-finance.md](bizops-commercial-finance.md) |
| P0-6 | **Corrupted code examples from a past bulk YAML-quoting sweep.** E.g. `z.string().min(1).max(100)` → `"zstringmin1max100"`. 4 confirmed sites; models copying these emit broken code. | `engineering-team` senior-qa:123/244, senior-backend:253, senior-frontend:425 | [engineering-team.md](engineering-team.md) |
| P0-7 | **Fabricated MCP tool names.** 3 Atlassian skills + project-management/CLAUDE.md document four different invented naming conventions; none match the bundled Remote MCP's real tools (`createJiraIssue`, `searchJiraIssuesUsingJql`, …). Every documented tool call fails. | `project-management/` (jira-expert, confluence-expert, atlassian-templates) | [product-pm.md](product-pm.md) |
| P0-8 | **Fabricated install coordinates.** Whole skill teaches a `gws` CLI from `npm i -g @anthropic/gws` / `github.com/googleworkspace/cli` — both almost certainly nonexistent; 43 recipes + 5 wrappers unusable. | `engineering-team/skills/google-workspace-cli` | [engineering-team.md](engineering-team.md) |
| P0-9 | **Skill instructs invoking agents that don't exist in this repo** (documents a different ecosystem: `planner`, `/build-fix`, …). | `engineering/skills/command-guide` | [engineering.md](engineering.md) |
| P0-10 | **Stale orchestrator text bypasses shipped converters.** "v2.10.0 foundation" wording tells the model to hand-render HTML instead of routing to md-document/md-review/md-slides, which shipped. Behavioral, not cosmetic. | `markdown-html/` orchestrator (+ domain CLAUDE.md, README) | [productivity-markdown-html.md](productivity-markdown-html.md) |
| P0-11 | **Script crash:** no argparse; `--help` (or any flag) treated as input filename → FileNotFoundError. Skill's only tool. | `marketing-skill/skills/webinar-marketing/scripts/webinar_funnel_scorer.py` | [marketing.md](marketing.md) |
---
## 3. P1 — Systemic wiring failures (one fix clears many skills)
1. **Phantom-path epidemic (the single biggest repo-wide defect).** A directory reorg added a `skills/` path segment; references never followed. **28 of 39 root commands** invoke scripts at `<domain>/<skill>/scripts/…` that live at `<domain>/skills/<skill>/scripts/…`; same stale shorthand in agents' `skills:` frontmatter, `orchestration/ORCHESTRATION.md` (points at skills that exist only as .zip archives), product/PM routers, c-level persona agents (~16 phantom reference filenames across 7 agents), email agents (`engineering/email/...` → `productivity/email/`), and **5 research skills whose final verification step calls `scripts/office/validate.py` — a file that exists nowhere**. → Build a path-existence linter (see §5) and fix in one sweep.
2. **Orphan-script epidemic.** 40+ working, `--help`-passing scripts are never named in their own SKILL.md (24 in marketing, 8 in product/PM, 6+ in engineering, reflect's all-3, ms365, incident-commander). The model loading these skills cannot use their best assets. → A3 wiring pass: exact CLI + consume-the-output step per script.
3. **Counter drift is structural.** Seven surfaces disagree (README 338 skills / CLAUDE.md header 338 / CLAUDE.md v2.10.3 block 343 / marketplace.json description 64 plugins while containing 66 / actual: **346-347 skills, 66 registered + 11 unregistered plugins, 555 tools, 700 references, 17 domains**). agents/CLAUDE.md says 16 agents; folder has 32. → Derive all counters from the tree via script; never hand-edit again.
4. **11 shippable plugins not in marketplace.json** — compliance-os (advertised in the marketplace's own description yet uninstallable), snowflake-development, behuman, claude-coach, grill-with-docs, llm-cost-optimizer, prompt-governance, business-investment-advisor, video-content-strategist, 2× ra-qm compliance-team.
5. **Marketing context-file path schism.** 19 skills read `.claude/product-marketing-context.md`, 16 read `marketing-context.md`, the creator skill writes `.agents/marketing-context.md`. The domain's "read context first" pattern silently no-ops for half its consumers.
6. **c-level role-registry drift.** Routing tables (agent-protocol, chief-of-staff, board-meeting, founder-mode, brief, c-level-agents frontmatter) stopped at 9 roles; domain has 14. CCO/CDO/CAIO/VPE questions silently misroute. Plus three competing decision-memory architectures and two onboarding interviews writing different schemas to the same file.
7. **Dual-publishing without a guard.** 11 byte-identical skill pairs (engineering ×4, c-level ×5, ra-qm ×2). Zero drift today — but no sync script and no CI check; drift is a matter of time.
8. **Trigger-description gap.** 79 skills and 77 of 92 agents lack "use when" phrasing — weak auto-invocation for new-gen models. Root cause for agents: `templates/agent-template.md` mandates a sub-150-char description with no trigger requirement. 8 v2.8.0 descriptions exceed the 1024-char spec limit (knowledge-ops 1,314 — this, not content, is why it "scored worst").
9. **Meta-tooling violates its own rubric.** `audit_skills.py --help` runs the full 30s audit; `generate-docs.py --help` **rewrites docs/ as a side effect** (verified live — this explains the dirty docs/ files found at session start); hermes/vibe/gemini sync scripts, convert.sh, and generate-docs don't know `markdown-html/` exists; CI's blocking `compileall` skips 8 post-v2.7 domains.
10. **35 stale .zip archives** in the public tree (engineering-team 18, compliance 12, marketing 5) plus 4 internal planning docs in the marketing plugin root.
---
## 4. What's already excellent (the template to copy)
- **research-ops/** — every hard rule verified in execution: ESTIMATE banners, dual-method TAM with triangulation-failure flag, anecdote-vs-insight recurrence gate, named-owner routing on every output. All-KEEP.
- **markdown-html/ + productivity/** — 24/27 empirical checks passed live: exit-code refusal gates, WCAG-AA validation, redaction linter (16 patterns, not the claimed 17 — fix the count), idempotent injection, kill-gate behavior in andreessen.
- **v2.8.0 bizops/commercial orchestrators** — `context: fork` signal-table routing with 2-signal thresholds and no-silent-chain gates verified real, not prose.
- **v2.2 security suite, playwright-pro, self-improving-agent, slo-architect, chaos-engineering, karpathy-coder, Pocock ports** — exit-code contracts, forcing questions, kill criteria, exact CLIs.
- **compliance-os layer** — Article-cited verdicts, explicit NOT-boundaries, outside-counsel routing; **no skill in the repo auto-decides compliance verdicts**.
The repo's quality story is generational, not random: everything built v2.4+ with forcing questions, refusal gates, and wired tools is KEEP-grade; v2.0–v2.1-era skills are capability brochures. The optimization play is to **retrofit the new-gen pattern onto the old generation, not to invent anything new**.
---
## 5. Recommended verification harness (CI gates to add)
Each gate below is the generalized guardrail derived from a defect class this audit found. Suggested home: `scripts/` + `ci-quality-gate.yml`.
| Gate | Catches | Spec |
|---|---|---|
| **G1 path-existence linter** | P1-1 phantom paths | Extract every `scripts/…`, `references/…`, `skills:` and relative-path mention from SKILL.md/agents/commands; assert the file exists. Fails today on ~40 surfaces; burn down, then make blocking. |
| **G2 semantic `--sample` smoke** | P0-4 silent zero-output | For every script with `--sample`/bundled sample data: run it, assert exit 0 **and** output passes a per-skill assertion (non-zero metric count, required JSON keys, banner strings). Per-skill assertions are already written: see "Verify (definition of done)" blocks in every domain report. |
| **G3 counter derivation** | P1-3 drift | `scripts/derive_counters.py` counts skills/plugins/tools/refs/agents/commands from the tree and rewrites the counter blocks in README/CLAUDE.md/marketplace.json. CI fails if claimed ≠ derived. |
| **G4 dual-publish drift guard** | P1-7 | `diff -rq` the 11 known pairs; fail on first divergence. |
| **G5 marketplace registration check** | P1-4 | Every `*/.claude-plugin/plugin.json` has a marketplace.json entry (or an explicit `unlisted` allowlist). |
| **G6 description linter upgrade** | P1-8 | Extend `skill_description_validator.py`: hard-fail >1024 chars, warn missing trigger phrasing, apply to agents too; fix `templates/agent-template.md` so new agents start compliant. |
| **G7 model-name freshness** | stale GPT-4/claude-3 era refs | Regex deny-list for retired model identifiers outside historical-context sentences (2 SKILL.md + 2 scripts today). |
| **G8 argparse contract** | P0-11 | Every `scripts/*.py` must exit 0 on `--help` within 5s unless listed in a by-design exceptions file (hooks, fixed evaluators). |
| **G9 meta-tool hygiene** | P1-9 | `generate-docs.py --help` must be side-effect-free; sync scripts/convert.sh/compileall enumerate domains from the tree, not a hardcoded list. |
---
## 6. Suggested execution order (follow-up PRs)
1. **PR-1 (P0 batch, ~1 day):** fix the 11 P0 defects. Highest stakes first: FDA/QMSR, ALARP, AI-Act sample, financial-analyst JSON shape, deal-desk formula, corrupted code literals, Atlassian tool-name appendix, webinar argparse, markdown-html orchestrator status text, retire command-guide + google-workspace-cli (or re-verify the CLI exists).
2. **PR-2 (path sweep):** G1 linter + one mechanical fix-all for the `skills/` segment; fix c-level agent KB filenames, research `office/validate.py` (write it or drop the step), email agent paths.
3. **PR-3 (registries):** G3 counter derivation + marketplace registration of the 11 plugins + c-level role-registry update (6 files) + marketing context-file unification.
4. **PR-4 (wiring):** orphan-script A3 pass per domain report lists; trigger-description batch (79 skills, 77 agents) using each report's per-skill suggested descriptions.
5. **PR-5 (CI):** land gates G2, G4–G9; remove 35 .zip archives; fix meta-tooling.
6. **PR-6+ (content):** the 16 REWRITE skills, then OPTIMIZE queue per domain, using the per-skill "Verify (definition of done)" blocks as acceptance criteria.
---
## 7. Where the per-skill verification criteria live
The user-requested **customized verification loops and validation criteria for every skill, plugin, agent, and command** are in the domain reports: every OPTIMIZE/REWRITE/CUT entry carries a "Verify (definition of done)" block of 2–4 executable checks, and every KEEP skill has a one-line verification contract in its report's "KEEP-verdict verification criteria" section. Those blocks are the input for gate G2.

55
audit/newgen-2026-06/RUBRIC.md Normal file
View file

@ -0,0 +1,55 @@
# New-Generation Model Optimization Rubric (v1)
Audit date: 2026-06-10 · Branch: `claude/skills-plugins-audit-vrttx1`
This rubric defines what "optimized for new-generation models" means for every artifact
type in this repository. New-gen frontier models (Claude Fable/Opus 4.x class) differ from
the models many of these skills were written for: they need **less hand-holding, more
context economy, and machine-checkable verification**. A skill earns its context window
or it gets cut.
## A. SKILL.md — 7 dimensions
| # | Dimension | What PASS looks like |
|---|-----------|----------------------|
| A1 | **Trigger quality** | Frontmatter `description` states what the skill does AND when to fire, in third person, < 1024 chars, with concrete trigger phrases ("Use when…", example user requests). Never just the skill name. |
| A2 | **Context economy** | Body is instruction-dense. Progressive disclosure: SKILL.md holds the workflow + decision rules; deep knowledge lives in `references/` and is loaded on demand. No "You are an expert…" filler, no restating what a frontier model already knows (generic advice = dead weight). |
| A3 | **Tool wiring** | Every referenced script exists, has exact CLI invocations in SKILL.md, and its output is consumed by a named next step. No orphan scripts, no phantom paths. |
| A4 | **Verification loop** | The workflow ends with a check the model can execute: run a script and assert exit code/output shape, validate against an explicit checklist, or hit a refusal gate. Skills without one get a *proposed* custom loop in this audit. |
| A5 | **Real-world expertise** | A practitioner would recognize domain mastery: named frameworks with thresholds, formulas, regulatory citations, decision trees — not "communicate clearly with stakeholders". |
| A6 | **Freshness** | No stale model names (claude-3-x, GPT-3.5-era), dead prices, or 2024-isms presented as current. |
| A7 | **No filler files** | Every file in the package earns its place. References cite sources and say something non-obvious. Assets are usable, not shells. No duplicated boilerplate. |
Verdicts: **KEEP** (ship as is) · **OPTIMIZE** (targeted edits, listed) · **REWRITE** (structure salvageable, content not) · **CUT-OR-MERGE** (does not earn its context).
## B. Agents (`agents/*.md`)
- B1 Frontmatter: `name`, `description` with trigger phrasing ("Use when…" / "Use PROACTIVELY…"), minimal `tools` list.
- B2 Differentiation: the system prompt could not be swapped with a sibling agent's without someone noticing. Personas must change behavior, not adjectives.
- B3 No placeholder/boilerplate body.
## C. Slash commands (`commands/*.md`)
- C1 Frontmatter description present and accurate.
- C2 `$ARGUMENTS` / argument-hint handled.
- C3 The command does something a bare prompt could not (orchestrates tools, enforces gates). Otherwise: candidate for merge or cut.
## D. Scripts (`scripts/*.py`)
- D1 `--help` exits 0 (verified repo-wide this audit: 583/593 pass).
- D2 Stdlib-only, no LLM calls, deterministic.
- D3 Output is machine-parseable where a workflow consumes it (JSON mode).
- D4 By-design exceptions (hooks reading stdin, fixed-contract evaluators) documented where they live.
## E. Plugins (`.claude-plugin/plugin.json`)
- E1 Schema valid (verified repo-wide: all pass `check_plugin_json.py --all`).
- E2 Description matches actual contents (pod/skill counts drift).
- E3 Version coherent with marketplace.json.
## Custom verification criteria — the contract
For **every skill** audited, the domain report includes 2–4 *executable* "definition of
done" checks specific to that skill (e.g. "`python3 scripts/x.py --sample` exits 0 and
emits JSON with keys `verdict`, `score`; verdict ∈ {GO, NO-GO}"). These are the
guardrails future optimization PRs must keep green.

133
audit/newgen-2026-06/bizops-commercial-finance.md Normal file
View file

@ -0,0 +1,133 @@
# Domain audit: business-operations/ + commercial/ + finance/ + business-growth/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 24 · Agents: 2 · Commands: 17 (+2 root finance commands) · Plugins: 5
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| business-operations/business-operations-skills | KEEP | — (orchestrator routing is real: signal table + 2-signal threshold + no-silent-chain) |
| business-operations/process-mapper | KEEP | — (deterministic VA% bands, 3 detection rules, profiles) |
| business-operations/vendor-management | OPTIMIZE | Frontmatter description 1,106 chars (> 1024 A1 limit) |
| business-operations/capacity-planner | KEEP | — (Erlang-C, P50/P90/P99, manager-trigger; best forcing-question library in scope) |
| business-operations/internal-comms | OPTIMIZE | Description 1,284 chars (> 1024) |
| business-operations/knowledge-ops | OPTIMIZE | Description 1,314 chars (> 1024) — the actual cause of its 2/6 repo-checklist infamy; content itself is strong |
| business-operations/procurement-optimizer | OPTIMIZE | Description 1,266 chars (> 1024) |
| commercial/commercial-skills | KEEP | — (orchestrator; 7-lane signal table, depth-first chaining gates) |
| commercial/pricing-strategist | KEEP | — (model+range hard rule operationalized in workflow Step 5 + anti-pattern #1) |
| commercial/deal-desk | OPTIMIZE | Margin math is internally contradictory (SKILL.md says 37.5% loss; script computes 24-pt / 30% via a different formula) |
| commercial/partnerships-architect | KEEP | — (deterministic tier floors, kill-criteria mandate) |
| commercial/channel-economics | OPTIMIZE | Description 1,178 chars (> 1024) |
| commercial/commercial-policy | KEEP | — (4-dim matrix, 10-rule linter, precedent-risk flag verified) |
| commercial/rfp-responder | KEEP | — (GAP-never-invent rule, no-bid < 20% threshold; winrate sample verified) |
| commercial/commercial-forecaster | KEEP | — (assumption block verified NON-OPTIONAL in script output) |
| finance/finance-skills | CUT-OR-MERGE | 55-line plugin README posing as a skill; broken paths; no trigger description |
| finance/financial-analyst | OPTIMIZE | All 4 scripts silently fail (exit 0, zeros) against their own bundled sample — schema mismatch |
| finance/saas-metrics-coach | KEEP | — (benchmark tables with thresholds, strict output contract, status labels) |
| finance/business-investment-advisor | OPTIMIZE | Nested plugin unregistered in marketplace; manifest description truncated mid-word |
| business-growth/business-growth-skills | CUT-OR-MERGE | References phantom "BizDev-toolkit" skill; broken quick-start paths |
| business-growth/contract-and-proposal-writer | OPTIMIZE | 423-line SKILL.md with full contract templates inline; no scripts/references/assets at all |
| business-growth/customer-success-manager | KEEP | — (weighted scorers with explicit weights/thresholds, segment-aware) |
| business-growth/revenue-operations | KEEP | — (formula+threshold tables, CRM cross-check verification steps) |
| business-growth/sales-engineer | KEEP | — (executable validation checkpoints between phases; strongest A4 in scope) |
**Counts: 14 KEEP · 8 OPTIMIZE · 0 REWRITE · 2 CUT-OR-MERGE**
## Domain-level findings
1. **The v2.8.0 claims hold.** Both orchestrators (`business-operations-skills`, `commercial-skills`) have `context: fork` in frontmatter and real routing logic — signal tables, a 2-signal confidence threshold, single-question fallback with recommended answer, and explicit "never silently chain" gates. Every one of the 13 bizops/commercial sub-skills ships a 5-8 question forcing-question library with per-question recommended answer + canon citation. This is not vague prose.
2. **Hard rules are operationalized, not just claimed.** Verified by execution: `deal_scorer.py --sample` emits an approver chain and "2 critical signal(s) detected; cannot APPROVE" (never auto-approves); `bookings_forecaster.py --sample` emits an "Assumption block (NON-OPTIONAL)" section; pricing-strategist's workflow Step 5 and anti-pattern #1 enforce model+range-never-a-number; vendor/procurement outputs are framed as "inputs to a human decision" with refusal logic (single-source tier-1 consolidation refused without break-glass).
3. **Systemic A1 failure in the v2.8.0 batch: 5 of 15 frontmatter descriptions exceed the 1,024-char limit** (knowledge-ops 1,314 · internal-comms 1,284 · procurement-optimizer 1,266 · channel-economics 1,178 · vendor-management 1,106). They cram "Distinct from" and tool inventories into the trigger field. This — not content quality — is what tanked knowledge-ops/procurement-optimizer on the repo's own checklist. One-pass fix: move everything after the trigger sentence into the body.
4. **Systemic A3 gap in the v2.8.0 batch: almost no fenced CLI examples.** 8 of 13 sub-skills score "0 code blocks" on the repo checklist; invocations live in prose/tables. deal-desk and commercial-policy (which have "Quick examples" sections) show the right pattern.
5. **finance/ and business-growth/ are a different generation.** No forcing questions, no profiles, no named-owner routing, meta-skills (`finance-skills`, `business-growth-skills`) that are plugin READMEs with broken paths. The per-skill content (saas-metrics-coach, customer-success-manager, revenue-operations, sales-engineer) still earns KEEP on calibrated thresholds, but the wrappers are dead weight.
6. **One genuinely broken tool chain: financial-analyst.** Its `assets/sample_financial_data.json` nests data under per-tool keys (`ratio_analysis`, `dcf_valuation`, `budget_variance`, `forecast`) while all four scripts read top-level keys. Result: every documented quick-start command "succeeds" (exit 0) while emitting all-zero ratios, "Error: Historical revenue data is required" (still exit 0), `Total Items: 0`, and $0.00 forecasts. The repo-wide `--help` smoke test cannot catch this class of failure.
7. **Domain-math inconsistency in deal-desk.** SKILL.md (citing `discount_economics.md`) says "a 30% discount on an 80% gross-margin product loses 37.5% of margin, not 30%" — correct under fixed COGS: margin dollars fall 30/80 = 37.5%. But `deal_scorer.py` and `discount_economics.md` actually use `net_margin = G − D·(G/100)` (proportional COGS) → 24-pt loss / 30% relative. The script's own docstring writes the correct `(G−D)/(1−D/100)` formulation, then discards it. Pick one model; the scorer's margin dimension (weight 0.30) currently understates discount damage.
## Per-skill findings
### business-operations/vendor-management — OPTIMIZE
- Issues: (1) description 1,106 chars > 1024 — trim to trigger sentence, move "Ships 3 tools…" and "Distinct from…" into the body; (2) no fenced CLI examples (checklist rule 5); (3) SKILL.md 170 lines — body content fine, but Steps 2-4 partially duplicate script-level docs.
- Verify: `python3 -c "import re;t=open('business-operations/skills/vendor-management/SKILL.md').read();d=re.search(r'description:(.*?)\n\w+:',t,re.S).group(1);assert len(d.strip())<1024"` · `python3 skills/vendor-management/scripts/vendor_scorer.py --sample` exits 0 with KEEP/REVIEW/REPLACE verdicts · `--profile healthcare` output differs from `--profile saas` · SKILL.md contains ≥ 1 fenced ```bash block.
### business-operations/internal-comms — OPTIMIZE
- Issues: (1) description 1,284 chars > 1024; (2) zero fenced CLI examples; (3) "Distinct from" appears in both description and body (duplicated context cost).
- Verify: description < 1024 chars · all 3 scripts pass `--sample` exit 0 · `change_announcement_builder.py` still rejects "exciting news" tone on `disruptive` magnitude (magnitude/tone validation preserved) · ≥ 1 fenced code block in SKILL.md.
### business-operations/knowledge-ops — OPTIMIZE
- Issues: (1) description 1,314 chars > 1024 — worst in repo, and the real driver of its 2/6 checklist score; (2) zero fenced CLI examples; (3) "a procurement tool sunset in 2024" tripped the time-sensitivity rule — rephrase relatively; (4) content (5W2H validator thresholds, SAFE ≥ 80 / NOT-SAFE < 60 bands, staleness×inbound-links ranking) is genuinely strong — do not rewrite.
- Verify: description < 1024 chars · `kb_ingester.py --sample` exits 0 and reports orphan/stale/glossary-drift counts on the synthetic 8-page vault · `runbook_validator.py --sample` returns NOT-SAFE on the deliberately-broken runbook · repo checklist (`skill_review_checklist_runner.py <folder>`) reaches ≥ 4/6.
### business-operations/procurement-optimizer — OPTIMIZE
- Issues: (1) description 1,266 chars > 1024; (2) zero fenced CLI examples; (3) SKILL.md 167 lines with tool inventory repeated 3× (description, Workflow, Scripts table).
- Verify: description < 1024 chars · `supplier_consolidation.py --sample` exits 0 and still emits the "DO NOT CONSOLIDATE — tier-1 cluster, no break-glass" refusal on a tier-1 cluster without break-glass flag · `spend_categorizer.py --sample --profile enterprise` differs from `--profile tech-startup`.
### commercial/deal-desk — OPTIMIZE
- Issues: (1) margin-formula contradiction: SKILL.md claims 37.5% margin loss (fixed-COGS, correct), `deal_scorer.py:123-133` + `references/discount_economics.md` compute `G − D·G/100` = 24 pts (proportional-COGS); the docstring names the correct `(G−D)/(1−D/100)` formula then ignores it — reconcile to one model across all three files; (2) discount_economics.md "Why the conventional shorthand is wrong" section is itself wrong under the standard fixed-COGS assumption.
- Verify: `deal_scorer.py --sample` exits 0, verdict DECLINE, output contains "cannot APPROVE" and a ≥ 4-hop approver chain · SKILL.md margin example, `discount_economics.md` worked table, and `score_margin()` produce the same number for (G=80, D=30) · `--profile services` composite differs from `--profile saas` · `terms_redliner.py --sample` flags uncapped indemnity as CRITICAL.
### commercial/channel-economics — OPTIMIZE
- Issues: (1) description 1,178 chars > 1024 — it embeds four "Not X (that's Y)" disambiguations plus a keyword list; (2) zero fenced CLI examples.
- Verify: description < 1024 chars · all 3 scripts pass `--sample` exit 0 · `channel_roi_analyzer.py --sample` emits one of DOUBLE-DOWN/MAINTAIN/DEFUND/EXIT per channel · cost-to-serve output contains both per-deal and per-$-ARR lines.
### finance/finance-skills — CUT-OR-MERGE
- Issues: (1) it is a plugin README, not a skill — no workflow, no decision rules, no trigger phrasing ("Financial analyst agent skill and plugin for Claude Code, Codex…"); (2) quick-start path `finance/financial-analyst/SKILL.md` doesn't exist (actual: `finance/skills/financial-analyst/`); (3) wholly duplicates plugin.json + finance/CLAUDE.md. Merge useful lines into README.md/plugin.json and delete, or rebuild as a real router (the bizops/commercial orchestrator pattern exists to copy).
- Verify (if merged): `finance/skills/finance-skills/` removed AND `finance/.claude-plugin/plugin.json` `skills` array updated AND `check_plugin_json.py --all` passes · no references to `finance/financial-analyst/` (without `/skills/`) remain: `grep -r "finance/financial-analyst" finance/ | grep -v skills/` returns nothing.
### finance/financial-analyst — OPTIMIZE
- Issues: (1) **broken tool wiring**: all 4 scripts read top-level keys (`income_statement`, …) while `assets/sample_financial_data.json` nests them under `ratio_analysis`/`dcf_valuation`/`budget_variance`/`forecast` — every documented quick-start emits zeros; (2) error masking: `dcf_valuation.py` prints "Error: Historical revenue data is required" and exits 0; (3) `references/financial-ratios-guide.md` cites zero sources (A7); (4) Phase 1/5 of the workflow is filler a frontier model doesn't need ("Define analysis objectives and stakeholder requirements").
- Verify: `ratio_calculator.py assets/sample_financial_data.json` produces zero "Insufficient data" lines and a nonzero Gross Margin · `dcf_valuation.py <bad input>` exits nonzero · `budget_variance_analyzer.py assets/sample_financial_data.json` reports Total Items > 0 · `forecast_builder.py` base-case revenue > $0 on the bundled sample.
### finance/business-investment-advisor — OPTIMIZE
- Issues: (1) nested plugin `finance/business-investment-advisor/.claude-plugin/plugin.json` is not registered in marketplace.json — either register it or fold the skill into the finance plugin's `skills` array and delete the nested manifest; (2) that manifest's description is truncated mid-word ("Also use f"); (3) prompt-only skill claiming "show all math" with no deterministic tool — acceptable for an advisor, but the IRR/NPV sections restate model-known formulas (A2); the rubric + proactive-triggers + anti-pattern table are the parts that earn context — trim the formula restatements.
- Verify: skill is reachable via exactly one registered plugin (`python3 scripts/check_plugin_json.py --all` passes; marketplace lookup finds it) · manifest description is a complete sentence < 1024 chars · SKILL.md ≤ ~150 lines after trimming formula primers.
### business-growth/business-growth-skills — CUT-OR-MERGE
- Issues: (1) names a fifth skill "BizDev-toolkit" that does not exist anywhere in the repo; (2) quick-start path `business-growth/customer-success-manager/SKILL.md` is wrong (actual: `business-growth/skills/customer-success-manager/`); (3) body says "4 production-ready skills", description says 5 — neither matches a real router; (4) duplicates plugin.json + CLAUDE.md. Same disposition as finance-skills: delete-and-merge, or rebuild on the bizops orchestrator pattern.
- Verify (if merged): folder removed, plugin.json skills path still valid, `grep -ri "bizdev-toolkit" business-growth/` returns nothing, `check_plugin_json.py --all` passes.
### business-growth/contract-and-proposal-writer — OPTIMIZE
- Issues: (1) 423-line SKILL.md with three full contract templates + a GDPR DPA block inline — move Templates A/B/C and the DPA block to `assets/` and keep selection logic + jurisdiction notes + pitfalls in SKILL.md (progressive disclosure, A2); (2) only single-file skill in scope — no references/assets despite being template-heavy by nature; (3) static legal claims (§126 BGB, §74 HGB, "post-Brexit") carry freshness risk with no last-reviewed marker; add one; (4) overlaps `commercial/rfp-responder` and `c-level-advisor/general-counsel-advisor` — the existing scope sentence is good, keep it.
- Verify: SKILL.md ≤ ~150 lines · `assets/` contains ≥ 4 template files referenced by name from SKILL.md · description still trigger-phrased ("Use when drafting…") · a "last legal review" date line exists.
## KEEP-verdict verification criteria
- **business-operations-skills**: frontmatter retains `context: fork`; signal table lists exactly 6 lanes matching plugin.json skill paths; "Do NOT chain silently" and ≤ 200-word digest rules present.
- **process-mapper**: 3 scripts pass `--sample` exit 0; `cycle_time_analyzer` emits VA% verdict ∈ {HEALTHY, TYPICAL, WASTE-HEAVY} with 25%/10% bounds; `bottleneck_detector.py --profile healthcare` ≠ `--profile saas` output.
- **capacity-planner**: `capacity_modeler.py --sample` exits 0 with risk band ∈ {SAFE, WATCH, AT_RISK, CRITICAL} and a P50/P90/P99 breach table; `hiring_sequencer` triggers a manager hire when span crosses 7; 7 forcing questions remain canon-cited.
- **commercial-skills**: `context: fork` retained; 7-lane signal table matches the 7 sub-skill folders; anti-pattern list keeps "recommend a range + model" and "never auto-approve" lines.
- **pricing-strategist**: `wtp_analyzer.py --sample` exits 0, emits OPP/IDP/PMC/PME + a sub-100-N sample-size warning; `packaging_designer.py --sample` flags ≥ 1 anti-pattern; SKILL.md anti-pattern #1 ("Recommending a specific number") intact.
- **partnerships-architect**: `partner_tier_classifier.py --sample` exits 0; STRATEGIC floor still requires named_accounts ≥ 5 AND multi-year commit AND dedicated resources; kill-criteria mandate in Assumptions.
- **commercial-policy**: `policy_linter.py --sample` exits FAIL-by-design with 4 BLOCKERs; `exception_router.py --sample` routes the 42% exception with ≥ 3 compensating commitments; precedent-risk (3+ similar exceptions) flag preserved.
- **rfp-responder**: `winrate_predictor.py --sample` exits 0 with estimate + confidence band + verdict ∈ {BID, PARTNER-BID, NO-BID}; < 20% auto-no-bid threshold intact; "never invents claims" GAP rule in both description and Step 2.
- **commercial-forecaster**: `bookings_forecaster.py --sample` output contains "Assumption block (NON-OPTIONAL"; three tiers (commit/best-case/pipe-only) emitted; CoV bands (10/25/50%) in `funnel_confidence_scorer` unchanged.
- **finance/saas-metrics-coach**: `metrics_calculator.py --mrr 50000 --customers 100 --churned 5 --json` exits 0 with `_missing` array; quick-ratio bands (<1 CRITICAL, >4 EXCELLENT) match references/benchmarks.md; output-format template (Metrics at a Glance → 90-Day Focus) preserved.
- **customer-success-manager**: all 3 scripts exit 0 against `assets/sample_customer_data.json` (its sample actually works — unlike financial-analyst's); dimension weights sum to 100% in both SKILL.md tables and scripts; Green/Yellow/Red bounds 75/50 unchanged.
- **revenue-operations**: 3 scripts exit 0 against bundled samples; coverage target 3-4x, MAPE rating table, and Rule-of-40 thresholds present in both SKILL.md and script output.
- **sales-engineer**: the inline python validation one-liners in Phases 1/3/4 execute without KeyError against `--format json` output of the corresponding scripts (these are the skill's A4 backbone — keep them runnable).
## Agents
2 agents in scope (`business-operations/agents/cs-bizops-orchestrator.md`, `commercial/agents/cs-commercial-orchestrator.md`); finance/ and business-growth/ ship none.
- **B1**: both have name/description/tools/model. Descriptions are persona-stated rather than "Use when…"-phrased — minor A1-style gap; routing context is otherwise clear. Both pin `model: sonnet` — verify that's intended for orchestration-heavy work on new-gen defaults.
- **B2**: genuinely differentiated — different signature questions ("Where does the work spend most of its time waiting?" vs "What's the margin at full discount?"), different lane tables, different hard-output contracts (named approver / model+range / disclosed assumption). Not swappable.
- **B3**: no boilerplate. One staleness bug in both: the "Available commands" sections still annotate 9 commands with "(Sprint 2)" although all shipped — delete the annotations.
- Gap: business-growth and finance rely on root-level `/saas-health`, `/financial-health` and no persona agent; acceptable for legacy skills, but if the meta-skills are rebuilt as routers, add agents then — not before.
## Commands
17 in scope (8 bizops, 9 commercial) + 2 root finance commands (`/saas-health`, `/financial-health`).
- **C1/C2**: all sampled commands have accurate frontmatter descriptions and `argument-hint`, and interpolate `$ARGUMENTS`.
- **C3**: routers (`/cs:bizops`, `/cs:commercial`) and grills (`/cs:grill-bizops`, `/cs:grill-commercial`) clearly orchestrate (signal scoring, one-question discipline, refusal-to-route gates) — pass. Per-skill commands (`/cs:vendor-review`, `/cs:deal-review`, `/cs:knowledge-ops`, etc.) mostly restate their SKILL.md's tool table + "Distinct from" section; they pass C3 only because they name exact tools/profiles/verdicts. If context budget ever matters, these 13 per-skill commands are the first merge candidates into their routers — but no action required now.
- `/saas-health` and `/financial-health` are thin wrappers over the scripts; `/financial-health` inherits the financial-analyst sample-schema bug (its documented `ratios <data.json>` path silently zeroes). Fix rides on the financial-analyst OPTIMIZE.
- business-growth/ has zero commands — its 4 real skills are invocable only by description-matching. Acceptable; note for any future refresh.
## Plugin manifests
All 5 schema-valid (repo-wide E1 pass confirmed); versions coherent at 2.9.0 where registered. E2 drift everywhere:
1. **business-operations**: claims "24+ reference docs each citing ≥7 authoritative sources" — actual count is 18 (6 sub-skills × 3). Fix the number.
2. **commercial**: claims "28+ reference docs" — actual is 21 (7 × 3). Fix the number.
3. **finance**: description counts business-investment-advisor among its "3 finance skills", but `"skills": ["./skills"]` excludes it (it lives at `finance/business-investment-advisor/`, outside the path). Either move the skill under `finance/skills/` or correct the description.
4. **business-investment-advisor** (nested): description truncated mid-word ("…Also use f"); not registered in `.claude-plugin/marketplace.json` — it is currently undiscoverable as a plugin. Register or fold into finance-skills.
5. **business-growth**: description enumerates "BizDev-toolkit", a skill that does not exist; "5 business & growth skills" counts the meta-README skill. Correct to the 4 real skills (or 5 only after the meta-skill is rebuilt as a real router).

281
audit/newgen-2026-06/c-level-advisor.md Normal file
View file

@ -0,0 +1,281 @@
# Domain audit: c-level-advisor/ — new-gen model optimization
Audited: 2026-06-10 · Unique skills: 61 (of 66 SKILL.md files incl. dual-published) · Agents: 14 (13 cs-* in c-level-agents/agents/ + devils-advocate; cs-ceo/cs-cto live outside the folder in /agents/c-level/) · Plugins: 8
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| **skills/ (main bundle, 33)** | | |
| agent-protocol | OPTIMIZE | Valid-roles list frozen at 9 roles; 5 newer roles (GC/CDO/CAIO/CCO/VPE) can't be invoked per protocol |
| board-deck-builder | OPTIMIZE | Phantom `/board-deck` command in Quick Start |
| board-meeting | OPTIMIZE | Role tables omit 5 newer roles; `/cs:board` vs `/cs:boardroom` naming clash |
| c-level-skills | CUT-OR-MERGE | Bundle README posing as a skill; contradicts cs-onboard and board-meeting on protocol details |
| ceo-advisor | KEEP | ~30 lines of shared boilerplate (Communication/Context Integration) duplicated across all role skills |
| cfo-advisor | KEEP | — |
| change-management | KEEP | — |
| chief-ai-officer-advisor | KEEP | A6 watch: hardcoded 2026 API/GPU pricing will rot |
| chief-customer-officer-advisor | KEEP | — |
| chief-data-officer-advisor | KEEP | — |
| chief-of-staff | OPTIMIZE | "28 skills" stale (33); routing matrix omits 5 roles; 3rd divergent decision-log path |
| chro-advisor | KEEP | — |
| ciso-advisor | KEEP | — |
| cmo-advisor | KEEP | — |
| company-os | KEEP | — |
| competitive-intel | OPTIMIZE | 5 phantom `/ci:*` commands in Quick Start |
| context-engine | KEEP | — |
| coo-advisor | KEEP | — |
| cpo-advisor | KEEP | — |
| cro-advisor | KEEP | — |
| cs-onboard | OPTIMIZE | Conflicts with c-level-agents `/cs:onboard` (7-dimension vs 12-question interview, same output file) |
| cto-advisor | KEEP | — |
| culture-architect | KEEP | — |
| decision-logger | KEEP | Memory path conflict with `/cs:decide` (flagged there) |
| founder-coach | KEEP | — |
| general-counsel-advisor | KEEP | — |
| internal-narrative | KEEP | — |
| intl-expansion | OPTIMIZE | Thin; no tool; no verification loop |
| ma-playbook | OPTIMIZE | Thinnest skill in domain; valuation numbers unsourced; no tool |
| org-health-diagnostic | KEEP | — |
| scenario-war-room | KEEP | Phantom `/war-room` invocation (minor) |
| strategic-alignment | KEEP | — |
| vpe-advisor | KEEP (dual-published) | Workflow CLI paths inconsistent with Quick Start paths |
| **executive-mentor/skills/ (6)** | | |
| executive-mentor | KEEP | — |
| challenge | KEEP | — |
| board-prep | KEEP | — |
| hard-call | OPTIMIZE | Placeholder description (A1 fail) |
| postmortem | OPTIMIZE | Placeholder description (A1 fail) |
| stress-test | OPTIMIZE | Placeholder description (A1 fail) |
| **c-level-agents/skills/ (22)** | | |
| c-level-agents (overview) | OPTIMIZE | Frontmatter says 8 agents / 17 commands; reality is 13 / 21 |
| founder-mode | OPTIMIZE | Routing table omits CDO/CAIO/CCO/VPE — auto-router can't reach 4 of 13 advisors |
| office-hours | KEEP | — |
| onboard | OPTIMIZE | Second, divergent founder interview writing the same `~/.claude/company-context.md` |
| brief | OPTIMIZE | Affected-roles checklist omits 5 newer advisors |
| boardroom | KEEP | — |
| decide | OPTIMIZE | Writes `~/.claude/decisions/` while decision-logger skill specifies `memory/board-meetings/` |
| execute | KEEP | — |
| post-mortem | KEEP | — |
| freeze | KEEP | `/cs:unfreeze` has no skill file (handled in-file; minor) |
| cross-eval | KEEP | — |
| cfo-review | KEEP | — |
| cmo-review | KEEP | — |
| cpo-review | KEEP | — |
| cro-review | KEEP | — |
| cto-review | KEEP | — |
| ciso-review | KEEP | — |
| gc-review | KEEP | — |
| cdo-review | OPTIMIZE | Routes to phantom `/cs:chro-review` |
| caio-review | OPTIMIZE | Routes to phantom `/cs:chro-review` |
| cco-review | OPTIMIZE | Routes to phantom `/cs:chro-review` |
| vpe-review | OPTIMIZE | Routes to phantom `/cs:chro-review` |
| **Dual-published standalone copies** | (counted above) | chief-ai-officer-advisor, chief-customer-officer-advisor, chief-data-officer-advisor, general-counsel-advisor, vpe-advisor |
**Totals: KEEP 40 · OPTIMIZE 20 · REWRITE 0 · CUT-OR-MERGE 1**
## Domain-level findings
### 1. Dual-publication map (5 pairs, zero drift today — but no guard)
Each of these exists twice, byte-identical (verified with `diff -rq` across SKILL.md + all references + all scripts):
| Bundle copy (`c-level-advisor/skills/<x>/`) | Standalone copy (`c-level-advisor/<x>/skills/<x>/`) | Drifted? |
|---|---|---|
| chief-ai-officer-advisor | chief-ai-officer-advisor | No |
| chief-customer-officer-advisor | chief-customer-officer-advisor | No |
| chief-data-officer-advisor | chief-data-officer-advisor | No |
| general-counsel-advisor | general-counsel-advisor | No |
| vpe-advisor | vpe-advisor | No |
The duplication is intentional (standalone-installable plugin AND bundled in c-level-skills) but there is **no sync script, no CI check, and no comment in either copy declaring the other copy exists**. Any future edit to one side silently forks the skill. **Recommendation:** add a `scripts/check_dual_published.py` (or extend ci-quality-gate) that diffs the 5 pairs and fails on divergence; alternatively replace standalone copies with a build step. This is the single highest-leverage guard for the domain. Drift status: GREEN today, unprotected.
### 2. Role-registry drift — the domain's 9-role core never learned about its 5 newest roles
The domain grew from 9 C-roles to 14 (GC v2.5.1, CDO v2.5.2, CAIO v2.5.3, CCO v2.5.4, VPE v2.5.5), but the orchestration core was never updated:
- `agent-protocol/SKILL.md` — "Valid roles: ceo, cfo, cro, cmo, cpo, cto, chro, coo, ciso". Per the protocol's own hard rules, `[INVOKE:gc|...]` etc. is undefined.
- `chief-of-staff/SKILL.md` — routing matrix and "routes to 28 skills total" (now 33) omit the 5 roles entirely.
- `board-meeting/SKILL.md` — Phase 1 role-activation table and Phase 2 ordering list only the original 9.
- `c-level-agents/skills/founder-mode/SKILL.md` — keyword routing table has no rows for data/AI/customer/VPE topics; "retention dropped" routes to CRO, never CCO.
- `c-level-agents/skills/brief/SKILL.md` — affected-roles checklist stops at cs-chief-of-staff.
- `c-level-agents/skills/c-level-agents/SKILL.md` frontmatter — "8 cs-* agents… 17 /cs:* commands" vs actual 13 / 21.
Fix once, in all six files, in one PR.
### 3. Three competing decision-memory architectures
- `decision-logger` skill: `memory/board-meetings/decisions.md` (Layer 2) + `YYYY-MM-DD-raw.md` (Layer 1)
- `chief-of-staff` skill: `~/.claude/decision-log.md`
- `/cs:decide`: `~/.claude/decisions/approved/` + `~/.claude/decisions/raw/`
All three claim to be "the" two-layer memory. An agent following decision-logger will never find decisions written by `/cs:decide`. Pick one canonical layout (the `~/.claude/decisions/` form is most portable) and update the other two.
### 4. Two competing founder-onboarding interviews
`cs-onboard` (7 dimensions, ~45 min, conversational probes) and `c-level-agents/onboard` (12 structured questions) both write `~/.claude/company-context.md` with **different schemas**; `c-level-skills/SKILL.md` describes a third, 7-question variant that writes to "the project root". The context-engine "Required Context Fields" match only the cs-onboard schema. Reconcile to one interview + one schema.
### 5. Phantom slash commands
Referenced but existing nowhere in `commands/` nor as plugin command/skill files: `/board-deck`, `/war-room`, `/health`, `/health:dimension`, `/ci:landscape|battlecard|winloss|update|map`, `/cs:chro-review`, `/cs:coo-review` (routed-to from 4+ review skills), `/cs:board` + `/cs:decisions` + `/cs:review` + `/cs:setup` + `/cs:update` (pre-date the c-level-agents `/cs:*` namespace and now collide with it). Either create thin command files or rewrite the Quick Starts as natural-language triggers.
### 6. Agent reference-file hallucinations (see Agents section)
7 of 13 cs-* agents cite knowledge-base filenames that do not exist on disk — apparently written from memory of what the references *should* be called. New-gen models will attempt to Read these paths and fail.
### 7. Shared boilerplate tax
Every role-advisor SKILL.md carries the identical ~25-line Communication / Context Integration / Internal Quality Loop block that `agent-protocol/SKILL.md` already owns. Across ~15 skills that's ~375 lines of duplicated context. A one-line pointer ("Output passes the Internal Quality Loop — see agent-protocol/SKILL.md") would reclaim it. Also: `Keywords` sections (10–40 terms each) are dead weight for new-gen trigger matching since the frontmatter description already carries triggers.
### 8. Repo hygiene
- `ceo-advisor.zip` (32K) and `cto-advisor.zip` (28K) are stray build artifacts at the domain root — delete.
- `c_level_leadership_skills_overview.md` at domain root duplicates CLAUDE.md content.
- `c-level-advisor/CLAUDE.md` says "Skills Deployed: 33 … + 21 /cs:* sub-skills" but also "28 skills" in the architecture intro of chief-of-staff; CLAUDE.md itself says "13 cs-* persona agents" correctly but root repo CLAUDE.md says "51+ agents (cs-* + 7 personas)" — counts drift in 3 places.
## Per-skill findings
### c-level-skills (skills/c-level-skills/)
- **Verdict: CUT-OR-MERGE**
- Issues: (1) It's the bundle's README wearing a SKILL.md frontmatter — `name: "c-level-advisor"` doesn't even match its folder. (2) Describes `/cs:setup` as a 7-question form writing company-context.md "to the project root", contradicting cs-onboard (7 dimensions, `~/.claude/`) and c-level-agents/onboard (12 questions). (3) Describes `/cs:board` as 3 phases; board-meeting skill defines 6. (4) Stale counts (28 skills, 25 tools). (5) As a trigger surface it competes with chief-of-staff for the same routing job.
- Verify: `grep -c "Phase" skills/c-level-skills/SKILL.md` no longer describes a board protocol that disagrees with `board-meeting/SKILL.md`; content merged into README.md or CLAUDE.md; `find c-level-advisor/skills -name SKILL.md | wc -l` drops by 1 (or file becomes a pure router stub < 40 lines).
### agent-protocol
- **Verdict: OPTIMIZE**
- Issues: (1) Valid-roles list omits gc/cdo/caio/cco/vpe. (2) Peer-verification table has no rows for legal/data/AI/customer claims. (3) At 418 lines it carries the Communication Standard that 15 sibling skills then duplicate — the duplication should collapse toward this file.
- Verify: `grep -E "gc|cdo|caio|cco|vpe" skills/agent-protocol/SKILL.md` returns the invocation registry rows; the 5 newer role SKILL.mds still render the `[INVOKE:role|...]` examples without contradiction; sibling role skills reference (not restate) the quality loop.
### chief-of-staff
- **Verdict: OPTIMIZE**
- Issues: (1) "routes to 28 skills total" — 33 exist. (2) Routing matrix has no rows for legal, data strategy, AI strategy, customer/retention, eng-delivery topics. (3) Decision log path `~/.claude/decision-log.md` is a third memory location (see domain finding 3). (4) References `references/routing-matrix.md` — confirm it covers all 14 roles too.
- Verify: routing matrix includes GC/CDO/CAIO/CCO/VPE rows; `grep "28 skills" SKILL.md` → no hits; decision-log path identical to decision-logger's canonical path.
### board-meeting
- **Verdict: OPTIMIZE**
- Issues: (1) Phase 1 activation table + Phase 2 ordering cover 9 roles. (2) Invoked as `/cs:board` here but `/cs:boardroom` in c-level-agents — two names, one protocol. (3) Memory paths must match the canonical decision-memory layout chosen in domain finding 3.
- Verify: one command name used in both files (`grep -r "cs:board\b" c-level-advisor/` returns 0 or all-consistent); activation table lists 14 roles; memory paths match decision-logger.
### board-deck-builder
- **Verdict: OPTIMIZE**
- Issues: (1) `/board-deck [quarterly|monthly|fundraising]` doesn't exist as a command anywhere. (2) No CISO/GC/data sections cross-referenced to the 5 newer roles where relevant (minor). Content itself (4-act structure, bad-news framework, asks slide) is genuinely good.
- Verify: Quick Start either points at an existing command file or is rephrased as a trigger sentence; `references/deck-frameworks.md` + `templates/board-deck-template.md` exist (they do — keep green).
### competitive-intel
- **Verdict: OPTIMIZE**
- Issues: (1) Five phantom `/ci:*` commands as the entire Quick Start. (2) No script despite tabular scoring (threat matrix, feature-gap) being mechanizable — optional. Frameworks (8 tracking dimensions, win/loss interview protocol, over/under-tracking signals) are real.
- Verify: Quick Start contains no `/ci:` strings OR `commands/ci-*.md` files exist; battlecard template still referenced and present.
### cs-onboard
- **Verdict: OPTIMIZE**
- Issues: (1) Same output file as c-level-agents/onboard with a different schema (see domain finding 4). (2) `/cs:setup` + `/cs:update` names collide with the c-level-agents `/cs:` namespace without skill files behind them.
- Verify: exactly one interview skill owns `~/.claude/company-context.md`; context-engine "Required Context Fields" match the surviving schema; `grep -rl "company-context.md" c-level-advisor | xargs grep -l "project root"` → 0 hits.
### intl-expansion
- **Verdict: OPTIMIZE**
- Issues: (1) No script, no verification loop — ends at a checklist. (2) Market-selection scoring matrix is the mechanizable core; a 20-line stdlib scorer would lift this to KEEP. (3) Weakest A5 in the cross-cutting set: most rows ("research local buying behavior") a frontier model already knows.
- Verify: add `scripts/market_entry_scorer.py --sample` exits 0 emitting JSON with per-market weighted score; SKILL.md Quick Start invokes it; `references/regional-guide.md` retains region-specific regulatory facts (data residency, entity requirements) that aren't generic.
### ma-playbook
- **Verdict: OPTIMIZE**
- Issues: (1) Thinnest skill in domain (98 lines), pure checklist. (2) "2-15x ARR for SaaS" and "$1-3M per engineer" unsourced and freshness-fragile (A6). (3) No tool — a DD red-flag scanner or earnout-structure checker would be in-pattern with general-counsel-advisor. (4) Overlaps general-counsel-advisor (LOI/negotiation) and chief-data-officer-advisor (data diligence) without cross-references.
- Verify: multiples carry a source + as-of date; Adjacent Skills section cross-links gc-advisor + cdo-advisor; either a script exists passing `--help`, or the skill explicitly delegates quantitative work to cfo-advisor tools.
### executive-mentor/hard-call, postmortem, stress-test (3 skills)
- **Verdict: OPTIMIZE** (each)
- Issues: descriptions are literal placeholders (`"/em -hard-call — Framework for Decisions With No Good Options"`) — no trigger phrasing, malformed command name (`/em -hard-call` vs `/em:hard-call`). Bodies are excellent (10/10/10, Grove test, proper 5-Whys, change-register-with-verification-date); only the frontmatter fails.
- Verify: `python3 scripts/audit_skills.py` (repo validator) no longer flags these three for missing trigger; each description ≥ 1 "Use when" clause and < 1024 chars.
### c-level-agents (overview skill)
- **Verdict: OPTIMIZE**
- Issues: (1) Frontmatter `agents:` lists 8 (13 exist), `commands:` lists 17 (21 exist) — a new-gen router using this metadata will never surface vpe/cdo/caio/cco surfaces. (2) References block links `../../references/persona-voices.md` and `../references/persona-voices.md` inconsistently (one resolves, one doesn't).
- Verify: frontmatter agent/command lists match `ls agents/ | wc -l` = 13 and `ls skills/ | wc -l` − 1 = 21; all relative links resolve from the file's own directory.
### founder-mode
- **Verdict: OPTIMIZE**
- Issues: (1) Routing table has no signal rows for retention/CS (CCO), data architecture/training data (CDO), model selection/AI risk (CAIO), DORA/eng hiring (VPE) — the self-described "killer command" silently misroutes 4 domains to the wrong advisor. (2) Claims routing knowledge of decisions via decision-logger — path depends on domain finding 3.
- Verify: table includes the 4 missing roles with ≥ 4 keywords each; example "`the win rate dropped`" vs "`gross retention dropped`" route to CRO vs CCO respectively.
### onboard (c-level-agents)
- **Verdict: OPTIMIZE** — see domain finding 4. Verify: one canonical schema; symlink guidance (llm-wiki bridge) unchanged.
### brief
- **Verdict: OPTIMIZE**
- Issues: affected-roles checklist (drives boardroom panel composition) omits cs-general-counsel/cdo/caio/cco/vpe — a pricing-with-data-licensing brief can't seat the right panel.
- Verify: checklist lists all 14 advisors; `grep -c "cs-" skills/brief/SKILL.md` ≥ 14.
### decide
- **Verdict: OPTIMIZE**
- Issues: writes `~/.claude/decisions/{raw,approved}/` while decision-logger (the skill it claims to invoke) specifies `memory/board-meetings/`. The "two-layer memory" exists in two incompatible places.
- Verify: `grep -r "decisions/approved\|board-meetings/decisions" c-level-advisor/ -l` shows one canonical layout across decide, decision-logger, chief-of-staff, board-meeting.
### cdo-review, caio-review, cco-review, vpe-review (4 skills)
- **Verdict: OPTIMIZE** (each, same one-line fix)
- Issues: Routing sections send follow-ups to `/cs:chro-review` (and vpe-review also implies `/cs:coo-review`) — neither exists. Everything else is exemplary: role-specific forcing questions with thresholds, exact CLI to the backing skill's tools, structured output with verdict gates.
- Verify: every `/cs:*` string in the Routing sections resolves to a file under `c-level-agents/skills/*/SKILL.md`; `grep -r "cs:chro-review\|cs:coo-review" c-level-agents/` → 0 hits (or the two commands are created).
## KEEP-verdict verification criteria
- **ceo-advisor** — metrics dashboard targets present (burn multiple < 2x, NPS > 40); `python3 skills/ceo-advisor/scripts/strategy_analyzer.py` exits 0; boilerplate block replaced by agent-protocol pointer without losing the Tree-of-Thought section.
- **cfo-advisor** — all 3 scripts exit 0 bare; SKILL.md keeps burn-multiple/Rule-of-40/NDR thresholds table; "not a financial analyst skill" disambiguation to finance/ retained.
- **cto-advisor** — tech-debt priority formula `(Severity × Blast Radius) / Cost-to-fix` intact; both scripts exit 0; ADR template with 3-year-TCO checklist retained.
- **coo-advisor** — process-maturity 5-level table + both scripts green; VPE-vs-COO scope note added when role registry is fixed (advisory).
- **cpo-advisor** — D30 retention thresholds (20% consumer / 40% B2B) + invest/maintain/kill table intact; `pmf_scorer.py` exits 0.
- **cmo-advisor** — channel-level CAC discipline + pipeline-coverage 3–4x targets intact; both scripts green.
- **cro-advisor** — Magic Number + CAC-payback formulas verbatim; NRR benchmark table intact; both scripts green.
- **ciso-advisor** — `ALE = SLE × ARO` formula + compliance sequencing (SOC2 T1 → T2 → ISO/HIPAA) intact; both scripts green.
- **chro-advisor** — calibrated rating distribution table + compa-ratio 0.95–1.05 target intact; both scripts green.
- **chief-data-officer-advisor** (dual) — `ai_training_data_audit.py` bare-run exits 0 with GO/MITIGATE/NO-GO verdicts; both copies stay byte-identical (`diff -rq` clean); GDPR Art. 6 citations present in references.
- **chief-ai-officer-advisor** (dual) — 3 scripts exit 0; EU AI Act tier table retains Article citations; pricing figures carry an as-of date (A6 guard); copies identical.
- **chief-customer-officer-advisor** (dual) — `retention_decomposition_analyzer.py` flags leaky-bucket (NRR>100 ∧ GRR<85) on sample; GRR/NRR threshold table intact; copies identical.
- **general-counsel-advisor** (dual) — `contract_risk_scanner.py` bare-run flags ≥ 1 finding on bundled sample; "Not legal advice" disclaimer in SKILL.md + both tools; copies identical.
- **vpe-advisor** (dual) — `delivery_throughput_analyzer.py` emits DORA verdict + bottleneck (verified: exits 0, "Overall DORA level: High", bottleneck stage + % of cycle); fix workflow paths `../../skills/vpe-advisor/...` → `scripts/...`; copies identical.
- **context-engine** — 90-day staleness gate + anonymization never-send list intact; aligned to surviving onboarding schema.
- **decision-logger** — `python3 scripts/decision_tracker.py --demo` exits 0; DO_NOT_RESURFACE enforcement block intact; canonical path winner of domain finding 3.
- **scenario-war-room** — max-3-variables rule + cascade map + trigger-point examples intact; `scenario_modeler.py` exits 0; `/war-room` string removed or backed by a command.
- **org-health-diagnostic** — `health_scorer.py --json` emits machine-parseable dimension scores; 8-dimension thresholds + dimension-interaction table intact.
- **strategic-alignment** — `alignment_checker.py` detects orphans/conflicts/coverage-gaps on sample JSON; 5-people articulation test intact.
- **culture-architect** — values→behavioral-anchors table + culture-health score bands (80/65/50) intact.
- **company-os** — L10 agenda + IDS + rocks 3–7 cap intact; no phantom commands introduced.
- **founder-coach** — Skill×Will matrix + delegation ladder + calendar-audit target % table intact.
- **change-management** — ADKAR per-change-type timelines + resistance-pattern table intact.
- **internal-narrative** — audience translation matrix + contradiction check + 4-hour crisis rule intact.
- **executive-mentor / challenge / board-prep** — both scripts exit 0; challenge keeps assumption-confidence×impact matrix; board-prep keeps numbers-cold list.
- **office-hours / boardroom / execute / post-mortem / freeze / cross-eval** — pipeline artifact paths (`~/.claude/briefs|boardroom|execution|postmortems|freezes`) mutually consistent; each Routing section's `/cs:*` targets resolve; boardroom keeps Phase-2 isolation + dissent column; post-mortem keeps pre-committed-criteria scoring; freeze keeps default-period table.
- **cfo/cmo/cpo/cro/cto/ciso/gc-review** — every relative `python ../../../skills/...` path resolves from the file's directory; six questions per role remain role-specific (no copy-paste across roles); verdict gates (🟢/🟡/🔴) intact.
## Agents
| Agent | B1 (frontmatter) | B2 (differentiation) | B3 (body) | Top issue |
|---|---|---|---|---|
| cs-cfo-advisor | ⚠️ no "Use when" | PASS — burn-multiple/dilution forcing Qs, bear-case rule | PASS | model: opus justified? |
| cs-cmo-advisor | ⚠️ | PASS — one-sentence-positioning gate | **FAIL refs** — cites `growth_playbooks.md`, `marketing_operations.md` (don't exist; actual: growth_frameworks.md, marketing_org.md) | phantom KB files |
| cs-cro-advisor | ⚠️ | PASS — coverage>forecast, discount-creep tell | **FAIL refs** — all 3 KB names wrong (`revenue_operations/sales_motion/retention_expansion` vs actual sales_playbook/pricing_strategy/nrr_playbook) | phantom KB files |
| cs-cpo-advisor | ⚠️ | PASS — retention-curve-before-roadmap | **FAIL refs** — all 3 wrong (`product_vision/portfolio_strategy/pmf_framework` vs product_strategy/product_org_design/pmf_playbook) | phantom KB files |
| cs-coo-advisor | ⚠️ | PASS — DRI/cadence refusal gate | **FAIL refs** — all 3 wrong (`operating_cadence/okr_execution/scaling_playbooks` vs ops_cadence/process_frameworks/scaling_playbook) | phantom KB files |
| cs-chro-advisor | ⚠️ | PASS — no-promotion-without-ladder refusal | **FAIL refs** — all 3 wrong (`hiring_systems/comp_philosophy/leveling_ladders` vs people_strategy/comp_frameworks/org_design) | phantom KB files |
| cs-ciso-advisor | ⚠️ | PASS — assume-breach, $-quantified risk | **FAIL ref** — cites `threat_modeling.md` (doesn't exist; actual security_strategy.md) | phantom KB file |
| cs-chief-of-staff | ⚠️ | PASS — pure router, distinct job | **FAIL refs** — `routing_logic.md`/`synthesis_patterns.md` vs actual routing-matrix.md/synthesis-framework.md; routing table omits 5 roles | phantom KB files + role drift |
| cs-general-counsel-advisor | PASS (has disclaimer + scope) | PASS — escalate-to-counsel hard rule | PASS — exact tool wiring, correct paths | — |
| cs-cdo-advisor | PASS | PASS — "what decision does this data drive" refusal gate | PASS | — |
| cs-caio-advisor | PASS | PASS — no-eval-no-ship gate | PASS | — |
| cs-cco-advisor | PASS | PASS — gross-over-NRR, which-customer-would-you-fire | PASS | — |
| cs-vpe-advisor | PASS | PASS — explicit 4-way differentiation (CTO/eng-lead/CHRO/COO) | PASS | — |
| devils-advocate (executive-mentor) | no frontmatter at all (prose file) | PASS — exactly-3-concerns + never-clean-approval rules; behavior-changing | PASS — worked example | add YAML frontmatter |
**B2 assessment:** the personas genuinely pass the swap test. Each agent has different refusal gates (CFO: no scale on broken unit economics; CAIO: no eval set, no ship; CCO: no CS hire without a named customer outcome; CHRO: no promotion without ladder step), different tool wiring, and different success metrics — swapping cs-cfo-advisor's prompt into cs-cmo-advisor would be noticed immediately. The voice bookending ("opening/forcing/closing") is thin but the underlying workflows differ structurally.
**The systemic agent defect is B-side tool wiring, not differentiation:** 7 of 13 agents (the v2.5.0 batch: cfo is clean; cmo, cro, cpo, coo, chro, ciso, chief-of-staff are not) cite knowledge-base filenames that don't exist on disk. The 5 newer agents (gc, cdo, caio, cco, vpe — written against real files) are clean. Fix: one PR correcting ~16 filenames; verify with a link-checker pass (`for f in agents/*.md; do grep -o '\.\./\.\./skills/[a-z-]*/references/[a-z_-]*\.md' $f | while read p; do test -f "$(dirname $f)/$p" || echo "$f → $p"; done; done` → empty).
Also: `cs-ceo-advisor` and `cs-cto-advisor` live in `/agents/c-level/` outside this folder while 11 sibling links point at them via `../../../../agents/c-level/` — fragile but currently resolving.
## Plugin manifests
8 manifests, all schema-valid, all version 2.9.0 and consistent with marketplace.json (E1/E3 PASS). E2 findings:
| Plugin | Drift |
|---|---|
| c-level-skills (root) | Description says "33 skills + 13 agents + 21 commands" — accurate. But `"skills": ["./skills"]` only ships the bundle dir; the c-level-agents layer named in the description is NOT included in this plugin's skills path (it's a separate plugin) — description overpromises the install. |
| c-level-agents | Accurate (13 agents / 21 commands) — but the bundled overview SKILL.md frontmatter still says 8/17 (see per-skill). Manifest is ahead of its own skill. |
| executive-mentor | Accurate. CLAUDE.md claims it is "the only skill with a plugin.json (namespace: em)" — false since v2.5.x; 7 other plugin.json files exist in the domain. CLAUDE.md statement is the drift, not the manifest. |
| chief-ai-officer-advisor | Accurate, rich. "2026 pricing" claim is a freshness liability shared with the skill (A6). |
| chief-customer-officer-advisor / chief-data-officer-advisor / general-counsel-advisor / vpe-advisor | Accurate; descriptions correctly state "Standalone-installable; also bundled in c-level-skills" — the only place the dual-publication is documented. Mirror this sentence into the SKILL.md of each pair so editors learn about the twin copy. |
Scripts: all 25 bundle scripts pass repo-wide smoke tests (D1); spot-runs of `delivery_throughput_analyzer.py` (DORA verdict + bottleneck %), `decision_tracker.py --demo`, and `health_scorer.py --json` confirm deterministic, sample-embedded, machine-parseable output (D2/D3 PASS).

219
audit/newgen-2026-06/compliance.md Normal file
View file

@ -0,0 +1,219 @@
# Domain audit: ra-qm-team/ + compliance-os/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 26 distinct (17 ra-qm-team incl. meta + 9 compliance-os; +2 verbatim sub-plugin duplicates) · Agents: 9 (8 compliance-os + cs-quality-regulatory) · Commands: 0 standalone (8 compliance-os skills are /cs:* command-shaped) · Plugins: 4 manifests (1 in marketplace)
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| ra-qm-team/capa-officer | OPTIMIZE | Cites 21 CFR 820.100 as current; removed by QMSR (eff. 2026-02-02) |
| ra-qm-team/eu-ai-act-specialist | OPTIMIZE | Embedded sample mis-teaches Art. 5(1)(f): tags RETAIL emotion recognition as prohibited (workplace/education only) |
| ra-qm-team/fda-consultant-specialist | REWRITE | Entire QSR section presents pre-QMSR 21 CFR 820 as current law; FY2024 user fees |
| ra-qm-team/gdpr-dsgvo-expert | OPTIMIZE | "30 days" deadlines (Art. 12(3) says one month + 2-month extension); WP29 framing; score-without-owner output |
| ra-qm-team/information-security-manager-iso27001 | OPTIMIZE | "Overall Compliance: 87%" auto-verdict example; thin clause citation; generic IR section |
| ra-qm-team/isms-audit-expert | KEEP | — |
| ra-qm-team/iso42001-specialist | KEEP | — (exemplary; template for the rest of the domain) |
| ra-qm-team/mdr-745-specialist | OPTIMIZE | PSUR table contradicts MDR Art. 86(1); IIb conformity-route table garbled; no Reg. 2023/607 transition note |
| ra-qm-team/qms-audit-expert | KEEP | — |
| ra-qm-team/quality-documentation-manager | OPTIMIZE | FDA table cites removed 820.40/.180/.181/.184/.186 as current |
| ra-qm-team/quality-manager-qmr | OPTIMIZE | Compliance matrix: "21 CFR 820 / QSR compliance" stale; "MPG/MPDG" half-stale |
| ra-qm-team/quality-manager-qms-iso13485 | OPTIMIZE | Record-retention table cites removed 820.30/.181/.184/.198 sections |
| ra-qm-team/ra-qm-skills (meta) | CUT-OR-MERGE | 66-line catalog with wrong paths and wrong skill count; adds no behavior |
| ra-qm-team/regulatory-affairs-head | OPTIMIZE | "~$22K (2024)" fee labeled current; QSR framing in pathway step 2 |
| ra-qm-team/risk-management-specialist | OPTIMIZE | ALARP w/ cost-benefit ("Proportionality") contradicts EU MDR "as far as possible" (EN ISO 14971:2019/A11:2021) |
| ra-qm-team/soc2-compliance | KEEP | — |
| ra-qm-team/compliance-team-eu-ai-act/* (dup) | CUT-OR-MERGE | Byte-identical copy of skills/eu-ai-act-specialist; drift risk |
| ra-qm-team/compliance-team-iso42001/* (dup) | CUT-OR-MERGE | Byte-identical copy of skills/iso42001-specialist; drift risk |
| compliance-os/compliance-os | KEEP | — (plugin.json description drift noted under Plugins) |
| compliance-os/compliance-readiness | KEEP | — |
| compliance-os/aims-audit | KEEP | — |
| compliance-os/ai-act-readiness | KEEP | — (phasing dates 2025-02-02/2025-08-02/2026-08-02/2027-08-02 correct) |
| compliance-os/gdpr-audit-prep | KEEP | — |
| compliance-os/iso27001-audit-prep | KEEP | — (typo: "Article 9.3" should be "Clause 9.3") |
| compliance-os/iso13485-audit-prep | KEEP | — |
| compliance-os/soc2-audit-prep | KEEP | — |
| compliance-os/fda-qsr-audit-prep | OPTIMIZE | Acknowledges QMSR yet cites removed 820.75/.100/.180/.198/.250 as live citations |
**Counts:** KEEP 13 · OPTIMIZE 11 · REWRITE 1 · CUT-OR-MERGE 1 (+2 duplicate copies)
## Domain-level findings
**1. The domain is two generations in one tree.** The 2026-05 wave (eu-ai-act-specialist, iso42001-specialist, all of compliance-os) is the best compliance work in the repo: Article/Clause-cited verdicts, explicit NOT-boundaries, deterministic tools with embedded samples, "Your Decision: [the call only the compliance officer can make]" output blocks, outside-counsel routing. The legacy 2025-era wave (the other 14 ra-qm-team skills) is competent practitioner content but pre-dates the citation-discipline pattern and has not been re-baselined against 2026 regulatory state.
**2. FDA QMSR is the single largest freshness failure (REWRITE/OPTIMIZE driver for 6 skills).** The FDA Quality Management System Regulation (final rule 89 FR 7496) replaced the QSR effective 2026-02-02 — four months before this audit. It incorporates ISO 13485:2016 by reference and REMOVES the subsection structure the legacy skills cite as current: 820.20/.30/.40/.50/.70/.75/.100/.180/.181/.184/.186/.198 no longer exist (retained/renumbered: 820.10 requirements, 820.35 records, 820.45 labeling+packaging; 21 CFR 801/803/806/830 unchanged). `fda-consultant-specialist` (skill + qsr_compliance_requirements.md reference + qsr_compliance_checker.py `--section 820.30` interface) has ZERO mentions of QMSR. Ironically, the compliance-os agent `cs-fda-qsr-auditor` and `fda-qsr-audit-prep` correctly state "substantially harmonized post-Feb 2026" — the fresh layer knows what the underlying skill it wraps does not.
**3. Citation precision: good-to-excellent in the new wave, mixed in legacy.** New-wave outputs cite Article+paragraph by contract ("do not paraphrase without cite"). Legacy skills cite at clause level (ISO 13485 4.2.3, 7.5.6, 8.5.2; GDPR Art. 6/9/35; MDR Annex II/VIII/XIV; MDCG 2019-11) — adequate — but carry concrete precision errors a notified-body auditor would flag: (a) mdr-745-specialist PSUR table says Class IIb "every 2 years" / IIa "when necessary" — MDR Art. 86(1) requires IIb+III at least annually and IIa at least every two years; (b) risk-management-specialist's ALARP framework includes "Cost-benefit of further reduction", which EU MDR Annex I §2 + the EN ISO 14971:2019/A11:2021 Z-annexes explicitly disallow (risk reduction "as far as possible" without economic consideration); (c) the eu-ai-act-specialist embedded sample tags a retail-store CCTV emotion-recognition system with `article_5_practice: emotion_recognition_in_workplace_or_education` — retail emotion recognition is Art. 50(3) transparency, not Art. 5 prohibited; the default `--sample` run teaches the wrong rule.
**4. Auto-decide vs route-to-human: NO skill auto-decides compliance verdicts; discipline is explicit in the new wave, implicit in legacy.** Every compliance-os and 2026-wave skill ends with a named-human handoff ("Your Decision: … compliance officer or legal counsel", "Outside Counsel Required" sections, cs-dpo-gdpr hard rule routing novel cases to GC). Legacy skills embed human signoff in workflows (CAPA approval signatures, "Classification confirmed with Notified Body", CER "reviewed by qualified evaluator") but lack an explicit handoff block, and two tool-output examples drift toward verdict-shaped numbers without an owner: information-security-manager's "Overall Compliance: 87%" and gdpr_compliance_checker's "Compliance score (0-100)". Not REWRITE-level — they are framed as prep/self-check tools — but every OPTIMIZE pass should add the new-wave "Your Decision" block.
**5. The "49 no-source references" repo flag is ~80% false positive in this domain.** 63 reference files in scope (55 distinct after sub-plugin dedup). Only ~8 have a formal "Sources" heading — which is what the repo validator keys on — but ~45 carry dense inline regulatory citations (Article/Clause/§/CFR/Annex markers; the AI Act and 13485 playbooks run 37–94 citation markers per file). Genuine zero-citation gaps ≈ 9 files, all generic-methodology docs: capa-officer/rca-methodologies.md + effectiveness-verification-guide.md, risk-management-specialist/risk-analysis-methods.md + risk-assessment-templates.md (77 lines, thin), quality-manager-qmr/quality-kpi-framework.md, information-security-manager-iso27001/incident-response.md, soc2-compliance/type1_vs_type2.md + evidence_collection_guide.md, qms-audit-expert/nonconformity-classification.md (1 marker). Fix: add a Sources block to those 9; do not bulk-rewrite the other 45.
**6. New-gen model lens.** Frontier models know ISO/GDPR/MDR basics; what earns context here is exactly what the new wave ships: clause-keyed gap analyzers with readiness verdicts, mock-audit scenario libraries (205 scenarios), evidence-reuse maps with confidence ratings, audit-prep interrogations with sample-driven "show me the record" questions. Legacy skills that mostly restate standard structure (info-sec manager's ISMS-implementation prose, parts of quality-manager-qmr) are the weakest A2 performers; their tools and checklists still earn their place.
**7. Cross-plugin coupling.** compliance-os skills invoke `../../../ra-qm-team/skills/*/scripts/*.py` by relative path. Works in the monorepo; breaks when plugins install independently (compliance-os plugin does not ship those scripts). Violates the repo "skills are self-contained" principle — at minimum document the ra-qm-skills co-install requirement in the manifest.
**8. Cruft.** 12 legacy `.zip` archives + `final-complete-skills-collection.md` committed at ra-qm-team/ root; ra-qm-team/CLAUDE.md says "14/14 skills" (folder has 16 + meta; omits eu-ai-act + iso42001 entirely, so the domain's own nav file hides its two best skills).
## Per-skill findings
### ra-qm-team/fda-consultant-specialist — REWRITE
Issues:
1. QSR section ("Quality System Regulation (21 CFR Part 820)") + subsystem table (820.20–820.181) presented as current; QMSR replaced this structure effective 2026-02-02 — wrong regulatory guidance in the highest-stakes lane.
2. `references/qsr_compliance_requirements.md` (753 lines) and `qsr_compliance_checker.py --section 820.30` interface built entirely on removed section numbers; zero QMSR mentions anywhere in the skill.
3. Fee table is FY2024 ($21,760 510(k) / $134,676 De Novo / $425,000+ PMA) with no fiscal-year label or MDUFA pointer.
4. Description still sells "QSR (21 CFR 820) compliance" — trigger text itself stale.
5. Pathway/eSTAR/cybersecurity/HIPAA content remains sound — structure salvageable, QSR third needs rebuild around ISO 13485-by-reference + retained 820.10/.35/.45 + unchanged 801/803/806/830.
Verify:
- `grep -ri QMSR ra-qm-team/skills/fda-consultant-specialist/ | wc -l` ≥ 5 (SKILL.md, description, qsr reference, checker help).
- `grep -rE '820\.(20|30|40|50|70|100|181|198)' SKILL.md references/` returns only lines explicitly marked historical/pre-2026.
- `python3 scripts/qsr_compliance_checker.py --help` exits 0 and help text names QMSR/ISO 13485, not "21 CFR 820 compliance" alone.
- Fee table rows carry an explicit FY label and "verify at fda.gov MDUFA" note.
### ra-qm-team/ra-qm-skills — CUT-OR-MERGE
Issues:
1. 66-line catalog page; duplicates README/plugin.json function; no workflow, no tools, no verification — fails A2/A4.
2. Says "12 skills" while the folder ships 16 and plugin.json says 14 — three conflicting counts.
3. Quick-start path `ra-qm-team/regulatory-affairs-head/SKILL.md` is wrong (missing `skills/` segment).
4. Omits eu-ai-act-specialist, iso42001-specialist, soc2-compliance from its table.
Verify:
- Folder removed (catalog content merged into ra-qm-team/README.md), OR rewritten as a real router; if kept: skill count matches `ls ra-qm-team/skills | wc -l` minus itself, and every path in the table resolves (`test -f` loop exits 0).
### ra-qm-team/risk-management-specialist — OPTIMIZE
Issues:
1. ALARP used as the acceptability framework incl. "Proportionality | Cost-benefit of further reduction" — EU MDR Annex I §2 + EN ISO 14971:2019/A11:2021 Z-annexes prohibit economic considerations; for CE-marked devices the criterion is "as far as possible" (AFAP). A notified body flags this exact table.
2. ISO 14971:2019 itself dropped ALARP from the normative body; skill presents it as the standard's method.
3. `references/risk-analysis-methods.md` + `risk-assessment-templates.md` (77 lines) cite zero sources.
4. No explicit named-human handoff for residual-risk acceptance (it's implied via "management signoff" only in iso42001-specialist, not here).
Verify:
- `grep -c 'as far as possible\|AFAP' SKILL.md` ≥ 2 and ALARP appears only with an explicit "non-EU / not acceptable under MDR" caveat.
- `grep -c 'Cost-benefit' SKILL.md` = 0 in the EU acceptability context.
- `python3 scripts/risk_matrix_calculator.py -p 4 -s 5 --output json` exits 0, emits `risk_level` key.
### ra-qm-team/mdr-745-specialist — OPTIMIZE
Issues:
1. PSUR table wrong vs MDR Art. 86(1): says IIb "Every 2 years", IIa "When necessary" — regulation requires IIb (all, not just implantable) at least annually, IIa at least every 2 years.
2. Conformity-route row "IIb | Annex IX + X or X + XI" garbled (routes are Annex IX, or Annex X+XI).
3. No mention of Reg. (EU) 2023/607 extended transition (legacy MDD devices to 2027/2028) — the question every MDR client asks first in 2026.
4. PMS table cites "PMS Plan | Article 84" correctly but omits Art. 83 (system) and Art. 86 (PSUR) cites where the schedule lives.
Verify:
- PSUR table matches Art. 86(1) verbatim cadence (`grep -A4 'PSUR Schedule' SKILL.md` shows IIb=annual, IIa=every 2 years).
- `grep -c '2023/607' SKILL.md references/` ≥ 1.
- `python3 scripts/mdr_gap_analyzer.py --device Test --class IIa --output json` exits 0 with gap list.
### ra-qm-team/eu-ai-act-specialist — OPTIMIZE
Issues:
1. Embedded sample system "Emotion recognition in retail store CCTV" is hard-tagged `article_5_practice: emotion_recognition_in_workplace_or_education` → default `--sample` output declares retail emotion recognition PROHIBITED. Correct treatment: Art. 50(3) transparency (limited-risk). Wrong teaching in the default demo of a flagship skill.
2. Classifier trusts caller-supplied `article_5_practice` flags rather than deriving from context fields it already collects (`users`, `intended_purpose`) — at minimum the docstring should state the flag is the user's legal pre-determination.
3. Verbatim duplicate at compliance-team-eu-ai-act/ (see Plugins).
Verify:
- `python3 scripts/ai_system_risk_classifier.py` sample output classifies the retail-CCTV system as LIMITED-RISK citing Art. 50(3), or the sample is changed to a genuine workplace context.
- All 3 scripts exit 0 on `--help` and bare run; every verdict line contains "Article".
### ra-qm-team/gdpr-dsgvo-expert — OPTIMIZE
Issues:
1. Rights table + body say "30 days" / "extendable to 90" — Art. 12(3) is one month, extendable by two further months; in a deadline-tracking tool the month/30-day distinction loses up to 3 days.
2. "WP29 high-risk criteria" — EDPB-endorsed but should be cited as EDPB/WP248 rev.01.
3. Compliance checker emits 0-100 score with no named-DPO routing block; SKILL.md has no "Your Decision" handoff (contrast gdpr-audit-prep which does this right).
4. No mention of EU-US Data Privacy Framework / Chapter V transfer tooling in SKILL.md (playbook reference covers it; surface a pointer).
Verify:
- `grep -c 'one month' SKILL.md` ≥ 1; `grep -c '30 days' SKILL.md` = 0 in the Art. 12 deadline context.
- `python3 scripts/data_subject_rights_tracker.py add --type access --subject T --email t@x.de` then `list` exits 0; due-date computed by calendar month.
- SKILL.md gains an output block routing final determinations to DPO/counsel.
### ra-qm-team/information-security-manager-iso27001 — OPTIMIZE
Issues:
1. Worked example ends "Overall Compliance: 87%" with no owner/handoff — the closest thing to an auto-verdict in the domain.
2. Body is clause-thin (only 6.1.2 cited); 2022 control IDs appear only in the example; A5 weak for a new-gen model (ISMS-implementation prose a frontier model already knows).
3. `references/incident-response.md` (420 lines) cites zero sources and duplicates engineering-team incident-response ground.
4. CLI surface in SKILL.md (`--template healthcare`, `--domains`) must be verified against actual argparse (legacy doc drift risk).
Verify:
- Every documented flag exists: `python3 scripts/risk_assessment.py --help` and `compliance_checker.py --help` list `--scope/--template/--standard/--gap-analysis`.
- Worked example ends with a named-human review step (ISMS owner / CISO) instead of bare percentage.
- incident-response.md gains a Sources block (≥3: ISO 27035, NIST SP 800-61r3, A.5.24-26) or is cut in favor of a pointer.
### ra-qm-team/capa-officer — OPTIMIZE
Issues:
1. "FDA 21 CFR 820.100" requirements section presents removed regulation as current (QMSR: CAPA now flows through ISO 13485 8.5.2/8.5.3 incorporated by reference).
2. `references/rca-methodologies.md` + `effectiveness-verification-guide.md` (917 lines combined) cite zero sources.
3. Otherwise the strongest legacy skill (decision trees, validated 5-Why example, metrics with formulas) — targeted edits only.
Verify:
- 820.100 section reframed as "pre-2026 QSR / now via ISO 13485 8.5 under QMSR" (`grep -c QMSR SKILL.md` ≥ 1).
- `python3 scripts/capa_tracker.py --sample > /tmp/c.json && python3 scripts/capa_tracker.py --capas /tmp/c.json --output json` exits 0 with summary metrics keys.
### ra-qm-team/quality-documentation-manager — OPTIMIZE
Issues:
1. "FDA 21 CFR 820" table (820.40/.180/.181/.184/.186) presents removed sections as current; under QMSR records requirements live in 820.35 + ISO 13485 4.2.4/4.2.5.
2. Part 11 content is solid and unaffected — single-table fix plus reference sweep of 21cfr11-compliance-guide.md for cross-refs into old 820.
Verify:
- FDA table updated to QMSR structure; `grep -E '820\.(40|181|184|186)' SKILL.md` only in historical context.
- `python3 scripts/document_validator.py --sample > /tmp/d.json && python3 scripts/document_validator.py --doc /tmp/d.json --output json` exits 0.
### ra-qm-team/quality-manager-qms-iso13485 — OPTIMIZE
Issues:
1. Record-retention table regulatory basis column cites removed 820.181/.184/.30/.198.
2. Otherwise strong (exclusion table, validation standards ISO 11135/11137/17665, supplier scoring) — single-table fix.
Verify:
- Retention table bases updated to QMSR/ISO 13485 cites.
- `python3 scripts/qms_audit_checklist.py --clause 7.3` exits 0 and emits 7.3-specific questions.
### ra-qm-team/quality-manager-qmr — OPTIMIZE
Issues:
1. Multi-jurisdiction matrix: "USA | 21 CFR 820 | FDA registration, QSR compliance" stale post-QMSR; "Germany | MPG/MPDG" — MPG repealed 2021, list MPDG/MPEUAnpG only.
2. Generic culture-survey and KPI content is the domain's weakest A2 (frontier model knows it); KPI reference cites zero sources.
Verify:
- Matrix row reads QMSR; `grep -c 'MPG/' SKILL.md` = 0.
- `python3 scripts/management_review_tracker.py --help` exits 0.
### ra-qm-team/regulatory-affairs-head — OPTIMIZE
Issues:
1. Pathway matrix fees "~$22K (2024)" — stale FY presented as current; needs FY label + MDUFA pointer.
2. Step 2 lists "FDA (US): 21 CFR Part 820" as applicable regulation without QMSR framing.
3. Overlap with mdr-745-specialist + fda-consultant-specialist is acceptable (strategy vs execution split) but should cross-link rather than restate the SE table.
Verify:
- Fee cells carry FY labels; `grep -c QMSR SKILL.md` ≥ 1.
- `python3 scripts/regulatory_tracker.py --help` exits 0.
### compliance-os/fda-qsr-audit-prep — OPTIMIZE
Issues:
1. Correctly states post-Feb-2026 harmonization, then cites removed sections as live law throughout (820.198, 820.75, 820.100, 820.180, 820.250) — internally inconsistent; the right cites are ISO 13485 clauses (8.2.2, 7.5.6, 8.5.2, 4.2.5) + retained 820.35/.45 + unchanged 803/801/830/806.
2. Workflow shells into fda-consultant-specialist scripts whose interfaces are themselves pre-QMSR (`--section 820.30`) — blocked on the REWRITE above.
Verify:
- Each of the six questions cites the QMSR-era source (ISO 13485 clause or retained CFR section); `grep -E '820\.(75|100|180|198|250)' SKILL.md` only with "pre-QMSR" annotation.
- Workflow paths resolve after the fda-consultant-specialist rewrite.
### Duplicate sub-plugins (compliance-team-eu-ai-act/, compliance-team-iso42001/) — CUT-OR-MERGE
Issues:
1. `diff -r` confirms byte-identical copies of ra-qm-team/skills/{eu-ai-act,iso42001}-specialist — two sources of truth; the Art. 5 sample bug must now be fixed twice.
2. Neither sub-plugin is registered in marketplace.json, so the duplication currently buys nothing.
Verify:
- Either sub-plugins deleted (standalone install served by marketplace entry pointing at the skills/ copy), or a sync script/CI check asserts `diff -r` emptiness on every PR.
## KEEP-verdict verification criteria
- **iso42001-specialist:** `python3 scripts/aims_gap_analyzer.py` exits 0, prints `Certification readiness:` ∈ {ready, stage_2_candidate, not_ready} + weighted coverage %; all 3 tools pass bare run; every gap line carries a Clause number.
- **isms-audit-expert:** `python3 scripts/isms_audit_scheduler.py --year 2026 --format markdown` exits 0 and emits a quarter-bucketed plan; finding template retains Requirement/Evidence/Gap triple.
- **qms-audit-expert:** `python3 scripts/audit_schedule_optimizer.py --interactive` help path exits 0; clause-scope table keeps 4.2→8.5 coverage; classification decision tree intact.
- **soc2-compliance:** `python3 scripts/control_matrix_builder.py --categories security --format json` exits 0 with ≥1 control per CC1–CC9; gap_analyzer distinguishes type1/type2 modes.
- **compliance-os (orchestrator):** all 4 tools exit 0 on bare run; `audit_simulator.py` output reports `healthy=` against the ≥40% observation / ≤15% critical rule; `assets/mock_audit_library.json` parses with 205 scenarios.
- **compliance-readiness:** output template retains the 🟢/🟡/🔴 verdict + "Top 3 Actions with owners" + routing block; all 4 workflow script paths resolve from the skill dir.
- **aims-audit:** 6 questions each name a Clause or Annex A control; workflow paths into ra-qm-team resolve; routes verdict to `/cs:decide`.
- **ai-act-readiness:** phasing dates remain exactly 2025-02-02 / 2025-08-02 / 2026-08-02 / 2027-08-02; "Legal Review Required" section retained; every question keeps its Article cite.
- **gdpr-audit-prep:** Art. 12(3) one-month language retained; Art. 30/35(7)/33(5) cites intact; "Outside Counsel Required" section retained.
- **iso27001-audit-prep:** fix "Article 9.3"→"Clause 9.3"; 3-year-coverage question + auditor-independence check retained; scheduler path resolves.
- **iso13485-audit-prep:** Clause cites (8.2.4, 7.5.6, 5.6.2/5.6.3) intact; DHF-sampling question retains stratification by class.
- **soc2-audit-prep:** observation-period discipline questions (cycle skips, first-month evidence, exception materiality) retained; AT-C 205 cite intact.
## Agents
All 9 pass B1–B3. The 8 compliance-os personas are the best-differentiated agent set audited: each has a distinct voice that changes behavior (cs-ciso-iso27001 "samples, not demos"; cs-dpo-gdpr refuses to paraphrase the Regulation; cs-fda-qsr-auditor tracks Form 483 gradient distinct from ISO NC grades), explicit vs-sibling differentiation paragraphs, and hard rules that route novel/legal calls to GC or outside counsel — the route-to-human discipline the legacy skills lack lives here. cs-fda-qsr-auditor is also the only artifact in either domain that correctly states the QMSR transition.
Issues: (1) cs-fda-qsr-auditor still cites removed 820.x section numbers in its forcing questions — inherits the fda-qsr-audit-prep fix. (2) All 8 pin `model: opus` — pre-Fable-era pin; revisit per repo model policy. (3) `skills:` frontmatter uses repo-relative paths (`ra-qm-team/skills/...`) that break outside the monorepo. (4) cs-quality-regulatory (agents/ra-qm-team/) is generic by comparison (sonnet, catalog-style body, no voice/forcing questions, no QMSR awareness) — OPTIMIZE to the compliance-os persona pattern, and its skill paths omit the `skills/` segment.
## Plugin manifests
| Manifest | E1 schema | E2 description | E3 marketplace |
|---|---|---|---|
| ra-qm-team/.claude-plugin/plugin.json | PASS (`"skills": ["./skills"]`) | DRIFT — "14 skills"; folder ships 16 + meta (eu-ai-act + iso42001 + soc2 uncounted) | Registered (v2.9.0) |
| compliance-os/.claude-plugin/plugin.json | PASS (9 explicit paths) | DRIFT — claims "9 supported frameworks" + "3 cs-* agents + 3 commands"; SKILL.md/tools support 12 frameworks, 8 agents, 8 command-skills ship | **NOT in marketplace.json** (66 plugins, none sourced from ./compliance-os) |
| ra-qm-team/compliance-team-eu-ai-act/plugin.json | PASS | OK | **NOT in marketplace.json** |
| ra-qm-team/compliance-team-iso42001/plugin.json | PASS | OK | **NOT in marketplace.json** |
Findings: (1) Three of four manifests are orphans — built as plugins, never registered; either register them or delete the sub-plugin duplicates and fold compliance-os registration into the next marketplace bump. (2) compliance-os skills depend at runtime on ra-qm-team scripts via `../../../` paths — manifest must declare the co-install requirement or vendor the scripts. (3) ra-qm-team ships 12 stale `.zip` skill archives + `final-complete-skills-collection.md` at domain root — remove from the public tree. (4) ra-qm-team/CLAUDE.md ("14/14 skills", omits the domain's two flagship 2026 skills) and root CLAUDE.md ("18 RA/QM skills") disagree with each other and with the folder; reconcile counts in one pass.

179
audit/newgen-2026-06/cross-cutting.md Normal file
View file

@ -0,0 +1,179 @@
# Cross-cutting audit: root agents, commands, standards, templates, marketplace, CI — new-gen model optimization
Audited: 2026-06-10
Scope: root `agents/` (32), root `commands/` (39), `standards/`, `templates/`, `orchestration/`, `custom-gpt/`, `assets/`, `.claude-plugin/marketplace.json`, `scripts/`, `.github/workflows/`, root README.md + CLAUDE.md. Rubric dimensions B/C/D/E.
---
## Counter-drift reconciliation table
Measured today (canonical tree, excluding `.codex/.gemini/.hermes/.vibe` sync copies and `docs/`):
| Metric | **Actual (measured)** | README.md | CLAUDE.md header (L9) | CLAUDE.md v2.10.3 block | CLAUDE.md footer (L515) | marketplace.json metadata | agents/CLAUDE.md |
|---|---|---|---|---|---|---|---|
| Skills (SKILL.md) | **346** (`audit_skills.py` count) / 347 (`find`) | 338 | 338 | 343 | 338 | 343 | "42 production skills" AND "177 existing skills" (same page) |
| Marketplace plugins | **66 entries** in marketplace.json; **77 plugin.json manifests** on disk (78 incl. `.codex-plugin` sync artifact) | — | 62 | 64 | 62 | **claims 64 — its own `plugins` array has 66** | — |
| Python tools (in-skill `scripts/*.py`) | **555** | 533 | 533 | 548 | — | 548 | — |
| Reference docs (`references/*.md`) | **700** | 676 | 676 | 691 | — | 691 | — |
| Agents (repo-wide / root) | **92 / 32** | 51+ | 51+ ("32 standalone") | — | — | 51+ | "16 Agents Currently Available" (table actually lists 19; folder has 32) |
| Slash commands (repo-wide / root) | **99 / 39** | 87+ | 87+ | 90+ | — | 90+ | — |
| Domains | **17** top-level skill domains | 16 | 16 | 17 | 16 | 17 | — |
| Version | — | — | — | v2.10.3 | **v2.9.0** | v2.10.3 | — |
Key drift facts:
1. **marketplace.json is internally inconsistent**: `metadata.description` and `description` both say "64 marketplace plugins" while the `plugins` array contains **66** entries (v2.10.x additions `universal-scraping-architect` and `youtube-full` were appended without bumping the counter).
2. **11 plugin.json manifests exist on disk but are NOT registered in marketplace.json** (invisible to marketplace installs):
`compliance-os/`, `engineering-team/snowflake-development/`, `engineering/behuman/`, `engineering/claude-coach/`, `engineering/grill-with-docs/`, `engineering/llm-cost-optimizer/`, `engineering/prompt-governance/`, `finance/business-investment-advisor/`, `marketing-skill/video-content-strategist/`, `ra-qm-team/compliance-team-eu-ai-act/`, `ra-qm-team/compliance-team-iso42001/`. (Plus `.codex-plugin/plugin.json`, a sync artifact.) Notably, `compliance-os` is *named as a domain* in the marketplace description yet has no marketplace entry.
3. **CLAUDE.md disagrees with itself in three places** (header 338/62/16, v2.10.3 block 343/64/17, footer v2.9.0/338/62/16). README still carries the pre-v2.10 numbers everywhere, including the shields badge (`Skills-338`).
4. Even the freshest claimed numbers (343/64/548/691) trail reality (346/66-77/555/700) — the counters were last trued up at v2.10.3 and have drifted again.
---
## Root agents
32 agents (25 `cs-*` + 7 personas). **17 of 32 (53%) lack trigger phrasing** ("Use when…" / "Spawn when…" / "Invoke via…") in `description` — B1 fail. All but 2 agents carry the identical generic `tools: [Read, Write, Bash, Grep, Glob]` list (B1 "minimal tools" not practiced). The personas use a non-standard frontmatter schema (`name` with spaces, `color`, `emoji`, `vibe` fields — not Claude Code agent fields).
| Agent | Verdict | Issue |
|---|---|---|
| engineering/cs-backend-engineer | KEEP | Exemplary: trigger + invocation path + `context: fork` + differentiated forcing questions |
| engineering/cs-frontend-engineer | KEEP | Same pattern; good |
| engineering/cs-fullstack-engineer | KEEP | Same pattern; good |
| engineering/cs-karpathy-reviewer | KEEP | Good trigger; near-duplicate of `engineering/karpathy-coder/agents/karpathy-reviewer.md` (differs, but two sources of truth) |
| engineering/cs-wiki-ingestor / -librarian / -linter (3) | KEEP | Good triggers; near-duplicates of `engineering/llm-wiki/agents/wiki-*.md` — pick one canonical home |
| engineering/cs-senior-engineer | OPTIMIZE | Trigger OK but scope ("architecture, code review, DevOps, API design") overlaps cs-engineering-lead + the 3 role engineers — B2 differentiation weak |
| engineering-team/cs-engineering-lead | OPTIMIZE | Trigger OK; differentiate from cs-senior-engineer or merge |
| engineering-team/cs-workspace-admin | KEEP | Specific, trigger present |
| marketing/cs-aeo | KEEP | Model trigger + voice + refusal rule |
| marketing/cs-webinar-marketer | KEEP | Model trigger + voice |
| marketing/cs-content-creator | OPTIMIZE | No trigger phrasing; description is a topic list |
| marketing/cs-demand-gen-specialist | OPTIMIZE | No trigger phrasing |
| c-level/cs-ceo-advisor | OPTIMIZE | No trigger; 360-line body is content-rich but description is a noun phrase |
| c-level/cs-cto-advisor | OPTIMIZE | No trigger |
| product/cs-product-manager | OPTIMIZE | No trigger; claims 8 skills incl. those owned by sibling agents (strategist, ux-researcher) — B2 overlap |
| product/cs-product-strategist | OPTIMIZE | No trigger; skill overlap with cs-product-manager |
| product/cs-agile-product-owner | OPTIMIZE | No trigger |
| product/cs-ux-researcher | OPTIMIZE | No trigger |
| product/cs-product-analyst | REWRITE | No trigger AND 31-line near-placeholder body (B3) — thinnest agent in the folder |
| project-management/cs-project-manager | OPTIMIZE | No trigger; 515-line body |
| business-growth/cs-growth-strategist | KEEP | "Spawn when…" present |
| finance/cs-financial-analyst | KEEP | "Spawn when…" present |
| ra-qm-team/cs-quality-regulatory | KEEP | "Spawn when…" present |
| personas/solo-founder | OPTIMIZE | No trigger; no `skills:` mapping; non-standard frontmatter |
| personas/startup-cto | OPTIMIZE | No trigger; overlaps cs-cto-advisor (B2 pair) |
| personas/growth-marketer | OPTIMIZE | No trigger; no `skills:`; overlaps cs-demand-gen-specialist |
| personas/content-strategist | OPTIMIZE | No trigger; overlaps cs-content-creator |
| personas/product-manager | OPTIMIZE | No trigger; overlaps cs-product-manager |
| personas/finance-lead | OPTIMIZE | No trigger; skills list (`ceo-advisor`, `cost-estimator`) is bare-name shorthand that doesn't resolve to paths; overlaps cs-financial-analyst |
| personas/devops-engineer | OPTIMIZE | No trigger; references `ms365-tenant-manager` / `aws-solution-architect` which exist only as **.zip archives** in engineering-team/ |
Cross-cutting agent issues:
- **`skills:` frontmatter shorthand is one directory level stale repo-wide**: e.g. `product-team/product-manager-toolkit` — actual path is `product-team/skills/product-manager-toolkit`. Every domain-prefixed `skills:` value resolves only via the `skills/` insertion.
- `templates/agent-template.md` is the root cause of the missing-trigger pattern: it mandates "One-line description… under 150 characters" with **no trigger-phrase requirement**, contradicting agents/CLAUDE.md's own current guidance and rubric B1.
---
## Root commands
39 commands. **34 of 39 never reference `$ARGUMENTS`** despite advertising `Usage: /cmd <args>` in descriptions (C2 weak; only focused-fix, tc, and the 4 cs-*-review/grill commands handle it). Only the 4 newest commands use `argument-hint`.
**Systemic C3 defect — phantom script paths: 28 of 39 commands contain ≥1 path that does not exist.** Root commands consistently reference `<domain>/<skill>/scripts/x.py`, but skills were reorganized into `<domain>/skills/<skill>/scripts/x.py` (and single-skill plugins into `<plugin>/skills/<name>/scripts/`). Every "Scripts" section pointing at e.g. `engineering/changelog-generator/...`, `finance/financial-analyst/...`, `product-team/product-manager-toolkit/...` is a dead path; the scripts exist one level deeper. A model following these commands hits file-not-found on first invocation.
| Command | Verdict | Issue |
|---|---|---|
| plugin-audit | KEEP | Real 8-phase orchestration; 4 stale paths to fix |
| seo-auditor | KEEP | Real pipeline; 8 stale paths |
| tc | KEEP | State machine + $ARGUMENTS dispatch; 6 stale paths |
| cs-aeo, cs-webinar | KEEP | Tool-wired workflows |
| cs-backend-review, cs-frontend-review, cs-fullstack-review, cs-engineer-grill | KEEP | argument-hint + agent fork + gates — the model pattern for the rest |
| a11y-audit | KEEP | Uses `{skill_path}` placeholder (resilient); fix Skill Reference path |
| code-to-prd | KEEP | `{skill_path}` placeholder pattern; 3 stale refs |
| chaos-experiment, slo-design, operator-audit, flag-cleanup | KEEP | Interactive wizards/gates; no stale paths detected |
| google-workspace | OPTIMIZE | Good content; 6 stale script paths |
| changelog, pipeline, okr, rice, persona, retro, user-story, saas-health, tech-debt, competitive-matrix, financial-health, project-health, sprint-health | OPTIMIZE | Script-wired (passes C3 in spirit) but **all script paths are phantoms** (missing `skills/` segment) |
| focused-fix | OPTIMIZE | Strong 5-phase protocol + $ARGUMENTS; "Related Skills" points to `engineering/focused-fix` (actual: `engineering/skills/focused-fix`) and to external `superpowers:systematic-debugging` (not in this repo). **Known-issue verified FALSE POSITIVE: the "TODO/FIXME" string is instructional content in the Phase 3 diagnostic checklist, not a real marker** — no actual TODO/FIXME/placeholder markers in commands/ or agents/ |
| karpathy-check | CUT-OR-MERGE (dedupe) | **Byte-identical** to `engineering/karpathy-coder/commands/karpathy-check.md`; also references bare `scripts/complexity_checker.py` which only resolves inside the plugin |
| wiki-ingest, wiki-init, wiki-lint, wiki-query, wiki-log (5) | CUT-OR-MERGE (dedupe) | **Byte-identical** to `engineering/llm-wiki/commands/wiki-*.md` — root copies are second sources of truth that will drift |
| prd | CUT-OR-MERGE | Bare-prompt restatement: 25 lines = output bullet list + skill pointer. A frontier model produces this without the command |
| sprint-plan | CUT-OR-MERGE | Same: 25 lines, no script, no gate, no $ARGUMENTS |
| tdd | CUT-OR-MERGE | References 4 scripts explicitly labeled "(library module)" — not CLI-invocable, so the command orchestrates nothing a bare prompt couldn't |
**Cut-or-merge candidates: 9** (6 byte-identical duplicates + prd + sprint-plan + tdd).
---
## standards/ + templates/ + orchestration/ + custom-gpt/ + assets/
**standards/** — NOT orphaned: referenced by `.github/workflows/skill-quality-review.yml`, `skill-security-audit.yml`, `commands/plugin-audit.md`, root CLAUDE.md, `.claude/commands/update-docs.md`. No stale model names or dead dates. Caveat: `communication-standards.md` is only **38 lines** (vs 319–545 for siblings) — underweight for a "standards" file. The other 4 are substantive.
**templates/** — Stale meta-documentation:
- `templates/CLAUDE.md` says `agent-template.md` exists "**(when created)**" — it has existed for a long time; also promises `command-template.md` and workflow templates "(when created)" that were **never created** (phantom inventory).
- `templates/agent-template.md` (318 lines) actively teaches the B1 anti-pattern: "description… under 150 characters", no trigger-phrase requirement, generic 5-tool list. This template is why 17/32 root agents fail B1. Verdict: REWRITE the frontmatter section.
**orchestration/ORCHESTRATION.md** (262 lines) — Referenced from README + agents/CLAUDE.md + mkdocs (not orphaned). Concept is sound, but its load examples are stale: `engineering/aws-solution-architect/SKILL.md` and `engineering/mcp-server-builder/SKILL.md` — `aws-solution-architect` exists only as `engineering-team/aws-solution-architect.zip` (an archive!) and mcp-server-builder lives at `engineering/skills/mcp-server-builder/`. Verdict: OPTIMIZE (fix example paths).
**custom-gpt/README.md** (128 lines) — Referenced from README + mkdocs; 6 ChatGPT GPT links. Not orphaned; external links unverifiable from here. Verdict: KEEP.
**assets/icon.png** — **Orphan.** Zero references from marketplace.json, any plugin.json, README, or mkdocs (grep across .json/.md/.yml). Either wire it into marketplace metadata or remove.
**engineering-team/*.zip** (12 archives: senior-fullstack.zip, aws-solution-architect.zip, etc.) — observed while tracing paths; zipped skill archives sitting in the published tree, referenced by personas/orchestration as if unzipped. Flagging for the engineering-team domain auditor.
---
## scripts/ (build & sync)
| Script | --help | Finding |
|---|---|---|
| check_plugin_json.py | PASS (argparse) | `--all` validates all 77 manifests, 0 WARN/FAIL today. Solid (D1–D3) |
| sync-codex-skills.py | PASS | Knows all 17 domains incl. markdown-html |
| sync-gemini-skills.py | PASS | **Missing `markdown-html` domain** — 5 skills never sync to Gemini |
| sync-hermes-skills.py | PASS | **Missing `markdown-html`** — never syncs to Hermes |
| sync-vibe-skills.py | PASS | **Missing `markdown-html`** — never syncs to Vibe |
| sync_skill_bundles.py | PASS (argparse) | OK |
| extract_release_notes.py | PASS (argparse) | OK |
| **audit_skills.py** | **FAIL** | No argparse; `--help` is ignored and the **full 346-skill audit runs** (~30s). D1 violation in the repo's own meta-audit tool |
| **generate-docs.py** | **FAIL — destructive** | No argparse; `--help` silently **regenerates the entire docs/ tree** (verified: modified 5 + created 4 files during this audit; reverted). A help invocation must never write. Also lacks markdown-html coverage (no docs pages exist for the 5 markdown-html skills) |
| convert.sh / install.sh / openclaw-install.sh / review-new-skills.sh / *-install.sh | header-documented | No hardcoded `/Users/...` or maintainer-specific paths found anywhere in scripts/ (good). `convert.sh` also has no markdown-html awareness |
---
## CI workflows
12 workflows. What actually gates PRs:
- **ci-quality-gate.yml** — runs on every PR. **CONFIRMED: `python scripts/check_plugin_json.py --all` runs as a blocking step**, exactly as CLAUDE.md claims (labeled "guards #539 + #686"). yamllint + workflow schema check (schema check is `|| true` — advisory). **Gap: the blocking `compileall` step covers only 9 pre-v2.7 folders** (`marketing-skill product-team c-level-advisor engineering-team ra-qm-team engineering business-growth finance project-management scripts`) — **8 newer domains are never syntax-checked in CI**: `productivity/`, `marketing/`, `research/`, `research-ops/`, `business-operations/`, `commercial/`, `markdown-html/`, `compliance-os/`. Safety scan and link check are `|| true` (advisory).
- **skill-quality-review.yml / skill-security-audit.yml** — PR-triggered, reference standards/; Tessl review depends on external secrets.
- **enforce-pr-target.yml** — pull_request_target gate (branch strategy enforcement). Runs.
- **claude.yml / claude-code-review.yml / pr-issue-auto-close.yml / virustotal-scan.yml** — event-driven; not quality gates per se.
- **release.yml** (push→main), **static.yml** (Pages), **sync-codex-skills.yml** (push), **smart-sync.yml** (issues; excluded from schema validation due to `projects_v2_item`).
Net: the only **blocking** code-quality gates are compileall (with the 8-domain hole) and check_plugin_json. Everything else is advisory or external-dependent. Note: `tests/` pytest suite is maintainer-local (gitignored) — no test gate runs in CI by design, but CLAUDE.md's claim "run locally; not in CI" is accurate.
---
## README/CLAUDE.md accuracy
- README header, badge, and FAQ all say **338 skills / 533 tools / 676 references / 51+ agents / 87+ commands / 16 domains** — all five numbers are stale (actual: 346 / 555 / 700 / 92 / 99 / 17). The shields badge hardcodes `Skills-338`.
- README relative links: all resolve in-tree (CHANGELOG.md, CONTRIBUTING.md, personas, orchestration). **No 404-for-cloners links found beyond the documented gitignored-folder exception.** CLAUDE.md's `documentation/...` links are covered by the Maintainer-Local Folders note (intentional).
- CLAUDE.md is **self-contradictory**: header (L9) 338/62/16, v2.10.3 block 343/64/17, footer "Last Updated May 27, 2026 / Version v2.9.0 / 338 skills…16 domains / 62 plugins". Three different repo states in one file.
- agents/CLAUDE.md is the worst offender: "42 production skills" and "177 existing skills" in adjacent paragraphs, "16 Agents Currently Available" heading over a 19-row table, while the folder holds 32 agent files.
- README claim "All 533 Python CLI tools… verified to run with `--help`" — falsified twice in scripts/ alone (audit_skills.py, generate-docs.py), and the count is 555.
---
## Top recommendations
1. **Single-source the counters.** Add a `scripts/update_counters.py` (or extend audit_skills.py) that computes skills/plugins/tools/references/agents/commands from the tree and rewrites README badge, CLAUDE.md header+footer, and marketplace.json metadata in one pass; wire it as a blocking CI check ("counters match tree"). Today 7 locations disagree, including marketplace.json with itself (says 64, contains 66).
2. **Fix the phantom-path epidemic in root commands (28/39 affected).** Mechanical fix: insert the missing `skills/` segment (`<domain>/skills/<skill>/scripts/…`); add a CI grep that fails on any in-repo path reference in commands/ + agents/ that doesn't exist. Same fix applies to agents' `skills:` shorthand, orchestration/ORCHESTRATION.md examples, and templates.
3. **Reconcile marketplace.json with disk**: register or explicitly de-list the 11 unregistered plugin.json manifests (compliance-os is even advertised in the marketplace description but uninstallable from it); bump the self-described plugin count to the real entry count.
4. **De-duplicate the 6 byte-identical root commands** (karpathy-check + 5 wiki-*) — keep the plugin copies as canonical; cut `prd`, `sprint-plan`, `tdd` or merge them into their skills (bare-prompt-replaceable).
5. **Repair the meta-tooling**: give audit_skills.py and generate-docs.py argparse (`--help` must be side-effect-free — generate-docs.py currently rewrites docs/ on `--help`); add `markdown-html` to sync-hermes/vibe/gemini + convert.sh + generate-docs; extend ci-quality-gate compileall to the 8 uncovered domains.
6. **Fix the template that breeds B1 failures**: add a mandatory trigger-phrase line ("Use when… / Spawn when…") to templates/agent-template.md, then backfill the 17 root agents missing triggers (the 4 v2.8.1 engineering agents are the pattern to copy); update templates/CLAUDE.md's "(when created)" phantom inventory.
### Custom verification criteria (cross-cutting contract)
- `python3 scripts/check_plugin_json.py --all` exits 0 with 77+ manifests OK (keep green).
- `python3 -c "import json; m=json.load(open('.claude-plugin/marketplace.json')); n=len(m['plugins']); assert str(n) in m['metadata']['description'], (n, 'not in metadata')"` exits 0 after counter fix.
- For every `*.py` path matched by `` grep -rhoE '`[a-z-]+(/[a-zA-Z0-9_.-]+)+\.py`' commands/*.md ``: the file exists relative to repo root (0 misses; today: 28 commands fail).
- `python3 scripts/audit_skills.py --help` and `python3 scripts/generate-docs.py --help` exit 0 in <2s with **zero filesystem writes** (`git status --porcelain` empty after).
- `grep -RLE "Use when|Spawn when|Invoke via|Use PROACTIVELY" $(find agents -name 'cs-*.md')` returns empty after trigger backfill.

305
audit/newgen-2026-06/engineering-team.md Normal file
View file

@ -0,0 +1,305 @@
# Domain audit: engineering-team/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 51 · Agents: 5 · Commands: 0 · Plugins: 6
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| skills/adversarial-reviewer | KEEP | — |
| skills/ai-security | KEEP | — |
| skills/aws-solution-architect | KEEP | cost figures unverified (minor A6) |
| skills/azure-cloud-architect | KEEP | Bicep API versions pinned to 2023 (minor A6) |
| skills/cloud-security | KEEP | — |
| skills/code-reviewer | KEEP | — |
| skills/email-template-builder | OPTIMIZE | 439-line code dump, zero scripts/references (A3, A7) |
| skills/engineering-skills | OPTIMIZE | index skill claims "23 skills" — actual 32; weak as a skill |
| skills/epic-design | KEEP | "You are a world-class expert" filler (minor A2) |
| skills/gcp-cloud-architect | KEEP | — |
| skills/incident-commander | OPTIMIZE | 3 orphan duplicate scripts; SEV taxonomy duplicates incident-response |
| skills/incident-response | KEEP | — |
| skills/ms365-tenant-manager | OPTIMIZE | 3 scripts exist but never referenced in SKILL.md (A3) |
| skills/red-team | KEEP | — |
| skills/security-pen-testing | KEEP | — |
| skills/senior-architect | OPTIMIZE | generic monolith-vs-microservices prose; no verification loop |
| skills/senior-backend | OPTIMIZE | corrupted code snippet (`name: "zstringmin1max100"`) |
| skills/senior-computer-vision | KEEP | — |
| skills/senior-data-engineer | OPTIMIZE | thin body; generic batch-vs-streaming tables (A2) |
| skills/senior-data-scientist | OPTIMIZE | phantom scripts referenced; real 3 scripts orphaned (A3 hard fail) |
| skills/senior-devops | KEEP | — |
| skills/senior-frontend | OPTIMIZE | corrupted snippet (`"cdnexamplecom"`); mid-file generic React dump |
| skills/senior-fullstack | KEEP | — |
| skills/senior-ml-engineer | OPTIMIZE | GPT-4/GPT-3.5/Claude 3 Opus pricing tables (A6 fail) |
| skills/senior-prompt-engineer | REWRITE | entire skill is GPT-4-era prompt engineering; stale models hardcoded in scripts |
| skills/senior-qa | OPTIMIZE | 2 corrupted code snippets; generic RTL cheatsheet content |
| skills/senior-secops | KEEP | trim BAD/GOOD security basics (minor A2) |
| skills/senior-security | CUT-OR-MERGE | duplicates senior-secops/pen-testing/incident-response; no exact CLI for its 2 scripts |
| skills/stripe-integration-expert | OPTIMIZE | pinned `apiVersion: "2024-04-10"`; pure code dump, no tools |
| skills/tdd-guide | KEEP | — |
| skills/tech-stack-evaluator | OPTIMIZE | "ecosystem health from GitHub/npm metrics" is offline static data — staleness unlabeled |
| skills/threat-detection | KEEP | — |
| a11y-audit/skills/a11y-audit | KEEP | — |
| google-workspace-cli/skills/google-workspace-cli | REWRITE | install coordinates almost certainly fabricated (`npm i -g @anthropic/gws`, `github.com/googleworkspace/cli`) |
| snowflake-development/skills/snowflake-development | KEEP | — |
| playwright-pro/skills/pw | KEEP | — |
| playwright-pro/skills/init | KEEP | — |
| playwright-pro/skills/generate | KEEP | — |
| playwright-pro/skills/review | KEEP | — |
| playwright-pro/skills/fix | KEEP | — |
| playwright-pro/skills/migrate | KEEP | — |
| playwright-pro/skills/coverage | KEEP | — |
| playwright-pro/skills/report | KEEP | — |
| playwright-pro/skills/testrail | KEEP | — |
| playwright-pro/skills/browserstack | KEEP | — |
| self-improving-agent/skills/self-improving-agent | KEEP | — |
| self-improving-agent/skills/review | KEEP | — |
| self-improving-agent/skills/promote | KEEP | — |
| self-improving-agent/skills/extract | KEEP | — |
| self-improving-agent/skills/remember | KEEP | — |
| self-improving-agent/skills/status | KEEP | — |
**Totals: KEEP 35 · OPTIMIZE 13 · REWRITE 2 · CUT-OR-MERGE 1**
## Domain-level findings
1. **Bulk-edit code corruption (systemic, 4 confirmed sites).** A past YAML/quoting sweep mangled string literals inside code blocks: `senior-qa/SKILL.md:123` (`name: "click-mei-tobeinthedocument"` — was `getByRole('button', { name: /click me/i })` + `toBeInTheDocument()`), `senior-qa:244` (`"submiti"`), `senior-backend:253` (`name: "zstringmin1max100"` — was `z.string().min(1).max(100)`), `senior-frontend:425` (`hostname: "cdnexamplecom"` — dots stripped). Any model copying these examples emits broken code. Grep pattern to find more: strings that are concatenated identifiers with punctuation stripped.
2. **Stale LLM-era content concentrated in 2 skills + their scripts.** senior-prompt-engineer and senior-ml-engineer present GPT-4/GPT-3.5/Claude 3 Opus model names, 8K context windows, and 2024 pricing as current — in SKILL.md, references (`llm_integration_guide.md`), and hardcoded in scripts (`prompt_optimizer.py` MODEL choices/prices, `agent_orchestrator.py` cost tables). A6 fail across the whole package, not just prose.
3. **Two generations of skills coexist.** The 2026-upgraded trio (senior-fullstack/frontend/backend: decision engines, profiles, forcing questions, composition maps, kill criteria) and the v2.2 security suite (ai-security, threat-detection, incident-response, cloud-security, red-team: exit-code contracts, ATT&CK/ATLAS mapping, anti-patterns) are the new-gen template. The 2025-era role skills (architect, data-scientist, data-engineer, prompt-engineer, qa) still carry "cheatsheet" bodies — generic tables (HTTP status codes, RTL queries, zero-shot vs few-shot) that a frontier model embodies and that cost context for nothing.
4. **Security skill sprawl with duplicated incident-response content.** Four skills carry SEV1-SEV4 frameworks + IR phase checklists (senior-secops, senior-security, incident-response, incident-commander), and OWASP Top 10 appears in 4 places. The v2.2 suite has explicit "this is NOT X" disambiguation tables; the older senior-security does not and is ~80% subsumed.
5. **Orphan/phantom script wiring (A3).** senior-data-scientist references `scripts/train.py`/`evaluate.py`/`health_check.py` (don't exist) while its 3 real scripts go unmentioned; ms365-tenant-manager never references its 3 scripts; incident-commander ships 6 scripts but wires only 3 (`severity_classifier.py`, `incident_timeline_builder.py`, `postmortem_generator.py` are duplicates of the wired ones).
6. **Count drift everywhere.** README says 18 skills, START_HERE says 14, engineering-skills SKILL.md says 23, plugin.json says 32, root CLAUDE.md says 51. engineering-team/CLAUDE.md documents 7 scripts that don't exist under those names (`fullstack_scaffolder.py`, `statistical_analyzer.py`, `etl_generator.py`, `mlops_setup_tool.py`, `llm_integration_builder.py`, `rag_system_builder.py` under prompt-engineer, `video_processor.py`).
7. **18 stale .zip archives at domain root** (senior-*.zip, code-reviewer.zip, etc.) — dead weight shipped to every cloner; almost certainly out of sync with the live folders.
8. **Unverifiable external-tool provenance.** google-workspace-cli teaches a `gws` CLI installed via `npm install -g @anthropic/gws` (not an Anthropic package) with releases at `github.com/googleworkspace/cli` (not a real repo). If the CLI doesn't exist under these coordinates, the entire 373-line skill + 43 recipes is unusable.
9. **Bright spots worth templating:** playwright-pro sub-skills end every workflow with an executable gate ("run `--repeat-each=10`, all 10 must pass"); code-reviewer ships regression fixtures with committed expected `--json` outputs; the security suite's exit-code contracts (0/1/2 with required action) are exactly the A4 pattern the rubric wants.
## Per-skill findings
### engineering-team/skills/senior-prompt-engineer
Verdict: REWRITE
Issues:
- A6 hard fail: GPT-4 cost estimates in sample output (line 57), `--model gpt-4` examples (line 72); `prompt_optimizer.py` restricts `--model` to gpt-4/gpt-3.5-turbo/claude-3-* with 2024 prices; `agent_orchestrator.py` defaults to `model: gpt-4` with stale cost table.
- A2: zero-shot/few-shot/CoT/role-prompting tables and "add format enforcement" guidance are 2023-era basics a frontier model embodies.
- A5 gap: nothing on current practice — structured outputs/tool-use APIs, prompt caching, eval-driven iteration, agent context engineering.
- No verification loop beyond "run both prompts against your eval set" (manual).
Verify (definition of done):
- `grep -rE "gpt-4|gpt-3\.5|claude-3-" skills/senior-prompt-engineer/` returns 0 hits.
- `python3 scripts/prompt_optimizer.py /tmp/p.txt --analyze` exits 0 and model list contains only current-generation model IDs (or is model-agnostic).
- SKILL.md workflow ends with an executable eval gate (script run + exit-code assertion), not "compare outputs".
### engineering-team/google-workspace-cli/skills/google-workspace-cli
Verdict: REWRITE
Issues:
- Install section points to `npm install -g @anthropic/gws` and `github.com/googleworkspace/cli/releases` — neither coordinate is verifiable as real; skill is unusable if the CLI doesn't exist as described.
- All 43 recipes, persona bundles, and command syntax inherit this provenance risk (A5/A6).
- The 5 Python wrappers (`gws_doctor.py` etc.) are fine but only meaningful if `gws` resolves.
Verify (definition of done):
- Documented install command succeeds on a clean machine (`gws --version` exits 0), or the skill is rebuilt around a verifiable tool (GAM7 / Google Workspace Admin SDK + gcloud).
- `python3 scripts/gws_doctor.py` exits non-zero with a clear "gws not installed" message (graceful degradation check).
- 5 randomly sampled recipe commands validated against the CLI's actual `--help` output.
### engineering-team/skills/senior-security
Verdict: CUT-OR-MERGE (fold into senior-secops; keep threat modeling)
Issues:
- ~80% duplicates siblings: incident-response workflow (also in senior-secops + incident-response), secure-code-review checklist (code-reviewer), security headers (senior-secops), tool lists (security-pen-testing).
- A3: scripts section says "see the script source files directly" — no exact CLI invocations for `threat_modeler.py`/`secret_scanner.py`, no output consumption.
- Unique value is only the STRIDE-per-element matrix + DREAD scoring + threat_modeler.py.
Verify (definition of done):
- `python3 scripts/threat_modeler.py --help` exits 0 and the surviving SKILL.md (wherever it lands) shows an exact invocation whose JSON output feeds a named next step.
- After merge, `grep -l "STRIDE" engineering-team/skills/*/SKILL.md` returns exactly one file.
- No SEV/IR phase table remains in the merged body (route to incident-response instead).
### engineering-team/skills/senior-ml-engineer
Verdict: OPTIMIZE
Issues:
- A6: cost table (lines 154-157) lists GPT-4/GPT-3.5/Claude 3 Opus/Haiku at 2024 prices; `references/llm_integration_guide.md` repeats it plus "GPT-4 8,192 context" and `model="gpt-4"` defaults.
- Provider abstraction + tenacity retry code is generic boilerplate (A2).
- Tools shown with one-line CLI but no output-consumption step (`--deploy` flag semantics unstated).
Verify (definition of done):
- `grep -rE "GPT-4|GPT-3\.5|Claude 3 " skills/senior-ml-engineer/` returns 0 hits.
- `python3 scripts/model_deployment_pipeline.py --help` exits 0 and SKILL.md states what artifact each tool emits and which workflow step consumes it.
### engineering-team/skills/senior-data-scientist
Verdict: OPTIMIZE
Issues:
- A3 hard fail: "Common Commands" references `scripts/train.py`, `scripts/evaluate.py`, `scripts/health_check.py` — none exist; the real scripts (`experiment_designer.py`, `feature_engineering_pipeline.py`, `model_evaluation_suite.py`) are never mentioned.
- Body is inline Python a frontier model writes on demand; the embedded checklists (SRM check <0.01, Bonferroni, parallel trends, HC3) are the actual value — keep those, cut the function bodies.
- Generic kubectl/docker/helm command block is irrelevant filler (A7).
Verify (definition of done):
- Every script path in SKILL.md exists: `grep -o "scripts/[a-z_]*\.py" SKILL.md | xargs -I{} test -f skills/senior-data-scientist/{}` all pass.
- `python3 scripts/experiment_designer.py --help` exits 0 and SKILL.md shows an exact invocation per tool.
### engineering-team/skills/senior-qa
Verdict: OPTIMIZE
Issues:
- Corrupted snippets at lines 123 and 244 (mangled `getByRole` calls) — copy-paste hazards.
- RTL query/async/MSW quick-reference is frontier-model-embodied content (A2); MSW example uses deprecated `rest` API (v1) — current msw is `http` (A6).
- `actions/upload-artifact@v3` in CI example is deprecated.
- Coverage workflow is good (threshold + `--strict` exit 1) — keep.
Verify (definition of done):
- All TS/TSX code blocks in SKILL.md parse (extract fenced blocks, run through `tsc --noEmit` or eslint-parse smoke check).
- `python3 scripts/coverage_analyzer.py assets-or-sample --threshold 80` documented and exits per stated contract (0 pass / 1 below threshold).
### engineering-team/skills/senior-frontend
Verdict: OPTIMIZE
Issues:
- Corrupted config at line 425: `remotePatterns: [{ hostname: "cdnexamplecom" }]` (dots stripped).
- Lines 197-465: compound-components/render-props/Image/Suspense dump duplicates what the model knows and what `references/react_patterns.md` already holds — violates progressive disclosure (A2).
- The 2026 wrapper (profiles, decision engine, forcing questions) is excellent; the legacy middle dilutes it.
Verify (definition of done):
- `python3 scripts/frontend_decision_engine.py --primary-device mobile-4g --lcp-target-ms 2000 --seo-dependent true --auth-walled false --team-size 5` exits 0 and emits matched profile + thresholds.
- SKILL.md under 350 lines with pattern code moved to references/; corrupted snippet fixed.
### engineering-team/skills/senior-backend
Verdict: OPTIMIZE
Issues:
- Corrupted Zod snippet at line 253 (`name: "zstringmin1max100"`).
- HTTP status-code table, REST response formats = frontier-embodied filler (A2).
- Load-tester flags shown (`--expect-rate-limit`, `--expect-status`) need verification against actual argparse surface.
Verify (definition of done):
- `python3 scripts/backend_decision_engine.py --team-size 8 --qps-p99 50 --read-write-ratio 20 --tenancy shared-multi-tenant --data-sensitivity pii --pattern modular-monolith --language-preference typescript` exits 0 with profile + SLO floor + approver chain.
- `python3 scripts/api_load_tester.py --help` lists every flag SKILL.md uses.
### engineering-team/skills/senior-architect
Verdict: OPTIMIZE
Issues:
- Monolith-vs-microservices checkboxes and team-size tables are generic (A2) — senior-fullstack's forcing-question + kill-criterion treatment of the same decision is strictly better; cross-link instead of duplicating.
- No verification loop: workflows end at "document decision" (A4).
- Tools are well-wired (exact CLI, sample outputs) — keep.
Verify (definition of done):
- `python3 scripts/dependency_analyzer.py . --output json` exits 0 and emits `circular` + `coupling_score` keys; SKILL.md workflow ends with "re-run analyzer, assert circular = 0".
- ADR step references a concrete template file that exists in the package.
### engineering-team/skills/senior-data-engineer
Verdict: OPTIMIZE
Issues:
- 34-line trigger-phrase section is frontmatter duplication (A2); body's batch-vs-streaming and Lambda-vs-Kappa tables are textbook content.
- "Workflows → See references/workflows.md" and "Troubleshooting → See ..." one-liners make the body a stub while references hold the substance — inverted disclosure (workflows.md is solid at 624 lines).
- Tool subcommand contracts (`generate`/`validate`/`analyze`) shown but outputs not consumed by named steps.
Verify (definition of done):
- `python3 scripts/data_quality_validator.py --help` exits 0 and supports the `validate --checks freshness,completeness,uniqueness` syntax shown.
- SKILL.md inlines a 10-line decision rule per workflow with the deep dive staying in references/.
### engineering-team/skills/incident-commander
Verdict: OPTIMIZE
Issues:
- Orphan scripts: `severity_classifier.py`, `incident_timeline_builder.py`, `postmortem_generator.py` duplicate the 3 wired tools (A3/A7) — delete or wire.
- SEV1-SEV4 definitions overlap incident-response (security flavor) with no disambiguation table; add "this is NOT security incident triage" routing.
- Marketing-prose header block ("battle-tested practices ... at scale") is filler (A2).
Verify (definition of done):
- `ls scripts/ | wc -l` equals the number of scripts referenced in SKILL.md.
- `echo '{"description":"...","affected_users":"80%","business_impact":"high"}' | python3 scripts/incident_classifier.py` exits 0 and output matches `expected_outputs/incident_classification_text_output.txt` semantics.
### engineering-team/skills/ms365-tenant-manager
Verdict: OPTIMIZE
Issues:
- 3 scripts (`powershell_generator.py`, `tenant_setup.py`, `user_management.py`) never referenced in SKILL.md; root-level `sample_input.json`/`expected_output.json` orphaned too (A3).
- PowerShell content is genuinely expert (Graph SDK, CA report-only-first) — keep; just wire or delete the Python layer.
- Verify Graph cmdlet names still current (MSOnline/AzureAD modules retired; this correctly uses Mg* — confirm references do too).
Verify (definition of done):
- Either SKILL.md shows exact CLI for all 3 scripts with consumed output, or `scripts/` is removed.
- `python3 scripts/powershell_generator.py --help` exits 0 (if retained).
### engineering-team/skills/stripe-integration-expert
Verdict: OPTIMIZE
Issues:
- Pinned `apiVersion: "2024-04-10"` presented as current (A6).
- 476 lines of TSX/route-handler code a frontier model writes; the durable value (lifecycle state machine, webhook event ordering, idempotency discipline) should lead, code moved to references/.
- No scripts, no references, no verification loop (A3/A4) — e.g., no webhook-handler checklist gate.
Verify (definition of done):
- `grep -c "apiVersion" SKILL.md` hits use a placeholder + "check current API version" instruction, not a pinned date.
- Workflow ends with executable check: `stripe listen`/`stripe trigger checkout.session.completed` smoke procedure with expected handler behavior stated.
### engineering-team/skills/email-template-builder
Verdict: OPTIMIZE (merge candidate with marketing email skills if it stays code-only)
Issues:
- Entire skill is one 439-line code dump: no scripts/, references/, assets/ (A3/A7).
- React Email component code is frontier-embodied; the value is the pitfalls list (600px, inline styles, dark-mode `!important`, separate sending domains) and provider matrix — invert the ratio.
- No verification loop (no spam-score check step, no preview-render gate) (A4).
Verify (definition of done):
- SKILL.md ≤ 200 lines centered on client-compatibility rules + deliverability checklist; full code in references/.
- Workflow ends with an executable gate (e.g., render template via `npx react-email` preview + checklist assertion of plain-text part present).
### engineering-team/skills/tech-stack-evaluator
Verdict: OPTIMIZE
Issues:
- "Ecosystem health from GitHub, npm metrics" is a stdlib offline tool — data is embedded snapshots with no as-of date; comparisons silently age (A6).
- Quick-start examples are bare prose prompts, not tool invocations — wire them to the scripts.
- 7 scripts but SKILL.md gives exact CLI for only 5 (format_detector, report_generator unmentioned).
Verify (definition of done):
- `python3 scripts/tco_calculator.py --input assets/sample_input_tco.json` exits 0 and matches `assets/expected_output_comparison.json` schema.
- Every embedded-data script prints a `data_as_of` field in JSON output and SKILL.md tells the model to label conclusions with it.
### engineering-team/skills/engineering-skills
Verdict: OPTIMIZE
Issues:
- Claims "23 production-ready engineering skills"; `skills/` holds 32; plugin.json says 32; README says 18; START_HERE says 14 — pick one truth (A6/E2).
- As a skill it's a static catalog; its only durable instruction ("load one SKILL.md, don't bulk-load") could live in the plugin description.
- `npx agent-skills-cli add ...` install path needs verification.
Verify (definition of done):
- `ls -d engineering-team/skills/*/ | wc -l` equals the count stated in SKILL.md, plugin.json, README.md, and START_HERE.md.
- Skill table lists every actual folder (no missing security-suite rows).
## KEEP-verdict verification criteria
- **adversarial-reviewer** — review output contains all 3 persona sections each with ≥1 finding and ends with verdict ∈ {BLOCK, CONCERNS, CLEAN}; promotion rule applied when 2+ personas overlap.
- **ai-security** — `python3 scripts/ai_threat_scanner.py --target-type llm --access-level black-box --json` exits 0/1/2 per contract and JSON has `overall_risk` + `findings[].finding_type`; `--access-level gray-box` without `--authorized` exits 2.
- **aws-solution-architect** — `python3 scripts/architecture_designer.py --input <sample>` emits `recommended_pattern` + `estimated_monthly_cost_usd`; CloudFormation output passes `aws cloudformation validate-template` (or cfn-lint) when run.
- **azure-cloud-architect** — `python3 scripts/bicep_generator.py --arch-type web-app --output /tmp/main.bicep` exits 0 and output parses with `az bicep build` where available.
- **cloud-security** — `python3 scripts/cloud_posture_check.py <iam-sample>.json --check iam --json` exits 2 on a PassRole+CreateFunction policy and 0 on least-privilege sample.
- **code-reviewer** — `python3 scripts/code_quality_checker.py assets/sample_java_smells.java --json | diff - expected_outputs/sample_java_smells_quality.json` is empty (regression fixture green); dispatch table covers every `languages/*.md` file.
- **epic-design** — `python3 scripts/inspect-assets.py --help` exits 0 without Pillow installed; output format matches references/asset-pipeline.md Step 4 contract.
- **gcp-cloud-architect** — `python3 scripts/cost_optimizer.py --resources <sample>.json --monthly-spend 2000` exits 0 with itemized savings.
- **incident-response** — `echo '{"event_type":"ransomware","host":"x","raw_payload":{}}' | python3 scripts/incident_triage.py --classify --json` exits 2 (SEV1) and maps T1486.
- **red-team** — `python3 scripts/engagement_planner.py --techniques T1059 --access-level external --json` (no `--authorized`) exits 1; with `--authorized` exits 0 and orders phases by kill chain.
- **security-pen-testing** — `python3 scripts/vulnerability_scanner.py --target web --scope quick --json` exits 0 and emits OWASP A01-A10 checklist items; `dependency_auditor.py --file package.json --json` parses.
- **senior-computer-vision** — `python3 scripts/dataset_pipeline_builder.py --help` lists `--analyze/--clean/--split/--generate-config` flags used in SKILL.md; `inference_optimizer.py --help` lists `--benchmark/--export`.
- **senior-devops** — `python3 scripts/terraform_scaffolder.py /tmp/infra --provider=aws --module=ecs-service` exits 0; generated HCL passes `terraform validate` where available; rollback procedure's `curl -sf .../healthz` gate retained.
- **senior-fullstack** — `python3 scripts/fullstack_decision_engine.py --sample --output json` exits 0 with `ranked_matches[0].profile_name` and empty `kill_criteria_tripped` (verified this audit); engine refuses (non-zero) when any of the 4 required inputs missing.
- **senior-secops** — `python3 scripts/security_scanner.py <dir>` exit codes follow 0/1/2 contract; `compliance_checker.py --framework soc2 --json` emits per-control results; CVE-triage SLA table retained (9.0+ internet-facing = 24h).
- **tdd-guide** — `python3 scripts/coverage_analyzer.py --report assets/sample_coverage_report.lcov --threshold 80` exits per contract and P0/P1/P2 buckets present; `test_generator.py --input <py> --framework pytest` output compiles.
- **threat-detection** — `python3 scripts/threat_signal_analyzer.py --mode anomaly --events-file <sample> --baseline-mean 100 --baseline-std 25 --json` exits 2 only when z ≥ 3.0; IOC mode flags >30-day-old IPs as `stale`.
- **a11y-audit** — `python3 scripts/contrast_checker.py --fg "#777777" --bg "#ffffff"` reports fail at 4.5:1; `a11y_scanner.py <dir> --ci` exits non-zero only on critical findings; `--baseline` comparison runs.
- **snowflake-development** — `python3 scripts/snowflake_query_helper.py merge --target t --source s --key id --columns a,b` exits 0 and emitted SQL contains colon-prefix rule compliance in proc templates.
- **playwright-pro/pw** — all 9 sub-skill routes listed exist as skill folders; Quick Start sequence references only shipped commands.
- **playwright-pro/init** — generated `playwright.config.ts` sets `retries: 2` in CI / `0` local and `trace: 'on-first-retry'`; first smoke test runs.
- **playwright-pro/generate** — workflow step 7 retained: `npx playwright test <file> --reporter=list` must run before reporting done; no `waitForTimeout` in output.
- **playwright-pro/review** — review loads `anti-patterns.md` (file exists) and flags a seeded `page.waitForTimeout()` fixture.
- **playwright-pro/fix** — fix loads `flaky-taxonomy.md` (file exists); completion requires `--repeat-each=10` 10/10 green.
- **playwright-pro/migrate** — post-migration step routes to `/pw:coverage` parity check before decommissioning old suite.
- **playwright-pro/coverage** — output lists tested vs untested routes with priority ranking.
- **playwright-pro/report** — report generation consumes `playwright-report/` or JSON reporter output, errors clearly when absent.
- **playwright-pro/testrail** — refuses gracefully with setup instructions when `TESTRAIL_URL/USER/API_KEY` unset.
- **playwright-pro/browserstack** — refuses gracefully when `BROWSERSTACK_USERNAME/ACCESS_KEY` unset.
- **self-improving-agent (root)** — memory-paths table matches current Claude Code memory layout (`~/.claude/projects/<path>/memory/MEMORY.md`, 200-line load) — recheck against docs each release.
- **si/review** — spawns memory-analyst; output buckets = promotion candidates / stale / consolidation / conflicts / health.
- **si/promote** — promotion writes to CLAUDE.md or `.claude/rules/` AND removes the MEMORY.md source entry (both halves verified).
- **si/extract** — extracted skill passes `scripts/audit_skills.py` (repo validator) with no FAIL.
- **si/remember** — entry written with timestamp + category into the active memory dir.
- **si/status** — dashboard reports line counts vs 200-line budget and flags overflow topic files.
## Agents
| Agent | B1 frontmatter | B2 differentiation | B3 body | Verdict |
|---|---|---|---|---|
| playwright-pro/agents/test-architect | PASS (read-only tools) | PASS — plans, explicitly does not write tests | PASS | KEEP |
| playwright-pro/agents/test-debugger | PASS — exemplary scoped `Bash(npx playwright test *)` allowlist + disallowedTools | PASS — taxonomy-driven diagnosis | PASS | KEEP |
| playwright-pro/agents/migration-planner | PASS (read-only) | PASS — detection protocol per framework | PASS | KEEP |
| self-improving-agent/agents/memory-analyst | PASS (Read/Glob/Grep, maxTurns 30) | PASS — read-only analyst, distinct outputs | PASS | KEEP |
| self-improving-agent/agents/skill-extractor | PASS (Write/Edit + disallowedTools) | PASS — portability rules (no hardcoded paths) | PASS | KEEP |
Note: agent descriptions use "Invoked by /pw:..." rather than "Use when..." trigger phrasing — acceptable since they are command-spawned, not auto-triggered.
## Commands
None in scope. engineering-team/ ships no `commands/` directory; the `/pw:*` and `/si:*` surfaces are skills-as-commands (audited above). The grep hits under `commands*` are reference docs, not slash commands.
## Plugin manifests
| Plugin | Issue |
|---|---|
| `.claude-plugin/plugin.json` (engineering-skills) | Says "32 skills" — matches `skills/` dir count, but conflicts with SKILL.md (23), README (18), START_HERE (14). Description is a 1,100-char wall; trim. |
| `a11y-audit` | Clean; description matches contents. |
| `google-workspace-cli` | Description repeats the unverifiable `gws` CLI claims; fix alongside the skill REWRITE. |
| `playwright-pro` (name: `pw`) | Clean; "55+ templates, 3 agents" — template count not verified file-by-file but folder structure exists. |
| `self-improving-agent` (name: `si`) | Clean; commands listed all exist as sub-skills. |
| `snowflake-development` | Description's "query helper script, 3 reference guides" verified accurate (1 script, 3 refs). Clean. |
Additional manifest-adjacent debt: 18 stale `.zip` archives at engineering-team root; engineering-team/CLAUDE.md documents 7 nonexistent script filenames and a "32 skills / 39+ tools" inventory that predates the security suite and sub-plugins.

333
audit/newgen-2026-06/engineering.md Normal file
View file

@ -0,0 +1,333 @@
# Domain audit: engineering/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 80 SKILL.md (63 distinct skills; 12 sub-command skills under agenthub/autoresearch; 4 dual-published duplicates; 1 sample asset excluded) · Agents: 14 · Commands: 14 · Plugins: 28 manifests
## Scorecard
Bundle = `engineering/skills/<name>`; standalone = `engineering/<name>/`.
| Skill | Verdict | Top issue |
|---|---|---|
| skills/agent-designer | REWRITE | 279 lines of taxonomy prose a frontier model already knows; 3 root-level scripts never wired |
| skills/agent-workflow-designer | OPTIMIZE | Thin body; overlaps agent-designer + workflow-builder |
| skills/api-design-reviewer | OPTIMIZE | ~300 lines of textbook REST; scripts named but no exact CLI in workflow |
| skills/api-test-suite-builder | KEEP | — |
| skills/browser-automation | KEEP | — |
| skills/changelog-generator | KEEP | — (absorb release-manager into it) |
| skills/chaos-engineering (+ standalone dup) | KEEP | — (deduplicate copies) |
| skills/ci-cd-pipeline-builder | KEEP | — |
| skills/codebase-onboarding | OPTIMIZE | Thin; 1 script, low expertise density |
| skills/command-guide | CUT-OR-MERGE | Documents another repo's (ECC) commands/agents that don't exist here |
| skills/database-designer | CUT-OR-MERGE | Overlaps 2 siblings; claims "included tools" with zero CLI wiring |
| skills/database-schema-designer | CUT-OR-MERGE | No scripts; broken seed-code example; overlaps database family |
| skills/dependency-auditor | REWRITE | Marketing brochure ("Future Enhancements", "Planned Features"); unverifiable claims |
| skills/engineering-advanced-skills | OPTIMIZE | Index says "25 skills", plugin says 40; wrong load paths |
| skills/env-secrets-manager | KEEP | — (fix dead cross-refs) |
| skills/feature-flags-architect (+ dup) | KEEP | — (deduplicate copies) |
| skills/focused-fix | KEEP | — (references external `superpowers:*` skills) |
| skills/full-page-screenshot | KEEP | — |
| skills/git-worktree-manager | KEEP | — |
| skills/interview-system-designer | OPTIMIZE | HR skill in engineering domain; 4 scripts, 1 wired |
| skills/kubernetes-operator (+ dup) | KEEP | — (deduplicate copies) |
| skills/mcp-server-builder | KEEP | — |
| skills/migration-architect | REWRITE | 477 lines textbook; scripts named only in "Tools" section, no CLI |
| skills/monorepo-navigator | KEEP | — |
| skills/observability-designer | REWRITE | Brochure prose; no exact CLI; overlaps slo-architect |
| skills/performance-profiler | KEEP | — |
| skills/pr-review-expert | KEEP | — |
| skills/rag-architect | REWRITE | Stale (ada-002, 2024 Pinecone pricing); 3 scripts never wired; textbook |
| skills/release-manager | CUT-OR-MERGE | 489-line textbook; duplicates changelog-generator; scripts unwired |
| skills/runbook-generator | OPTIMIZE | Thin skeleton generator, low expertise density |
| skills/secrets-vault-manager | KEEP | — |
| skills/self-eval | KEEP | — |
| skills/ship-gate | KEEP | — |
| skills/skill-security-auditor | KEEP | — |
| skills/skill-tester | REWRITE | 390-line brochure incl. "Future Enhancements"; CLI shown without paths |
| skills/slo-architect (+ dup) | KEEP | — (deduplicate copies) |
| skills/spec-driven-workflow | KEEP | — |
| skills/sql-database-assistant | KEEP | — (merge target for the database trio) |
| skills/tc-tracker | KEEP | — |
| skills/tech-debt-tracker | REWRITE | Roadmap/KPI filler; 5 passing scripts, zero CLI wiring |
| agenthub (8 SKILL.md) | KEEP | — |
| autoresearch-agent (6 SKILL.md) | KEEP | — (document evaluator --help exception in SKILL.md) |
| behuman | KEEP | — (not registered in marketplace) |
| caveman | KEEP | — |
| claude-coach | OPTIMIZE | Duplicate frontmatter keys; README content pasted into SKILL.md tail |
| code-tour | KEEP | — |
| data-quality-auditor | KEEP | — |
| demo-video | KEEP | — |
| docker-development | KEEP | — |
| grill-me | KEEP | — |
| grill-with-docs | KEEP | — (not registered in marketplace) |
| handoff (engineering) | KEEP | — |
| helm-chart-builder | KEEP | — |
| karpathy-coder | KEEP | — |
| llm-cost-optimizer | KEEP | — (not registered in marketplace) |
| llm-wiki | KEEP | — |
| prompt-governance | KEEP | — (not registered in marketplace) |
| security-guidance | KEEP | — |
| statistical-analyst | KEEP | — |
| terraform-patterns | KEEP | — |
| universal-scraping-architect | OPTIMIZE | 3 orphan scripts; placeholder agent + command; non-stdlib deps |
| workflow-builder | KEEP | — |
| write-a-skill | KEEP | — |
**Totals: KEEP 44 · OPTIMIZE 8 · REWRITE 7 · CUT-OR-MERGE 4** (63 distinct skills)
## Domain-level findings
1. **Two clear generations.** v2.4+ skills (slo-architect, chaos-engineering, kubernetes-operator, feature-flags-architect, karpathy-coder, workflow-builder, the Pocock ports, agenthub, autoresearch) are exemplary: trigger-rich descriptions, exact CLI per tool, refusal gates, "Verifiable success" sections. ~10 v2.0-era skills in `engineering/skills/` are capability brochures ("Future Enhancements", "Conclusion", "Planned Features" sections) whose body is knowledge a frontier model already has — pure context dead weight.
2. **Orphan-script epidemic in v2.0-era skills.** agent-designer, rag-architect, release-manager, database-designer (root-level `.py`), tech-debt-tracker and skill-tester (in `scripts/`) all ship working scripts (`--help` passes) that SKILL.md never invokes with a runnable command. A model following the SKILL.md will never run them — A3 failure across the board. universal-scraping-architect same pattern.
3. **Overlap clusters burning context.** (a) Database trio: database-designer / database-schema-designer / sql-database-assistant — sql-database-assistant alone covers ~90%; (b) release pair: release-manager vs changelog-generator (changelog-generator is the wired, lean one); (c) observability-designer vs slo-architect (slo-architect is strictly better on the SLO half).
4. **Byte-identical dual-published copies.** slo-architect, chaos-engineering, kubernetes-operator, feature-flags-architect each exist in both `engineering/skills/` and `engineering/<name>/skills/<name>/` (verified `diff` identical). No single source of truth; edits will diverge.
5. **Counter and registry drift.** Bundle index SKILL.md says "25 advanced engineering skills"; its plugin.json says 40; the marketplace description for `engineering-advanced-skills` lists skills (llm-cost-optimizer, prompt-governance, behuman, code-tour, demo-video, data-quality-auditor, statistical-analyst, llm-wiki…) that live in standalone plugin folders OUTSIDE the manifest's `"skills": ["./skills"]` path. Separately, 5 plugins with valid plugin.json (behuman, claude-coach, grill-with-docs, llm-cost-optimizer, prompt-governance) are not registered in marketplace.json at all.
6. **Dead cross-references.** env-secrets-manager points to `engineering/senior-secops`, `engineering/infrastructure-as-code`, `engineering/container-orchestration` (none exist; senior-secops lives in engineering-team/); sql-database-assistant points to nonexistent `observability-platform`; focused-fix references external `superpowers:*` skills; command-guide is entirely about a foreign ecosystem.
7. **Freshness spots.** rag-architect: `text-embedding-ada-002` as "quality model", "$70/month Pinecone 1M vectors" — 2023/24 facts presented as current. command-guide: `/fast` "(Opus 4.6 only)". api-design-reviewer example timestamps "2024-…".
8. **Reference quality is bimodal.** v2.0-era references (rag-architect, dependency-auditor, agent-designer) are uncited encyclopedic prose a frontier model regenerates on demand; v2.6+ references cite canon by name (Evans/Nygard/Google SRE Workbook/Pocock).
9. **By-design script exceptions partly documented.** autoresearch evaluators carry "DO NOT MODIFY — fixed evaluator" headers, but the SKILL.md never states they intentionally fail `--help`; security-guidance hook's stdin contract IS documented in its SKILL.md (good).
## Per-skill findings
### engineering/skills/agent-designer
Verdict: REWRITE
Issues:
- Entire 279-line body is generic multi-agent taxonomy (Supervisor/Swarm/Pipeline pros-cons) — A2/A5 fail; a frontier model knows all of it.
- 3 working scripts (`agent_planner.py`, `tool_schema_generator.py`, `agent_evaluator.py`, all pass `--help`) are never mentioned in SKILL.md — A3 fail; assets/expected_outputs unused.
- Description is bare trigger sentence with no mention of tools.
- Overlaps agent-workflow-designer and workflow-builder.
Verify: `python3 engineering/skills/agent-designer/agent_planner.py --help` exits 0 AND SKILL.md contains the literal string `agent_planner.py` with a runnable invocation; SKILL.md < 150 lines; `grep -c "Pros:" SKILL.md` returns 0.
### engineering/skills/agent-workflow-designer
Verdict: OPTIMIZE
Issues:
- 83-line body is mostly headers; pattern map duplicates `references/workflow-patterns.md` one-liners.
- No verification loop — scaffolder output is never validated by a named next step.
- Scope collision with workflow-builder (Claude Code Workflow tool) and agent-designer; needs explicit "NOT for" routing.
Verify: `python3 scripts/workflow_scaffolder.py sequential --name t` exits 0 and emits JSON; SKILL.md gains a "When NOT to use" block naming workflow-builder.
### engineering/skills/api-design-reviewer
Verdict: OPTIMIZE
Issues:
- Lines 41–333 restate REST conventions/pagination/status codes any frontier model knows — cut to references or delete.
- Tools section describes features but the only invocations are inside CI YAML examples; no first-class Quick Start CLI.
- Example timestamp `2024-02-16` (A6 nit).
Verify: `python3 scripts/api_linter.py --help` exits 0; SKILL.md has a Quick Start with all 3 script invocations; body ≤ 200 lines.
### engineering/skills/codebase-onboarding
Verdict: OPTIMIZE
Issues:
- 84 lines, single analyzer script; "Tailor output depth by audience" is the only non-obvious content.
- No verification loop (generated doc never validated against repo facts).
Verify: `python3 scripts/codebase_analyzer.py . --json` exits 0 and emits JSON with language/file-count keys; SKILL.md adds a post-generation check (e.g. "every setup command in the doc was executed once").
### engineering/skills/command-guide
Verdict: CUT-OR-MERGE
Issues:
- Documents commands/agents from the ECC ecosystem (`planner`, `build-error-resolver`, `tdd-guide`, `/build-fix`, `/learn`, `/remember`) — none ship in this repo; actively misleads the model into invoking nonexistent tools.
- `/fast` "(Opus 4.6 only)" — stale model gating (A6).
- Zero scripts, zero references; auto-trigger table tells the model to "immediately invoke" agents that don't exist here.
Verify (if kept at all): every command/agent named in the file resolves to a file in this repo (`grep -o '/[a-z-]*' SKILL.md` cross-checked against commands/); otherwise delete from plugin.
### engineering/skills/database-designer
Verdict: CUT-OR-MERGE (fold unique tables into sql-database-assistant)
Issues:
- "The included tools automate common analysis" but no script invocation anywhere; 3 root scripts orphaned (A3).
- JOIN/CTE/window-function content is textbook (A2); decision matrices duplicate sql-database-assistant's.
- Three-way overlap with database-schema-designer and sql-database-assistant; cross-refs to both admit it.
Verify: after merge, `engineering/skills/sql-database-assistant/SKILL.md` contains the sharding/replication tables; `schema_analyzer.py`/`index_optimizer.py`/`migration_generator.py` either wired into sql-database-assistant or deleted.
### engineering/skills/database-schema-designer
Verdict: CUT-OR-MERGE
Issues:
- No scripts at all; SKILL.md is one worked example + RLS snippets.
- Seed-data example is syntactically broken (`name: "fakercompanycatchphrase"` — missing comma, dead faker call, line ~155).
- ERD/normalization mandate duplicates database-designer's claims.
Verify: RLS policy block and pitfalls table migrated into the surviving database skill; broken seed example deleted or fixed to parse with `npx tsc --noEmit`.
### engineering/skills/dependency-auditor
Verdict: REWRITE
Issues:
- ~250 of 337 lines are brochure ("Use Cases & Applications", "Future Enhancements", "Metrics & KPIs") — A2/A7 fail.
- Claims "built-in vulnerability database with 500+ CVE patterns", live "PyPI/npm advisory" cross-referencing — SKILL.md's own scripts are offline pattern matchers; over-claims capability.
- Quick Start has 3 CLI lines buried at the bottom; no output-consumption step, no verification loop.
Verify: `python3 scripts/dep_scanner.py --help` exits 0; rewritten SKILL.md ≤ 150 lines, leads with the 3 CLIs + JSON keys consumed; no "Future Enhancements"/"Planned Features" headings remain.
### engineering/skills/engineering-advanced-skills
Verdict: OPTIMIZE
Issues:
- H1/body says "25 advanced engineering skills"; plugin.json says 40; folder has 39 + index — three different counts.
- Quick Start path `/read engineering/agent-designer/SKILL.md` is wrong (real path `engineering/skills/agent-designer/SKILL.md`).
- Table lists 25 of 39 skills; missing the reliability quartet, ship-gate, self-eval, tc-tracker, etc.
Verify: `ls engineering/skills | wc -l` matches the count stated in SKILL.md and plugin.json description; every path in the table resolves.
### engineering/skills/interview-system-designer
Verdict: OPTIMIZE
Issues:
- Hiring-process skill living in the engineering plugin — domain misfit (product-team/c-level fit better).
- 4 scripts present, only `interview_planner.py` wired; 59-line body with generic best practices.
Verify: all shipped scripts referenced with exact CLI in SKILL.md or removed; `python3 scripts/interview_planner.py --role "SWE" --level senior --json` exits 0 with JSON.
### engineering/skills/migration-architect
Verdict: REWRITE
Issues:
- 477 lines; Strangler Fig/CDC/blue-green content is textbook (A2); "Communication Templates" and "Success Metrics" sections are filler (A7).
- Scripts (`migration_planner.py`, `compatibility_checker.py`, `rollback_generator.py`) appear only as bullet names + one CI YAML snippet — no Quick Start CLI (A3).
- No verification loop; checklists are prose, not machine-checkable.
Verify: `python3 engineering/skills/migration-architect/migration_planner.py --help` exits 0; rewritten SKILL.md ≤ 200 lines with all 3 CLIs and a "plan must pass compatibility_checker with 0 CRITICAL" gate.
### engineering/skills/observability-designer
Verdict: REWRITE
Issues:
- 268 lines of golden-signals/RED/USE/three-pillars prose — pure frontier-model knowledge (A2/A5).
- "Scripts Overview" describes I/O shapes but gives zero runnable commands (A3); scripts pass `--help`.
- Overlaps slo-architect (which does the SLO half with thresholds + math + refusal gates); this skill should shrink to dashboards + alert-noise tooling and route SLO work to slo-architect.
Verify: `python3 scripts/slo_designer.py --help`, `alert_optimizer.py --help`, `dashboard_generator.py --help` all exit 0 AND appear as exact CLIs in SKILL.md; "When NOT to use → slo-architect" block present.
### engineering/skills/rag-architect
Verdict: REWRITE
Issues:
- Stale facts as current: `text-embedding-ada-002` as the quality tier, "Pinecone $70/month for 1M vectors", model lists from 2023/24 (A6).
- 3 root scripts (`chunking_optimizer.py`, `rag_pipeline_designer.py`, `retrieval_evaluator.py`, all pass `--help`) never referenced in SKILL.md (A3).
- 318 lines of chunking/retrieval taxonomy a frontier model knows; only 1 reference doc, uncited (A7).
Verify: `python3 engineering/skills/rag-architect/chunking_optimizer.py --help` exits 0 AND is invoked in SKILL.md; zero occurrences of `ada-002` / hardcoded vendor prices; body ≤ 200 lines.
### engineering/skills/release-manager
Verdict: CUT-OR-MERGE (into changelog-generator)
Issues:
- 489-line SemVer/Git-Flow/conventional-commits textbook (A2); changelog-generator already ships the wired, lean version of the changelog/bump core.
- 3 root scripts named in "Key Components" but never invoked (A3).
- Hotfix SLAs and rollback triggers are the only practitioner content — migrate those tables.
Verify: hotfix-severity and rollback-trigger tables present in the surviving skill; `version_bumper.py`/`release_planner.py` wired with exact CLI or deleted; no duplicate conventional-commit spec across the two skills.
### engineering/skills/runbook-generator
Verdict: OPTIMIZE
Issues:
- 76 lines, one template-skeleton script, generic best practices; weakest of the wired DevOps set.
- No verification loop (runbook never validated — e.g., "every command block has an expected-output check").
Verify: `python3 scripts/runbook_generator.py payments-api --owner x` exits 0 and emits the standard sections; SKILL.md adds a post-generation checklist the model executes (rollback section non-empty, every step has a verify line).
### engineering/skills/skill-tester
Verdict: REWRITE
Issues:
- 390 lines, heavy brochure: "Performance & Scalability", "Security & Safety", "Future Enhancements", "Conclusion" (A7).
- CLI examples lack paths (`skill_validator.py path/to/skill` won't run from repo root); one example references nonexistent `trend_analyzer.py` (phantom script, A3).
- Tier line-count requirements conflict with write-a-skill's "SKILL.md under 100 lines" doctrine — repo-internal contradiction.
Verify: `python3 engineering/skills/skill-tester/scripts/skill_validator.py engineering/skills/self-eval --json` exits 0 with JSON; no reference to `trend_analyzer.py`; body ≤ 200 lines.
### engineering/skills/tech-debt-tracker
Verdict: REWRITE
Issues:
- Body is a 6-week "Implementation Roadmap" + aspirational KPIs ("25% reduction in debt interest rate") — filler, zero operational instructions (A2/A5).
- 5 scripts incl. `debt_scanner.py`/`debt_prioritizer.py`/`debt_dashboard.py` all pass `--help` but SKILL.md contains not one CLI invocation (A3) — worst wiring gap in the domain relative to tooling quality.
- 4 references + 4 assets unreferenced from the body (A7).
Verify: SKILL.md Quick Start runs all 3 core scripts with exact flags; `python3 scripts/debt_scanner.py --help` exits 0; scan→prioritize→dashboard pipeline shows which JSON keys flow between steps.
### engineering/claude-coach
Verdict: OPTIMIZE
Issues:
- Frontmatter has duplicate/case-variant keys (`Name:` + `name:`, `Version: 1.0.0` + `version: 2.9.0`, stray `Tier/Category/Dependencies`) — undefined parse behavior.
- Lines 145–205 re-paste Name/Description/Features/Usage (README content) after the body ends — duplication (A7).
- Scripts listed at the very bottom with no CLI; `coach_tip_classifier.py` is core to Rule 5 but never invoked.
Verify: `python3 -c "import yaml,io; yaml.safe_load(open('engineering/claude-coach/skills/claude-coach/SKILL.md').read().split('---')[1])"` yields exactly one `name`/`version`; `python3 scripts/coach_tip_classifier.py --help` exits 0 and appears as a CLI in the body.
### engineering/universal-scraping-architect
Verdict: OPTIMIZE
Issues:
- 3 scripts (`validate_extraction.py`, `firecrawl_example.py`, `local_bs4_example.py`) never referenced in SKILL.md (A3).
- Agent (`cs-scraping-architect.md`, 6 lines) and command (`cs-scrape.md`, 6 lines) are placeholders — B3/C3 fail.
- "You are an expert…" opener (A2 filler); non-stdlib deps (firecrawl/pandas/bs4) acceptable (BYOK documented) but should be listed per-script.
- Layout anomaly: only engineering plugin with SKILL.md at plugin root (no `skills/` dir).
Verify: `python3 engineering/universal-scraping-architect/scripts/validate_extraction.py --help` exits 0 and is invoked in SKILL.md step 4 ("Validate & Clean"); agent file ≥ 40 lines with tools + triggers or deleted.
## KEEP-verdict verification criteria
- **api-test-suite-builder** — Next.js route-scan command from SKILL.md runs against a sample app dir without error; auth matrix table retains all 6 rows.
- **browser-automation** — `python3 scripts/anti_detection_checker.py --help` exits 0; all 3 referenced reference files exist.
- **changelog-generator** — `printf 'feat: x\nfix: y\n' | python3 scripts/generate_changelog.py --next-version v1.0.0 --format json` exits 0 with `Added`/`Fixed` sections; `commit_linter.py --strict` exits non-zero on `bad message`.
- **chaos-engineering** — `python3 scripts/blast_radius_calculator.py --traffic-share 0.05 --user-pop 1000000 --duration-min 15` exits 0, output contains GREEN/YELLOW/RED; bundle and standalone copies stay byte-identical (`diff -r`) until deduped.
- **ci-cd-pipeline-builder** — `python3 scripts/stack_detector.py --repo . --format json` exits 0 with detected-language keys; generated YAML parses (`python3 -c "import yaml,sys; yaml.safe_load(open('out.yml'))"`).
- **env-secrets-manager** — `python3 scripts/env_auditor.py . --json` exits 0 with severity-tagged findings; cross-reference table contains no path that fails `ls`.
- **feature-flags-architect** — `python3 scripts/rollout_planner.py --population 100000 --target-percent 100 --duration-days 14 --strategy ring` exits 0 with a phased table; `kill_switch_audit.py --help` exits 0.
- **focused-fix** — 5-phase headings (SCOPE/TRACE/DIAGNOSE/FIX/VERIFY) and the 3-strike escalation rule remain; `superpowers:` references either resolve or are reworded as optional externals.
- **full-page-screenshot** — `node scripts/full-page-screenshot.mjs --check` exits with documented status; anti-pattern table intact.
- **git-worktree-manager** — `python3 scripts/worktree_manager.py --help` and `worktree_cleanup.py --help` exit 0; validation checklist (ports file, env copy) retained.
- **kubernetes-operator** — `python3 scripts/crd_validator.py --help` exits 0; capability levels L1–L5 retained; dedupe with bundle copy.
- **mcp-server-builder** — `python3 scripts/openapi_to_mcp.py --help` and `mcp_validator.py --help` exit 0; strict mode returns non-zero on a manifest with a duplicate tool name.
- **monorepo-navigator** — `python3 scripts/monorepo_analyzer.py . --json` exits 0; pitfalls table keeps the `--filter` and `git filter-repo` rows.
- **performance-profiler** — `python3 scripts/performance_profiler.py . --json` exits 0; before/after template and "Measure First" rule retained.
- **pr-review-expert** — security-scan grep block runs against a sample diff without syntax errors; 30+ item checklist count ≥ 30.
- **secrets-vault-manager** — 3 tool names in the Tools table map to existing files in scripts/ (add exact CLI when touched); Vault HCL snippets parse visually.
- **self-eval** — composite matrix unchanged (Low ambition caps at 2; 5 requires High+Strong); scores append to `.self-eval-scores.jsonl`.
- **ship-gate** — `references/checks.md` and `references/patterns.md` exist; category table sums (55 auto + 27 manual) match checks.md entries.
- **skill-security-auditor** — `python3 scripts/skill_security_auditor.py engineering/skills/self-eval --json` exits 0 with verdict ∈ {PASS, WARN, FAIL}.
- **slo-architect** — `python3 scripts/error_budget_calculator.py --target 99.9 --window-days 30` exits 0 and prints 43.20 min allowed downtime (verified this audit); `slo_review.py` flags `target ≥ 99.99` docs.
- **spec-driven-workflow** — `python3 scripts/spec_validator.py --help` and `test_extractor.py --help` exit 0; Iron Law + bounded-autonomy STOP list retained.
- **sql-database-assistant** — `python3 scripts/query_optimizer.py --query "SELECT * FROM t" --dialect postgres` exits 0 with findings; dialect table retains all 4 engines.
- **tc-tracker** — `python3 scripts/tc_init.py --project T --root /tmp/tc-test && python3 scripts/tc_validator.py --registry /tmp/tc-test/docs/TC/tc_registry.json` both exit 0; state machine rejects `planned → deployed`.
- **agenthub** — `python3 scripts/hub_init.py --help`, `dag_analyzer.py --help`, `result_ranker.py --help` exit 0; all 7 `/hub:*` sub-skills name a script or Agent-tool call.
- **autoresearch-agent** — `python3 scripts/run_experiment.py --help` exits 0; evaluators intentionally fail `--help` (fixed contract) — add one sentence to SKILL.md documenting this; `setup_experiment.py --help` exits 0.
- **behuman** — Show/Quiet mode contract + 3 worked examples retained; token-cost table present. Register in marketplace or document why not.
- **caveman** — Matt's persistence + auto-clarity rules verbatim; `python3 scripts/caveman_lint.py "Sure! I'd be happy to help" ` flags filler.
- **code-tour** — schema block contains `$schema: https://aka.ms/codetour-schema`; validation checklist (verified line numbers, ≤2 content steps) intact.
- **data-quality-auditor** — `python3 scripts/data_profiler.py --help`, `missing_value_analyzer.py --help`, `outlier_detector.py --help` all exit 0; DQS weights sum to 100%.
- **demo-video** — fallback ladder (MCPs → manual build.sh) retained; output artifact list (scenes/, narration/, scenes.json, build.sh) unchanged.
- **docker-development** — `python3 scripts/dockerfile_analyzer.py --help` and `compose_validator.py --help` exit 0; 3 multi-stage patterns + base-image decision tree retained.
- **grill-me / grill-with-docs** — one-question-per-turn + recommended-answer rules verbatim; `python3 scripts/context_md_linter.py --help` (grill-with-docs) exits 0. Register grill-with-docs in marketplace.
- **handoff** — `mktemp` convention + no-duplication rule verbatim; 5 sections list unchanged.
- **helm-chart-builder** — `python3 scripts/chart_analyzer.py --help` exits 0; scaffold tree includes pdb.yaml + networkpolicy.yaml.
- **karpathy-coder** — `python3 scripts/complexity_checker.py --help` and `diff_surgeon.py --help` exit 0; 4 principles + relax conditions retained.
- **llm-cost-optimizer** — ROI-ordered 6 techniques with % ranges retained; proactive-flag table (max_tokens unset, >2k-token system prompt) intact; model-tier examples refreshed when model names rotate.
- **llm-wiki** — `python3 scripts/init_vault.py --help` and `lint_wiki.py --help` exit 0; Iron rule (never write raw/) retained; 8 references exist.
- **prompt-governance** — registry YAML schema + eval-type table retained; golden-dataset minimums (20/100+) intact.
- **security-guidance** — `echo '{}' | python3 hooks/security_reminder_hook.py` exits 0 (clean input); pattern table has all 12 rows; attribution block in plugin.json present.
- **statistical-analyst** — `python3 scripts/hypothesis_tester.py --test ztest --control-n 5000 --control-x 250 --treatment-n 5000 --treatment-x 310` exits 0 reporting +1.2pp (verified this audit); effect-size tables intact.
- **terraform-patterns** — `python3 scripts/tf_module_analyzer.py --help` and `tf_security_scanner.py --help` exit 0; review checklist (state, providers, security) retained.
- **workflow-builder** — `python3 scripts/validate_workflow.py --sample` and `workflow_intake.py --help` exit 0; hard-rules list (pure-literal meta, no Date.now, thunks) retained.
- **write-a-skill** — Matt's 3-phase flow + description requirements verbatim; `python3 scripts/skill_review_checklist_runner.py engineering/write-a-skill/skills/write-a-skill` exits 0.
## Agents
| Agent | Verdict | Issue |
|---|---|---|
| agenthub/hub-coordinator | KEEP | Strong: scoped tools allowlist/denylist, hard rules, re-spawn policy |
| autoresearch/experiment-runner | OPTIMIZE | No YAML frontmatter at all (no name/description/tools) — B1 fail; body is good |
| caveman/cs-caveman-mode | KEEP | — |
| claude-coach/cs-claude-coach | KEEP | — |
| grill-me/cs-grill-master | KEEP | Distinct voice + forcing-question pattern |
| grill-with-docs/cs-grill-with-docs | KEEP | — |
| handoff/cs-handoff-author | KEEP | Hard refusals make persona behavioral, not adjectival |
| karpathy-coder/karpathy-reviewer | KEEP | Model exemplar: tool allow/deny lists, exact workflow, report shape |
| llm-wiki/wiki-ingestor | KEEP | — |
| llm-wiki/wiki-librarian | KEEP | — |
| llm-wiki/wiki-linter | KEEP | — |
| universal-scraping-architect/cs-scraping-architect | REWRITE | 6-line placeholder: no tools, no triggers, no workflow — B1/B2/B3 fail |
| workflow-builder/cs-workflow-architect | KEEP | — |
| write-a-skill/cs-skill-author | KEEP | — |
## Commands
| Command | Verdict | Issue |
|---|---|---|
| caveman/cs-caveman | KEEP | Enforces persistence + auto-clarity; wires 3 scripts |
| claude-coach/cs-claude-coach | KEEP | Handles $ARGUMENTS, fixed activation sequence |
| grill-me/cs-grill-me | KEEP | — |
| grill-with-docs/cs-grill-with-docs | KEEP | — |
| handoff/cs-handoff | KEEP | — |
| karpathy-coder/karpathy-check | KEEP | Orchestrates 2 scripts + sub-agent — earns its slot |
| llm-wiki/wiki-init | KEEP | — |
| llm-wiki/wiki-ingest | KEEP | — |
| llm-wiki/wiki-query | KEEP | — |
| llm-wiki/wiki-lint | KEEP | — |
| llm-wiki/wiki-log | KEEP | — |
| universal-scraping-architect/cs-scrape | CUT-OR-MERGE | 6-line placeholder; a bare prompt does strictly more — C3 fail; no $ARGUMENTS handling |
| workflow-builder/cs-workflow-build | KEEP | — |
| write-a-skill/cs-write-a-skill | KEEP | — |
Note: agenthub's 7 `/hub:*` and autoresearch's 5 `/ar:*` surfaces ship as command-style sub-skills (frontmatter `command:` key) rather than `commands/*.md` files — all are substantive and wired; counted under their parent skill verdicts.
## Plugin manifests
1. **engineering-advanced-skills (engineering/.claude-plugin/plugin.json + marketplace.json:227)** — description claims skills not shipped by the manifest: llm-cost-optimizer, prompt-governance, behuman, code-tour, demo-video, data-quality-auditor, statistical-analyst, llm-wiki live in standalone plugin folders, while `"skills": ["./skills"]` only packages `engineering/skills/` (40 dirs). E2 fail.
2. **Triple count mismatch** — bundle index SKILL.md "25 skills" vs plugin description "40" vs 39 actual skills + 1 index dir.
3. **Five orphan plugins** — behuman, claude-coach, grill-with-docs, llm-cost-optimizer, prompt-governance have valid `.claude-plugin/plugin.json` but no marketplace.json entry (handoff is registered as `handoff-engineering`; these five aren't registered at all).
4. **Dual-published duplicates** — slo-architect, chaos-engineering, kubernetes-operator, feature-flags-architect exist byte-identical in two paths; only the standalone copies are marketplace-registered, but the bundle copies also ship via engineering-advanced-skills → users installing both get duplicates with identical trigger descriptions.
5. **Version coherence** — workflow-builder plugin.json is `1.0.0` while every sibling is `2.9.0` (marketplace itself is at v2.10.x per root CLAUDE.md — domain-wide version lag is cosmetic but uniform).

246
audit/newgen-2026-06/marketing.md Normal file
View file

@ -0,0 +1,246 @@
# Domain audit: marketing-skill/ + marketing/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 49 (47 in marketing-skill/skills + video-content-strategist + marketing/landing) · Agents: 6 · Commands: 4 · Plugins: 5
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| ab-test-setup | OPTIMIZE | Orphan script `sample_size_calculator.py` never named in SKILL.md |
| ad-creative | OPTIMIZE | Stale Meta ">20% image text = reduced distribution" rule (retired 2021) presented as current |
| aeo | KEEP | — |
| ai-seo | CUT-OR-MERGE | Near-total overlap with `aeo` (same goal, no tooling); two skills own one lane |
| analytics-tracking | OPTIMIZE | GA4 "Conversions" terminology (renamed Key events, Mar 2024); script wiring vague |
| app-store-optimization | KEEP | — |
| brand-guidelines | CUT-OR-MERGE | 93-line generic checklist a frontier model already knows; hardcoded Anthropic identity |
| campaign-analytics | KEEP | — |
| churn-prevention | KEEP | — |
| cold-email | KEEP | — |
| competitor-alternatives | OPTIMIZE | Orphan script `comparison_matrix_builder.py` |
| content-creator | CUT-OR-MERGE | Deprecated redirect still shipping 4 refs + 1 asset + agent + zip |
| content-humanizer | OPTIMIZE | 2/6 on repo checklist (worst in domain); AI-tell list itself aging ("delve" era) |
| content-production | OPTIMIZE | 3 of 4 scripts orphaned in SKILL.md |
| content-strategy | OPTIMIZE | Hollow core ("→ see references"); orphan `topic_cluster_mapper.py` |
| copy-editing | OPTIMIZE | Both scripts (`ai_content_detector`, `readability_scorer`) orphaned |
| copywriting | OPTIMIZE | Orphan `headline_scorer.py` |
| email-sequence | OPTIMIZE | Phantom `../../tools/REGISTRY.md` + 5 integration guide links; none exist |
| form-cro | OPTIMIZE | Hollow core; orphan `form_field_analyzer.py` |
| free-tool-strategy | KEEP | — |
| launch-strategy | OPTIMIZE | 74-line shell; orphan `launch_readiness_scorer.py` |
| marketing-context | OPTIMIZE | Writes `.agents/marketing-context.md` while siblings read 2 other paths |
| marketing-demand-acquisition | OPTIMIZE | `updated: 2025-01`, "q1-2025" examples; persona-narrow (Series A+ EU/US) |
| marketing-ideas | KEEP | — |
| marketing-ops | OPTIMIZE | Router missing 11 of 47 skills (incl. aeo, webinar, ASO, x-twitter) |
| marketing-psychology | KEEP | — |
| marketing-skills | CUT-OR-MERGE | Index-as-skill: stale counts (42/7/27 vs actual 47/8/58+), all example paths broken |
| marketing-strategy-pmm | KEEP | — |
| onboarding-cro | OPTIMIZE | Orphan `activation_funnel_analyzer.py` |
| page-cro | OPTIMIZE | Orphan `conversion_audit.py` |
| paid-ads | OPTIMIZE | Phantom tools/REGISTRY.md; 2 orphan scripts; "2024Q1/Mar24" naming examples |
| paywall-upgrade-cro | KEEP | — |
| popup-cro | OPTIMIZE | Hollow core ("→ see references"); zero tooling |
| pricing-strategy | KEEP | — |
| programmatic-seo | OPTIMIZE | Orphan `url_pattern_generator.py` |
| prompt-engineer-toolkit | REWRITE | All 3 references are stubs (328 B / 675 B / 1.5 KB); body ≠ marketing description |
| referral-program | KEEP | — |
| schema-markup | KEEP | — |
| seo-audit | OPTIMIZE | Hollow core; both scripts orphaned |
| signup-flow-cro | OPTIMIZE | Orphan `funnel_drop_analyzer.py` |
| site-architecture | KEEP | — |
| social-content | KEEP | — |
| social-media-analyzer | KEEP | — |
| social-media-manager | OPTIMIZE | Orphan `social_calendar_generator.py` |
| webinar-marketing | OPTIMIZE | `webinar_funnel_scorer.py` has no argparse — `--help` crashes (only D1 fail in domain) |
| x-twitter-growth | KEEP | — |
| youtube-full | KEEP | — |
| video-content-strategist | KEEP | — |
| landing (marketing/) | KEEP | — |
Verdict counts: **KEEP 20 · OPTIMIZE 24 · REWRITE 1 · CUT-OR-MERGE 4**
## Domain-level findings
1. **24 orphan scripts (systemic A3 failure).** Scripts exist and pass `--help` (583/593 repo sweep) but are never named in their own SKILL.md, so a model loading the skill never knows they exist: ab-test-setup, cold-email, competitor-alternatives, content-production (×3), content-strategy, copy-editing (×2), copywriting, email-sequence, form-cro, launch-strategy, marketing-context, marketing-ops, onboarding-cro, page-cro, paid-ads (×2), programmatic-seo, seo-audit (×2), signup-flow-cro, social-media-manager. One repo-wide wiring PR fixes ~half the OPTIMIZE verdicts.
2. **Context-file path schism (foundational pattern silently no-ops).** 19 skills check `.claude/product-marketing-context.md`, 16 check `marketing-context.md`, and the `marketing-context` skill that *creates* the file writes `.agents/marketing-context.md`. Whatever path the user's file is at, half the domain won't find it. Pick one canonical path.
3. **Count drift in 4 places.** marketing-skills SKILL.md: "42 skills / 7 pods / 27 tools"; marketplace.json: "44 skills / 7 pods"; plugin.json + CLAUDE.md: "45 skills / 8 pods"; actual: 47 skill dirs (incl. 1 deprecated redirect and 1 index). All example invocation paths in marketing-skills/SKILL.md omit the `skills/` segment and are broken.
4. **Duplicate AI-search lane.** `aeo` (v2.7.3 port, 3 working scripts, calibrated industry thresholds) and `ai-seo` (older, prose-only) both own "get cited by ChatGPT/Perplexity." The router routes AI-search queries to `ai-seo` and doesn't know `aeo` exists. Merge ai-seo's bot-access/robots.txt + content-pattern material into aeo references.
5. **Router drift.** marketing-ops claims to be the central router but its matrix omits 11 skills: aeo, app-store-optimization, brand-guidelines, marketing-demand-acquisition, marketing-strategy-pmm, prompt-engineer-toolkit, social-media-analyzer, webinar-marketing, x-twitter-growth, youtube-full (+ the marketing-skills index).
6. **Plugin hygiene.** marketing-skill/ root ships 5 .zip archives (~120 KB) and 4 internal planning docs (MARKETING-AUDIT-REPORT.md, -EXECUTION-PLAN.md, -EXPANSION-PLAN.md, marketing_skills_roadmap.md — 1,194 lines) inside the public plugin folder.
7. **Phantom references.** email-sequence and paid-ads link `../../tools/REGISTRY.md` and 5 `../../tools/integrations/*.md` guides; no `tools/` directory exists anywhere in marketing-skill/.
8. **Freshness is better than feared, with 3 specific stales:** Meta's 20%-image-text rule (retired 2021) in ad-creative SKILL + reference; GA4 "Conversions" (renamed "Key events" March 2024) in analytics-tracking; 2024/2025 dating in paid-ads naming examples and marketing-demand-acquisition metadata. x-twitter-growth explicitly labels its algorithm table "2025-2026" — the right pattern.
9. **New-gen model lens: the domain splits cleanly.** Skills that pair calibrated thresholds with deterministic scorers (aeo, campaign-analytics, ASO, churn-prevention, webinar funnel math, landing's validator gate) earn their context. ~8 skills are persona-prompt shells ("Core Principles → see references") whose body adds nothing a frontier model lacks — the value is locked in references the SKILL.md barely indexes.
10. **video-content-strategist plugin not registered.** It has `.claude-plugin/plugin.json` but no entry in root marketplace.json (E3).
## Per-skill findings
### ab-test-setup — OPTIMIZE
Issues: (1) `scripts/sample_size_calculator.py` orphaned — SKILL.md points users to external web calculators instead of its own tool; (2) sample-size quick table good but unverified against the script's output.
Verify: `python3 scripts/sample_size_calculator.py --help` exits 0; SKILL.md contains the literal string `sample_size_calculator.py` with an invocation; script output for baseline 5%/MDE 20% matches the table's ~7k/variant.
### ad-creative — OPTIMIZE
Issues: (1) "Image text <20%" Meta rule stated in SKILL.md spec table and references/platform-specs.md as causing "reduced distribution" — Meta retired the enforcement in 2021; (2) `ad_copy_validator.py` wired but invocation lacks args/format.
Verify: `grep -c "20%" references/platform-specs.md` returns 0 (or the claim is rewritten as historical); `python3 scripts/ad_copy_validator.py --help` exits 0; SKILL.md shows an exact CLI line with input format.
### ai-seo — CUT-OR-MERGE
Issues: (1) duplicates `aeo`'s mission with zero tooling (0 scripts vs aeo's 3); (2) router sends AI-search traffic here, starving aeo; (3) unique value (robots.txt bot matrix, 6 content patterns, GSC AI Overviews monitoring) belongs in aeo/references.
Verify: after merge, `marketing-ops/SKILL.md` routes "AI search/AEO/GEO" triggers to `aeo`; aeo references contain the bot-access table; `ai-seo/` directory removed or reduced to a redirect stub ≤ 30 lines.
### analytics-tracking — OPTIMIZE
Issues: (1) "GA4 → Admin → Conversions" + "Max 30 conversion events" uses pre-2024 terminology (now Key events); (2) `tracking_plan_generator.py` only mentioned in passing in the artifacts table — no CLI invocation or output contract.
Verify: SKILL.md says "Key events"; SKILL.md contains `python3 scripts/tracking_plan_generator.py` with args; `python3 scripts/tracking_plan_generator.py --json` emits parseable JSON.
### brand-guidelines — CUT-OR-MERGE
Issues: (1) 93 lines of generic audit checklist any frontier model reproduces unprompted (A5 fail); (2) "Anthropic Brand Identity" section hardcodes one company's identity into a generic skill; (3) no scripts, 1 reference; (4) overlaps marketing-context §10-11 (Brand Voice + Style Guide).
Verify: brand dimensions folded into marketing-context template (§10/§11 expanded); references/brand-identity-and-framework.md content preserved or moved; routing matrix no longer lists it OR skill rewritten with a deterministic brand-audit scorer.
### competitor-alternatives — OPTIMIZE
Issues: (1) `comparison_matrix_builder.py` orphaned; (2) otherwise strong 4-format framework.
Verify: SKILL.md names `comparison_matrix_builder.py` with exact CLI + consuming step; script `--help` exits 0.
### content-creator — CUT-OR-MERGE
Issues: (1) deprecated redirect skill still ships 4 references + 1 asset that the redirect never uses (A7); (2) `cs-content-creator` agent and `personas/content-strategist` still target it; (3) `content-creator.zip` lingers in plugin root; (4) routing duplicate of one row in marketing-ops.
Verify: references/ + assets/ removed (≤ 1 file redirect remains) or skill deleted with router rows updated; `grep -r "content-creator" agents/` returns no skill-target hits; zip deleted.
### content-humanizer — OPTIMIZE
Issues: (1) 2/6 on repo's own checklist (261 lines, time-sensitive content flags); (2) the AI-tell vocabulary ("delve", "landscape", em-dash) is itself a 2023-24 snapshot — new-gen models have different tells, list needs dating + refresh cadence; (3) "HubSpot published... in 2023" dated example; (4) `humanizer_scorer.py` wired only in artifacts table, no CLI contract.
Verify: `skill_review_checklist_runner.py content-humanizer` ≥ 4/6; SKILL.md shows `python3 scripts/humanizer_scorer.py <file>` with score interpretation thresholds; references/ai-tells-checklist.md carries a "last validated" date.
### content-production — OPTIMIZE
Issues: (1) `brand_voice_analyzer.py`, `content_quality_gates.py`, `seo_optimizer.py` all orphaned — only `content_scorer.py` is named; (2) marketing-skills index advertises these very scripts while the owning skill doesn't.
Verify: all 4 scripts named in SKILL.md with exact CLI; `python3 scripts/content_scorer.py --json` emits JSON with a 0-100 score; Mode 3 consumes brand_voice_analyzer + content_quality_gates outputs by name.
### content-strategy — OPTIMIZE
Issues: (1) core knowledge deferred ("Searchable vs Shareable → see references") leaving a 127-line shell; (2) `topic_cluster_mapper.py` orphaned.
Verify: SKILL.md names `topic_cluster_mapper.py` with invocation; the searchable-vs-shareable decision rule (not just pointer) appears inline; script `--help` exits 0.
### copy-editing — OPTIMIZE
Issues: (1) both scripts (`ai_content_detector.py`, `readability_scorer.py`) orphaned; (2) Seven Sweeps framework is genuinely good — wiring is the only gap.
Verify: each sweep that has a matching script names it (Sweep on AI patterns → ai_content_detector; clarity → readability_scorer); both `--help` exit 0; outputs consumed in the sweep workflow text.
### copywriting — OPTIMIZE
Issues: (1) `headline_scorer.py` orphaned; (2) headline formula section never points at its own scorer.
Verify: SKILL.md "Above the Fold" section invokes `python3 scripts/headline_scorer.py "<headline>"`; script exits 0 with a numeric score.
### email-sequence — OPTIMIZE
Issues: (1) phantom `../../tools/REGISTRY.md` + 5 `tools/integrations/*.md` links — directory doesn't exist; (2) `sequence_analyzer.py` orphaned; (3) core principles deferred to one reference, 135-line shell.
Verify: `grep -c "tools/REGISTRY" SKILL.md` returns 0; `sequence_analyzer.py` named with CLI; all relative links in SKILL.md resolve (`find` check).
### form-cro — OPTIMIZE
Issues: (1) `form_field_analyzer.py` orphaned; (2) hollow core ("Core Principles → see references").
Verify: script named with CLI and consumed in the audit output format; field-count/friction thresholds inline in SKILL.md (not only in playbook).
### launch-strategy — OPTIMIZE
Issues: (1) 74 lines — everything substantive deferred to one reference; (2) `launch_readiness_scorer.py` orphaned; (3) thinnest non-deprecated skill in domain.
Verify: SKILL.md ≥ inline ORB definition + phase model summary; `launch_readiness_scorer.py` named with CLI; `--help` exits 0.
### marketing-context — OPTIMIZE
Issues: (1) writes `.agents/marketing-context.md` while 19 sibling skills read `.claude/product-marketing-context.md` and 16 read `marketing-context.md` — the foundation file is invisible to half its consumers; (2) `context_validator.py` orphaned.
Verify: one canonical path declared and used by this skill's output instruction; `grep -rl "product-marketing-context" skills/*/SKILL.md` and `grep -rl "marketing-context.md"` agree with that path; `python3 scripts/context_validator.py --json` emits completeness score 0-100 and is named in SKILL.md.
### marketing-demand-acquisition — OPTIMIZE
Issues: (1) `metadata.updated: 2025-01`, "q1-2025-linkedin-enterprise" examples; (2) description hard-scopes to "Series A+ scaling internationally EU/US/Canada hybrid PLG/Sales-Led" — over-narrow trigger for a general demand-gen skill; (3) HubSpot-specific workflows presented as the default stack.
Verify: dates refreshed or genericized; description triggers cover demand-gen broadly with the persona as a default profile not a gate; campaign workflow validation step still names the UTM-in-CRM check.
### marketing-ops — OPTIMIZE
Issues: (1) routing matrix omits 11 skills (aeo, ASO, webinar-marketing, x-twitter-growth, social-media-analyzer, marketing-strategy-pmm, marketing-demand-acquisition, brand-guidelines, prompt-engineer-toolkit, youtube-full, video-content-strategist); (2) AI-search row routes to ai-seo only; (3) `campaign_tracker.py` orphaned.
Verify: `for d in skills/*/; do grep -q "$(basename $d)" marketing-ops/SKILL.md || echo MISS; done` prints nothing (minus deliberate exclusions); aeo present in SEO pod rows; `campaign_tracker.py` named with CLI.
### marketing-skills — CUT-OR-MERGE
Issues: (1) it's a README/index in SKILL.md clothing — no workflow, no trigger utility; (2) stale counts (42 skills/7 pods/27 tools vs actual 47/8/58+); (3) every example path broken (omits `skills/` segment: `marketing-skill/content-production/scripts/...`); (4) references 6 scripts that live in other skills (phantom `scripts/*.py` paths); (5) duplicates marketing-ops (router) and README.md (index).
Verify: file demoted to README.md (or deleted) and removed from skill counts; if kept as SKILL.md, all paths resolve (`grep -oE "marketing-skill[^ )]*" | xargs -I{} test -e {}`) and counts match `ls skills/ | wc -l`.
### onboarding-cro — OPTIMIZE
Issues: (1) `activation_funnel_analyzer.py` orphaned; (2) no references dir — all knowledge inline (acceptable) but no verification loop.
Verify: script named with CLI; `--help` exits 0; output (drop-off by step) consumed in the audit output format section.
### page-cro — OPTIMIZE
Issues: (1) `conversion_audit.py` orphaned; (2) framework is solid but ends with no machine-checkable gate (A4).
Verify: SKILL.md invokes `python3 scripts/conversion_audit.py` and the audit report format references its score; `--help` exits 0.
### paid-ads — OPTIMIZE
Issues: (1) phantom `../../tools/REGISTRY.md` reference; (2) `ad_health_scorer.py` + `roas_calculator.py` both orphaned; (3) naming-convention examples dated "2024Q1"/"Mar24"; (4) 5 refs exist but only 1 linked from SKILL.md.
Verify: zero phantom links; both scripts named with CLI; `python3 scripts/roas_calculator.py --help` exits 0; example campaign names use current-year placeholders or `{YYYY}` tokens.
### popup-cro — OPTIMIZE
Issues: (1) hollow core ("Core Principles → see references/popup-cro-playbook.md"); (2) zero tooling; (3) experiment lists are the kind of generic ideation a frontier model produces unaided (A5 risk).
Verify: trigger-timing and frequency-cap thresholds (the calibrated part of the playbook) surfaced inline; SKILL.md ≤ 250 lines with decision rules, not idea lists.
### programmatic-seo — OPTIMIZE
Issues: (1) `url_pattern_generator.py` orphaned; (2) otherwise strong (data-defensibility hierarchy, penalty avoidance).
Verify: script named with CLI in the page-generation workflow; `--help` exits 0.
### prompt-engineer-toolkit — REWRITE
Issues: (1) references are stubs: evaluation-rubric.md 328 B, technique-guide.md 675 B, prompt-templates.md 1.5 KB — no citations, no marketing templates despite the description promising "prompt templates for marketing use cases (ad copy, email campaigns, social media)" (A1/A7 fail); (2) body is generic LLM-feature governance, not marketing — arguably belongs in engineering/; (3) scripts (`prompt_tester.py`, `prompt_versioner.py`) are real and wired — keep them.
Verify: each reference ≥ 3 KB with ≥ 5 cited sources OR skill relocated to engineering/ with description rewritten to match the body; prompt-templates.md contains ≥ 5 concrete marketing prompt templates if it stays in marketing; both scripts still pass `--help`.
### seo-audit — OPTIMIZE
Issues: (1) both scripts (`seo_checker.py`, `seo_health_scorer.py`) orphaned; (2) audit framework wholly deferred ("→ See references/seo-audit-reference.md"); (3) 4 references are good (CWV thresholds, E-E-A-T) but SKILL.md gives the model no decision rules inline.
Verify: both scripts named with CLI and consumed in the report structure; CWV pass/fail thresholds (LCP/INP/CLS numbers) inline in SKILL.md; `--help` exits 0 on both.
### signup-flow-cro — OPTIMIZE
Issues: (1) `funnel_drop_analyzer.py` orphaned.
Verify: script named with CLI; `--help` exits 0; output consumed in audit format.
### social-media-manager — OPTIMIZE
Issues: (1) `social_calendar_generator.py` orphaned; (2) overlaps social-content's platform tables (duplicate cadence specs that can drift independently).
Verify: script named with CLI; cadence table either deduplicated with social-content or marked as the canonical copy; `--help` exits 0.
### webinar-marketing — OPTIMIZE
Issues: (1) **confirmed known issue:** `scripts/webinar_funnel_scorer.py` has no argparse — `python3 ... --help` raises FileNotFoundError treating `--help` as a JSON filename (only D1 failure in marketing scope; it is the skill's only script, no affected siblings); (2) SKILL.md itself is among the best in the domain (backward funnel math, benchmark-tagged outputs) — fix is surgical.
Verify: `python3 scripts/webinar_funnel_scorer.py --help` exits 0 and prints usage; no-arg run still executes embedded sample and prints `WEBINAR FUNNEL SCORE: \d+/100` plus a JSON block; `echo '{}' | python3 scripts/webinar_funnel_scorer.py -` doesn't crash.
## KEEP-verdict verification criteria
- **aeo** — all 3 scripts pass `--help`; `aeo_audit.py --input <md> --output json` emits composite 0-100 + 4 dimension keys; industry table thresholds (healthcare/finance/legal ≥ 85) unchanged.
- **app-store-optimization** — all 8 scripts pass `--help`; `metadata_optimizer.py --platform ios --title "<31 chars>"` flags the over-limit title; char-limit table matches Apple 30/30/100 + Play 50/80.
- **campaign-analytics** — 3 scripts run on `assets/sample_campaign_data.json` with `--format json` exit 0; attribution output includes all 5 models; funnel analyzer names a bottleneck stage.
- **churn-prevention** — `churn_impact_calculator.py` runs no-arg with sample, exits 0; benchmark table retains save-rate ≥ 10-15% / recovery 25-35% calibration.
- **cold-email** — 3 references resolve; deliverability section still names SPF/DKIM/DMARC + warmup ramp; orphan `email_sequence_analyzer.py` gets wired (carryover from A3 sweep).
- **free-tool-strategy** — `tool_idea_scorer`-class script passes `--help` and is named in Mode 1; 6-factor evaluation framework present.
- **marketing-ideas** — references/ideas-by-category.md contains all 139 numbered ideas; SKILL.md stage-mapping numbers (#79, #81...) resolve to entries in the reference.
- **marketing-psychology** — references/mental-models-catalog.md contains ≥ 70 models; the 6-category count table matches the catalog's actual counts.
- **marketing-strategy-pmm** — 4 references resolve; April Dunford positioning workflow + ICP validation checklist intact; no scripts claimed (none promised).
- **paywall-upgrade-cro** — self-contained; description's distinct-from-pricing-page boundary preserved; router row intact.
- **pricing-strategy** — `pricing_modeler.py` passes `--help` and stays named in SKILL.md; three-axes model + Van Westendorp trigger words remain in description.
- **referral-program** — incentive-structure script passes `--help` and is named; LTV-ceiling logic for incentive sizing intact.
- **schema-markup** — `schema_validator.py` named in Mode 1 step 1 and passes `--help`; schema selection table covers FAQ/HowTo/Article/Product/Organization/Person.
- **site-architecture** — `sitemap_analyzer.py` named in Mode 1 and passes `--help`; subfolder-over-subdomain rule intact.
- **social-content** — references/platforms.md + post-templates.md resolve; cadence table consistent with social-media-manager's (post-dedup).
- **social-media-analyzer** — both scripts pass `--help`; engagement-rate formula (engagements/reach×100) and validation gates (ER < 100%) intact.
- **x-twitter-growth** — all 5 scripts pass `--help` and stay named; algorithm-signal table keeps an explicit date label ("2025-2026" or refreshed); cadence-by-account-size table intact.
- **youtube-full** — BYOK note + OSS fallback table intact; fix 3 cross-reference paths (`marketing-skill/skills/video-content-strategist` → actual location); endpoint table matches credit-cost table.
- **video-content-strategist** — niche/positioning framework + 90-day plan intact; plugin gets registered in marketplace.json (currently missing).
- **landing (marketing/)** — 3 scripts pass `--help`; `html_validator.py --file <out>.html` checks all 8 listed gates; GSAP CDN pins resolve; SKILL.md keeps gsap.set()-before-timeline FOUC rule.
## Agents
| Agent | Verdict | Notes |
|---|---|---|
| agents/marketing/cs-aeo.md | KEEP | B1-B3 pass; differentiated voice (refuses fake authority, AEO≠SEO routing); trigger phrasing present. |
| agents/marketing/cs-webinar-marketer.md | KEEP | Differentiated (refuses vanity metrics; fixes the broken stage); trigger phrasing present. |
| marketing/landing/agents/cs-landing.md | KEEP | Forcing-intake persona with concrete refusals; wired to skill + scripts. |
| agents/marketing/cs-content-creator.md | CUT-OR-MERGE | Targets the **deprecated** content-creator skill via a wrong path (`marketing-skill/content-creator`); no trigger phrasing (B1 fail); 3 paragraphs of swappable boilerplate (B2/B3 fail). Retarget to content-production or delete. |
| agents/marketing/cs-demand-gen-specialist.md | REWRITE | No trigger phrasing; wrong skill path (`marketing-skill/marketing-demand-acquisition`, missing `skills/`); body is the same boilerplate template as cs-content-creator — swappable (B2 fail). |
| agents/personas/content-strategist.md | OPTIMIZE | Skills list includes deprecated `content-creator`; otherwise differentiated persona frontmatter. |
## Commands
| Command | Verdict | Notes |
|---|---|---|
| commands/cs-aeo.md | KEEP | C1-C3 pass; orchestrates 3 scripts with modes; explicit when-NOT-to-run; distinct from /cs:seo-audit documented. |
| commands/cs-webinar.md | KEEP | C1-C3 pass; plan/rescue/evergreen modes; gates on funnel-math feasibility. |
| marketing/landing/commands/cs-landing.md | KEEP | C1-C3 pass; 4-question forcing intake + validator gate; routes away to landing-page-generator when conversion-optimized output needed. |
| commands/seo-auditor.md | KEEP | Repo-docs SEO utility (not marketing-skill plugin surface); 7-phase pipeline with report-only flag; does real orchestration. |
Gap: no `/cs:*` commands exist for the other 45 marketing skills — the domain relies on skill triggers alone. Acceptable, but the marketing-skills index promises slash-command-grade entry points it doesn't have.
## Plugin manifests
| Manifest | Verdict | Notes |
|---|---|---|
| marketing-skill/.claude-plugin/plugin.json | OPTIMIZE | Schema valid (`"skills": ["./skills"]` ✓). E2 fail: description says "45 skills across 8 pods" — actual 47 skill dirs (incl. deprecated redirect + index); marketplace.json entry says 44/7; marketing-skills SKILL.md says 42/7. Three counts, four places. |
| marketing-skill/skills/aeo/.claude-plugin/plugin.json | KEEP | Schema valid; `source` extension block documented; description matches contents. |
| marketing-skill/skills/youtube-full/.claude-plugin/plugin.json | KEEP | Schema valid; attribution block present; BYOK disclosed (ClawHub rule 3 satisfied — free tier + OSS fallbacks documented). |
| marketing-skill/video-content-strategist/.claude-plugin/plugin.json | OPTIMIZE | Schema valid but **not registered in root marketplace.json** (E3 fail) — plugin is undiscoverable. |
| marketing/landing/.claude-plugin/plugin.json | OPTIMIZE | Schema valid; `source` block present. E2 drift: marketplace.json description for `landing` describes the *other* landing skill ("4 design styles, brand palette validation" = product-team TSX generator language), not this GSAP/HTML one. |
Hygiene: marketing-skill/ plugin root ships 5 .zip archives and 4 internal planning markdown docs (1,194 lines) that don't belong in a distributed plugin.

150
audit/newgen-2026-06/product-pm.md Normal file
View file

@ -0,0 +1,150 @@
# Domain audit: product-team/ + project-management/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 26 (17 product-team + 9 project-management) · Agents: 6 · Commands: 11 · Plugins: 6 (+1 .mcp.json)
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| product-team/skills/product-skills (router) | CUT-OR-MERGE | 61-line index with broken `/read` paths and stale counts; adds no orchestration |
| product-team/skills/product-manager-toolkit | OPTIMIZE | Two contradictory RICE CSV schemas in one file; ~120 lines of generic PM advice |
| product-team/agile-product-owner | KEEP | — |
| product-team/skills/product-strategist | OPTIMIZE | Generator emits canned OKR prose a frontier model writes better; keep the alignment scorer |
| product-team/skills/ux-researcher-designer | KEEP | — |
| product-team/skills/ui-design-system | KEEP | — |
| product-team/skills/competitive-teardown | OPTIMIZE | Its only script (competitive_matrix_builder.py) is never referenced in SKILL.md |
| product-team/skills/landing-page-generator | OPTIMIZE | Own script + all 4 references orphaned; overlaps marketing/landing |
| product-team/skills/saas-scaffolder | OPTIMIZE | project_bootstrapper.py orphaned; stack pins aging (Next.js 14, NextAuth v4) |
| product-team/skills/product-analytics | KEEP | — |
| product-team/skills/experiment-designer | KEEP | — |
| product-team/skills/product-discovery | KEEP | — |
| product-team/skills/roadmap-communicator | OPTIMIZE | Mostly framework-explainer prose; value is the changelog tool + templates |
| product-team/skills/spec-to-repo | KEEP | — |
| product-team/code-to-prd | OPTIMIZE | Malformed frontmatter (duplicate `Name:`/`name:` + non-standard keys) |
| product-team/research-summarizer | CUT-OR-MERGE | Duplicates research/ domain (litreview/dossier); phantom `/research:*` commands |
| product-team/apple-hig-expert | REWRITE | Known 3/6; persona filler, no exact CLI, citation-free references with dubious claims |
| project-management/skills/pm-skills (router) | CUT-OR-MERGE | Thin index; broken paths; says 6 skills, domain has 9 |
| project-management/skills/senior-pm | OPTIMIZE | Strong quant core buried in ~150 lines of governance boilerplate; invented KPI targets |
| project-management/skills/scrum-master | KEEP | — |
| project-management/skills/jira-expert | REWRITE | Fabricated MCP syntax (`mcp jira create_project --flags`) naming tools the bundled server doesn't have |
| project-management/skills/confluence-expert | REWRITE | Fabricated MCP tool names + phantom MACROS.md/PERMISSIONS.md + legacy wiki markup for Cloud |
| project-management/skills/atlassian-admin | OPTIMIZE | Factual errors (DELETE /rest/api/3/user ≠ deactivate; "7 years for GDPR"); script orphaned |
| project-management/skills/atlassian-templates | REWRITE | Claims "exact parameter names expected by the Atlassian MCP server" for tools that don't exist |
| project-management/skills/meeting-analyzer | KEEP | — |
| project-management/skills/team-communications | KEEP | — |
**Totals:** KEEP 10 · OPTIMIZE 9 · REWRITE 4 · CUT-OR-MERGE 3
## Domain-level findings
1. **MCP wiring is fiction in 3 of the 4 Atlassian skills (highest-severity finding).** The bundled `.mcp.json` correctly points to the Atlassian Remote MCP (`https://mcp.atlassian.com/v1/sse`, SSE), whose real tools are camelCase: `createJiraIssue`, `editJiraIssue`, `searchJiraIssuesUsingJql`, `transitionJiraIssue`, `createConfluencePage`, `updateConfluencePage`, `searchConfluenceUsingCql`, etc. The skills document three different *invented* conventions, none matching: jira-expert uses CLI-flag pseudo-syntax (`mcp jira create_project --name ... --type scrum`), confluence-expert uses snake_case JS calls (`create_space({...})`, `delete_page`, `add_label`), atlassian-templates uses JSON tool blocks (`confluence_create_page`, `jira_update_field_configuration`) while asserting these are "the exact parameter names expected by the Atlassian MCP server." Several referenced capabilities (`create_project`, `create_sprint`, `create_filter`, `create_space`, field-configuration editing) do not exist on the Remote MCP at all. `project-management/CLAUDE.md` adds a fourth convention (`mcp__atlassian__create_issue`, `mcp__atlassian__create_sprint`, `mcp__atlassian__link_issue`). A new-gen model following any of these will emit failing tool calls.
2. **8 orphaned scripts (A3 systemic).** Script dirs exist but SKILL.md never invokes them: competitive-teardown, landing-page-generator, saas-scaffolder, atlassian-admin (1 each); jira-expert, confluence-expert (2 each); atlassian-templates (1). The repo-wide smoke test passes them (D1 fine) but no workflow consumes their output — dead weight per the rubric.
3. **Stale path layout in agents, commands, and routers.** Skills moved under `*/skills/` subdirs but `agents/product/*` reference `../../product-team/product-manager-toolkit/`, commands reference `project-management/scrum-master/SKILL.md`, and both router skills instruct `/read product-team/product-manager-toolkit/SKILL.md`. All resolve to nothing.
4. **Count drift everywhere.** product-skills plugin.json: "13 production-ready product skills" then lists 16 names. product-skills SKILL.md: "10" in description, "8" in body, 13 on disk. pm-skills: 9 in marketplace, 6 in plugin description and SKILL.md, 9 on disk. project-management/CLAUDE.md claims 9 skills but documents only 6 — meeting-analyzer and team-communications (two of the three best skills in the domain) are invisible to it.
5. **PM references are citation-free**, consistent with the repo-wide flag: jql-examples.md (0 sources), team-dynamics-framework.md (0), governance-framework.md (0), template-design-patterns.md (0), retro-formats.md (1). Only senior-pm's prioritization/risk references cite anything.
6. **Generic-knowledge dead weight (A2).** "Handoff Protocols", "Best Practices", "Common Pitfalls" sections across senior-pm, jira-expert, confluence-expert, product-manager-toolkit, roadmap-communicator restate what a frontier model already knows. The skills that skip this (product-analytics, experiment-designer, meeting-analyzer, scrum-master) are the domain's best.
## Per-skill findings
### product-team/skills/product-skills — CUT-OR-MERGE
- Issues: (1) Pure index page — no routing logic, no classifier, nothing a model can execute. (2) Quick Start path `/read product-team/product-manager-toolkit/SKILL.md` is wrong (missing `skills/`). (3) Description says 10 skills, body table lists 8, directory holds 13. (4) Duplicates product-team/CLAUDE.md content.
- Verify: `grep -c "product-team/skills/" product-team/skills/product-skills/SKILL.md` ≥ 1 if retained; otherwise plugin.json `"skills"` array still validates via `python3 scripts/check_plugin_json.py --all` after removal.
### product-team/skills/product-manager-toolkit — OPTIMIZE
- Issues: (1) Two incompatible RICE CSV schemas shown — Quick Start (`feature,reach,impact,confidence,effort` numeric) vs Tools Reference (`name,reach,impact,confidence,effort,description` with `high`/`massive`/`l` categorical values); only one can match the script's parser. (2) ~120 lines of generic PM advice (Best Practices, Pitfalls tables) a frontier model already knows. (3) Verification loop is checklist-only — no machine-checkable gate.
- Verify: `python3 scripts/rice_prioritizer.py sample && python3 scripts/rice_prioritizer.py sample_features.csv --output json` exits 0 and emits JSON with per-feature `rice_score`; the single canonical CSV header in SKILL.md matches `sample_features.csv` byte-for-byte; `python3 scripts/customer_interview_analyzer.py <file> json` exits 0 emitting `pain_points` key.
### product-team/skills/product-strategist — OPTIMIZE
- Issues: (1) Generator output is canned objective prose ("Build viral product features...") — new-gen models write better OKRs unaided; the durable value is the 4-score alignment math (vertical/horizontal/coverage/balance) and thresholds. (2) Sample output hardcodes "Q1 2025" (A6 minor). (3) No verification loop beyond a checklist.
- Verify: `python3 scripts/okr_cascade_generator.py growth --json | python3 -c "import json,sys; d=json.load(sys.stdin); assert d['alignment_scores']['overall']>0"` exits 0; thresholds table (>90/>75/>80/>80) still present in SKILL.md after trimming.
### product-team/skills/competitive-teardown — OPTIMIZE
- Issues: (1) `scripts/competitive_matrix_builder.py` exists but is never mentioned — the 12-dimension rubric is manual-only. (2) Step 4 templates live in `references/analysis-templates.md`; the workflow never says when to load it vs the inline summary (mild progressive-disclosure confusion). (3) No final verification gate after step 6.
- Verify: `python3 scripts/competitive_matrix_builder.py --help` exits 0 AND SKILL.md contains an exact `python3 scripts/competitive_matrix_builder.py` invocation whose output feeds step 3 (scorecard); validation checkpoint at step 2 (pricing + ≥20 reviews + job counts) retained.
### product-team/skills/landing-page-generator — OPTIMIZE
- Issues: (1) `scripts/landing_page_scaffolder.py` (the tool product-team/CLAUDE.md advertises for this skill) is never referenced — only marketing-skill's brand_voice_analyzer is. (2) All 4 reference files (conversion-patterns, copy-frameworks, landing-page-patterns, seo-checklist) unreferenced. (3) Functional overlap with `marketing/landing` (v2.7.0) — needs an explicit distinct-from note (TSX/Next.js vs single-file HTML). (4) SEO "validation step" is honor-system, no executable check.
- Verify: `python3 scripts/landing_page_scaffolder.py --help` exits 0 and SKILL.md shows `--format tsx|html` invocation consumed by the generation workflow; a "distinct from marketing/landing" sentence exists; all 4 reference files cited or deleted.
### product-team/skills/saas-scaffolder — OPTIMIZE
- Issues: (1) `scripts/project_bootstrapper.py` orphaned — phase checklist never calls it. (2) Freshness: NextAuth v4 patterns (`NextAuthOptions`, `getServerSession`) and "Next.js 14+" pins will mislead in 2026 (Auth.js v5 / Next 15 era). (3) Reference Files section asks the model to *generate* CUSTOMIZATION.md/PITFALLS.md/BEST_PRACTICES.md rather than shipping them (A7 — shells).
- Verify: `python3 scripts/project_bootstrapper.py --help` exits 0 and is invoked in Phase 1 of the checklist; Phase 4 webhook idempotency validation retained; stack-version claims dated or generalized.
### product-team/skills/roadmap-communicator — OPTIMIZE
- Issues: (1) ~70% of body is audience-framing advice a frontier model knows (board = outcomes, engineers = dependencies). (2) Only real asset is `changelog_generator.py` + two template references; quality checklist is non-executable. (3) No JSON-mode mention despite the script supporting `--json` (per CLAUDE.md).
- Verify: from a git repo, `python3 scripts/changelog_generator.py --from <tag> --to HEAD --json` exits 0 emitting grouped conventional-commit entries; both `references/roadmap-templates.md` and `references/communication-templates.md` load (exist, non-empty).
### product-team/code-to-prd — OPTIMIZE
- Issues: (1) Frontmatter contains duplicate keys (`Name:` and `name:`) plus non-standard `Tier/Category/Dependencies/Author/Version` at top level — fragile under strict YAML parsers and fails the repo's own description conventions. (2) 507 lines; the README/per-page templates could move to `references/` (progressive disclosure). (3) Otherwise the strongest large skill in the domain (mock-detection signals, enum exhaustiveness, [TBC] uncertainty rule).
- Verify: `python3 -c "import yaml; yaml.safe_load(open('SKILL.md').read().split('---')[1])"` parses with exactly one `name` key; `python3 scripts/codebase_analyzer.py <dir> -o analysis.json && python3 scripts/prd_scaffolder.py analysis.json -o /tmp/prd` exits 0 producing `prd/README.md`.
### product-team/research-summarizer — CUT-OR-MERGE
- Issues: (1) Core capability (structured summarization) is native frontier-model behavior; wrapper value is one regex citation extractor. (2) Direct overlap with `research/litreview`, `research/dossier`, `research/notebooklm` (v2.7.0) — no disambiguation anywhere. (3) Advertises `/research:summarize|compare|cite` slash commands that exist nowhere in `commands/` (phantom). (4) `format_summary.py` emits empty templates — a template printer, not analysis. (5) Installation section references `./scripts/convert.sh` not shipped with the skill.
- Verify: if retained, `grep -r "research:summarize" commands/` returns ≥1 file or the Slash Commands section is removed; a "distinct from research/litreview" note exists; `python3 scripts/extract_citations.py <file> --output json` exits 0 with deduplicated entries.
### product-team/apple-hig-expert — REWRITE
- Issues: (1) Confirmed 3/6 on repo checklist: description has no "Use when" trigger phrases; "You are a Senior Apple Design Lead with decades of experience" is exactly the A2 filler the rubric bans; zero concrete examples (no sample audit, no before/after). (2) A3 fail: "Run the `hig_checker.py` tool" with no invocation — actual CLI is `hig_checker.py {contrast,target,batch}` with subcommand args the SKILL.md never shows. (3) References cite zero sources (no developer.apple.com links) and contain unverifiable claims ("SF Camera" as a public SF variant; "Liquid Glass introduced in late 2025" — WWDC25 was June 2025) — for a freshness-critical Apple skill this is fatal. (4) 90 lines of pointers with the actual expertise missing: no Liquid Glass API names (`glassEffect`, materials hierarchy), no per-platform metric tables in SKILL.md. (5) Scorecard "0-100" output promised with no rubric to compute it.
- Verify: `python3 scripts/hig_checker.py contrast --help && python3 scripts/hig_checker.py batch --help` exit 0 and both invocations appear verbatim in SKILL.md; description matches `Use when` trigger regex of `scripts/audit_skills.py` (skill scores ≥5/6 on `skill_review_checklist_runner.py`); every reference doc cites ≥3 developer.apple.com URLs; at least one worked audit example (input mockup description → scored findings) present.
### project-management/skills/pm-skills — CUT-OR-MERGE
- Issues: (1) Index-only router; `/read project-management/jira-expert/SKILL.md` path wrong (missing `skills/`). (2) Claims 6 skills; domain ships 9 — meeting-analyzer, team-communications invisible. (3) Example tool paths (`senior-pm/scripts/...`) also missing the `skills/` segment.
- Verify: every path in the file resolves (`while read p; do test -e "$p"; done`) or the file is removed and pm-skills plugin.json still passes `check_plugin_json.py --all`.
### project-management/skills/senior-pm — OPTIMIZE
- Issues: (1) ~150 lines of Handoff Protocols / Continuous Improvement / Stakeholder Feedback boilerplate (A2 dead weight). (2) Success-metric targets (">70% risk prediction accuracy", "10% transformational") presented with no source or basis (A5 weakness). (3) Description promises "Monte Carlo simulation" — confirm `risk_matrix_analyzer.py` actually simulates rather than just the formula snippets shown. (4) Quant core (EMV, category weights, three-point estimation, response thresholds >18/12-18/8-12/<8, STOP gates) is genuinely good — keep all of it.
- Verify: all three scripts run against `assets/sample_project_data.json` exiting 0; `project_health_dashboard.py ... --format json` emits composite score + RAG consistent with the >80/60-80/<60 thresholds documented; if Monte Carlo isn't in the scripts, the claim is removed from the description.
### project-management/skills/jira-expert — REWRITE
- Issues: (1) Every "MCP" example uses invented CLI syntax (`mcp jira create_project --name "My Project" --type scrum`) — not MCP, not the bundled server. Real server: `createJiraIssue`, `searchJiraIssuesUsingJql`, `editJiraIssue`, `transitionJiraIssue`; it has NO project/sprint/filter creation. (2) Both scripts (`jql_query_builder.py`, `workflow_validator.py` — which work and produce useful JQL) are never mentioned. (3) `--startDate "2024-06-01"` 2024-ism (A6). (4) JQL operator/function content is generic knowledge a frontier model has; the JQL examples references cite 0 sources. (5) Verdict REWRITE not CUT: the JQL recipes + escalation framework + the two scripts are a salvageable core.
- Verify: every MCP call in SKILL.md names a tool that exists on the Atlassian Remote MCP (assert each appears in the server's tool list; non-existent operations rewritten as REST-API or UI steps); `python3 scripts/jql_query_builder.py "high priority bugs assigned to me"` exits 0 emitting valid JQL and is wired into the JQL workflow; no pre-2026 literal dates.
### project-management/skills/confluence-expert — REWRITE
- Issues: (1) MCP examples (`create_space`, `update_page`, `delete_page`, `get_children`, `add_label`) don't match the real server (`createConfluencePage`, `updateConfluencePage`, `getConfluencePage`, `getConfluencePageDescendants`, `searchConfluenceUsingCql`; no space-creation/delete/label tools). (2) Phantom references: cites `MACROS.md`, `TEMPLATES.md`, `PERMISSIONS.md` — actual files are `macro-cheat-sheet.md`, `templates.md`, `space-architecture-patterns.md`; PERMISSIONS.md doesn't exist at all. (3) Macro sections teach legacy wiki markup (`{info}`, `{section}{column}`) which Confluence Cloud pages (what the MCP writes, storage-format XHTML/ADF) won't accept. (4) Scripts (`space_structure_generator.py`, `content_audit_analyzer.py`) orphaned. (5) Long generic sections (governance, handoffs) a model already knows.
- Verify: every file path cited in SKILL.md exists (`grep -oE '[A-Za-z-]+\.md' SKILL.md` all resolve under references/); every MCP example names a real Remote-MCP tool; macro examples shown in storage format with a note on wiki-markup legacy; both scripts invoked with exact CLI and outputs consumed by Space Creation / KB audit workflows.
### project-management/skills/atlassian-admin — OPTIMIZE
- Issues: (1) Factual errors: `DELETE /rest/api/3/user` deletes (org-admin deactivation is a different endpoint) yet documented as "Deactivate"; "minimum 7 years for SOC 2/GDPR compliance" is invented — GDPR mandates no such retention and pushes minimization. (2) `permission_audit_tool.py` orphaned. (3) Strength: admin.atlassian.com click-paths and REST endpoints are real specificity (A5 pass) — admin operations aren't covered by the Remote MCP, so the "Atlassian MCP Integration" closing section over-promises and should be cut or scoped. (4) References dir exists but is never pointed to from the workflows.
- Verify: `python3 scripts/permission_audit_tool.py --help` exits 0 and an exact invocation appears in the Permission Scheme Design workflow; deactivation step cites the org API (`POST /admin/v1/orgs/{orgId}/directory/users/{accountId}/suspend-access`) or the console path only; retention claim sourced or deleted.
### project-management/skills/atlassian-templates — REWRITE
- Issues: (1) States "All MCP calls below use the exact parameter names expected by the Atlassian MCP server" — then lists `confluence_create_page`, `confluence_update_page`, `confluence_get_page`, `jira_update_field_configuration`, none of which exist (real: `createConfluencePage`/`updateConfluencePage`/`getConfluencePage`; no field-configuration tool at all). False precision is worse than vagueness. (2) Phantom references: `TEMPLATES.md` and `HANDOFFS.md` cited; actual files are `governance-framework.md`, `template-design-patterns.md`. (3) Conflates "Confluence storage format (wiki markup)" — storage format is XHTML, wiki markup is a different legacy syntax; the example is wiki markup and will not round-trip through the Cloud API. (4) `template_scaffolder.py` (which generates storage-format XHTML per CLAUDE.md — the actually-correct artifact) is never mentioned.
- Verify: `python3 scripts/template_scaffolder.py meeting-notes` exits 0 emitting storage-format XHTML and is the documented deployment path; every MCP tool named in SKILL.md exists on the Remote MCP; cited reference filenames resolve on disk; "storage format" vs "wiki markup" used correctly throughout.
## KEEP-verdict verification criteria
- **agile-product-owner**: AC-count-by-points table (1-2→3-4 … 13+→split) and availability-factor table intact; `python3 scripts/user_story_generator.py sprint 30` exits 0 emitting committed ≤85% of capacity; weighted prioritization (40/30/15/15) unchanged.
- **ux-researcher-designer**: `python3 scripts/persona_generator.py json` exits 0 with `confidence` field; sample-size confidence table (5-10 low / 11-30 med / 31+ high) and severity 1-4 table retained.
- **ui-design-system**: `python3 scripts/design_token_generator.py "#0066CC" modern json` exits 0 emitting color/typography/spacing token groups; WCAG AA thresholds (4.5:1 / 3:1) stated in Workflow 1 step 5.
- **product-analytics**: all three subcommands (`retention`, `cohort`, `funnel`) run against documented CSV headers with `--format json` exiting 0; anti-pattern table (6 rows) retained.
- **experiment-designer**: `python3 scripts/sample_size_calculator.py --baseline-rate 0.12 --mde 0.02 --mde-type absolute` exits 0 printing `n_per_group`/`n_total`; If/Then/Because hypothesis gate and peeking warning retained.
- **product-discovery**: `python3 scripts/assumption_mapper.py <csv>` exits 0 emitting prioritized test plan; OST quality gates (≥3 opportunities, ≥2 experiments/opportunity) retained.
- **spec-to-repo**: `python3 scripts/validate_project.py <dir> --format json` exits 0; Phase 4 checklist wired to the script; anti-pattern table (9 rows incl. phantom-imports) retained.
- **scrum-master**: all 3 scripts run on `assets/sample_sprint_data.json` matching `assets/expected_output.json` anchors (velocity avg ≈20.2, CV ≈12.7%, health ≈78.3); <3-sprint refusal gate fires on truncated input.
- **meeting-analyzer**: calibrated thresholds preserved (filler >3/100 words, speaking share >60%, interruption >2:1, 3+ meetings for trends); no script claims introduced without scripts existing.
- **team-communications**: all 4 routing targets (`references/3p-updates.md` etc.) exist and load; ambiguity rule ("ask one clarifying question") retained.
## Agents
6 agents (5 product + 1 PM), all `model: sonnet`, all `tools: [Read, Write, Bash, Grep, Glob]`.
- **B1 partial fail (all 6):** descriptions state capability but no trigger phrasing ("Use when…" / "Use PROACTIVELY") — they read like catalog blurbs.
- **Stale skill paths (all 6):** `skills:` values and body paths (`../../product-team/product-manager-toolkit/`, `../../project-management/senior-pm/scripts/...`) predate the `skills/` subdirectory move; none resolve. cs-project-manager's `skills: project-management` is the only one that survives by accident (directory-level).
- **B2 weak:** cs-product-manager orchestrates all 8 legacy skills (incl. landing-page + saas-scaffolder — scope sprawl into build work); cs-product-strategist and cs-product-manager bodies are interchangeable catalog tables, not differentiated behavior. cs-product-analyst is the cleanest (2 skills, focused).
- Verify: every path in each agent file resolves from `agents/<domain>/`; each description gains a trigger clause; cs-product-manager skill list trimmed to PM-decision skills.
## Commands
11 in scope: /rice, /okr, /persona, /user-story, /competitive-matrix, /prd, /sprint-plan, /code-to-prd (product); /sprint-health, /project-health, /retro (PM).
- **C1 pass** all 11 (frontmatter description present, usage string embedded).
- **C3 strong:** /sprint-health, /project-health, /retro, /code-to-prd — wire exact scripts with input schemas and JSON examples. Keep.
- **C3 weak:** /prd and /sprint-plan are thin prompt wrappers (output-structure bullets a bare prompt produces) — merge candidates into /rice and /user-story or beef up with script gates.
- **Stale skill-reference paths (all that cite SKILL.md):** `project-management/scrum-master/SKILL.md`, `product-team/product-manager-toolkit/SKILL.md` etc. all miss the `skills/` segment.
- **Mismatch:** /retro and /sprint-health input JSON schemas (flat per-sprint objects) don't match the scripts' actual schema (`team_info` + `sprints[]` + `retrospectives[]` per scrum-master SKILL.md) — a model following the command's example will feed the script malformed input. Verify: run each command's documented example JSON through its script; exit 0 required.
## Plugin manifests + MCP wiring
- **E1 pass:** all 6 plugin.json files schema-valid (`"skills": ["./skills"]` / `["./skills"]` canonical forms); repo-wide `check_plugin_json.py --all` green.
- **E2 fail — count/description drift:** product-skills plugin.json says "13 production-ready product skills" then enumerates 16 (incl. code-to-prd, research-summarizer, apple-hig-expert, spec-to-repo — three of which are *separate* plugins, so the description oversells what `./skills` ships). pm-skills plugin description lists 6 skills; marketplace.json says 9; disk has 9 (meeting-analyzer + team-communications + router undocumented). product-team/CLAUDE.md header says 13, lists 16, footer says "13/13". project-management/CLAUDE.md says 9, documents 6.
- **E3 pass:** all at 2.9.0, coherent with marketplace.json.
- **.mcp.json:** correct and minimal (`atlassian` → SSE `https://mcp.atlassian.com/v1/sse`). This is the only accurate piece of MCP wiring in the domain.
- **MCP documentation contradiction (cross-cutting):** four different fabricated tool-naming conventions across project-management/CLAUDE.md (`mcp__atlassian__create_issue`, `create_sprint`, `link_issue`), jira-expert (CLI flags), confluence-expert (snake_case JS), atlassian-templates (JSON blocks) — zero match the live Remote MCP surface (`createJiraIssue`, `editJiraIssue`, `searchJiraIssuesUsingJql`, `getJiraIssue`, `transitionJiraIssue`, `createConfluencePage`, `updateConfluencePage`, `getConfluencePage`, `searchConfluenceUsingCql`, `getConfluenceSpaces`, …). One canonical tool-name appendix should be written once and referenced from all four places. Verify: `grep -rE "mcp jira |mcp__atlassian__[a-z_]+|confluence_create_page|create_space\(" project-management/` returns 0 hits after fix.

131
audit/newgen-2026-06/productivity-markdown-html.md Normal file
View file

@ -0,0 +1,131 @@
# Domain audit: productivity/ + markdown-html/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 11 · Agents: 7 · Commands: 14 · Plugins: 6 · Hooks: 2
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| markdown-html-orchestrator | OPTIMIZE | Stale v2.10.0 "foundation status" text instructs the model NOT to use the (now-shipped) converters |
| design-system | KEEP | Validator script exits 0 even on FAIL verdict (refusal lives in onboard.py — documented, but easy to misread) |
| md-document | KEEP | <100-line "hard rule" is prose/command-enforced, not script-enforced (parser accepted a 70-line file) |
| md-review | KEEP | — |
| md-slides | KEEP | Boundary-less 1-slide file exits 6 (no-boundary), not 5 (poster) — doc nuance |
| capture | KEEP | dump_classifier CLI shape (positional arg) not documented in SKILL.md tooling table |
| inbox-setup | KEEP | — (its agent has a phantom skills path; see Agents) |
| inbox-triage | KEEP | — (same agent issue) |
| reflect | OPTIMIZE | 3 scripts are unwired — no CLI invocations in SKILL.md, no step consumes their output |
| handoff | KEEP | "17 regex patterns" claim is actually 16; tools table lacks exact CLI invocations |
| andreessen | KEEP | — |
Verdicts: 9 KEEP · 2 OPTIMIZE · 0 REWRITE · 0 CUT-OR-MERGE
## Empirical verification results
All runs used `MARKDOWN_HTML_NO_CONFIG=1` or an isolated `HOME` to avoid touching real config. Scratch: /tmp/audit-pmh.
| # | Check | Expected | Actual | Result |
|---|---|---|---|---|
| 1 | md-document pipeline (parser → renderer → injector) on 515-line repo CLAUDE.md | valid single-file HTML | 88 KB HTML, parses clean, 16 sections, all 4 JS features injected (+5,081 B) | PASS |
| 2 | Output single-file discipline | only Google Fonts + Prism externals | external hosts: `fonts.googleapis.com`, `cdn.jsdelivr.net` (+ content links) | PASS |
| 3 | interactivity_injector idempotency | re-inject is no-op | "no-op: marker … already present", exit 0 | PASS |
| 4 | md-document <100-line refusal at script level | refuse per SKILL.md hard rule #1 | parser/renderer accepted a 70-line file (gate lives in orchestrator `route_explainer.py` + command prose `wc -l`) | PARTIAL — claim overstates script behavior |
| 5 | slide_splitter 1-slide deck → exit 5 | exit 5 | exit 5 (with `--boundary h1` single-H1, and 3-HR degenerate deck) | PASS |
| 6 | slide_splitter no-boundary → exit 6 | exit 6 | exit 6 on 120-line prose file (also on plain 1-slide file — exit 6 fires before exit 5 when no boundaries detected) | PASS |
| 7 | md-slides happy path (5 slides, 3 with notes) | working deck | 10.8 KB single-file HTML, 5 `<section class="slide">`, keydown handlers, 1 `@media print`, 60% notes coverage reported | PASS |
| 8 | md-review diff_parser on real ```diff block | hunks JSON | 1 file / 1 hunk parsed; extractor found 2 annotations (1 BLOCKER, 1 NIT) | PASS |
| 9 | review_html_renderer without `--reviewer` → exit 3 | exit 3 | exit 3, "A code review must name a human reviewer" | PASS |
| 10 | review_html_renderer with 0 hunks → exit 4 | exit 4 | exit 4, "route to md-document instead" | PASS |
| 11 | LGTM approval capture | approvals counted | standalone `LGTM` line → 1 approval (regex requires standalone line; "LGTM otherwise." is not counted — by design) | PASS |
| 12 | brand_palette_validator refuses AA-failing palette | FAIL verdict | `--text #CCCCCC --bg #FFFFFF` → FAIL 1.61:1; but script exit 0 (verdict-only); save refusal is onboard.py | PASS (with caveat) |
| 13 | onboard.py exit 4 on AA-fail save | exit 4 | exit 4, "refusing to save: WCAG AA contrast failed" | PASS |
| 14 | onboard.py exit 3 on empty/unwritable output dir | exit 3 | exit 3 on empty path (unwritable case untestable as root — `os.access` always true; code path present at line 226) | PASS |
| 15 | orchestrator <100-line refusal | REFUSE | exit 3, Shihipar citation, design-system status surfaced | PASS |
| 16 | orchestrator silent-route on review doc | ROUTE_SILENTLY → md-review | score 13 vs runner-up 1, routed silently | PASS |
| 17 | orchestrator ambiguity → ASK_USER | one question | CLAUDE.md scored slides 18 / document 15 → ASK_USER with recommended answer (correct: CLAUDE.md is full of `---` HRs) | PASS |
| 18 | handoff redaction_linter on fake AWS key (strict) | exit 1, block | exit 1, `[high] aws_access_key`, fix suggestion + whitelist tip | PASS |
| 19 | redaction_linter whitelist `<!-- handoff:allow secret -->` | exit 0 | exit 0, "OK: no findings" | PASS |
| 20 | "17 patterns" claim | 17 Pattern() defs | **16** Pattern() defs (aws×2, github, openai, anthropic, slack, google, stripe, private-key, jwt, env-assign, db-conn, bearer, email, phone, url-token) | FAIL (off-by-one in docs) |
| 21 | handoff hooks | stdin-safe, env-disable | SessionStart: exit 0 disabled + exit 0 no-handoff; SessionEnd prints reminder, exit 0; hooks.json wires both via `${CLAUDE_PLUGIN_ROOT}` | PASS |
| 22 | andreessen market_first_evaluator --sample | verdict + weights | BUILD-POUR-FUEL, market weighted 0.55 (contribution 4.4) | PASS |
| 23 | andreessen kill gate: market 3.0, team/product 10 | KILL despite 6.15 composite | KILL-OR-REPICK-MARKET + explicit "trap" note that team/product cannot override sub-4 market | PASS |
| 24 | anti_todo_card 6th must-do | reject | exit 2, "the cap IS the discipline" | PASS |
| 25 | operating prompt operationalized | posture table | references/operating_prompt.md: verbatim prompt + 6-row instruction→behavior mapping + binding confidence-level discipline + "what this is NOT" | PASS |
| 26 | inbox-triage draft_safety_validator | exit 1 on send-shaped call | `--sample-fail` exit 1 / `--sample-pass` exit 0 | PASS |
| 27 | all 22 productivity scripts `--help` | exit 0 | 22/22 exit 0 | PASS |
Tally: **24 PASS · 1 PARTIAL · 1 FAIL** (plus 1 caveat). The domains' empirical claims are overwhelmingly real.
## Domain-level findings
1. **Staleness cascade in markdown-html/ (the one real defect).** The domain shipped complete at v2.10.3, but three files still describe the v2.10.0 foundation: `markdown-html/CLAUDE.md` (skills table marks md-document/review/slides "v2.10.1"), `markdown-html/README.md` ("Status — v2.10.0 (foundation)", converters "v2.10.1 (next PR)"), and the orchestrator SKILL.md ("Until v2.10.1, the orchestrator's job stops at step 4 — … lets Claude do the rendering inline"). A new-gen model following the orchestrator SKILL.md today is **instructed to bypass the shipped converters** and hand-render. This is an A6 failure with behavioral consequence, not cosmetic.
2. **Refusal gates split between scripts and prose — mostly fine, but SKILL.md wording overclaims twice.** md-document's "Hard rule 1: Refuses input < 100 lines" and design-system's validator both read as script-level gates; in reality the 100-line gate lives in the orchestrator's `route_explainer.py` and in the converter commands' `wc -l` instruction, and the palette refusal lives in `onboard.py` (validator exits 0 on FAIL verdict). Direct script invocation skips both. Acceptable for a model that follows the commands, but the prose should say where each gate is enforced.
3. **A3 weakness across productivity/: tool tables without exact CLI invocations.** reflect, handoff, and capture (dump_classifier) list scripts in a table but never show how to call them — I had to discover arg shapes by trial (`redaction_linter.py FILE` positional, not `--file`; `bias_pattern_detector.py --conversation`). markdown-html/ does this right (every SKILL.md has copy-pasteable invocations); productivity/ should match.
4. **Counter/spec drift.** Redaction patterns 16 vs claimed 17 (root CLAUDE.md v2.8.2 notes). reflect's spec is `megaprompts/02-reflect-megaprompt.md` per SKILL.md + plugin.json, but root CLAUDE.md v2.7.0 notes call reflect "megaprompt 08". Minor, but counters are this repo's brand — keep them true.
5. **Trigger quality is uniformly strong (A1).** Every skill in scope has concrete trigger phrases, third-person descriptions, refusal conditions in the description itself, and "distinct from" disambiguation. This is the best trigger discipline of any domain pattern observed; no action needed.
6. **Context economy is good but markdown-html SKILL.md bodies duplicate the domain CLAUDE.md hard rules ~3×** (domain CLAUDE.md, SKILL.md "Hard rules", command "Pre-flight gates"). Tolerable since skills ship standalone, but the duplication is what made the staleness cascade possible — single-source the version/status table.
## Per-skill findings
### markdown-html-orchestrator — OPTIMIZE
- **Verdict:** OPTIMIZE (targeted edits; routing logic and scripts are excellent and fully verified)
- **Issues:**
1. SKILL.md "Foundation status (v2.10.0)" paragraph + Step 5 ("Until v2.10.1 … lets Claude do the rendering inline") + Output-artifacts table ("v2.10.1" status column) instruct the model to bypass shipped converters. Delete the transitional text.
2. Frontmatter `version: 2.10.0` while plugin is 2.10.3.
3. `markdown-html/CLAUDE.md` skills table and `README.md` status section carry the same stale v2.10.0 framing (fix together).
4. Pipeline snippets use `skills/markdown-html-orchestrator/...` relative paths while Step-1 uses repo-rooted `markdown-html/skills/...` — pick one convention.
- **Verify:**
- `grep -c "v2.10.1" markdown-html/skills/markdown-html-orchestrator/SKILL.md` returns 0
- `grep -c "foundation" markdown-html/README.md markdown-html/CLAUDE.md` returns 0 stale-status hits (status table lists all 5 skills "✓ live")
- `printf '# s\n' > /tmp/s.md && python3 markdown-html/skills/markdown-html-orchestrator/scripts/doctype_classifier.py --input /tmp/s.md --output json | python3 .../route_explainer.py; test $? -eq 3` (refusal stays green)
- review-shaped ≥100-line input still yields `ROUTE_SILENTLY -> md-review`
### reflect — OPTIMIZE
- **Verdict:** OPTIMIZE (the prompt body is strong; the script layer is dead weight as wired)
- **Issues:**
1. A3: no CLI invocations anywhere in SKILL.md for the 3 scripts; no workflow step consumes their output. For an in-conversation reflection skill the model cannot trivially produce a transcript file, so `bias_pattern_detector.py --conversation FILE` and `conversation_depth_analyzer.py` have no realistic input path described.
2. A4: `directional_recommendation_validator.py` is the natural verification loop (assert output ends Continue/Pivot/Pause) but is never invoked in the workflow. Wire it: "pipe your draft reflection through the validator before sending; exit 0 required."
3. Either wire all 3 scripts with exact invocations + an input-capture step, or cut detector/analyzer and keep only the validator (A7).
- **Verify:**
- SKILL.md "Tooling" section contains ≥1 fenced `python3 …` invocation per retained script
- `printf 'analysis...\nContinue. Because X and Y are verified.\n' | python3 productivity/reflect/skills/reflect/scripts/directional_recommendation_validator.py -` (or documented file form) exits 0; output missing a closing recommendation exits non-zero
- `python3 .../bias_pattern_detector.py --sample --output json` exits 0 with keys `biases_detected`, `biases_clear`, `details` (if retained)
## KEEP-verdict verification criteria
- **design-system:** `HOME=$(mktemp -d) python3 markdown-html/skills/design-system/scripts/onboard.py --defaults` exits 0; `--set brand.text='#CCCCCC' --set brand.bg='#FFFFFF'` exits 4; `--set default_output_dir=` exits 3; `config_loader.py --status` reports `setup_completed: true` after defaults.
- **md-document:** full 3-script pipeline on a ≥100-line file exits 0×3 and produces HTML whose only external hosts are `fonts.googleapis.com` + `cdn.jsdelivr.net`; second injector run prints `no-op` and exits 0. (Optimization PRs must also fix Hard-rule-1 wording to name where the 100-line gate is enforced.)
- **md-review:** renderer without `--reviewer` exits 3; with 0-hunk input exits 4; with valid input exits 0 and output contains the reviewer name + per-severity counts; standalone `LGTM` line yields `approvals: 1`.
- **md-slides:** `slide_splitter.py` exits 5 on a boundary-detected 1-slide deck, 6 on boundary-less input, 0 on a 5-slide HR deck; rendered deck contains 5 `class="slide"` sections, `addEventListener`, and `@media print`.
- **capture:** `dump_classifier.py <file>` and `--sample` exit 0; `workspace_inventory.py --root . --keywords "a,b"` exits 0 (documented invocation stays true); `complexity_estimator.py --sample small` recommends compressed format.
- **inbox-setup:** `kb_validator.py --sample` exits 0 with verdict PASS and 7-file contract checks; SKILL.md section count stays 8 with S4 skip-logic intact.
- **inbox-triage:** `draft_safety_validator.py --sample-fail` exits 1, `--sample-pass` exits 0; SKILL.md states DRAFTS-ONLY in ≥3 places; `search_window_calculator.py --help` exits 0.
- **handoff:** `redaction_linter.py <file-with-AKIA-key>` exits 1 strict / 0 with `<!-- handoff:allow secret -->`; `echo '{}' | HANDOFF_SESSIONSTART=0 python3 hooks/session_start.py` exits 0; `handoff_self_check.py --sample` exits 0; fix the "17 patterns" claim to 16 (or add the 17th) wherever it appears.
- **andreessen:** `market_first_evaluator.py --size 3 --growth 3 --timing 3 --pull 3 --team 10 --product 10` verdict is KILL-OR-REPICK-MARKET; `anti_todo_card.py --new --must-do a b c d e f` exits 2; `references/operating_prompt.md` retains the verbatim prompt + 6-row posture table.
## Agents
7 agents. One real bug, otherwise differentiated and non-boilerplate (B2/B3 pass — capture's 210-line persona, inbox pair's halting rules, and andreessen's binding voice could not be swapped unnoticed).
- **BUG — `cs-inbox-setup.md` and `cs-inbox-triage.md` declare `skills: engineering/email/skills/inbox-setup` / `...inbox-triage`. The skills live at `productivity/email/skills/...`; `engineering/email/` does not exist.** Phantom path (B1). Fix: `skills: productivity/email/skills/inbox-setup` (resp. `-triage`).
- B1 trigger phrasing: only `cs-handoff-author` uses explicit "Invoke when…" language. The other six describe the persona but not when to fire; cheap win to prepend "Use when…" to each description.
- `cs-markdown-html-orchestrator` (model: sonnet) carries the same stale assumption indirectly via the skill it wraps — no edit needed once the SKILL.md is fixed.
- Frontmatter style is inconsistent across the set (`tools: [..]` vs `tools: "..."` vs quoted lists; `model: opus`/`sonnet`/`inherit`) — harmless but worth normalizing in an optimization PR.
## Commands
14 commands. All have accurate descriptions (C1). All orchestrate tools or enforce gates a bare prompt would not (C3): the six markdown-html commands embed pre-flight refusal gates + exact pipelines; `/cs:handoff` enforces checklist→linter→save ordering; `/cs:inbox-*` enforce the one-question-per-turn and DRAFTS-ONLY disciplines; `/cs:andreessen` + `/cs:pmf-check` bind verdict tools.
- C2: markdown-html commands + handoff pair carry `argument-hint`; the 6 productivity megaprompt-era commands (andreessen, pmf-check, capture, inbox-setup, inbox-triage, reflect) embed usage in the body instead of `argument-hint` frontmatter — minor normalization.
- `/cs:grill-markdown-html` and `/cs:design-system` are genuinely distinct surfaces (grill vs route vs onboard); no merge candidates.
## Plugin manifests
6 plugins, all schema-valid (repo-wide `check_plugin_json.py --all` green), all using canonical `./`-prefixed skills arrays.
- **markdown-html-skills (2.10.3):** description counts verified — 15 tools (3×5 ✓), 15 references (3×5 ✓), 4 assets (1 schema + 3 templates ✓), 5 skill paths ✓. E2/E3 pass. Best manifest in scope.
- **Productivity five (all 2.9.0):** coherent with their marketplace.json entries (E3 pass), though frozen at 2.9.0 while the repo is at 2.10.3 — per repo policy versions should track releases; bump at next touch.
- **Name drift (low):** marketplace entry names differ from plugin.json `name` for four plugins — `capture-skill`/`capture`, `email-pair`/`email`, `reflect-skill`/`reflect`, `handoff-productivity`/`handoff`. If intentional (ClawHub slug conflicts), document it; otherwise align.
- `handoff` plugin correctly omits a `hooks` key in plugin.json while shipping `hooks/hooks.json` — Claude Code's auto-discovery convention; hooks verified working via `${CLAUDE_PLUGIN_ROOT}` commands.
## Hooks
2 hooks (handoff SessionStart + SessionEnd). Both stdlib-only, fail-open (`sys.exit(0)` on import error — "hook must never break a session"), env-disable verified (`HANDOFF_SESSIONSTART=0` / `HANDOFF_SESSIONEND=0`), 12,000-char body cap on injected handoff prevents context blowout. D4 by-design stdin exception documented in-file. PASS.

133
audit/newgen-2026-06/research.md Normal file
View file

@ -0,0 +1,133 @@
# Domain audit: research/ + research-ops/ — new-gen model optimization
Audited: 2026-06-10 · Skills: 13 (8 research/ + 5 research-ops/) · Agents: 9 · Commands: 14 · Plugins: 9
## Scorecard
| Skill | Verdict | Top issue |
|---|---|---|
| research-ops/research-ops-skills (orchestrator) | KEEP | Routing is prose-only (no classifier script like research/ ships) — acceptable, but inconsistent with sibling |
| research-ops/clinical-research | KEEP | — (model citizen; all hard rules verified in tool output) |
| research-ops/research-finance | KEEP | — (capex router never auto-decides; named owner verified) |
| research-ops/market-research | KEEP | — (both-methods TAM + triangulation flag verified) |
| research-ops/product-research | KEEP | — (INSIGHT vs ANECDOTE gate verified) |
| research/research (orchestrator) | OPTIMIZE | Single-keyword signals ("funding", "fda", "patent", "grant") cause weak-match misroutes; 319-line body restates generic search methodology |
| research/pulse | OPTIMIZE | Unauthenticated reddit.com/search.json is post-2023-API fragile; duplicated Agent Integrity boilerplate |
| research/litreview | OPTIMIZE | Hard Consensus-MCP dependency with no free-API fallback; phantom `scripts/office/validate.py` |
| research/grants | OPTIMIZE | Phantom `scripts/office/validate.py`; otherwise the strongest skill in the pack (RePORTER POST, dynamic FY, correct NIH receipt dates) |
| research/dossier | OPTIMIZE | Phantom `scripts/office/validate.py`; 318-line body |
| research/patent | OPTIMIZE | Phantom validate.py; `patents.uspto.gov/patent/...` hyperlink pattern is wrong (PPS lives at ppubs.uspto.gov) |
| research/syllabus | OPTIMIZE | Phantom validate.py; bundled JS requires npm `docx` (fails clean, but install path undocumented in plugin) |
| research/notebooklm | REWRITE | Hardcoded UI inventory of a fast-moving Google product has already rotted; description (8 Studio types) contradicts body (9) |
Verdict counts: **KEEP 5 · OPTIMIZE 7 · REWRITE 1 · CUT-OR-MERGE 0**
## Domain-level findings
1. **Phantom tool path across 5 research/ skills (A3 fail).** `python scripts/office/validate.py <docx>` is referenced as the DOCX validation step in litreview, grants, dossier, patent, and syllabus SKILL.md (plus litreview's README/agent/command and two reference docs). The file exists nowhere in the repo (`find -path "*office/validate.py"` → empty). Every DOCX workflow ends with an instruction the model cannot execute. One fix (ship the validator or delete the step) clears 5 skills at once.
2. **research-ops/ hard rules are genuinely operationalized — all sample runs passed.** `sample_size_estimator.py --sample` prints the "ESTIMATE ONLY — confirm with a biostatistician" banner + assumptions block + named-owner requirement; `market_sizer.py --sample` prints top-down AND bottoms-up TAM/SAM/SOM, a 73.4% divergence figure, and a "TRIANGULATION FAILED" flag; `insight_synthesizer.py --sample` promotes the 3-participant cluster to INSIGHT and flags 1- and 2-participant clusters as ANECDOTE; `capex_vs_opex_router.py --sample` routes all three verdicts to "R&D Finance Controller (+ External Auditor)"; `phase_gate_scorer.py --sample --output json` emits `verdict: GO` with a 3-name owner chain. Config consumption is real (tools import `config_loader`, CLI overrides, `RESEARCH_OPS_NO_CONFIG=1` bypass). This domain is the template the research/ pack should be refactored toward.
3. **research/ context economy is poor and boilerplate is forked, not shared.** SKILL.md bodies run 251–319 lines each; the "Agent Integrity Rules (Research-Pack Convention)" block is repeated near-verbatim in 7 files; `citation_tracker.py` exists as **6 divergent copies** (217–303 lines, all different md5s, 1,556 lines total). Per-skill self-containment is repo policy, but the variants have already drifted — a bug fix in one will not propagate. A shared reference + per-skill thin wrapper would cut ~40% of the pack's context weight.
4. **The repo's own checklist flags are partly a phrasing artifact, partly real.** Re-ran `skill_review_checklist_runner.py` on all 13: research-ops = 4/6 across the board (only fails the under-100-lines rule + the light 'skill'/'tool' terminology heuristic); research/ = 2–4/6. The "Missing trigger" failures on 7 of 8 research/ skills are because descriptions say `Triggers: 'pulse on [topic]'…` instead of the validator's `Use when…` pattern — the descriptions themselves are substantively rich (A1 passes on content, fails the repo gate on phrasing). The notebooklm 2/6 and research 2/6 KNOWN scores reproduce; research additionally trips the time-sensitive check ("in 2026").
5. **External-surface fragility is concentrated in research/.** Consensus MCP is a hard dependency for litreview, syllabus, and grants Phase 2A with zero fallback to free academic APIs (PubMed E-utilities, OpenAlex, Semantic Scholar — all keyless); pulse leans on unauthenticated Reddit JSON endpoints that Reddit increasingly blocks from datacenter IPs; notebooklm hardcodes a Google SPA's UI inventory. New-gen models with native WebSearch/WebFetch make free-API fallbacks cheap to specify — the skills predate that assumption.
6. **The orchestrator routing claim verifies.** `classifier.py` SIGNALS dict matches the SKILL.md table phrase-for-phrase; live tests: 3-signal litreview question → `route_to: litreview`, "research Microsoft" → `fallback` (as the SKILL.md explicitly promises), "dossier on Acme Corp for due diligence" → `dossier` (2 signals). The ≥2-signal threshold, single-weak-match rule, and fallback rule are all implemented. The followability problem is precision, not existence (see per-skill).
7. **All 48 Python scripts across both domains pass `--help` exit 0**; stdlib-only confirmed. The one non-Python script (`generate_reading_list.js`) fails without `npm install docx` but fails with a clear actionable message (acceptable, documented).
8. **Stray `__pycache__/*.pyc` committed under 4 research-ops script dirs** — repo hygiene, should be gitignored.
## Per-skill findings
### research/research (orchestrator) — OPTIMIZE
- Single-keyword signals over-trigger: "funding", "fda", "grant" (grants), "patent", "invention" (patent), "curriculum" (syllabus) each score 1 alone → the "single weak match" rule silently routes e.g. "research FDA approval trends" to grants. Multi-word phrases route reliably; bare nouns don't.
- 319 lines; Phase 3b fallback (decompose → search → synthesize → cite) restates what a frontier model does unprompted — keep the budget numbers + audit-log contract, cut the how-to prose.
- "Waits 1 turn… or auto-proceeds after 5s" is an un-executable affordance (the model cannot wait wall-clock time); checklist also flags "in 2026" as time-sensitive.
- Description lacks `Use when` phrasing → fails repo A1 gate (2/6 known score reproduces).
- Verify: `python3 scripts/classifier.py --question "research Microsoft" --output json` → `route_to: "fallback"`.
- Verify: `python3 scripts/classifier.py --question "literature review on PICO meta-analysis" --output json` → `route_to: "litreview"`, ≥2 signals.
- Verify: bare-noun precision test added: "research FDA approval trends" must NOT route to grants (after signal-list fix).
- Verify: checklist runner item 1 (trigger) and item 3 (time-sensitive) pass.
### research/pulse — OPTIMIZE
- Reddit phase depends on unauthenticated `reddit.com/search.json`; since the 2023 API changes these endpoints are routinely 403'd from non-browser/datacenter clients. Fallbacks exist (`raw_json=1`, subreddit-restricted) but a "Reddit fully blocked → degrade to Web-phase reddit site: search" path is missing.
- Hardcoded trusted-publisher `site:` list (NYT/WSJ/Wired/Verge/TechCrunch) is US-tech-centric and will silently skew non-tech topics.
- 258 lines incl. duplicated Agent Integrity block; checklist fails under-100-lines + terminology.
- Verify: `python3 scripts/time_window_calculator.py --window 30d` exits 0 and emits both HN `created_at_i` timestamp and Reddit `t=month`.
- Verify: `python3 scripts/citation_tracker.py --help` exits 0; session file lands at `~/.pulse_sessions/`.
- Verify: SKILL.md documents an explicit all-Reddit-blocked degradation path.
### research/litreview — OPTIMIZE
- Hard Consensus-MCP dependency; no fallback to free academic APIs (PubMed E-utilities / OpenAlex / Semantic Scholar are keyless) — the skill is inert in any harness without that one MCP.
- References phantom `python scripts/office/validate.py output.docx` (file does not exist anywhere in repo).
- Plan-tier detection parses marketing copy ("Showing top 10" / "upgrade") — brittle heuristic; will mis-detect when Consensus rewords.
- Verify: `python3 scripts/framework_recommender.py --help` and `cross_search_aggregator.py --help` exit 0.
- Verify: no reference to `scripts/office/validate.py` remains (grep returns empty) OR the validator ships.
- Verify: SKILL.md names at least one free-API fallback for the no-Consensus case.
### research/grants — OPTIMIZE
- Phantom `scripts/office/validate.py` in Phase 4 (only blocking edit — domain expertise is otherwise the best in the pack: RePORTER v2 POST templates, NOSI URL pattern, scope-aware mechanism matrix, dynamic FY window, NIH standard receipt dates all check out).
- Phase 2A (5 Consensus searches) has no free fallback; RePORTER core works without it but the SKILL treats Consensus as mandatory.
- Description fails the `Use when` gate (phrasing only).
- Verify: `python3 scripts/fiscal_year_calculator.py --output json` → `current_fy` correct for today's date (Oct 1 boundary), 4-year window.
- Verify: `python3 scripts/mechanism_matcher.py --career-stage early_career --prelim-data pilot --environment r01_eligible --scope single_site --output json` → shortlist excludes R01, includes R21/K-series.
- Verify: phantom validate.py reference removed or implemented.
### research/dossier — OPTIMIZE
- Phantom `scripts/office/validate.py` in Phase 10; 318-line body (longest in pack) with duplicated integrity boilerplate.
- The ≥30% disconfirming-evidence rule, source-tier tagging, and mandatory-hypothesis gate are excellent new-gen design (forces the model out of confirmation mode) — preserve verbatim.
- Glassdoor/Comparably scraping listed as a source will be blocked in practice; "degrade gracefully" is stated but the degraded output shape isn't.
- Verify: `python3 scripts/disconfirming_evidence_balance.py --help` exits 0; given a session with <30% disconfirming queries it returns a non-zero/warn signal.
- Verify: `python3 scripts/source_tier_classifier.py --help` exits 0; sec.gov → primary, a substack URL → tertiary.
- Verify: phantom validate.py reference removed or implemented.
### research/patent — OPTIMIZE
- Phantom `scripts/office/validate.py` in Phase 7.
- DOCX styling section gives `https://patents.uspto.gov/patent/...` as the USPTO hyperlink pattern — that host pattern is wrong (the skill's own source list correctly says `ppubs.uspto.gov`); links generated from it will 404.
- Sub-use-case routing, date discipline (filing/priority/publication/grant per use case), and CPC class follow-up are real practitioner expertise — keep.
- Verify: `python3 scripts/sub_use_case_router.py --sub-use-case novelty --jurisdictions "" --risk strict --known-art "US10000000B2"` exits 0 and emits a 5-8 query plan.
- Verify: `python3 scripts/family_resolver.py --help` exits 0.
- Verify: no `patents.uspto.gov/patent/` literal remains in SKILL.md.
### research/syllabus — OPTIMIZE
- Phantom `python scripts/office/validate.py` in Phase 6; Consensus-MCP hard dependency (same fix as litreview).
- `generate_reading_list.js` requires npm `docx`; fails with a clear message (verified) but neither SKILL.md Portability note nor plugin docs give the install one-liner next to the invocation.
- Applied-domain weaving + Bloom higher-order validator are genuinely non-obvious value — keep.
- Verify: `node scripts/generate_reading_list.js --help` without docx installed exits non-zero with the "npm install docx" message (graceful-fail contract).
- Verify: `python3 scripts/discussion_question_validator.py --help` and `topic_grouper.py --help` exit 0.
- Verify: phantom validate.py reference removed or implemented.
### research/notebooklm — REWRITE
- Freshness rot on a fast-iterating Google SPA: the hardcoded Studio inventory (9 types incl. "Table of Contents") no longer matches the product — NotebookLM added Video Overviews (2025) and Flashcards/Quiz, and reorganized report-style outputs; none appear anywhere in skill, scripts, or references (moderate-high confidence; needs re-verification against the live UI).
- Internal inconsistency: frontmatter description lists 8 Studio types, body Action 3 lists 9 — the plugin.json mirrors the stale 8.
- Known 2/6 checklist score reproduces: no `Use when` trigger phrasing, 290 lines, zero code blocks (no concrete invocation examples).
- Structure is salvageable (Step-0 environment gate, fire-and-notify async table, screenshot-first, find()-before-click are all sound discipline; `async_action_classifier.py` works); the rot-prone content is the hardcoded UI inventory + timing estimates. Rewrite to discover output types from the live Studio panel screenshot instead of enumerating them, add a "verified against NotebookLM as of <date>" maintenance marker, fix the 8-vs-9 contradiction.
- Verify: `python3 scripts/async_action_classifier.py --action "audio overview"` → `FIRE_AND_NOTIFY`; `--action "add source"` → wait verdict.
- Verify: frontmatter description and Action 3 list enumerate the same set (or neither enumerates).
- Verify: SKILL.md contains ≥1 fenced concrete-example block and a `Use when`-style trigger; checklist item 5 passes.
- Verify: a dated "UI verified" marker exists and is < 6 months old at release time.
## KEEP-verdict verification criteria
- **research-ops-skills (orchestrator):** SKILL.md signal table lists exactly 4 lanes matching the 4 sub-skill folder names; `grep -c "Never silently chain" SKILL.md` ≥ 1; every `skills/<sub-skill>/scripts/onboard.py` path it references resolves from `research-ops/`.
- **clinical-research:** `python3 scripts/sample_size_estimator.py --sample` exits 0, output contains "ESTIMATE" banner and `n_group1_with_dropout` > `n_group1_raw`; `phase_gate_scorer.py --sample --output json` → `verdict` ∈ {GO, GO-WITH-CONDITIONS, REDESIGN, NO-GO} and `named_owners` non-empty; `endpoint_selector.py --sample` flags the unvalidated surrogate below PRIMARY.
- **research-finance:** `capex_vs_opex_router.py --sample --standard ifrs` exits 0, every item carries `route to:` a named owner and the "DECISION SUPPORT ONLY" banner prints; `burn_runway_tracker.py --sample --output json` → `runway_months_approx` float + per-milestone `verdict`.
- **market-research:** `market_sizer.py --sample` prints BOTH `[top-down]` and `[bottoms-up]` TAM/SAM/SOM lines, a divergence %, and "TRIANGULATION FAILED" when delta > tolerance; `sample_size_planner.py --population 62000 --confidence 0.95 --moe 0.05` exits 0 with FPC-corrected n; `segmentation_scorer.py --sample` drops the solopreneur slice.
- **product-research:** `insight_synthesizer.py --sample --min-sources 3` promotes the 3-source cluster to INSIGHT and labels 1–2-source clusters ANECDOTE; `saturation_planner.py --method thematic --segments 3` emits a confidence label and the "not a power calculation" disclaimer; `study_designer.py --goal evaluative --stage live` redirects live A/B to experiment-designer.
## Agents
9 agents total (8 in `research/<plugin>/agents/`, 1 in `research-ops/agents/`). **All pass B2/B3 strongly** — each persona has distinct refusal behaviors that change outcomes (cs-dossier refuses without a hypothesis; cs-patent refuses without a sub-use-case; cs-research surfaces routing + override; cs-research-ops-orchestrator demands method-before-number) and verbatim voice lines, not adjective swaps. B1 issues:
- research/ agent descriptions describe behavior but lack `Use when`/`Use PROACTIVELY` trigger phrasing (same artifact as the SKILL.md gate).
- All 8 research/ agents pin `model: opus` — for a deterministic-routing front door (cs-research) sonnet would do; cost note only.
- research/ agents carry non-standard `skills:`/`domain:` frontmatter keys (harmless, but not part of the agent schema the repo's other domains use).
- cs-research-ops-orchestrator is the cleanest: standard frontmatter, `model: sonnet`, Skill tool wired for fork-routing.
## Commands
14 total: 8 `/cs:*` in research/ plugins, 6 in research-ops/. All pass C1 + C3 (each orchestrates intake gates, tool sequences, and refusal rules a bare prompt would not enforce). Findings:
- **research-ops commands are the better pattern:** proper `argument-hint:` field + explicit `$ARGUMENTS` interpolation + per-command three-tool workflow. `/cs:grill-research-ops` adds real value (docs-anchored one-question-at-a-time gate before any sub-skill).
- **research/ commands** embed the argument shape inside the description string and omit `argument-hint` / `$ARGUMENTS` (C2 partial) — they read as documentation pages for the agent rather than parameterized commands. Targeted fix: add `argument-hint` + `$ARGUMENTS` block to all 8.
- Mild redundancy: `/cs:research` + 6 specialist commands + the router skill itself is three entry points to the same routing logic; acceptable, but the specialist commands should state "or just use /cs:research" to avoid user confusion.
## Plugin manifests
All 9 pass `scripts/check_plugin_json.py --all` (E1). Versions uniformly 2.9.0 and present in marketplace.json (E3). Issues:
- **Name mismatch (E3 minor):** marketplace entry `research-orchestrator` points at `./research/research` whose plugin.json `name` is `research`. Intentional slug-disambiguation per ClawHub rules, but the inconsistency is undocumented in either file.
- **Stale content drift (E2):** `notebooklm` plugin.json description carries the 8-type Studio list (mirrors the stale SKILL.md frontmatter) — fix together with the notebooklm rewrite.
- research-ops single-domain-plugin description accurately enumerates the 4 sub-skills + orchestrator; matches contents.
- Hygiene: committed `__pycache__/*.pyc` under `research-ops/skills/{clinical-research,market-research,product-research,research-finance}/scripts/` should be removed/ignored.

4
business-growth/.claude-plugin/plugin.json
View file

@ -1,6 +1,6 @@
{
"name": "business-growth-skills",
"description": "5 business & growth skills: customer success manager, sales engineer, revenue operations, contract & proposal writer, and BizDev-toolkit. Agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw.",
"description": "4 business & growth skills plus a router: customer success manager (health scoring, churn), sales engineer (RFP analysis, PoC planning), revenue operations (pipeline, forecast accuracy, GTM), and contract & proposal writer. Agent skill and plugin for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw.",
"version": "2.9.0",
"author": {
"name": "Alireza Rezvani",
@ -12,4 +12,4 @@
"skills": [
"./skills"
]
}
}

45
business-growth/skills/business-growth-skills/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: "business-growth-skills"
description: "4 business growth agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Customer success (health scoring, churn), sales engineer (RFP), revenue operations (pipeline, GTM), contract & proposal writer. Python tools (stdlib-only)."
description: "Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP')."
version: 2.9.0
author: Alireza Rezvani
license: MIT
@ -16,41 +16,30 @@ agents:
- openclaw
---
# Business & Growth Skills
# Business & Growth Skills — Router
4 production-ready skills for customer success, sales, and revenue operations.
This plugin bundles **4 skills** (this router is the 5th folder under `business-growth/skills/`). Each skill is self-contained.
## Quick Start
## Routing table
### Claude Code
```
/read business-growth/customer-success-manager/SKILL.md
```
Match the request, then load `business-growth/skills/<skill>/SKILL.md`. If multiple rows match, ask one clarifying question first.
### Codex CLI
```bash
npx agent-skills-cli add alirezarezvani/claude-skills/business-growth
```
| Request signals | Skill | Path |
|---|---|---|
| Customer health scores, churn risk, expansion plays | customer-success-manager | `skills/customer-success-manager/` |
| RFP/RFI coverage, competitive positioning, PoC plans | sales-engineer | `skills/sales-engineer/` |
| Pipeline coverage, forecast accuracy (MAPE), GTM efficiency | revenue-operations | `skills/revenue-operations/` |
| Proposals, contracts, statements of work, DPAs | contract-and-proposal-writer | `skills/contract-and-proposal-writer/` |
## Skills Overview
| Skill | Folder | Focus |
|-------|--------|-------|
| Customer Success Manager | `customer-success-manager/` | Health scoring, churn prediction, expansion |
| Sales Engineer | `sales-engineer/` | RFP analysis, competitive matrices, PoC planning |
| Revenue Operations | `revenue-operations/` | Pipeline analysis, forecast accuracy, GTM metrics |
| Contract & Proposal Writer | `contract-and-proposal-writer/` | Proposal generation, contract templates |
## Python Tools
9 scripts, all stdlib-only:
## Quick start
```bash
python3 customer-success-manager/scripts/health_score_calculator.py --help
python3 revenue-operations/scripts/pipeline_analyzer.py --help
# Example: route an account-health request
cat business-growth/skills/customer-success-manager/SKILL.md
python3 business-growth/skills/customer-success-manager/scripts/health_score_calculator.py --help
```
## Rules
- Load only the specific skill SKILL.md you need
- Use Python tools for scoring and metrics, not manual estimates
- Route to exactly one skill, then follow that skill's workflow. This router ships no tools of its own.
- Use the skills' Python scorers for metrics, not manual estimates; deal/contract outputs are drafts for human legal/commercial review.

6
business-growth/skills/sales-engineer/SKILL.md
View file

@ -211,9 +211,9 @@ python scripts/poc_planner.py poc_data.json --format json # JSON output
## Integration Points
- **Marketing Skills** - Leverage competitive intelligence and messaging frameworks from `../../marketing-skill/`
- **Product Team** - Coordinate on roadmap items flagged as "Planned" in RFP analysis from `../../product-team/`
- **C-Level Advisory** - Escalate strategic deals requiring executive engagement from `../../c-level-advisor/`
- **Marketing Skills** - Leverage competitive intelligence and messaging frameworks from `marketing-skill/`
- **Product Team** - Coordinate on roadmap items flagged as "Planned" in RFP analysis from `product-team/`
- **C-Level Advisory** - Escalate strategic deals requiring executive engagement from `c-level-advisor/`
- **Customer Success** - Hand off POC results and success criteria to CSM from `../customer-success-manager/`
---

7
business-operations/skills/capacity-planner/SKILL.md
View file

@ -83,6 +83,13 @@ It produces three artifacts:
All three accept `--input <path>` (JSON), `--output {markdown,json}`,
`--sample` (built-in example), and `--help`. Stdlib only.
## Quick example
```bash
# Emits an Erlang-C capacity model (required headcount + P50/P90/P99 breach probabilities) for the built-in example
cd business-operations/skills/capacity-planner && python3 scripts/capacity_modeler.py --sample
```
## References
- `references/queueing_theory_canon.md` — Erlang, Little, Hopp &

9
business-operations/skills/internal-comms/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: internal-comms
description: Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a benefit change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience is employees (not customers). Triggers on "all-hands announcement", "town-hall script", "change comms", "internal newsletter", "rollout comms", "policy change announcement", "re-org announcement", "internal FAQ", "manager talking points", "Prosci ADKAR", "Kotter 8-step", "layoff comms", "RIF comms", "internal memo". Pairs Prosci ADKAR (Awareness / Desire / Knowledge / Ability / Reinforcement) and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points. Industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Distinct from marketing-skill/* (external/customer-facing), c-level-advisor/internal-narrative (strategic framing, not tactical drafts), and c-level-advisor/change-management (executive change strategy, not the comms package itself).
description: Use when a Head of People Ops, BizOps lead, or Internal Communications owner needs to draft and sequence an internal-only change-management communication — a re-org announcement, a tool rollout, a policy change, a leadership transition, a layoff, an acquisition close, or an internal product launch — and the audience is employees (not customers). Pairs Prosci ADKAR and Kotter's 8-step change model with deterministic stdlib-only Python tools to produce a sequenced touchpoint calendar, a Kotter-compliant primary announcement, an audience-segmented FAQ, and manager cascade talking points; industry-tuned via --profile {tech-startup, scaleup, enterprise, public-company, non-profit}. Triggers on "all-hands announcement", "change comms", "rollout comms", "re-org announcement", "manager talking points", "layoff comms".
version: 2.8.0
author: claude-code-skills
license: MIT
@ -59,6 +59,13 @@ Five-step deterministic flow. Follow in order.
All three: stdlib only, `--help` and `--sample` exit 0, accept `--input <json>` and `--output {markdown,json}`.
## Quick example
```bash
# Emits the 4-artifact comms package (pre-comm, announcement, FAQ, follow-up) for the built-in tool-rollout example
cd business-operations/skills/internal-comms && python3 scripts/comms_template_filler.py --sample
```
## References
- `references/change_management_canon.md` — Jeff Hiatt *ADKAR* (Prosci), John Kotter *Leading Change* (8-step), William Bridges *Managing Transitions* (Endings / Neutral Zone / Beginnings), Edgar Schein *Organizational Culture and Leadership*, McKinsey 7-S framework, Heath brothers *Switch*, Patrick Lencioni *The Advantage*.

11
business-operations/skills/knowledge-ops/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: knowledge-ops
description: Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding, expense reimbursement, system-access provisioning, customer-escalation playbook) — including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, ops onboarding doc generation, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Kaoru Ishikawa's 5W2H method, Atul Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4 Service Operation, FDA 21 CFR Part 211, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists. Distinct from `engineering/llm-wiki` (Karpathy-style personal PKM second brain), `engineering-team/runbook-generator` (system-ops production debugging runbook), `project-management/*` (Jira/Confluence delivery + ticket tracking), and sibling `business-operations/process-mapper` (BPMN process *design*, while knowledge-ops is process *documentation*).
description: Use when a Head of Ops, Knowledge Manager, or TPM-Internal needs to author, validate, or clean up company SOPs and internal runbooks (procurement intake, vendor offboarding, incident-comms cascade, employee onboarding) — including 5W2H completeness checks (Who-What-When-Where-Why-How-HowMuch), cross-link and orphan-page validation across a sprawling Notion/Confluence/Obsidian wiki, KB ingestion + hygiene reporting, and runbook step verification (named owner, expected duration, observable success signal, rollback path, escalation contact). Pairs Ishikawa's 5W2H method, Gawande's *The Checklist Manifesto*, ISO 9001, ITIL v4, and Google SRE Workbook runbook discipline with deterministic stdlib-only Python tools that score completeness, detect anti-patterns, and emit prioritized cleanup lists (e.g., "validate this runbook before it goes into rotation", "audit our Confluence wiki for stale and orphaned SOPs").
context: fork
version: 2.8.0
author: claude-code-skills
@ -18,7 +18,7 @@ Company SOP + internal runbook authoring, 5W2H completeness validation, and KB h
An ops organization three years in accumulates a sprawl: 600 Notion pages, 200 Confluence runbooks, three Obsidian vaults, a `Drive/SOPs/` folder, and a `Slack #ops-questions` channel that exists because nobody can find the canonical doc. Predictable failure modes:
1. **No owner** — 40% of SOPs name "the team" instead of a person. When the doc rots, nobody is accountable.
2. **No last-reviewed date** — a 2023 vendor-offboarding SOP still references a procurement tool sunset in 2024.
2. **No last-reviewed date** — a years-old vendor-offboarding SOP still references a procurement tool that was sunset over a year ago.
3. **Vague success signals** — runbook step 4 says "verify the service is up". A new operator can't tell what that means.
4. **No rollback path** — incident-comms cascade runbook tells you how to send the alert. It doesn't tell you how to retract it when the alert was wrong.
5. **Orphan pages** — half the KB has no inbound links. Nobody finds them via navigation; they only exist because somebody knew the URL.
@ -52,6 +52,13 @@ Four-step deterministic flow (matches the ops org's actual workflow, not an abst
**`scripts/kb_ingester.py`** — Walks a directory of markdown files (Notion export, Confluence space export, Obsidian vault, `Drive/SOPs/` directory). Extracts: (a) cross-link map (which page references which, via markdown `[link](path)` syntax), (b) glossary candidates (frequently used proper nouns and acronyms that recur in 3+ docs without a single canonical definition page), (c) orphan pages (no inbound links from anywhere in the vault), (d) glossary drift (the same term defined or used inconsistently across docs — e.g., "CSM" expanded differently in two places), (e) stale pages (no edit in > 12 months, detected via filesystem mtime or YAML `last_reviewed` frontmatter), (f) missing-owner pages (no `owner:` field in frontmatter). Emits a KB health report markdown with a prioritized top-20 cleanup list ranked by `staleness × inbound-link-count` (high-traffic stale docs first). `--sample` builds a tiny synthetic 8-page vault in a tmpdir and runs the full pipeline against it. Stdlib only.
## Quick example
```bash
# Builds a synthetic 8-page vault and emits a KB health report (orphans, stale pages, glossary drift, top-20 cleanup list)
cd business-operations/skills/knowledge-ops && python3 scripts/kb_ingester.py --sample
```
## References
- `references/5w2h_sop_canon.md` — Kaoru Ishikawa's 5W2H method, Toyota standard-work discipline, Atul Gawande's checklist manifesto, Atlassian Confluence SOP guidance, ISO 9001 SOP requirements, ITIL v4 Service Operation, FDA 21 CFR Part 211. Eight cited sources covering SOP authoring canon.

7
business-operations/skills/process-mapper/SKILL.md
View file

@ -47,6 +47,13 @@ Five-step deterministic flow:
**`scripts/cycle_time_analyzer.py`** — Computes total P50 and P90 cycle time, value-add ratio (VA%), wait %, rework %, and a Little's-Law throughput estimate (WIP / cycle time). Per Lean canon: VA% > 25% = HEALTHY, 10–25% = TYPICAL (most non-manufacturing processes land here), < 10% = WASTE-HEAVY.
## Quick example
```bash
# Renders a BPMN-style swim-lane diagram + normalized JSON for the built-in 6-stage procurement-intake example
cd business-operations/skills/process-mapper && python3 scripts/process_documenter.py --sample
```
## References
- `references/lean_six_sigma_canon.md` — TIMWOOD wastes, value-stream mapping, Theory of Constraints, Kanban WIP, Little's Law. Cites Womack & Jones, Rother & Shook, Goldratt, Ohno, Liker, Pyzdek, Anderson.

9
business-operations/skills/procurement-optimizer/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: procurement-optimizer
description: Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base — when the user needs to do a spend audit, spend categorization (UNSPSC-aligned), purchasing-cycle analysis, or risk-balanced supplier consolidation. Triggers on "spend audit", "SaaS audit", "spend categorization", "supplier rationalization", "supplier consolidation", "purchasing cycle", "procurement review", "category strategy", "duplicate SaaS", "renewal cluster". Ships 3 stdlib-only Python tools (UNSPSC-aligned spend categorizer with Pareto breakdown and industry profiles, purchasing-cycle analyzer that surfaces bottleneck categories per Goldratt's Theory of Constraints, supplier-consolidation planner that refuses single-source recommendations for tier-1 categories without a documented break-glass plan), 3 reference docs each citing 7+ authoritative sources (A.T. Kearney / Hackett / Spend Matters / UNSPSC / Productiv / Vendr / Tropic / IACCM / ISM / BCG), and a 20-minute spend-intake template. Distinct from sibling vendor-management (performance scoring of vendors you keep paying), finance/financial-analysis (close + report, not category strategy), and c-level-advisor/general-counsel-advisor (contract law, not category rationalization).
description: Use when running an annual SaaS audit, doing category-level spend review, or rationalizing the supplier base — when the user needs a spend audit, spend categorization (UNSPSC-aligned with Pareto breakdown and industry profiles), purchasing-cycle analysis (bottleneck categories per Goldratt's Theory of Constraints), or risk-balanced supplier consolidation that refuses single-source recommendations for tier-1 categories without a documented break-glass plan. Triggers on "spend audit", "SaaS audit", "spend categorization", "supplier rationalization", "supplier consolidation", "category strategy", "duplicate SaaS", "renewal cluster".
version: 2.8.0
author: claude-code-skills
license: MIT
@ -99,6 +99,13 @@ Combine the 3 artifacts into a BizOps-ready digest:
All three accept `--input` (JSON), `--output` (markdown path), `--sample` (run with built-in sample data), and `--help`. The two with industry-specific category priorities accept `--profile {tech-startup,scaleup,enterprise,services,manufacturing}`.
## Quick example
```bash
# Emits a UNSPSC-aligned spend categorization with Pareto breakdown for the built-in sample spend file
cd business-operations/skills/procurement-optimizer && python3 scripts/spend_categorizer.py --sample
```
## References
- `references/spend_management_canon.md` — A.T. Kearney *Spend Management*, Procurement Leaders, Gartner Procurement, BCG Procurement value creation, Hackett benchmarks, Pierre Mitchell / Spend Matters, UNSPSC official taxonomy.

9
business-operations/skills/vendor-management/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: vendor-management
description: Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships — running a vendor scorecard, tracking SLA compliance, classifying third-party risk, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Triggers on "vendor SLA", "vendor scorecard", "third-party risk", "TPRM", "vendor review", "SaaS audit", "supplier performance", "vendor health check", "renewal review". Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Ships 3 stdlib-only Python tools (vendor scorer with industry tuning, SLA compliance tracker with credit-claim flags, vendor risk classifier across 4 risk vectors), 3 reference docs each citing 7+ authoritative sources (Gartner / Shared Assessments / NIST / ISO 27036 / breach post-mortems), and a 5-vendor catalog template. Distinct from c-level-advisor/general-counsel-advisor (contract law, not operational management), business-growth/contract-and-proposal-writer (outbound proposals, not inbound vendor scoring), and sibling procurement-optimizer (spend categorization, not vendor performance).
description: Use when reviewing, scoring, or auditing third-party SaaS / vendor relationships — running a vendor scorecard with industry tuning, tracking SLA compliance with credit-claim flags, classifying third-party risk across 4 risk vectors, preparing a tier-1 vendor review, or auditing the SaaS portfolio. Forks context so large vendor catalogs (50-500 line items) and SLA logs don't pollute the parent thread. Triggers on "vendor SLA", "vendor scorecard", "third-party risk", "TPRM", "vendor review", "supplier performance", "vendor health check", "renewal review".
context: fork
version: 2.8.0
author: claude-code-skills
@ -110,6 +110,13 @@ Combine the 3 artifacts into a final BizOps / VMO digest:
All three accept `--input` (JSON), `--output` (markdown path), `--sample` (run with built-in sample data), and `--help`. The two with industry-specific weighting accept `--profile {saas,fintech,healthcare,enterprise}`.
## Quick example
```bash
# Emits a weighted vendor scorecard (industry-tuned dimensions + per-vendor verdict) for the built-in sample catalog
cd business-operations/skills/vendor-management && python3 scripts/vendor_scorer.py --sample
```
## References
- `references/vendor_management_canon.md` — Gartner / Shared Assessments / ISO 27036 / NIST 800-161 / Forrester / ISACA / Vendr industry reports

8
c-level-advisor/README.md
View file

@ -36,10 +36,10 @@ npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor --agent
```bash
# CEO Advisor
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/ceo-advisor
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/skills/ceo-advisor
# CTO Advisor
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/cto-advisor
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/skills/cto-advisor
```
**Supported Agents:** Claude Code, Cursor, VS Code, Copilot, Goose, Amp, Codex
@ -148,7 +148,7 @@ This C-Level advisory skills collection provides executive leadership guidance f
1. **Install CEO Advisor:**
```bash
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/ceo-advisor
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/skills/ceo-advisor
```
2. **Evaluate Strategic Initiative:**
@ -170,7 +170,7 @@ This C-Level advisory skills collection provides executive leadership guidance f
1. **Install CTO Advisor:**
```bash
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/cto-advisor
npx ai-agent-skills install alirezarezvani/claude-skills/c-level-advisor/skills/cto-advisor
```
2. **Analyze Technical Debt:**

2
c-level-advisor/c-level-agents/agents/cs-caio-advisor.md
View file

@ -158,7 +158,7 @@ python ../../skills/chief-ai-officer-advisor/scripts/ai_cost_economics.py worklo
## Related Agents
- [cs-cdo-advisor](cs-cdo-advisor.md) — Training data rights, data strategy (chains directly to model decisions)
- [cs-cto-advisor](../../../../agents/c-level/cs-cto-advisor.md) — Architecture capacity, scaling cliffs
- [cs-cto-advisor](../../../agents/c-level/cs-cto-advisor.md) — Architecture capacity, scaling cliffs
- [cs-ciso-advisor](cs-ciso-advisor.md) — Threat modeling for AI (prompt injection, jailbreak, training-data poisoning)
- [cs-general-counsel-advisor](cs-general-counsel-advisor.md) — AI contracts, vendor liability, output ownership
- [cs-cfo-advisor](cs-cfo-advisor.md) — Build-vs-buy TCO, multi-year vendor commitments

2
c-level-advisor/c-level-agents/agents/cs-cco-advisor.md
View file

@ -160,7 +160,7 @@ python ../../skills/chief-customer-officer-advisor/scripts/cs_coverage_calculato
- [cs-cmo-advisor](cs-cmo-advisor.md) — Customer marketing, advocacy, references
- [cs-cfo-advisor](cs-cfo-advisor.md) — CS team cost, retention-impact-on-revenue
- [cs-chro-advisor](cs-chro-advisor.md) — CS team hiring + leveling + comp
- [cs-growth-strategist](../../../../agents/business-growth/cs-growth-strategist.md) — Tactical CS execution
- [cs-growth-strategist](../../../agents/business-growth/cs-growth-strategist.md) — Tactical CS execution
## References

4
c-level-advisor/c-level-agents/agents/cs-cdo-advisor.md
View file

@ -104,7 +104,7 @@ python ../../skills/chief-data-officer-advisor/scripts/data_asset_valuator.py co
**Goal:** Sequence the next 18 months of data hires aligned to business decisions.
1. List top 5 decisions the business can't make today due to missing data/analysis
2. Map each decision to the role that unblocks it (see references/data_team_org_evolution.md)
2. Map each decision to the role that unblocks it (see ../../skills/chief-data-officer-advisor/references/data_team_org_evolution.md)
3. Sequence hires (one at a time, ramp before next)
4. Cross-check with cs-chro-advisor on comp bands + leveling
5. Identify centralize-vs-embed trigger date
@ -144,7 +144,7 @@ echo "Kill criteria + checkpoint dates in each output."
## Related Agents
- [cs-cto-advisor](../../../../agents/c-level/cs-cto-advisor.md) — architecture capacity
- [cs-cto-advisor](../../../agents/c-level/cs-cto-advisor.md) — architecture capacity
- [cs-ciso-advisor](cs-ciso-advisor.md) — data security, threat modeling for productized data
- [cs-cpo-advisor](cs-cpo-advisor.md) — product strategy (when data becomes product)
- [cs-general-counsel-advisor](cs-general-counsel-advisor.md) — contractual constraints, DPA, training-rights

4
c-level-advisor/c-level-agents/agents/cs-cfo-advisor.md
View file

@ -114,9 +114,9 @@ echo "Artifacts ready in /tmp/. Feed into /cs:boardroom brief."
## Related Agents
- [cs-ceo-advisor](../../../../agents/c-level/cs-ceo-advisor.md) — strategy & capital allocation partner
- [cs-ceo-advisor](../../../agents/c-level/cs-ceo-advisor.md) — strategy & capital allocation partner
- [cs-cro-advisor](cs-cro-advisor.md) — revenue forecast feed
- [cs-financial-analyst](../../../../agents/finance/cs-financial-analyst.md) — deep modeling
- [cs-financial-analyst](../../../agents/finance/cs-financial-analyst.md) — deep modeling
- [cs-chief-of-staff](cs-chief-of-staff.md) — routes financial questions here
## References

6
c-level-advisor/c-level-agents/agents/cs-chief-of-staff.md
View file

@ -29,8 +29,8 @@ This is the agent the founder talks to **first**. It pulls company-context.md, p
### Knowledge Bases
- `../../skills/chief-of-staff/references/routing_logic.md` — keywords → role mapping, multi-role triggers
- `../../skills/chief-of-staff/references/synthesis_patterns.md` — how to combine inputs from multiple advisors
- `../../skills/chief-of-staff/references/routing-matrix.md` — keywords → role mapping, multi-role triggers
- `../../skills/chief-of-staff/references/synthesis-framework.md` — how to combine inputs from multiple advisors
### Coordination Skills
@ -119,7 +119,7 @@ echo "Decision logged to ~/.claude/decisions/raw/$(date +%Y-%m-%d)-$RANDOM.md"
## Related Agents
- All cs-* C-level advisors (routes to them)
- [cs-ceo-advisor](../../../../agents/c-level/cs-ceo-advisor.md) — primary upward report
- [cs-ceo-advisor](../../../agents/c-level/cs-ceo-advisor.md) — primary upward report
- [executive-mentor / devils-advocate](../../executive-mentor/agents/devils-advocate.md) — pre-decision adversarial check
## References

12
c-level-advisor/c-level-agents/agents/cs-chro-advisor.md
View file

@ -39,9 +39,9 @@ Pairs with `cs-coo-advisor` (org design), `cs-cfo-advisor` (comp budget), and `c
### Knowledge Bases
- `../../skills/chro-advisor/references/hiring_systems.md` — sourcing channels, interview rubrics, scorecards, time-to-fill
- `../../skills/chro-advisor/references/comp_philosophy.md` — band design, equity strategy, refresh policy
- `../../skills/chro-advisor/references/leveling_ladders.md` — IC + manager tracks, level expectations, promotion criteria
- `../../skills/chro-advisor/references/people_strategy.md` — sourcing channels, interview rubrics, scorecards, time-to-fill
- `../../skills/chro-advisor/references/comp_frameworks.md` — band design, equity strategy, refresh policy
- `../../skills/chro-advisor/references/org_design.md` — IC + manager tracks, level expectations, promotion criteria
## Workflows
@ -92,7 +92,7 @@ python ../../skills/chro-advisor/scripts/hiring_plan_modeler.py
echo "👥 CHRO Quarterly Review"
python ../../skills/chro-advisor/scripts/hiring_plan_modeler.py
python ../../skills/chro-advisor/scripts/comp_benchmarker.py
echo "Ladder reference: ../../skills/chro-advisor/references/leveling_ladders.md"
echo "Ladder reference: ../../skills/chro-advisor/references/org_design.md"
```
## Success Metrics
@ -107,8 +107,8 @@ echo "Ladder reference: ../../skills/chro-advisor/references/leveling_ladders.md
- [cs-coo-advisor](cs-coo-advisor.md) — org design partner
- [cs-cfo-advisor](cs-cfo-advisor.md) — comp budget
- [cs-ceo-advisor](../../../../agents/c-level/cs-ceo-advisor.md) — exec team
- [cs-workspace-admin](../../../../agents/engineering-team/cs-workspace-admin.md) — onboarding tooling
- [cs-ceo-advisor](../../../agents/c-level/cs-ceo-advisor.md) — exec team
- [cs-workspace-admin](../../../agents/engineering-team/cs-workspace-admin.md) — onboarding tooling
## References

8
c-level-advisor/c-level-agents/agents/cs-ciso-advisor.md
View file

@ -39,7 +39,7 @@ Pairs with `cs-cto-advisor` (security architecture), `cs-cfo-advisor` (risk quan
### Knowledge Bases
- `../../skills/ciso-advisor/references/threat_modeling.md` — STRIDE, PASTA, attacker journey
- `../../skills/ciso-advisor/references/security_strategy.md` — STRIDE, PASTA, attacker journey
- `../../skills/ciso-advisor/references/compliance_roadmap.md` — SOC 2 Type 2, ISO 27001, GDPR sequencing
- `../../skills/ciso-advisor/references/incident_response.md` — IR runbooks, comms plan, regulator notification windows
@ -110,10 +110,10 @@ echo "IR runbook check: ../../skills/ciso-advisor/references/incident_response.m
## Related Agents
- [cs-cto-advisor](../../../../agents/c-level/cs-cto-advisor.md) — security architecture
- [cs-cto-advisor](../../../agents/c-level/cs-cto-advisor.md) — security architecture
- [cs-cfo-advisor](cs-cfo-advisor.md) — risk → insurance, audit budget
- [cs-quality-regulatory](../../../../agents/ra-qm-team/cs-quality-regulatory.md) — ISO 27001, GDPR execution
- [cs-senior-engineer](../../../../agents/engineering/cs-senior-engineer.md) — secure coding
- [cs-quality-regulatory](../../../agents/ra-qm-team/cs-quality-regulatory.md) — ISO 27001, GDPR execution
- [cs-senior-engineer](../../../agents/engineering/cs-senior-engineer.md) — secure coding
## References

8
c-level-advisor/c-level-agents/agents/cs-cmo-advisor.md
View file

@ -40,8 +40,8 @@ Pairs with `cs-cpo-advisor` (positioning ↔ product), `cs-cro-advisor` (positio
### Knowledge Bases
- `../../skills/cmo-advisor/references/brand_positioning.md` — category design, message house, narrative arcs
- `../../skills/cmo-advisor/references/growth_playbooks.md` — channel-specific motions, PLG vs sales-led
- `../../skills/cmo-advisor/references/marketing_operations.md` — attribution, cadence, content ops
- `../../skills/cmo-advisor/references/growth_frameworks.md` — channel-specific motions, PLG vs sales-led
- `../../skills/cmo-advisor/references/marketing_org.md` — attribution, cadence, content ops
### Adjacent Execution
@ -111,8 +111,8 @@ echo "📚 Reference: positioning + playbooks"
- [cs-cpo-advisor](cs-cpo-advisor.md) — positioning ↔ product alignment
- [cs-cro-advisor](cs-cro-advisor.md) — pipeline contribution
- [cs-content-creator](../../../../agents/marketing/cs-content-creator.md) — execution
- [cs-demand-gen-specialist](../../../../agents/marketing/cs-demand-gen-specialist.md) — execution
- [cs-content-creator](../../../agents/marketing/cs-content-creator.md) — execution
- [cs-demand-gen-specialist](../../../agents/marketing/cs-demand-gen-specialist.md) — execution
## References

10
c-level-advisor/c-level-agents/agents/cs-coo-advisor.md
View file

@ -39,9 +39,9 @@ Pairs with `cs-cfo-advisor` (finance cadence), `cs-cro-advisor` (revenue cadence
### Knowledge Bases
- `../../skills/coo-advisor/references/operating_cadence.md` — weekly/monthly/quarterly rhythm, meeting design
- `../../skills/coo-advisor/references/okr_execution.md` — OKR design, scoring, cascading
- `../../skills/coo-advisor/references/scaling_playbooks.md` — 1-10, 10-100, 100-1000 transitions
- `../../skills/coo-advisor/references/ops_cadence.md` — weekly/monthly/quarterly rhythm, meeting design
- `../../skills/coo-advisor/references/process_frameworks.md` — OKR design, scoring, cascading
- `../../skills/coo-advisor/references/scaling_playbook.md` — 1-10, 10-100, 100-1000 transitions
### Adjacent Skills
@ -97,7 +97,7 @@ python ../../skills/coo-advisor/scripts/okr_tracker.py
echo "⚙️ COO Quarterly Review"
python ../../skills/coo-advisor/scripts/okr_tracker.py
python ../../skills/coo-advisor/scripts/ops_efficiency_analyzer.py
echo "Reference: ../../skills/coo-advisor/references/operating_cadence.md"
echo "Reference: ../../skills/coo-advisor/references/ops_cadence.md"
```
## Success Metrics
@ -113,7 +113,7 @@ echo "Reference: ../../skills/coo-advisor/references/operating_cadence.md"
- [cs-cfo-advisor](cs-cfo-advisor.md) — finance cadence
- [cs-cro-advisor](cs-cro-advisor.md) — revenue cadence
- [cs-chief-of-staff](cs-chief-of-staff.md) — decision logging
- [cs-engineering-lead](../../../../agents/engineering-team/cs-engineering-lead.md) — eng ops
- [cs-engineering-lead](../../../agents/engineering-team/cs-engineering-lead.md) — eng ops
## References

14
c-level-advisor/c-level-agents/agents/cs-cpo-advisor.md
View file

@ -39,13 +39,13 @@ Pairs with `cs-cmo-advisor` (positioning ↔ product), `cs-cro-advisor` (win/los
### Knowledge Bases
- `../../skills/cpo-advisor/references/product_vision.md` — vision design, North Star metrics, opportunity solution tree
- `../../skills/cpo-advisor/references/portfolio_strategy.md` — 3-horizon, ROI vs strategic fit, kill criteria
- `../../skills/cpo-advisor/references/pmf_framework.md` — Sean Ellis, retention, organic pull, what PMF actually looks like
- `../../skills/cpo-advisor/references/product_strategy.md` — vision design, North Star metrics, opportunity solution tree
- `../../skills/cpo-advisor/references/product_org_design.md` — 3-horizon, ROI vs strategic fit, kill criteria
- `../../skills/cpo-advisor/references/pmf_playbook.md` — Sean Ellis, retention, organic pull, what PMF actually looks like
### Adjacent Execution
- `../../../../product-team/product-manager-toolkit/` — RICE, OKR cascade, user stories
- `../../../product-team/skills/product-manager-toolkit/` — RICE, OKR cascade, user stories
## Workflows
@ -96,7 +96,7 @@ python ../../skills/cpo-advisor/scripts/pmf_scorer.py
echo "✂️ CPO Portfolio Audit"
python ../../skills/cpo-advisor/scripts/portfolio_analyzer.py
python ../../skills/cpo-advisor/scripts/pmf_scorer.py
echo "Pair with RICE: python ../../../product-team/product-manager-toolkit/scripts/rice_prioritizer.py"
echo "Pair with RICE: python ../../../product-team/skills/product-manager-toolkit/scripts/rice_prioritizer.py"
```
## Success Metrics
@ -111,8 +111,8 @@ echo "Pair with RICE: python ../../../product-team/product-manager-toolkit/scrip
- [cs-cmo-advisor](cs-cmo-advisor.md) — positioning alignment
- [cs-cro-advisor](cs-cro-advisor.md) — win/loss feedback
- [cs-product-manager](../../../../agents/product/cs-product-manager.md) — execution
- [cs-product-strategist](../../../../agents/product/cs-product-strategist.md) — OKR cascade
- [cs-product-manager](../../../agents/product/cs-product-manager.md) — execution
- [cs-product-strategist](../../../agents/product/cs-product-strategist.md) — OKR cascade
## References

8
c-level-advisor/c-level-agents/agents/cs-cro-advisor.md
View file

@ -39,9 +39,9 @@ Pairs with `cs-cfo-advisor` (revenue → cash conversion), `cs-cmo-advisor` (pip
### Knowledge Bases
- `../../skills/cro-advisor/references/revenue_operations.md` — pipeline cadence, win/loss process, forecasting hygiene
- `../../skills/cro-advisor/references/sales_motion.md` — PLG vs sales-led, hiring profiles, ramp curves
- `../../skills/cro-advisor/references/retention_expansion.md` — NRR levers, customer success cadence, expansion plays
- `../../skills/cro-advisor/references/sales_playbook.md` — pipeline cadence, win/loss process, forecasting hygiene
- `../../skills/cro-advisor/references/pricing_strategy.md` — PLG vs sales-led, hiring profiles, ramp curves
- `../../skills/cro-advisor/references/nrr_playbook.md` — NRR levers, customer success cadence, expansion plays
## Workflows
@ -109,7 +109,7 @@ echo "Pipeline coverage and retention dashboard ready."
- [cs-cfo-advisor](cs-cfo-advisor.md) — revenue → cash conversion
- [cs-cmo-advisor](cs-cmo-advisor.md) — pipeline contribution
- [cs-cpo-advisor](cs-cpo-advisor.md) — product gaps in win/loss
- [cs-growth-strategist](../../../../agents/business-growth/cs-growth-strategist.md) — execution
- [cs-growth-strategist](../../../agents/business-growth/cs-growth-strategist.md) — execution
## References

4
c-level-advisor/c-level-agents/agents/cs-general-counsel-advisor.md
View file

@ -152,8 +152,8 @@ echo " ☐ /cs:freeze applied if irreversible (term sheet, M&A LOI, employment
- [cs-cfo-advisor](cs-cfo-advisor.md) — term sheet → dilution math
- [cs-ciso-advisor](cs-ciso-advisor.md) — data-touching contracts, compliance overlap
- [cs-ceo-advisor](../../../../agents/c-level/cs-ceo-advisor.md) — board / fundraising strategic context
- [cs-quality-regulatory](../../../../agents/ra-qm-team/cs-quality-regulatory.md) — regulated-industry execution (ISO 13485, MDR, FDA)
- [cs-ceo-advisor](../../../agents/c-level/cs-ceo-advisor.md) — board / fundraising strategic context
- [cs-quality-regulatory](../../../agents/ra-qm-team/cs-quality-regulatory.md) — regulated-industry execution (ISO 13485, MDR, FDA)
## References

4
c-level-advisor/c-level-agents/agents/cs-vpe-advisor.md
View file

@ -145,11 +145,11 @@ python ../../skills/vpe-advisor/scripts/eng_team_structure_designer.py current-t
## Related Agents
- [cs-cto-advisor](../../../../agents/c-level/cs-cto-advisor.md) — Architecture, scaling cliffs (CTO decides what to build; VPE decides how to ship)
- [cs-cto-advisor](../../../agents/c-level/cs-cto-advisor.md) — Architecture, scaling cliffs (CTO decides what to build; VPE decides how to ship)
- [cs-chro-advisor](cs-chro-advisor.md) — Hiring systems (ladders, bands)
- [cs-coo-advisor](cs-coo-advisor.md) — Operating cadence company-wide
- [cs-cfo-advisor](cs-cfo-advisor.md) — Cost-per-hire envelope, eng budget
- [cs-engineering-lead](../../../../agents/engineering-team/cs-engineering-lead.md) — Day-to-day incident + on-call coordination
- [cs-engineering-lead](../../../agents/engineering-team/cs-engineering-lead.md) — Day-to-day incident + on-call coordination
## References

2
c-level-advisor/c-level-agents/skills/boardroom/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: "boardroom"
description: "/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo."
description: "/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call."
---
# /cs:boardroom — Multi-Role Boardroom Deliberation

7
c-level-advisor/c-level-agents/skills/brief/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: "brief"
description: "/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline."
description: "/cs:brief <topic> — Generate a one-page strategy brief from an office-hours intake. First step in the strategic sprint pipeline. Use when a strategic question needs to be framed before boardroom deliberation — e.g. locking options, assumptions, and success criteria for a pricing change or a market-entry decision."
---
# /cs:brief — One-Page Strategy Brief
@ -68,6 +68,11 @@ A single Markdown file under `~/.claude/briefs/YYYY-MM-DD-<slug>.md` with this s
- [ ] cs-coo-advisor
- [ ] cs-chro-advisor
- [ ] cs-ciso-advisor
- [ ] cs-general-counsel-advisor
- [ ] cs-cdo-advisor
- [ ] cs-caio-advisor
- [ ] cs-cco-advisor
- [ ] cs-vpe-advisor
- [ ] cs-chief-of-staff
## Success Criteria

22
c-level-advisor/c-level-agents/skills/c-level-agents/SKILL.md
View file

@ -1,6 +1,6 @@
---
name: "c-level-agents"
description: "Founder-mode executive team. 8 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff) and 17 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions."
description: "Founder-mode executive team. 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, GC, CDO, CAIO, CCO, VPE, Chief of Staff) and 21 /cs:* slash commands for forcing-question office hours, multi-role boardroom deliberation, strategic sprint pipeline, and meta routing. Use when the founder needs a virtual executive team, when invoking /cs:* commands, or when orchestrating multi-role decisions."
license: MIT
metadata:
version: 1.0.0
@ -8,8 +8,8 @@ metadata:
category: c-level
domain: executive-orchestration
updated: 2026-05-12
agents: cs-cfo-advisor, cs-cmo-advisor, cs-cro-advisor, cs-cpo-advisor, cs-coo-advisor, cs-chro-advisor, cs-ciso-advisor, cs-chief-of-staff
commands: cs-office-hours, cs-cfo-review, cs-cmo-review, cs-cpo-review, cs-cro-review, cs-cto-review, cs-ciso-review, cs-gc-review, cs-brief, cs-boardroom, cs-decide, cs-execute, cs-post-mortem, cs-founder-mode, cs-onboard, cs-cross-eval, cs-freeze
agents: cs-cfo-advisor, cs-cmo-advisor, cs-cro-advisor, cs-cpo-advisor, cs-coo-advisor, cs-chro-advisor, cs-ciso-advisor, cs-general-counsel-advisor, cs-cdo-advisor, cs-caio-advisor, cs-cco-advisor, cs-vpe-advisor, cs-chief-of-staff
commands: cs-office-hours, cs-cfo-review, cs-cmo-review, cs-cpo-review, cs-cro-review, cs-cto-review, cs-ciso-review, cs-gc-review, cs-cdo-review, cs-caio-review, cs-cco-review, cs-vpe-review, cs-brief, cs-boardroom, cs-decide, cs-execute, cs-post-mortem, cs-founder-mode, cs-onboard, cs-cross-eval, cs-freeze
---
# c-level-agents — Founder-Mode Executive Team
@ -22,7 +22,7 @@ founder mode, virtual c-suite, executive team, boardroom, office hours, cfo revi
## What This Plugin Provides
### 8 cs-* Agents (in `agents/`)
### 13 cs-* Agents (in `agents/`)
Each agent wraps an existing c-level skill and adds:
- A distinct cognitive voice (numerate skeptic, narrative-first, etc.)
@ -30,11 +30,11 @@ Each agent wraps an existing c-level skill and adds:
- Workflow orchestration tied to skill Python tools
- Output template: Bottom Line → What → Why → How to Act → Your Decision
See `../references/persona-voices.md` for voice specs.
See `../../references/persona-voices.md` for voice specs.
### 17 /cs:* Slash Commands (in `skills/`)
### 21 /cs:* Slash Commands (in `skills/`)
**Forcing-question office hours (8):**
**Forcing-question office hours (12):**
- `/cs:office-hours` — YC-style 6-question intake
- `/cs:cfo-review` — unit economics, runway, dilution
- `/cs:cmo-review` — ICP, CAC payback, positioning
@ -43,6 +43,10 @@ See `../references/persona-voices.md` for voice specs.
- `/cs:cto-review` — architecture risk, scaling cliff
- `/cs:ciso-review` — threat model, blast radius, compliance
- `/cs:gc-review` — contracts, IP, regulatory, term sheets
- `/cs:cdo-review` — training-data rights, data products, data assets
- `/cs:caio-review` — model selection, evals, AI risk, AI costs
- `/cs:cco-review` — GRR/NRR decomposition, churn root cause, CS coverage
- `/cs:vpe-review` — DORA metrics, cycle time, eng hiring funnel, team structure
**Strategic sprint pipeline (5):**
- `/cs:brief` → `/cs:boardroom` → `/cs:decide` → `/cs:execute` → `/cs:post-mortem`
@ -86,11 +90,11 @@ User question
## Integration Points
- **Existing 28 c-level skills** — wrapped, not replaced
- **Existing 33 c-level skills** — wrapped, not replaced
- **decision-logger** — every `/cs:decide` writes here
- **chief-of-staff** — routing layer the agent orchestrates
- **board-meeting** — protocol the `/cs:boardroom` command runs
- **llm-wiki** — optional persistent memory bridge (see `../references/llm-wiki-bridge.md`)
- **llm-wiki** — optional persistent memory bridge (see `../../references/llm-wiki-bridge.md`)
- **executive-mentor** — adversarial `/em:*` commands stack cleanly on top
## Design Principles

Some files were not shown because too many files have changed in this diff Show more