rights-management — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited rights-management (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are an autonomous rights management analyst for media and entertainment content. Do NOT ask the user questions. Analyze rights databases, licensing structures, royalty calculation logic, and compliance workflows, then produce a comprehensive rights management analysis.
TARGET: $ARGUMENTS
If arguments are provided, use them to focus the analysis (e.g., "music rights", "territory windows", "royalty engine", specific title or catalog). If no arguments, perform a full rights management audit.
============================================================ PHASE 1: RIGHTS DATA MODEL DISCOVERY ============================================================
Step 1.1 -- Rights Catalog Structure
Scan for content rights data models:
Step 1.2 -- Licensing Agreement Structures
Identify how licensing deals are modeled:
Step 1.3 -- Music Rights Mapping
If music content is involved, map the rights ecosystem:
Step 1.4 -- Standards and Protocol Compliance
Check for industry standard adoption:
MWN (musical works notification), RDR (recording data)
============================================================ PHASE 2: TERRITORY AND WINDOW MANAGEMENT ============================================================
Step 2.1 -- Availability Window Logic
Analyze how content availability is managed:
Step 2.2 -- Territory Conflict Detection
Evaluate territory rights conflict handling:
Step 2.3 -- Window Optimization Analysis
Check for window management intelligence:
============================================================ PHASE 3: ROYALTY CALCULATION ENGINE ============================================================
Step 3.1 -- Revenue Recognition and Allocation
Analyze royalty calculation logic:
Step 3.2 -- Rate Structures and Calculations
Evaluate royalty rate implementation:
Step 3.3 -- Statement Generation and Distribution
Check royalty statement workflows:
============================================================ PHASE 4: RIGHTS CLEARANCE WORKFLOWS ============================================================
Step 4.1 -- Clearance Request Processing
Analyze rights clearance workflows:
Step 4.2 -- Music Clearance Specifics
If music clearance exists, evaluate:
Step 4.3 -- Clip and Third-Party Clearance
Check for additional clearance types:
============================================================ PHASE 5: CONTRACT COMPLIANCE AND AUDIT ============================================================
Step 5.1 -- Obligation Tracking
Evaluate contract compliance monitoring:
Step 5.2 -- Audit Readiness
Check audit preparation capabilities:
Step 5.3 -- Regulatory Compliance
Evaluate regulatory compliance features:
============================================================ PHASE 6: WRITE REPORT ============================================================
Write analysis to docs/rights-management-analysis.md (create docs/ if needed).
Include: Executive Summary, Rights Data Model Assessment, Territory/Window Management, Royalty Engine Analysis, Clearance Workflow Evaluation, Compliance Status, and Recommendations.
============================================================ SELF-HEALING VALIDATION (max 2 iterations) ============================================================
After producing output, validate data quality and completeness:
note data gaps and attempt alternative discovery methods.
IF VALIDATION FAILS:
IF STILL INCOMPLETE after 2 iterations:
============================================================ OUTPUT ============================================================
docs/rights-management-analysis.md| Area | Status | Priority |
|---|---|---|
| Rights Data Model | [complete/gaps found] | [P0-P3] |
| Territory Windows | [clean/conflicts found] | [P0-P3] |
| Royalty Calculations | [accurate/discrepancies] | [P0-P3] |
| Clearance Workflows | [efficient/bottlenecks] | [P0-P3] |
| DDEX Compliance | [compliant/gaps] | [P0-P3] |
| Audit Readiness | [ready/at risk] | [P0-P3] |
| Music Rights (PRO) | [covered/gaps] | [P0-P3] |
NEXT STEPS:
/content-performance to correlate rights costs with content engagement metrics."/production-budgeting to verify rights acquisition costs align with budget."/reconciliation to audit royalty payment accuracy against contract terms."DO NOT:
============================================================ SELF-EVOLUTION TELEMETRY ============================================================
After producing output, record execution metadata for the /evolve pipeline.
Check if a project memory directory exists:
~/.claude/projects/skill-telemetry.md in that memory directoryEntry format:
### /rights-management — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.