← vidIQCONTENT HISTORY

Update to vidIQ

Snapshot Sep 30, 2026 · 23:18 UTC · version 9.0.0

Collection source: not recorded for this historical snapshot. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED · RULE-BASED ANALYSIS

Supporting file metadata differs

Newly listed paths: agents/openai.yaml. This compares saved file lists, not package contents; a different collection source can change the list.

Observed in package metadata. These changes alone do not establish a new customer-facing feature.

Supporting files

Before

[{"relative_path":"references/discovery-evidence.md","size_in_bytes":849},{"relative_path":"references/job-lifecycle.md","size_in_bytes":724},{"relative_path":"references/live-surface-notes.md","size_in_bytes":2014},{"relative_path":"ref...

After

[{"relative_path":"agents/openai.yaml","size_in_bytes":439},{"relative_path":"references/discovery-evidence.md","size_in_bytes":849},{"relative_path":"references/job-lifecycle.md","size_in_bytes":724},{"relative_path":"references/live-su...

Compare saved observations

Download comparison JSON
Full technical diff · 1 changed fields

changed /included_files

BEFORE
[
  {
    "relative_path": "references/discovery-evidence.md",
    "size_in_bytes": 849
  },
  {
    "relative_path": "references/job-lifecycle.md",
    "size_in_bytes": 724
  },
  {
    "relative_path": "references/live-surface-notes.md",
    "size_in_bytes": 2014
  },
  {
    "relative_path": "references/production.md",
    "size_in_bytes": 2933
  }
]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 439
  },
  {
    "relative_path": "references/discovery-evidence.md",
    "size_in_bytes": 849
  },
  {
    "relative_path": "references/job-lifecycle.md",
    "size_in_bytes": 724
  },
  {
    "relative_path": "references/live-surface-notes.md",
    "size_in_bytes": 2014
  },
  {
    "relative_path": "references/production.md",
    "size_in_bytes": 2933
  }
]
Full snapshot data
{
  "name": "vidiq-packaging-comparison",
  "description": "Compare distinct YouTube title-and-thumbnail concepts for the same video when alternative creative directions are explicitly requested. Route single titles, thumbnail edits, or complete packages without a comparison request to vidiq-packaging-studio.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 439
    },
    {
      "relative_path": "references/discovery-evidence.md",
      "size_in_bytes": 849
    },
    {
      "relative_path": "references/job-lifecycle.md",
      "size_in_bytes": 724
    },
    {
      "relative_path": "references/live-surface-notes.md",
      "size_in_bytes": 2014
    },
    {
      "relative_path": "references/production.md",
      "size_in_bytes": 2933
    }
  ],
  "skill_md_contents": "---\nname: vidiq-packaging-comparison\ndescription: Compare distinct YouTube title-and-thumbnail concepts for the same video when alternative creative directions are explicitly requested. Route single titles, thumbnail edits, or complete packages without a comparison request to vidiq-packaging-studio.\n---\n\n# vidIQ Packaging Comparison\n\nRead [Live surface notes](references/live-surface-notes.md) first, even when using only supplied evidence.\n\nCompare the requested number of distinct title-thumbnail concepts for the same video, defaulting\nto three if unspecified. Use `vidiq-packaging-studio` for focused edits or one package. Generated\nimages are optional.\n\n## Compare concepts\n\nPreserve what each number measures: video length does not prove how quickly an action was\ncompleted. Use a speed claim only when demonstrated or explicitly supported by the brief.\n\n1. Use the supplied viewer, promise, proof, format, language, and assets. Establish which story\n   facts are supported and whether the host is the subject or an analyst.\n2. Keep research within scope. Generate images only when requested, using the selected direction\n   or the requested number of variants.\n3. Clarify content only when necessary: `vidiq_video_transcript` supplies untimed spoken text;\n   `vidiq_video_watch` serves long-form and `vidiq_watch_shortform_content` serves Shorts.\n   Verify the source before watching. Read\n   [Job lifecycle](references/job-lifecycle.md) before any asynchronous watch or production call.\n4. Create distinct, truthful promises or framing choices, not cosmetic rewrites. Pair each title\n   with thumbnail tension, proof, or stakes that adds information. Make subject attribution clear.\n5. Research references only when they can change the comparison. Use the guidance below.\n6. Compare audience fit, truthful payoff, differentiation, production feasibility, and evidence.\n   A concept can remain useful despite a lower model score. Before using vidIQ tools for\n   title generation/scoring, rendering, refinement, or thumbnail scoring, read\n   [Production and scoring](references/production.md).\n\n## Optional reference research\n\nRead [Discovery evidence](references/discovery-evidence.md) before searching or evaluating external\nreferences. Skip research when the supplied brief suffices.\n\nFor long-form visual conventions, `vidiq_similar_thumbnails` takes exactly one of `description`\nor `videoId`; it does not support Shorts. Description retrieval is approximate and may be\nirrelevant. Inspect actual images before claiming visual similarity or saturation.\n\nFor title mechanisms, use `vidiq_outliers` with semantic `requireAllTitleTerms: false`; strict\n`true` phrases provide supporting evidence only. Preserve format and language: outliers rejects\nnon-English Shorts, has no live-only lane, narrows non-English `all` to long-form, and caps\nnon-English discovery at six months. Pass a supported `language` explicitly; use a supported\nalternative or disclose missing coverage.\nNormalize outlier `videoPublishedAt` epoch seconds and ISO dates before comparing publication ages.\n\nExclude the story's originating video/creator and sources of material adapted for the story from\nthe packaging reference set, even if licensed. Without image access, mark visual relevance unverified.\n\nA reference is optional design evidence, not permission to copy another creator's distinctive\nexpression. Preserve the creator's authorized assets and name any reference's abstract contribution.\n\n## Deliver\n\nReturn the agreed concepts, their matched titles and thumbnail directions, evidence and\nlimitations, and the recommended choice with its strongest counterargument. Honor a request for\ncomparison without forcing a winner.\n\nFor executed production, report image URLs or pending job IDs, visual-review status, and score/proxy\ncontext. Separate concept judgments from inspected renders; never claim a\nvisual winner before inspection. Log only useful iterations actually performed.\n"
}

SHA-256: 8b4a23eb38d6109c11e55aeb8dd14ebc0505f7897fe3c12d5a6600900acc3a14