c2pa-spec-compliance

Included with Lifetime

$97 forever

Verifies software compliance with the C2PA specification. Invoke during planning or code review to check implementations against the spec. Provide code/design context and optionally a target version.

Design

What this skill does


# C2PA Compliance Check

Verify code or designs against the C2PA (Coalition for Content Provenance and Authenticity) specification.

## Input

When invoking this skill, provide:
- **Code or design to review**: The specific files, functions, or design decisions to check
- **Review type**: `planning` | `code-review` | `testing`
- **Version** (optional): Target spec version (defaults to latest)

## Output

Return a compliance report with:
- **Version checked**: The spec version used
- **Findings**: List of compliance issues or confirmations, each citing the relevant spec section
- **Verdict**: `compliant` | `non-compliant` | `needs-clarification`

## Process

1. **Determine version**:
   - Use provided version if specified
   - Or check project config (`package.json`, `Cargo.toml`, etc.) for C2PA library versions
   - Or discover latest by fetching `https://github.com/c2pa-org/specifications/tree/main/build/site/specifications` and finding the highest numbered folder (e.g., if folders are 1.0, 1.1, 2.0, 2.1, 2.2, 2.3, 2.4 → use 2.4)

2. **Fetch relevant spec sections**: Use WebFetch to retrieve the specification:
   ```
   https://github.com/c2pa-org/specifications/blob/main/build/site/specifications/{version}/specs/C2PA_Specification.html
   ```

   Other documents if needed:
   - `specs/ContentCredentials.html` - Content credentials
   - `guidance/Guidance.html` - Implementation guidance
   - `ai-ml/ai_ml.html` - AI/ML requirements

3. **Compare implementation to spec**: For each C2PA-relevant component in the code/design:
   - Find the corresponding spec requirement
   - Verify the implementation matches
   - Note any deviations with spec section reference

4. **Report findings**: Return structured findings with spec citations

## C2PA Components to Check

When reviewing, look for these areas:
- **Manifest/JUMBF structure**: Box format, labels, nesting
- **Claims**: Required fields, claim linkage
- **Assertions**: Standard labels, custom handling
- **Signatures**: Algorithm support, certificate handling
- **Hash binding**: Asset hashing, hard/soft binding
- **Trust validation**: Certificate chains, revocation

## Example Invocation

```
Review type: code-review
Version: 2.3
Code: [manifest.rs - the create_manifest function]

Check that the manifest structure and required claim fields
comply with C2PA 2.3 specification.
```

## Example Output

```
## C2PA Compliance Report

**Spec Version**: 2.3
**Component**: create_manifest function

### Findings

1. **Compliant**: JUMBF box structure uses correct `c2pa` label
   (per spec section 6.2)

2. **Non-compliant**: Missing `claim_generator` field in claim
   (required per spec section 8.1.2)

3. **Compliant**: Signature algorithm ES256 is supported
   (per spec section 12.3)

### Verdict: non-compliant

**Action required**: Add `claim_generator` field to claim structure.
```

## References

See `references/` for:
- `VERSIONS.md` - Version matrix and URL construction
- `WORKFLOW.md` - Detailed review workflows by phase
- `CHECKLIST.md` - Compliance checklist template

Files: 4

Size: 10.6 KB

Complexity: 31/100

Category: Design

Source: https://github.com/kempsterrrr/personal-claude-skills/tree/main/skills/c2pa-spec-compliance

Related in Design

contribute

Included

Local-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".

Designscripts

architectural-analysis

Included

User-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).

Designscripts

mcp

Included

Model Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.

Designscripts

react-native-skia

Included

Design, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.

Designscripts

plaid

Included

Product Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".

Designscripts

nextjs-framer-motion-animations

Included

Adds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.

Designscripts