---
name: youtube-cadence-diagnosis
description: Diagnose YouTube publishing cadence, gaps, streaks, and post-gap performance effects against channel and peer evidence
type: research
version: v0.1
argument-hint: "<channel slug or handle> [--peer <channel>...] [--count N]"
---

## Pack Availability Guard

Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `/pack install <pack>` instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.

# YouTube Cadence Diagnosis

Invoke as `/youtube-cadence-diagnosis`.

## Report-First Approval Gate

Default to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.

Do not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write/update/fix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research/report writes.

When stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.

Quantify publishing consistency, gap costs, and realistic cadence choices before turning strategy into a programming plan.

## Inputs

- `research/youtube/channel-audit-<slug>.md`
- `research/youtube/data/<slug>/videos-*.jsonl`
- Optional `research/youtube/peer-benchmark-<slug>.md`
- Optional peer raw metadata under `research/youtube/data/<peer-slug>/`

## Workflow

1. Require a channel slug, handle, or channel audit path.
2. Ensure raw upload metadata exists. If not, run `/youtube-channel-audit <channel> [--count N]`.
3. Parse publish dates, views, views/day, content roles, and video archetypes from raw metadata.
4. Compute upload intervals, streaks, longest gaps, rolling 30/60/90-day publish counts, and current streak status.
5. Compare pre-gap and post-gap performance while controlling for topic, video age, and outlier videos where the evidence allows it.
6. Compare cadence against stage-matched peers when peer metadata exists.
7. Decide whether the data points to frequency, topic selection, packaging, or production quality as the more likely bottleneck.
8. Write `research/youtube/cadence-diagnosis-<slug>.md`.

Create the `research/youtube/` directory if it does not exist.

## Report Sections

- Evidence coverage: videos analyzed, date range, peer coverage, and missing fields.
- Upload timeline: chronological table with intervals, gaps, topics, roles, and views/day.
- Cadence metrics: median interval, longest gaps, streaks, rolling publish counts, and current streak.
- Gap analysis: pre-gap baseline, post-gap performance, outlier handling, and confidence level.
- Peer cadence benchmark: publish frequency and consistency compared with comparable channels.
- Bottleneck diagnosis: cadence vs topic vs packaging vs production constraints.
- Practical cadence recommendation: minimum viable cadence, stretch cadence, batching options, and warning signs.
- Strategic programming implication.

## Constraints

- Do not claim causation when the evidence only supports correlation.
- Always name confounders such as topic mix, video age, search seasonality, and packaging changes.
- Use exact dates and intervals.
- Keep recommendations realistic for solo or small-team production unless evidence shows otherwise.
- Route the resulting rhythm into `/content-programming`.

## Approved Artifact Handoff

After an approved synthesized write, explicit write/update mode, or any direct artifact mutation:

- List every created or updated synthesized artifact path in the final response.
- State the verification performed, such as readback, schema/check command, or why no executable verification applies for a Markdown-only strategy artifact.
- Check and report the relevant git status for intended artifacts when the project is a git repository. If intended artifacts are modified or untracked, make the next action shipping, committing, or an explicit dirty-artifact handoff before recommending downstream strategy work.
- Do not imply the research workflow is complete while approved artifacts remain untracked or uncommitted unless the user explicitly asked not to ship.
- If stopping for approval before writing, the approval request remains the next action; do not include downstream routing.

## Intent-Aware Routing

Before applying the default `## Next-Skill Routing` sequence, classify the user's immediate intent and route to the missing action that best serves that intent:

- Strategy refresh: recommend the missing or stale positioning, programming, portfolio, metrics, or product-media artifact.
- Recording prep: recommend the missing series spec, script, build proof, walkthrough guide, or validation artifact needed before recording.
- Upload prep: recommend packaging, title/thumbnail, description, chapters, or final metadata work before broader strategy work.
- Performance review: recommend metrics, cadence, portfolio, peer benchmark, or owner-analytics export work before new content planning.
- Owner analytics or private/manual platform evidence: route to an explicit manual/guide handoff instead of inventing unavailable metrics.
- Dirty intended artifacts: route to shipping/commit/handoff first, not another creator strategy skill.

Use the default next-skill sequence only when no stronger user intent, missing artifact, manual blocker, or dirty-artifact handoff applies.

## Next-Skill Routing

After writing the artifact, recommend the next contextual creator-media skill in the final response as `Recommended next skill: <command>`.

Default recommendation: `/creator-positioning`.

If the default successor already exists and is current, recommend the first missing or stale downstream creator-media artifact in this order:

`/youtube-channel-audit` -> `/youtube-video-audit` -> `/youtube-vid-research` -> `/youtube-concept-research` -> `/youtube-competitive-research` -> `/youtube-title-thumbnail-audit` -> `/youtube-description-optimizer` -> `/youtube-portfolio` -> `/youtube-peer-benchmark` -> `/youtube-search-positioning` -> `/youtube-cadence-diagnosis` -> `/creator-positioning` -> `/content-programming` -> `/series-spec` -> `/product-led-media-map` -> `/creator-metrics-review`

If the sequence is ambiguous, multiple upstream artifacts are stale, or the recommendation depends on channel-level strategy vs programming-level changes, recommend `/creator-metrics-review` when metrics evidence exists, otherwise recommend the default successor and explain the missing artifact.

## Alignment Page

When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/youtube-cadence-diagnosis-{topic}.html`.
