skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
pawbytes/skill-suites173 installs

paw-cra-quality-control

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

How do I install this agent skill?

npx skills add https://github.com/pawbytes/skill-suites --skill paw-cra-quality-control
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    This skill performs campaign-wide quality control by aggregating asset data. It uses a local Python script for path management and relies on standard system tools like ffprobe. The primary security consideration is the ingestion of untrusted manifest data which could lead to indirect prompt injection.

  • Socketpass

    No alerts

  • Snykpass

    Risk: LOW · No issues

What does this agent skill do?

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.

StagePurposeReference
1. Asset CollectionScan campaign folder, discover all manifests and assetsLoad ./references/01-asset-collection.md
2. Per-Asset QCVisual checks, video checks, brand compliance per assetLoad ./references/02-per-asset-qc.md
3. Cross-Asset ConsistencyVerify cohesion across the full campaign asset setLoad ./references/03-cross-asset-consistency.md
4. Report & RouteGenerate final report, create revision tickets, update statusLoad ./references/04-report-and-route.md

Severity Model

All issues use a three-tier severity:

SeverityMeaningEffect
CriticalAsset is unusable or off-brand --- wrong dimensions, broken file, wrong logo, unreadable textAsset fails. Revision ticket created.
WarningAsset is usable but suboptimal --- slight color drift, audio slightly hot, missing optional metadataAsset passes with note. Revision recommended.
InfoObservation or suggestion --- could improve but not a quality gate issueLogged 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:

ManifestProducerContains
design-manifest.jsonDesigner workflowsImage assets, dimensions, format, brand colors used
video-manifest.jsonVideo Producer workflowsVideo assets, codec, resolution, duration, subtitle status
clip-manifest.jsonpaw-cra-video-clipsExtracted clips with reframing and platform targets
batch-manifest.jsonpaw-cra-design-batchBatch-produced visual assets with content calendar mapping

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/pawbytes/skill-suites/paw-cra-quality-control">View paw-cra-quality-control on skillZs</a>