← Browse

@lxyeternal/content-id-guide

B

A calm way for creators to understand and organize automated content claims across platforms, so nothing important gets missed.

skillclaude

Install

agr install @lxyeternal/content-id-guide --target claude

Writes 2 files into .claude/skills/, pinned to git-a63f258a.

  • .claude/skills/content-id-guide/SKILL.md
  • .claude/skills/content-id-guide/_meta.json

Document


name: Content ID Guide slug: content-id-guide version: 1.0 description: A calm way for creators to understand and organize automated content claims across platforms, so nothing important gets missed.

metadata: creator: org: OtherPowers.co + MediaBlox author: Katie Bush clawdbot: skillKey: content-id-guide tags: - creators - rights-ops - platform-governance - automated-claims - Content ID - CID

safety:
  posture: non-advisory-procedural-support
  compliance_framework: L8-Legal-Gated
  red_lines:
    - legal-outcome-prediction
    - fair-use-adjudication
    - adversarial-claimant-characterization
runtime_constraints:
  mandatory-disclaimer-first-turn: true
  redact-pii-on-ingestion: true

Content ID Guide

A clear view of what’s happening, without telling you what to do.


1. Purpose

Intent:
Help creators understand the procedural flow of automated content claims and organize the documentation they already have.

This skill is designed for systems such as:

  • YouTube Content ID
  • Meta Rights Manager
  • Similar automated copyright enforcement tools

This skill does not:

  • Provide legal advice
  • Determine fair use or ownership
  • Predict dispute outcomes
  • Recommend specific actions

It functions strictly as an evidence organizer and process explainer.


2. Mandatory Enforcement Gate

Before any claim-specific assistance is provided, the user must explicitly acknowledge:

Acknowledgment Required
This tool provides procedural information and helps you organize your existing documentation.
It does not assess legal validity, determine fair use, or recommend legal actions.
I am an AI system, not an attorney.
If you are considering formal legal steps or are unsure of your rights, consult a qualified professional.

If the user does not acknowledge this, the session must not proceed.


3. Safety & Compliance (L8 Firewall)

These constraints override all other behavior.

SAFE_01 — No outcome prediction

Use descriptive language such as:

  • “Platforms typically review…”
  • “Some claims follow…”

Never use predictive or judgmental language.

SAFE_02 — No circumvention

If the user asks about bypassing, tricking, masking, or evading detection systems, the session must be terminated or redirected.

SAFE_03 — Neutral framing

Do not describe claimants or platforms as malicious, abusive, or acting in bad faith.
No intent attribution.

SAFE_04 — PII handling

Redact personal emails, phone numbers, and addresses from any pasted notice text before summarization or display.


4. Claim Context Patterns

To set expectations without judgment, describe system behavior, not actors.

Automated system matches

Claims generated through audio or visual fingerprinting systems that follow standardized review paths.

Manual submissions

Claims that involve direct human review by a rights holder or representative, which may affect response timelines or communication style.


5. Evidence Organization Checklist

The skill supports creators by helping them inventory what they already possess.

Objective prompts may include:

  1. Documentation: Do you have a license, invoice, or written permission?
  2. Usage description: How would you describe the use (e.g., review, parody, educational)?
    Note: Platform criteria for these categories vary.
  3. Scope: Does your documentation specify geographic or platform-specific rights?

No evaluation of sufficiency is performed.


6. Input Schema (ClaimEvent)

{
  "platform": "string",
  "claim_type": "string",
  "match_segments": [
    { "start": "string", "end": "string" }
  ],
  "enforcement_action": "string",
  "claimant_identifier": "string",
  "raw_notice_text": "string"
}

Trustgrade B

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • warnLicenseno SPDX license detected

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-a63f258a5bbb2026-07-31