skillpacks 0.1.1 → 0.1.2

package/packs/youtube-ops/codex/youtube/archive/v0.1/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: youtube
+description: Intent-based router and play composer for youtube-ops skills — classifies what the user needs and recommends a single skill or queues a multi-step play for $exec
+type: router
+version: v0.1
+argument-hint: "[natural language] | --health <channel> | --concept \"<idea>\" [--channel <slug>] | --launch <unlisted-video-url> | --intel <video-urls...> | --status"
+---
+
+## 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 — Intent Router & Play Composer
+
+Invoke as `$youtube`.
+
+Entry point for the `youtube-ops` pack. Classifies the user's intent and either recommends a single skill or composes a multi-step "play" written to `tasks/todo.md` for `$exec` to drive.
+
+This skill does not produce research artifacts or alignment pages. It is a routing and planning layer over the 13 standalone youtube-ops skills (plus `youtube-format-research` from the `remotion` pack when installed).
+
+## Modes
+
+### Mode A — Intent Router (default)
+
+When invoked with natural language and no flags, classify the user's intent against the table below. Recommend 1–3 skills inline with a one-sentence rationale per skill. Do not write files. If the intent maps cleanly to a play (Modes B–E), suggest the corresponding flag instead.
+
+| Intent | Signal Words | Routes To |
+|--------|-------------|-----------|
+| Channel health | "audit", "how is my channel", channel URL | `$youtube-channel-audit` or suggest `--health` play |
+| Video diagnosis | "why did this video", single video URL | `$youtube-video-audit` |
+| Prelaunch review | "unlisted", "pre-release", "prelaunch", "ready to publish", "needs editing", "launch strategy", single unlisted video URL | `$youtube-video-prelaunch-audit` |
+| Video understanding | "watch this", "summarize", external URL | `$youtube-vid-research` |
+| Concept validation | "should I make", "video idea" | `$youtube-concept-research` or suggest `--concept` play |
+| Competitive analysis | "why did their video", "competitor" | `$youtube-competitive-research` |
+| Packaging | "title", "thumbnail", "CTR" | `$youtube-title-thumbnail-audit` |
+| Description/SEO | "description", "tags", "metadata" | `$youtube-description-optimizer` |
+| Search opportunity | "search", "keywords", "ranking" | `$youtube-search-positioning` |
+| Cadence | "cadence", "how often", "schedule" | `$youtube-cadence-diagnosis` |
+| Peer comparison | "compare", "benchmark", "peers" | `$youtube-peer-benchmark` |
+| Portfolio | "portfolio", "content mix" | `$youtube-portfolio` |
+| General audit | "full audit", "everything" | `$youtube-audit` |
+| Format/production | "format", "editing", "pacing" | `$youtube-format-research` (remotion pack) |
+
+When routing to `youtube-format-research`, verify the `remotion` pack is enabled in `.agents/project.json` `enabled_packs`. If not, note that `$pack install remotion` is required first.
+
+### Mode B — Channel Health Play (`--health <channel>`)
+
+Queue a 5-step channel health audit play to `tasks/todo.md`:
+
+1. `$youtube-channel-audit <channel> --count 20`
+2. `$youtube-portfolio`
+3. `$youtube-peer-benchmark <channel>`
+4. `$youtube-cadence-diagnosis <channel>`
+5. `$youtube-title-thumbnail-audit <channel>`
+
+### Mode C — Pre-Production Play (`--concept "<idea>" [--channel <slug>]`)
+
+Queue a concept validation play to `tasks/todo.md`:
+
+1. `$youtube-concept-research "<idea>" [--channel <slug>]`
+2. `$youtube-competitive-research` (using comparables surfaced in step 1)
+3. `$youtube-search-positioning`
+4. `$youtube-format-research` (only if `remotion` pack is enabled — mark optional if missing)
+
+### Mode D — Video Launch Play (`--launch <unlisted-video-url>`)
+
+Queue a launch preparation play for an unlisted or scheduled video to `tasks/todo.md`. If the video is already public and the user asks why it performed a certain way, recommend `$youtube-video-audit` instead.
+
+1. `$youtube-video-prelaunch-audit <video-url>`
+2. `$youtube-title-thumbnail-audit`
+3. `$youtube-description-optimizer <video-url> --mode draft`
+
+### Mode E — Competitive Intel Play (`--intel <video-urls...>`)
+
+Queue a competitive analysis play to `tasks/todo.md`:
+
+1. `$youtube-vid-research <video-urls>`
+2. `$youtube-competitive-research <video-urls>`
+3. `$youtube-format-research` (only if `remotion` pack is enabled — mark optional if missing)
+
+### Mode F — Status (`--status`)
+
+Read-only scan of `research/youtube/` artifacts. Report:
+
+- Which research files exist and their last-modified dates
+- Staleness (files older than 30 days)
+- Coverage gaps (which skills have never produced output)
+- Any active working packets in `research/youtube/_working/`
+
+Do not write files in this mode.
+
+## Play Approval Gate
+
+Before writing a play to `tasks/todo.md`:
+
+1. **Check for existing work.** Read `tasks/todo.md`. If it contains unfinished items (unchecked checkboxes), warn the user and ask whether to append, replace, or abort. Do not silently overwrite existing plans.
+2. **Present the play.** Show the numbered steps with skill names and arguments. Note any optional steps and their prerequisites (e.g., remotion pack).
+3. **Write on approval.** Write the play to `tasks/todo.md` as a checklist. Include a header line identifying the play type and timestamp. Each step is a `- [ ]` item with the full skill invocation command.
+
+After writing the play, recommend `$exec` to begin execution.
+
+## Play Format for `tasks/todo.md`
+
+```markdown
+## YouTube Play: {Play Type} — {timestamp}
+
+- [ ] Step 1: `$<skill-name> <args>`
+- [ ] Step 2: `$<skill-name> <args>`
+...
+```
+
+## Approved Artifact Handoff
+
+After an approved play write or any direct artifact mutation:
+
+- List every created or updated synthesized artifact path, including `tasks/todo.md` when a play was written.
+- State the verification performed, such as readback, schema/check command, or why no executable verification applies for a Markdown-only routing 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.
+
+## Intent-Aware Routing
+
+Before applying the default next-step routing or writing a queued play, 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, prelaunch review, or final metadata work before broader strategy work.
+- Performance review: recommend metrics, cadence, portfolio, peer benchmark, owner-analytics export, or post-publication video audit 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-Step Routing
+
+When Mode A recommends skills without writing files, the recommended next step is the selected youtube-ops skill or pack installation command shown in the routing response.
+
+After Mode B-E writes an approved play to `tasks/todo.md`, recommend `Recommended next command: $exec` to begin execution. If play writing is blocked by existing unfinished tasks, the next step is the user's append, replace, or abort decision.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/youtube-ops/codex/youtube/archive/v0.2/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: youtube
+description: Intent-based router and play composer for youtube-ops skills — classifies what the user needs and recommends a single skill or queues a multi-step play for $exec
+type: router
+version: v0.2
+argument-hint: "[natural language] | --health <channel> | --concept \"<idea>\" [--channel <slug>] | --launch <unlisted-video-url> | --intel <video-urls...> | --status"
+---
+
+## 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 `npx skillpacks 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 — Intent Router & Play Composer
+
+Invoke as `$youtube`.
+
+Entry point for the `youtube-ops` pack. Classifies the user's intent and either recommends a single skill or composes a multi-step "play" written to `tasks/todo.md` for `$exec` to drive.
+
+This skill does not produce research artifacts or alignment pages. It is a routing and planning layer over the 13 standalone youtube-ops skills (plus `youtube-format-research` from the `remotion` pack when installed).
+
+## Modes
+
+### Mode A — Intent Router (default)
+
+When invoked with natural language and no flags, classify the user's intent against the table below. Recommend 1–3 skills inline with a one-sentence rationale per skill. Do not write files. If the intent maps cleanly to a play (Modes B–E), suggest the corresponding flag instead.
+
+| Intent | Signal Words | Routes To |
+|--------|-------------|-----------|
+| Channel health | "audit", "how is my channel", channel URL | `$youtube-channel-audit` or suggest `--health` play |
+| Video diagnosis | "why did this video", single video URL | `$youtube-video-audit` |
+| Prelaunch review | "unlisted", "pre-release", "prelaunch", "ready to publish", "needs editing", "launch strategy", single unlisted video URL | `$youtube-video-prelaunch-audit` |
+| Video understanding | "watch this", "summarize", external URL | `$youtube-vid-research` |
+| Concept validation | "should I make", "video idea" | `$youtube-concept-research` or suggest `--concept` play |
+| Competitive analysis | "why did their video", "competitor" | `$youtube-competitive-research` |
+| Packaging | "title", "thumbnail", "CTR" | `$youtube-title-thumbnail-audit` |
+| Description/SEO | "description", "tags", "metadata" | `$youtube-description-optimizer` |
+| Search opportunity | "search", "keywords", "ranking" | `$youtube-search-positioning` |
+| Cadence | "cadence", "how often", "schedule" | `$youtube-cadence-diagnosis` |
+| Peer comparison | "compare", "benchmark", "peers" | `$youtube-peer-benchmark` |
+| Portfolio | "portfolio", "content mix" | `$youtube-portfolio` |
+| General audit | "full audit", "everything" | `$youtube-audit` |
+| Format/production | "format", "editing", "pacing" | `$youtube-format-research` (remotion pack) |
+
+When routing to `youtube-format-research`, verify the `remotion` pack is enabled in `.agents/project.json` `enabled_packs`. If not, note that `npx skillpacks install remotion` is required first.
+
+### Mode B — Channel Health Play (`--health <channel>`)
+
+Queue a 5-step channel health audit play to `tasks/todo.md`:
+
+1. `$youtube-channel-audit <channel> --count 20`
+2. `$youtube-portfolio`
+3. `$youtube-peer-benchmark <channel>`
+4. `$youtube-cadence-diagnosis <channel>`
+5. `$youtube-title-thumbnail-audit <channel>`
+
+### Mode C — Pre-Production Play (`--concept "<idea>" [--channel <slug>]`)
+
+Queue a concept validation play to `tasks/todo.md`:
+
+1. `$youtube-concept-research "<idea>" [--channel <slug>]`
+2. `$youtube-competitive-research` (using comparables surfaced in step 1)
+3. `$youtube-search-positioning`
+4. `$youtube-format-research` (only if `remotion` pack is enabled — mark optional if missing)
+
+### Mode D — Video Launch Play (`--launch <unlisted-video-url>`)
+
+Queue a launch preparation play for an unlisted or scheduled video to `tasks/todo.md`. If the video is already public and the user asks why it performed a certain way, recommend `$youtube-video-audit` instead.
+
+1. `$youtube-video-prelaunch-audit <video-url>`
+2. `$youtube-title-thumbnail-audit`
+3. `$youtube-description-optimizer <video-url> --mode draft`
+
+### Mode E — Competitive Intel Play (`--intel <video-urls...>`)
+
+Queue a competitive analysis play to `tasks/todo.md`:
+
+1. `$youtube-vid-research <video-urls>`
+2. `$youtube-competitive-research <video-urls>`
+3. `$youtube-format-research` (only if `remotion` pack is enabled — mark optional if missing)
+
+### Mode F — Status (`--status`)
+
+Read-only scan of `research/youtube/` artifacts. Report:
+
+- Which research files exist and their last-modified dates
+- Staleness (files older than 30 days)
+- Coverage gaps (which skills have never produced output)
+- Any active working packets in `research/youtube/_working/`
+
+Do not write files in this mode.
+
+## Play Approval Gate
+
+Before writing a play to `tasks/todo.md`:
+
+1. **Check for existing work.** Read `tasks/todo.md`. If it contains unfinished items (unchecked checkboxes), warn the user and ask whether to append, replace, or abort. Do not silently overwrite existing plans.
+2. **Present the play.** Show the numbered steps with skill names and arguments. Note any optional steps and their prerequisites (e.g., remotion pack).
+3. **Write on approval.** Write the play to `tasks/todo.md` as a checklist. Include a header line identifying the play type and timestamp. Each step is a `- [ ]` item with the full skill invocation command.
+
+After writing the play, recommend `$exec` to begin execution.
+
+## Play Format for `tasks/todo.md`
+
+```markdown
+## YouTube Play: {Play Type} — {timestamp}
+
+- [ ] Step 1: `$<skill-name> <args>`
+- [ ] Step 2: `$<skill-name> <args>`
+...
+```
+
+## Approved Artifact Handoff
+
+After an approved play write or any direct artifact mutation:
+
+- List every created or updated synthesized artifact path, including `tasks/todo.md` when a play was written.
+- State the verification performed, such as readback, schema/check command, or why no executable verification applies for a Markdown-only routing 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.
+
+## Intent-Aware Routing
+
+Before applying the default next-step routing or writing a queued play, 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, prelaunch review, or final metadata work before broader strategy work.
+- Performance review: recommend metrics, cadence, portfolio, peer benchmark, owner-analytics export, or post-publication video audit 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-Step Routing
+
+When Mode A recommends skills without writing files, the recommended next step is the selected youtube-ops skill or pack installation command shown in the routing response.
+
+After Mode B-E writes an approved play to `tasks/todo.md`, recommend `Recommended next command: $exec` to begin execution. If play writing is blocked by existing unfinished tasks, the next step is the user's append, replace, or abort decision.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/youtube-ops/codex/youtube-audit/ALIGNMENT-PAGE.md

