Skip to content
Back to skills

Paw Cra Quality Control

ASecurity

Aggregate cross-asset quality control for campaigns. Use when the user requests 'run QC', 'quality check campaign', 'review all assets', or 'generate QA report'.

  • 116 stars
  • 0 votes
  • 0 copies
  • 4 views
  • Added September 10, 2026
content-marketinggo

Works with

  • cli

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned November 9, 2026

npx -y skills add pawbytes/skill-suites --skill paw-cra-quality-control --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Paw Cra Quality Control?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Paw Cra Quality Control
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pawbytes-paw-cra-quality-control/badge)](https://www.skillsdirectory.com/skills/pawbytes-paw-cra-quality-control)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: paw-cra-quality-control
description: Aggregate cross-asset quality control for campaigns. Use when the user requests 'run QC', 'quality check campaign', 'review all assets', or 'generate QA report'.
---

# Quality Control

## Overview

This workflow aggregates quality control across all produced visual and video assets in a campaign, then generates a pass/fail report with revision tickets for anything that needs rework. Act as a meticulous QA lead who understands both brand standards and platform technical requirements.

**Args:** Accepts `--headless` / `-H` for autonomous execution against a campaign folder.

**Output:** `qa-report.md` with per-asset pass/fail verdicts, severity-rated issues, and revision tickets routed back to owning production workflows.

**Key distinction:** This is campaign-level cross-asset QC. Individual production workflows (Designer, Video Producer) already have embedded per-asset review gates. This workflow aggregates those results and adds cross-asset consistency checking that no single production workflow can do alone --- verifying that all campaign assets feel like a cohesive set.

## On Activation

Load available config from `{project-root}/.pawbytes/config/config.yaml` and `{project-root}/.pawbytes/config/config.user.yaml` (root level and `cra` section). If config is missing, let the user know `paw-cra-setup` can configure the module at any time. Resolve and apply throughout the session (defaults in parens):

- `{user_name}` (null) --- address the user by name
- `{communication_language}` (English) --- use for all communications
- `{document_output_language}` (English) --- use for generated document content
- `{suite-root}` is `root` from `uv run {skill-root}/scripts/paw-paths.py detect` (`{skill-root}` is this skill's folder), normally `{project-root}/paw-suites/creative`. Every `{suite-root}/...` path below is relative to it. A custom folder in config `cra.output_directory` wins (`detect` lists it under `overrides`; an old default is not one).
- When `detect` reports `mode: legacy` or `both`, the user's files are still partly in the old `.pawbytes/creative-suites/` tree. Pass every path through `paw-paths.py locate <path>` (add `--write` for a new file) and use the path it returns. Once per session, tell the user that `paw-cra-setup` can move them to `paw-suites/creative/`, and offer it. Keep working either way.

Load shared agency memory from `{suite-root}/_memory/index.md`. Identify the active brand and campaign. Load brand guidelines from `{suite-root}/brands/{brand-name}/guidelines.md`.

**Campaign folder resolution:** Accept a campaign folder path as argument, or infer from the active campaign in memory. The campaign folder is expected at `{suite-root}/brands/{brand-name}/campaigns/{campaign-name}/` (campaigns without a brand live under `brands/unassigned/`). If no campaign can be resolved, ask the user.

If `--headless` or `-H` is passed, run the full pipeline without interaction: collect assets, run all QC checks, generate report, route results.

Otherwise, greet the user, confirm the target campaign, and proceed through the stages below. Offer a summary of what will be checked before starting.

## Stages

This workflow progresses through four stages. Each stage writes findings to the in-progress `qa-report.md` using the document-as-cache pattern for compaction survival.

| Stage | Purpose | Reference |
|-------|---------|-----------|
| 1. Asset Collection | Scan campaign folder, discover all manifests and assets | Load `./references/01-asset-collection.md` |
| 2. Per-Asset QC | Visual checks, video checks, brand compliance per asset | Load `./references/02-per-asset-qc.md` |
| 3. Cross-Asset Consistency | Verify cohesion across the full campaign asset set | Load `./references/03-cross-asset-consistency.md` |
| 4. Report & Route | Generate final report, create revision tickets, update status | Load `./references/04-report-and-route.md` |

## Severity Model

All issues use a three-tier severity:

| Severity | Meaning | Effect |
|----------|---------|--------|
| **Critical** | Asset is unusable or off-brand --- wrong dimensions, broken file, wrong logo, unreadable text | Asset fails. Revision ticket created. |
| **Warning** | Asset is usable but suboptimal --- slight color drift, audio slightly hot, missing optional metadata | Asset passes with note. Revision recommended. |
| **Info** | Observation or suggestion --- could improve but not a quality gate issue | Logged for reference. No revision ticket. |

An asset **passes** if it has zero critical issues. A campaign is **QC-approved** only when all assets pass.

## Manifest Types

Production workflows emit these manifest files. This workflow reads all of them:

| Manifest | Producer | Contains |
|----------|----------|----------|
| `design-manifest.json` | Designer workflows | Image assets, dimensions, format, brand colors used |
| `video-manifest.json` | Video Producer workflows | Video assets, codec, resolution, duration, subtitle status |
| `clip-manifest.json` | `paw-cra-video-clips` | Extracted clips with reframing and platform targets |
| `batch-manifest.json` | `paw-cra-design-batch` | Batch-produced visual assets with content calendar mapping |

Files in this skill

  • SKILL.md4.5 KB
  • references/01-asset-collection.md2.8 KB
  • references/02-per-asset-qc.md3.4 KB
  • references/03-cross-asset-consistency.md3.3 KB
  • references/04-report-and-route.md3.7 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in content-marketing →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.