Content Id Guide

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

MIT-0 · Free to use, modify, and redistribute. No attribution required.
1 · 2.4k · 10 current installs · 11 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (organize procedural Content ID evidence) match the SKILL.md instructions (checklists, redaction, mandatory disclaimer). The skill requests no binaries, env vars, or installs. Minor provenance note: source is listed as "unknown" with no homepage, which affects trust but not internal coherence.
Instruction Scope
SKILL.md restricts behavior (mandatory disclaimer, PII redaction, no legal advice, no circumvention). Instructions only describe how to intake claim data and help organize evidence; they do not instruct reading unrelated files, accessing environment variables, or sending data to external endpoints.
Install Mechanism
No install spec and no code files — instruction-only skill; nothing is written to disk or downloaded during installation.
Credentials
No required environment variables, credentials, or config paths are declared. The skill's input schema accepts pasted notice text and metadata and this is proportionate to the described purpose.
Persistence & Privilege
always is false and the skill is user-invocable. It requests no persistent privileges or modification of other skills or system-wide settings.
Assessment
This skill appears coherent and safe in design: it asks for no credentials, has no install, and enforces PII redaction and a mandatory legal-disclaimer. Before installing, consider: (1) provenance — the source/homepage is unknown, so you may want to confirm the author or publisher if you need higher trust; (2) avoid pasting sensitive or privileged documents (legal filings, non-public contracts) into the tool because the platform's retention/telemetry policies determine where that text is stored; and (3) the skill is explicitly non-legal-advisory—consult an attorney for legal decisions. If those points are acceptable, the skill's instructions and requirements are proportionate to its stated purpose.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.3
Download zip
2026-readyvk978wa824wb89vchfmx07bzj3982qm2bUGCvk97514x7dpeg0ktyww32knx4an800qy4ai-disclosurevk978wa824wb89vchfmx07bzj3982qm2battributionvk978wa824wb89vchfmx07bzj3982qm2bbranded-contentvk978wa824wb89vchfmx07bzj3982qm2bc2pavk97514x7dpeg0ktyww32knx4an800qy4claimsvk97514x7dpeg0ktyww32knx4an800qy4compliancevk978wa824wb89vchfmx07bzj3982qm2bcontent IDvk978wa824wb89vchfmx07bzj3982qm2bcontent rightsvk978wa824wb89vchfmx07bzj3982qm2bcontent-credentialsvk97514x7dpeg0ktyww32knx4an800qy4content-idvk97514x7dpeg0ktyww32knx4an800qy4copyrightvk97514x7dpeg0ktyww32knx4an800qy4creator toolsvk97514x7dpeg0ktyww32knx4an800qy4creator-rightsvk978wa824wb89vchfmx07bzj3982qm2bcreatorsvk97514x7dpeg0ktyww32knx4an800qy4latestvk971bhykg74xs9ed1ca2rqmnj182wysdmedia-opsvk978wa824wb89vchfmx07bzj3982qm2bmetavk97514x7dpeg0ktyww32knx4an800qy4metadatavk97514x7dpeg0ktyww32knx4an800qy4monetizationvk97514x7dpeg0ktyww32knx4an800qy4provenancevk978wa824wb89vchfmx07bzj3982qm2brightsvk97514x7dpeg0ktyww32knx4an800qy4tiktokvk97514x7dpeg0ktyww32knx4an800qy4transparencyvk978wa824wb89vchfmx07bzj3982qm2byoutubevk97514x7dpeg0ktyww32knx4an800qy4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

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"
}


Files

2 total
Select a file
Select a file to preview.

Comments

Loading comments…