@@ -9,6 +9,8 @@ When this skill produces durable deliverables (research, specs, plans, reports,
 
 The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected by the upgrade script). The bundled ALIGNMENT-PAGE.md receives tier-appropriate rendering guidance from the generator.
 
+**Context intake.** This skill declares `context_intake: artifact_only` (Artifact-driven). Work from concrete artifacts, data, logs, or existing instructions by default; ask concise clarification questions only when the available artifacts are missing, contradictory, or unsafe to interpret.
+
 **Alignment lifecycle.** Alignment pages have three lifecycle states. `review` is the draft/pre-approval page: it contains the complete deliverable preview, evidence, required inline gate questions, section feedback controls, local section-feedback YAML only after a section feedback choice is selected, and one bottom `Compile Responses` control. `confirmed` is the post-approval page after the agent has consumed final compiled response YAML, made any approved user-requested edits, and written or updated the approved canonical artifacts. A confirmed page is finished and current for the completed alignment cycle, but it remains amendable when later research changes or extends the conclusions. `amended` is a future revision of a confirmed page: archive the previous confirmed page first, mark what changed, preserve the prior approval record, and highlight the new evidence, decisions, or scope that changed the earlier conclusion.
 
 **Central alignment index.** When a research-producing skill writes or updates an HTML alignment page, also maintain the repository's central alignment index. Look for `alignment/index.html` at the repository root; if the target repo documents a different central alignment-index path, use that path and report it. If the index does not exist, create it as a self-contained HTML page that works from `file://`, links to every active `alignment/*.html` page except itself, and includes the newly written page. Every index entry must include the page's alignment date in a muted meta span after the link, formatted `YYYY-MM-DD`, for example `<a href="page.html">Title</a> <span class="meta">2026-06-09</span>`. The alignment date is the review or confirmed date written inside the page itself; new pages use today's date. If the index exists, update it instead of blindly appending: preserve valid existing entries, metadata, and entry dates; remove duplicate entries for the same page path; keep links repo-relative; and include the new or updated page. When updating an existing index, add a date only to entries that are missing one, deriving it from the page's internal alignment date, or from file history when the page has no internal date. If a `new` marker is used, combine it with the date as `<span class="meta">new · YYYY-MM-DD</span>`, and remove stale `new` markers from entries that are no longer the latest addition.
