Hdr Audit

This skill should be used when the user asks "is this real HDR", "check HDR metadata", "fake HDR", "is this Dolby Vision legitimate", "HDR vs SDR", "check HDR peak brightness", or wants to verify whether HDR content is genuine or inverse tonemapped from SDR.

42 stars 2 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add robbyt/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add robbyt/claude-skills --skill hdr-audit
Manual install
git clone --depth 1 https://github.com/robbyt/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/plugins/multimedia/skills/hdr-audit ~/.claude/skills/hdr-audit

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# HDR Content Audit

Analyze HDR metadata and detect fake/invalid HDR content. HDR is not automatically better than SDR—many "HDR" releases are fake.

## What Makes HDR Real

Legitimate HDR requires:
1. **10-bit color depth** (minimum)
2. **HDR transfer function** (PQ or HLG)
3. **Actual extended brightness** (content above 100 nits)
4. **Mastered in HDR** from HDR source or graded for HDR

## Fake HDR Indicators

**Inverse tonemapped SDR**:
- SDR content artificially expanded to HDR range
- No actual detail gained in highlights
- Often looks flat or washed out on HDR displays
- Content never officially released in HDR

**HDR container, SDR content**:
- HDR metadata present but peak brightness never exceeds ~100 nits
- Tagged as HDR but visually identical to SDR

**Suspicious Dolby Vision**:
- Content only officially released in SDR
- DV metadata on old catalog titles
- Random releases that don't match official offerings

## MediaInfo HDR Fields

Key fields to check in Video section:

```
HDR format                   : SMPTE ST 2086 / SMPTE ST 2094...
Color primaries              : BT.2020
Transfer characteristics     : PQ (SMPTE 2084) or HLG
Matrix coefficients          : BT.2020 non-constant
Mastering display color prim : BT.2020 or DCI-P3
Mastering display luminance  : min: 0.0050 cd/m2, max: 1000 cd/m2
MaxCLL                       : 1000 cd/m2
MaxFALL                      : 400 cd/m2
```

## Audit Workflow

### Step 1: Check Basic HDR Presence
Read the full skill on GitHub

Details

Skill name
hdr-audit
Path
plugins/multimedia/skills/hdr-audit/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Hdr Audit skill do?

This skill should be used when the user asks "is this real HDR", "check HDR metadata", "fake HDR", "is this Dolby Vision legitimate", "HDR vs SDR", "check HDR peak brightness", or wants to verify whether HDR content is genuine or inverse tonemapped from SDR.

How do I install the Hdr Audit skill?

Claude Code plugin: /plugin marketplace add robbyt/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Hdr Audit popular?

It lives in robbyt/claude-skills, which has 42 GitHub stars and 2 forks.

Related skills

Actions

42

robbyt/claude-skills

GitHub Actions workflow management using GitHub CLI. Trigger when user wants to check CI status ("check CI", "is the build passing"), view workflow runs ("show recent runs", "view action logs"), watch running workflows ("watch CI"), or rerun failed workflows ("rerun the build").

Productivity & Notes

Adversarial Review

42

robbyt/claude-skills

Have Codex try to break a change before it ships — a skeptical review that challenges the design, assumptions, and failure modes of a diff or branch and returns structured findings (verdict, severity, file:line, confidence). Trigger on "adversarial review", "challenge this change/design with Codex", "pressure-test this before I ship", "have Codex try to break this", "is this safe to merge", or a review focused on a risk area (auth, data loss, rollback, race conditions, retries). Do NOT use for a routine bug/style pass over a diff (that's diff-review), for critiquing a plan before code exists (

Software Development

API Review

42

robbyt/claude-skills

This skill should be used when reviewing API designs, auditing REST or gRPC endpoints, designing backend APIs, evaluating BFF architecture, or discussing API best practices. Also triggers on: "review this API", "API design review", "is this API correct", "REST API audit", "gRPC API review", "PATCH vs PUT", "etag", "idempotency", "pagination design", "API error handling", "backward compatibility", "BFF architecture", "resource-oriented design", "TOCTOU", "race condition", "optimistic concurrency", "field mask", "long-running operation", "custom method", "soft delete", "API naming conventions",

Software Development

Client Docs

39

ShawhinT/non-coding-skills

Draft ABA's formal client-facing documents — proposals, statements of work (SOW, the signable contract version of an accepted proposal), and proposal decks. Fire whenever Shaw asks to draft, revise, or send a proposal, SOW, contract, engagement outline, pricing quote, or scope for a client, even when he names no format ("draft a proposal for X", "write the SOW", "update [Client]'s proposal"). The default proposal format is the branded PDF document; build a slide deck only when he asks for a deck or slides ("proposal deck", "put the proposal in slides"). Also covers training outlines, workshop

Writing & Content

Write Post

37

iamneilroberts/claude-skills

Turn a rough brief into a blog deep-dive draft. Takes a topic or brief, gathers the relevant sources, runs one short focused interview to pin down the angle and the claims, then writes a draft to docs/posts/<date>-<slug>.md. The default output is a rich outline — a dense, factual skeleton meant to be rewritten in your own voice — not finished prose. Pass `--draft` for full prose, `--outline` to force the outline. This is the no-BS technical counterpart to `/brag` (which builds a sales/hype showcase page); reach for write-post when the goal is an accurate deep dive. Triggers on `/write-post <to

Writing & Content

Linkedin Audience

39

ShawhinT/non-coding-skills

Weekly ICP sweep of Shaw's LinkedIn audience. Pull everyone who reacted, commented, voted, followed, viewed his profile, newly connected in a window, or sent a pending invite, qualify them against the ABA ICP page in Notion using LinkedIn's own data (current role, company headcount, HQ country, connection degree — no Apollo), and return two tables in chat — Tier 1 people at companies that match the ICP and Tier 2 people at adjacent companies, each row marked DM or Connect — plus which of the week's new connections are worth a DM. Use whenever Shaw asks who in his audience fits the ICP, "run th

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.