/cf-help

name: cf-help
description: "Show the ContentForge user guide with live plugin state — version, agent/skill/command counts, connector availability, and runtime environment read from scripts/plugin-metadata.py, never hardcoded — plus pipeline overview, per-skill listings, worked examples, brand-setup methods, and a troubleshooting matrix. Triggers on \"/contentforge:cf-help\", \"how do I use ContentForge\", \"list the ContentForge skills\", \"explain the content pipeline\", \"ContentForge isn't working\". Flags route to sections (--pipeline, --skills, --examples, --troubleshoot, --brand), and a Cowork sandbox warning is surfaced automatically when detected. Documentation only — it renders guidance from live metadata and runs no production pipeline."
argument-hint: "[--pipeline | --skills | --commands | --examples | --connectors | --troubleshoot | --brand]"
effort: low

/contentforge:cf-help

Show the ContentForge user guide with live plugin state (version, asset counts, connector counts, runtime environment) pulled from disk — not hardcoded — plus pipeline overview, available skills, usage examples, and troubleshooting.

CRITICAL: never hardcode version, asset counts, or connector counts

Versions and counts in this plugin used to be baked into this skill body as literal version strings and count strings ("Agents: 13 · Skills: 19 · Connectors: 9 HTTP + 19 npx"). Those drifted out of sync with the actual install every release (reported by users in v3.12.7 testing: "I'm on 3.12.7, but the help output shows an old version").

**Always read live values from `scripts/plugin-metadata.py`. Never quote a version number, skill count, agent count, or connector count from memory or from this skill body.**

Behavior

Step 1 — Fetch live plugin metadata

Run **first**, every time this skill is invoked (any argument or none):

python scripts/plugin-metadata.py --section all-with-environment

This returns JSON with `version`, `assets` (agent/skill/command/script counts), `connectors` (HTTP + npx counts), `skills` list, `commands` list, `pipeline_phases` list (read from agent file names), and `environment` (detects Cowork sandbox vs local Claude Code, with a warning if filesystem writes won't reach the user's host).

Substitute the values from this JSON into every place the help output references a count, a version, or a slash-command list. Do **not** invent or quote numbers from elsewhere.

Step 2 — Default rendering (no args)

Render a clean help overview using the live data. Suggested format:

=== CONTENTFORGE ===
Version: <version from JSON>
Agents: <agents> | Skills: <skills_total> | Commands: <commands> | Scripts: <scripts>
Connectors: <available_http> HTTP + <available_npx> npx available
  (<active_count> currently active in your .mcp.json)
  Cowork-compatible: <cowork_compatible_count> (HTTP only — npx connectors don't run in Cowork)
Environment: <environment from JSON>
<if environment.cowork_warning is non-null, show it as a WARNING block>

Getting Started:
  1. /contentforge:brand-setup           -- Configure brand voice, terminology, guardrails
  2. /contentforge:cf-integrations       -- See which connectors are active
  3. /contentforge:create-content        -- Run the full content pipeline
  4. /contentforge:cf-help --examples    -- Worked example workflows

Step 3 — Cowork warning (when applicable)

If `environment.cowork_warning` is non-null, surface it prominently after the orientation block:

⚠ COWORK SANDBOX DETECTED
<cowork_warning text from JSON>

What this means in practice:
  - File writes to ~/Documents/ContentForge/ and ~/.claude-marketing/
    land inside the sandbox, NOT on your Windows / macOS host
  - Files persist only for this Cowork session
  - The full /contentforge:create-content pipeline can run, but the
    dual-copy save and per-phase checkpointing target the sandbox FS
  - For full host-filesystem behavior, run ContentForge in local
    Claude Code (CLI or VS Code / JetBrains IDE extension) instead

Step 4 — Argument routing

| Argument | What to render | |----------|---------------| | (none) | Steps 2 + 3 + Quick command list | | `--pipeline` | Steps 2 + 3 + full phase-by-phase overview (use `pipeline_phases` from JSON) | | `--skills` | Steps 2 + 3 + list every skill from JSON `skills` array with slash command + description | | `--commands` | Steps 2 + 3 + list every command from JSON `commands` array with slash command + description | | `--connectors` | Steps 2 + 3 + redirect: "For active/available connector status, run /contentforge:cf-integrations" | | `--examples` | Steps 2 + 3 + the worked-example workflows (see below) | | `--troubleshoot` | Steps 2 + 3 + troubleshooting matrix (see below) | | `--brand` | Steps 2 + 3 + brand setup methods (see below) |

When rendering the skills/commands list, **iterate over the JSON arrays** — do not paste a hand-maintained list. Each row should show the `slash_command` field as the user-facing label and the `description` field as the explanation.

Pipeline phase rendering (--pipeline)

The pipeline phases come from agent file names (`01-researcher.md` → "Phase 01: Researcher"). Iterate `pipeline_phases` from the JSON and render phase + role + description. Add this preamble:

=== CONTENTFORGE PIPELINE (10 phases) ===
Step 0.5: Title Curation runs BEFORE Phase 1 (SERP recon + 4-5 SEO title options;
          user selects before draft starts).

Quality gates: composite score >=7.0 to pass | max 2 loops per phase |
3-layer verification (Fact Checker -> Scientific Validator -> Reviewer).

Then list every phase from the JSON. **Do not invent timing estimates** — they vary by topic complexity and model speed. If the agent description in the JSON includes a timing hint, surface it; otherwise omit.

Brand setup rendering (--brand)

Show the three brand-setup methods (interactive / JSON template / Drive Knowledge Vault), referencing the actual current commands. v