@@ -57,7 +59,9 @@ The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected
 
 **Report-only research gates.** For report-only or pre-approval research skills, the first `review` alignment page must explicitly contain proposed research scope, source plan, assumptions/confidence, recommended output path, proposed file changes, and approval gates before synthesized research begins and before any working packet, canonical research, spec, or task file is created or updated.
 
-**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-youtube-audit-research.md`; product-path mode uses `research/{slug}/_working/preliminary-youtube-audit-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, research-scope approval gates, and a `Stage 2 Preview / Expected Review Format` section that shows the future Stage 2 review shape before research starts. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-youtube-audit-research.md`; product-path mode uses `research/{slug}/_working/preliminary-youtube-audit-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `<pre><code>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+
+**Stage 2 review-page template.** Stage 1 scope-review pages must include a `Stage 2 Preview / Expected Review Format` section that previews the exact section sequence, table shapes, evidence treatment, visual density, and approval gates the user will see after research; make it specific enough for the user to flag preferred content formats, grouping, labels, visuals, and evidence density before the agent does heavy research. After scope approval and research, the Stage 2 review page must include these sections as structured HTML, not as raw Markdown dumps: `Research Scope Approved` status block with approved scope, source plan, output paths, and unresolved caveats; `Executive Findings` or a skill-specific top-findings section with confidence labels; `Evidence Matrix` mapping claim, evidence/source/path, inference, confidence, assumptions, and decision impact; `Working Packet Review` with the complete working-packet substance rendered as purpose-built HTML sections, lists, tables, matrices, cards, and tier-appropriate charts or diagrams; `Alternatives / Rejected or Lower-Confidence Findings`; `Source Coverage & Gaps`; `Assumptions / Confidence Register`; `Proposed Canonical Artifacts & File Changes`; a required `User Format Preferences` gate asking whether the layout, tables, grouping, visuals, labels, and evidence density match expectations; and a required `Final Artifact Approval` gate for Stage 3 readiness. Raw Markdown packet text, search logs, or source notes may appear only as supplemental source views after the rendered review UI and never replace the Stage 2 review sections.
 
 **Glossary Additions gate.** When this research introduces domain-specific terms, acronyms, or concept definitions that a reader outside the project would not know, include a `## Glossary Additions` section in the alignment page. Render a table of proposed terms with columns: Term, Definition, Source (`youtube-audit`), Category (business/tooling/workflow/technical/domain), and per-term Approve/Edit/Reject/Flag radio controls. Only user-approved terms are appended to the target glossary (`research/glossary.md` or `research/{slug}/glossary.md` for scoped paths) during the confirmed-page write step. When the skill operates in a product-path scope, ask whether each term belongs in the parent or scoped glossary; default to the scoped glossary.
 

