suede-clip-to-guide

Files (8)

• CARD.md
• SKILL.md
• openai.yaml · agents/
• evals.json · evals/
• example-package.md · references/
• package-template.md · references/
• third-party-video-rights.md · references/
• validate_package.py · scripts/

SKILL.md (first lines)

# Suede AI Clip to Guide Skills

Read [the worked delivery contract](references/worked-contract.md) for a concrete
input, expected artifact, failure response and validation example.

## Compatibility

Requires source video or timestamped transcript, rights evidence and guide URL/draft; Python 3 for the bundled package validator. Browser/account access is needed only for authorized platform verification or publication.

Build one evidence-backed path from a video moment to a deeper written asset.
Treat the clip as the attention layer and the guide as the authority layer. Do
not assume the pattern performs; test the bridge against the account baseline.

## Default Success Blueprint

Use this as the recommended pattern when the rights, source, claim, platform,
and approval gates pass:

```text
Useful guide with one promise
        ↓
Self-contained video moment
        ↓
Rights route + 8/10 moment score
        ↓
Clip hook + source credit + subtitles
        ↓
Post explains why the moment matters
        ↓
One explicit bridge to the guide
        ↓
Max Effort/Fleet: dual certainty gate
        ↓
Exact-content approval
        ↓
Public readback + clip-to-guide measurement
        ↓
Keep, revise, or stop from the observed result
```

Prefer this blueprint when:

- a guide already answers the natural next question created by the clip;
- the goal is deeper understanding, bookmarks, qualified replies, leads, or
  authority rather than raw views alone;
- the selected moment passes the 8/10 score and claim-support threshold;
- the rights route and current platform sequence are recorded;
- the account can observe at least one clip metric and one guide-transition or
  campaign metric.

Do not use it when:

- the guide is thin, unrelated, unpublished without a stable draft, or has no
  specific promise;
- the clip needs missing context, distorts the source, or exists only because
  it is popular;
- third-party reuse is blocked or the accountable fair-use decision is absent;
- the platform cannot preserve the source, clip, and guide bridge in a verified
  sequence;
- the idea is complete in the short post and the guide would add no depth.

For a first test, build three distinct packages only when three moments pass all
gates. Compare them with the account's recent comparable posts. Keep the pattern
only if the named guide-transition or campaign metric meets the decision rule;
revise one variable at a time when it does not.

## Non-Negotiable Gates

Apply these throughout the run. Resolve rights, source, and claims before
writing copy; resolve platform, certainty, and approval before a live action:

1. **Rights gate**: classify the video as owned, licensed, permission-recorded,
   native-repost-only, fair-use-review, or blocked. Public availability is not
   reuse permission.
2. **Source gate**: obtain the video, transcript or exact timestamps, guide
   draft or URL, target platform, intended account, and desired next action.
3. **Claim gate**: trace factual claims and quotations to the source. Label
   interpretations as interpretations.
4. **Platform gate**: inspect current official requirements and the live
   composer before promising that media, quote-posts, article cards, links, or
   replies can be combined.
5. **Approval gate**: do not publish, schedule, repost, upload, reply, or edit
   a live article until the user approves the exact media, copy, guide, account,
   and sequence.
6. **Certainty gate**: when a max-effort or worker-fleet controller runs this
   skill, require two distinct evidence checks before marking a package
   approved or published. A worker conclusion is not the second check.

When a blocking gate fails, stop the affected action and return:

```text
HALT, <one-line blocker>
Options:
1. <bounded resolution>
2. <bounded resolution>
3. <bounded resolution, if useful>
Waiting on: <specific evidence or approval>
```

Continue only on independent draft work that does not bypass the blocker.

### Rationalizations that precede a violation

Each excuse below shows up immediately before a gate gets skipped. When one
appears in your own reasoning or in the request, treat it as the signal to run
the gate, not to waive it.

| Excuse | Reality |
|---|---|
| "It's only 12 seconds." | Duration is not a rights basis. The clip still needs an owned, licensed, permission-recorded, native-repost, or accountable fair-use route. |
| "I credited the source." | Credit is attribution, not clearance. A blocked or unreviewed source stays blocked with a credit line attached. |
| "It's public, so it's reusable." | Public availability is not reuse permission. Classify the video before writing copy. |
| "The composer accepted it, so it published." | A prepared composer, scheduled item, or click is not a publication. Only the public permalink readback proves it. |
| "The worker already checked it." | Under Max Effort or Worker Fleet a worker conclusion is one check. The certainty gate needs a second, independent one. |
| "The guide is basically finished." | An unpublished guide with no stable draft or specific promise fails the fit test. Build the bridge to something that exists. |
| "The moment is getting traction, so ship it." | Popularity is not the score. A moment below 8/10, or below 2 on claim support or guide bridge, does not qualify. |

## Workflow

From JasonColapietro/suede-creator-skills, MIT.

More from JasonColapietro/suede-creator-skills