package/packs/youtube-ops/codex/youtube-audit/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.6 - 2026-06-12
+
+- Clarified staged research review pages must render complete working-packet substance as structured HTML UI, with raw Markdown packet text allowed only as a supplemental source view.
+
 ## v0.5 - 2026-06-10
 
 - Changed report-first research flow to require alignment-page research-scope approval before synthesized findings, candidate rankings, recommendations, working packets, or canonical research writes.

package/packs/youtube-ops/codex/youtube-audit/SKILL.md

@@ -2,9 +2,9 @@
 name: youtube-audit
 description: Analyze a YouTube channel with evidence-first metadata, transcripts, performance fields, portfolio shape, and repeated content-quality patterns
 type: research
-version: v0.5
+version: v0.6
 argument-hint: "<channel URL or handle> [--count N]"
-interview_depth: none
+context_intake: artifact_only
 ---
 
 # YouTube Audit — Evidence-First Channel Analysis
@@ -26,7 +26,7 @@ Do not include `Recommended next skill`, `Recommended next command`, or downstre
 Use this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.
 
 1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled YAML approval of the research scope. Do not perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.
-2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback, perform the synthesized research, run required source/code checks, and write only a non-canonical working packet: flat mode uses `research/_working/preliminary-<skill>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page with the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
+2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback, perform the synthesized research, run required source/code checks, and write only a non-canonical working packet: flat mode uses `research/_working/preliminary-<skill>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `<pre><code>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
 3. **Stage 3 - Finalize approved artifacts.** Consume final compiled YAML for artifact approval only when it has no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths below, and convert the alignment page to `confirmed` with the approval record preserved.
 
 Canonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.