agentsclimarketplace

Quality review

Skill derekslinz/photography-workflow/skills/quality-review

Step 2 of 6 in the photo intake pipeline. Assesses each candidate photo against technical, editorial, and print-readiness criteria before the image moves to legal review. Produces a PASS / CONDITIONAL PASS / FAIL verdict per image. On FAIL, surfaces specific reasons and waits for user instruction — takes no destructive action. Mandatory 2048px downscale before the model views any image, plus a deterministic measurement pass (bundled Pillow/numpy extractor) that grounds the technical and print-readiness verdicts in real metrics. USE WHEN: quality check, quality gate, review photos before publishing, are these good enough, editorial review, technical review, print-ready check, assess photos. NOT FOR: metadata tagging (use /Photo-Metadata-Helper), rights audits (use /property-release-review and /model-release-review), final publishing (use /reviewed-photo-publish).From its SKILL.md

Install
npx -y skills add derekslinz/photography-workflow --skill quality-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

20.4 KB, as published. Nobody here has run it

Quality Review

Step 2 of 6 in the photo intake pipeline. Reviews each photo for technical quality, editorial merit, and print-readiness before committing time to legal review and publishing.

Intake Sequence (Step 2 of 6)

  1. Photo-Metadata-Helper — metadata, naming, subject-name embed
  2. quality-review (this skill) — technical, editorial, print-readiness gate
  3. property-release-review — depicted-object audit
  4. model-release-review — depicted-person audit
  5. localization-audit-review — Dutch customer-facing content QA
  6. reviewed-photo-publish — catalog entry, Stripe listing, remove from queue

If a photo fails quality review, do not proceed to steps 3–6 for that photo. Surface the failure and wait for user instruction.

🚨 MANDATORY FIRST ACTIONS: the visual gate AND the measurement pass

Two things happen before any verdict, and they are deliberately different.

(a) Visual gate — downscale to 2048px for the model's eyes

Before the model views any image, downscale to 2048px on the long edge and view only that copy. If resize fails, HALT and prompt the user.

magick "$FILE" -resize "2048x2048>" "/tmp/qr_$(basename "$FILE")"

Read the downscaled file from /tmp/qr_* using the Read tool — never the full-res original. Clean up /tmp/qr_* after the review is complete.

This stage uses 2048px, aligned with the pipeline default: a print gate has to tell "soft" from "tack-sharp," and lower resolution is too coarse to judge critical focus or fine detail. The visual copy is now for composition, subject, and editorial merit — the hard technical numbers come from the measurement pass below. The cross-cutting [[downscale-gate-load-bearing]] rule still governs the model's viewing: 2048px is the resolution cap.

(b) Measurement pass — run the extractor on the ORIGINAL file

A script reading the file is not the model reading the file: it computes numbers and prints a few lines, it never pours megapixels into context. This is exactly why exiftool and magick already run on the original here. Run the bundled extractor once per image:

python3 "${CLAUDE_PLUGIN_ROOT}/skills/quality-review/scripts/analyze_image.py" "$FILE" \
  --json "/tmp/qr_$(basename "$FILE").json"

(If ${CLAUDE_PLUGIN_ROOT} isn't set, use this skill's own scripts/analyze_image.py.) It needs only Pillow + numpy. It returns measured focus (variance of Laplacian, global + per-tile), exposure (clip %, dynamic-range span), noise, colour cast (per-channel means + tint), true pixel dimensions / aspect ratio, and scene key — the evidence that grounds the Technical and Print-Readiness verdicts below.

These measurements are deterministic facts, not opinions. Use them as the source of truth for the technical criterion; reserve the model's eyes for what only eyes can judge (composition, subject, "does this work"). If the script genuinely can't run, say so and fall back to visual-only technical judgement, marking those calls estimated.

The Three Criteria

1. Technical Quality

FactorPASSCONDITIONAL PASSFAIL
FocusPrimary subject sharpSoft but subject identifiable; blur reads as intentionalPrimary subject out of focus; unrecoverable
ExposureFull tonal range; highlights and shadows retain detailMild clipping in non-critical areasBlown highlights or crushed blacks in subject
NoiseClean at expected print sizesVisible noise; acceptable at smaller sizes onlyNoise destroys detail; print unusable
ColourAccurate or clearly intentionalMinor cast; correctable in postSevere uncorrected cast that misrepresents the scene
ArtefactsNoneMild CA or minor vignettingHeavy CA, banding, diffraction softness, JPEG blocking

Intentional creative choices (motion blur, grain film simulation, high contrast B&W) are not failures — read the image as a whole before flagging.

Ground each Technical factor in the measurement-pass numbers (/tmp/qr_*.json). The metrics map onto the table above as follows — let the measured value drive the verdict, and use your eyes only to decide whether a flagged miss is intentional:

FactorMeasured signalRead it as
Focusfocus_blur.global_sharpness_lapvar + tile_sharpness_max / share_tiles_above_global_pct + dof_topbottom_gradientA low global value with a high tile max = a sharp subject on soft surroundings (shallow DOF → fine, not a FAIL). A low global value with a low tile max = nothing is sharp → soft capture.
Exposuretonal_dr.clipping.highlight_clip_pct / shadow_clip_pct + dynamic_range.usable_span_0_255Clipping in the subject is the FAIL case; crushed blacks in a deliberately low-key background are not. Judge against the genre profile thresholds (below), not a fixed number.
Noisenoise_artifacts.luma_noise_sigma_proxy (+ noise_label_proxy)Compare to the profile's noise.warn / noise.high. High ISO grain in documentary work can be intentional — eyes decide.
Colourlargest tonal_dr.*.mean channel difference + color.white_balance.tint / cct_kelvin_proxyA cast only fails if it misrepresents the scene and the profile penalizes casts (B&W / night / abstract set the penalty to 0).
Artefactsnoise_artifacts.blockiness_flag + chromatic_aberration_edge_rb + stage0.estimated_compressionBlockiness flag true + low bytes-per-pixel = heavy recompression. High CA on contrasty edges → lens artefact.

Use the genre profile for fair thresholds. Read references/profiles.json (an exact snapshot of the project's 14-genre PROFILE_CONFIG). Infer the genre from the image as a confidence-gated hypothesis; if you can't land it confidently, fall back to studio_photography (strictest). Then judge sharpness / clipping / noise / cast against that profile's numbers, so a low-key night frame isn't failed for the very darkness that defines it. This keeps the technical verdict auditable: "highlight_clip 6% exceeds landscape warn_pct 8%? no → PASS on exposure" beats "looks a bit bright."

2. Editorial Merit

FactorQuestions to ask
Subject interestIs there something worth stopping for? Is there a clear subject?
CompositionDoes the framing serve the subject? Are there distracting elements that can't be cropped away?
Emotional / aesthetic impactRate as Strong, Adequate, or Weak
Catalog differentiationIs this too similar to an existing entry in the same series? If so, which is stronger?

A photo needs at minimum Adequate on all four to PASS. Weak on two or more = FAIL.

3. Print-Readiness

All offered sizes (20×30, 40×60, 60×90 cm) share a 2:3 aspect ratio. Two checks are required: resolution and aspect ratio alignment.

3a. Aspect Ratio Check

Use the true pixel dimensions — the measurement pass already has them in /tmp/qr_*.json (stage0_ingest.width_px / height_px / aspect_ratio / megapixels), which is the source of truth here because it reads the actual pixel grid, not a possibly-stale EXIF tag. exiftool is a fine cross-check:

exiftool -ImageWidth -ImageHeight /root/intake/My-Photo.jpg

Compute AR = width ÷ height (landscape) or height ÷ width (portrait — always use the longer edge in the numerator).

Tolerance: ±10% of 1.5 → acceptable range 1.364–1.636 (landscape), 0.606–0.733 (portrait).

Images outside this range require >10% linear crop to fit a 2:3 print — a material loss of content buyers are not told about. Restrict their sizes accordingly.

For images outside tolerance, compute the effective long edge after a 2:3 crop:

Image AR (L = long, S = short edge)Effective long edge
Landscape, AR > 1.636 (wider than 2:3)S × 1.5
Portrait, AR < 0.606 (taller than 2:3)S × 1.5 (where S is the short/narrow edge)
Within tolerance 1.364–1.636L (no crop penalty)

Use the effective long edge — not the raw pixel count — in the resolution check below.

3b. Resolution Check (viewing-distance-aware — DPI is NOT fixed)

Required DPI is not constant. Bigger prints are viewed from farther away, so the per-inch demand drops as the print grows (rule of thumb: required ppi ≈ 3438 ÷ viewing-distance-in-inches). A flat 240-dpi-everywhere floor rejects large prints for resolution they don't actually need — a 60×90 cm wall piece seen from 1.5 m does not need the same ppi as an 8×12 held at arm's length. Check the effective long edge against the floor for that size:

Print sizeTypical viewing distIdeal dpiFloor dpiFloor long-edge pxIdeal long-edge px
20 × 30 cm (8 × 12 in)~40 cm3002402 835 px3 543 px
40 × 60 cm (16 × 24 in)~1 m2401804 252 px5 670 px
60 × 90 cm (24 × 36 in)~1.5 m2001505 315 px7 087 px

A size is supported when the effective long edge meets that size's floor. At/above the ideal it is comfortably print-sharp; between floor and ideal is acceptable and worth a note in the listing.

~5% grace band. Treat an effective long edge within 5% of a floor (≥ 0.95 × floor) as qualifying — the difference between ~228 and 240 dpi is imperceptible at fine-art viewing distances, so a near-miss is not restricted.

Upscaling is a separate flag. If a file only clears a size because it was AI-upscaled, flag it for interpolation (a CONDITIONAL reservation), not as a dpi failure — the two concerns are independent.

If the effective long edge falls below the smallest size's floor minus grace (≈2 693 px for 20×30), the photo can't print at any offered size → FAIL. Otherwise record the maximum supportable size as a listing ceiling. A pure size cap (e.g. supports up to 40×60 only) with all quality factors ≥3 stays a ✅ PASS with that ceiling — resolution-for-max-size is a listing parameter, not a quality reservation (see Verdict derivation). An 8 256 px file clears all three sizes here, where the old flat-240 rule would have capped it at 40×60.

Verdicts

VerdictMeaningNext step
✅ PASSMeets all three criteriaProceed to step 3 (property-release-review)
⚠️ CONDITIONAL PASSMeets minimum bar; noted reservationsProceed to step 3; carry reservations into listing notes
❌ FAILDoes not meet the barStop; surface reasons; wait for user instruction

Workflow

  1. Scope — list the files under review; note pixel dimensions for each

  2. Downscale & Measure — magick each file to /tmp/qr_* at 2048px (HALT on any resize failure); and run scripts/analyze_image.py on each original to /tmp/qr_*.json for the deterministic technical evidence. Both happen before any verdict.

  3. Duplicate Check — before assigning any verdict, check for duplicates in two passes:

    Pass A — byte-identical (within batch):

    md5sum /tmp/qr_*.jpg | sort | awk 'seen[$1]++ { print "DUPLICATE:", $2 }'
    

    If any match: identify primary (earliest timestamp or highest resolution), report clearly, delete the duplicate from the batch, and proceed with only unique files.

    Pass B — semantic near-duplicates (within batch + against published catalog): After viewing the downscaled images in step 4, flag any pair where:

    • Same subject / same scene with near-identical framing (different angle or moment alone is not enough)
    • Same shoot, same prop, same model in essentially the same pose
    • Both images cover the same catalog slot without adding meaningfully different value

    For catalog-sweep reviews, also compare against existing entries by same-series keyword overlap + visual similarity.

    On detection: HALT and present both candidates to the user with titles, IDs, current Stripe/size state, and a one-sentence distinction. Do NOT remove either entry until the user explicitly confirms which to drop.

  4. Assess — for each image, work through the three criteria in order: drive Technical and Print-Readiness from the measured JSON (/tmp/qr_*.json) against the genre profile, and use the 2048px visual copy for Editorial merit and to confirm whether any flagged technical miss is intentional rather than a defect

  5. Verdict — assign PASS / CONDITIONAL PASS / FAIL; write one-line reasons for every CONDITIONAL or FAIL criterion

  6. Report — the mandatory multi-factor scoring table (see Report Format), one row per photo, every factor column scored 1–5

  7. Decision — for FAIL photos, surface options to the user:

    • Delete from inbox
    • Keep in inbox for re-edit / reshoot
    • Move to /root/intake/_rejected/ for later review
  8. Proceed — PASS and CONDITIONAL PASS photos continue to property-release-review; FAIL photos wait

Report Format

ALWAYS print the multi-factor scoring table below — one row per photo, every factor column scored. This is mandatory on every run, including a single photo. Never collapse the per-factor columns into a single "Technical"/"Editorial" cell; the per-factor breakdown is the point — it shows why a verdict landed where it did and makes borderline calls auditable.

Score each factor 1–5 against this anchored scale:

ScoreMeaning
5Exceptional — gallery-reference execution on this axis. Rare; reserve it.
4Strong — clearly above the commercial standard
3Competent — meets the commercial fine-art bar. This is where most professional work lands.
2Weak — a noticeable, real deficiency on this axis
1Disqualifying

Calibration check — guard against top-heavy scoring. A competent commercial frame is a 3, not a 5. If most photos in a batch are scoring 4–5 across the board, you are not discriminating — re-anchor and spread the scores. Expect a real distribution: 5s should be rare, most factors should sit at 3–4, and genuine weaknesses must be scored 2 (don't round a real flaw up to 3 to be kind). Differentiation pulls redundant near-duplicates down: when several frames cover the same subject/scene, only the strongest one or two keep high Subject/Impact scores; the rest drop — being the fifth competent version of the same shot is itself a weakness. The scores exist to separate photos, not to flatter them.

The columns mirror the three criteria defined above:

  • Technical: Focus · Exposure · Noise · Colour · Artefacts
  • Editorial: Subject · Composition · Impact (Differentiation noted in Notes when relevant)
  • Print: the maximum supportable size from the resolution check (not a 1–5 score)
  • Avg: the mean of the eight factor scores (Σ ÷ 8), to one decimal — a single sortable quality signal. Use it to rank a batch and spot the weak frames at a glance; it does not override the verdict (a single 1 still governs). Typical competent work lands around 3.3–4.0; a batch whose averages all exceed 4.3 is a calibration red flag.
Quality Review — {n} photos

| File | Foc | Exp | Noi | Col | Art | Subj | Comp | Impact | Avg | Print (max) | Verdict | Notes |
|------|:---:|:---:|:---:|:---:|:---:|:----:|:----:|:------:|:---:|-------------|---------|-------|
| my-photo.jpg     | 4 | 3 | 2 | 4 | 4 | 4 | 4 | 3 | 3.5 | 40×60 | ⚠️ CONDITIONAL | Noise (2) is a real flaw; also caps print at ≤40×60cm |
| another.jpg      | 4 | 4 | 4 | 5 | 4 | 4 | 5 | 5 | 4.4 | 40×60 | ✅ PASS | all factors ≥3; 40×60 ceiling is a resolution/listing parameter, not a quality reservation |
| third.jpg        | 1 | 3 | 4 | 3 | 4 | 2 | 2 | 2 | 2.6 | 60×90 | ❌ FAIL | Subject out of focus (1); no compositional anchor |

Verdict derivation (deterministic from the scores):

  • Any factor scored 1, OR two or more editorial factors ≤2 → ❌ FAIL
  • Any factor scored 2, OR a noted reservation (e.g. AI-upscaled, mild artefacts) → ⚠️ CONDITIONAL PASS
  • All factors ≥3 → ✅ PASS. The maximum supportable print size is recorded in the Print column as a listing/ladder parameter — a cap below the largest size (e.g. 40×60) does not by itself lower the verdict. Resolution-for-max-size is not a quality reservation.

The Notes cell must name every factor scored ≤3 and the reason, so the score is never a bare number. For every ❌ FAIL row, follow the table with a short paragraph explaining the specific issue and what, if anything, could be done to recover it (crop, resend for re-edit, discard).

Calibrated Judgment

Do not fail a photo for stylistic choices you personally dislike. The question is whether the image meets a reasonable commercial fine-art standard — not whether you would have made the same creative decisions.

When uncertain, lean toward CONDITIONAL PASS with explicit notes rather than FAIL. The user has the final call on every FAIL.

Gotchas

  • The multi-factor scoring table is mandatory on every run — even for a single photo. Score all eight factors (Focus, Exposure, Noise, Colour, Artefacts, Subject, Composition, Impact) 1–5 per photo and derive the verdict from the scores. Never collapse the per-factor columns into a single Technical/Editorial cell, and never emit a verdict without the table.
  • Duplicate check is mandatory at step 3 — both byte-identical (MD5) and semantic near-duplicates (same shoot, same subject). Do not assign verdicts until the duplicate scan is complete. Never remove an entry without explicit user confirmation of which to drop.
  • No Stripe changes without explicit permission. Quality review produces verdicts and recommendations only. Do not archive products, deactivate prices, or modify any Stripe objects — not even as a "logical next step" after a sweep. Wait for the user to confirm before touching Stripe.
  • Motion blur is often intentional in travel and documentary work — look at the whole image before flagging focus.
  • Grain / high ISO noise in a documentary street photo may be a deliberate aesthetic.
  • Check composition for both portrait and landscape crop potential — a photo that looks tight in one orientation may work in the other.
  • Print dimensions are orientation-agnostic (20×30cm works for both 20 wide × 30 tall and the reverse) — use the longer pixel dimension vs. the longer print dimension.
  • Aspect ratio matters for resolution. A wide-panoramic image (AR > 1.636) loses resolution when cropped to 2:3 — use the effective long edge (short edge × 1.5), not the raw long edge, when checking against the dpi thresholds.
  • A pure size cap is not a verdict reduction. A photo with all quality factors ≥3 that only supports 40×60cm and 20×30cm is a ✅ PASS with a 40×60 listing ceiling — not a CONDITIONAL PASS. Resolution-for-max-size is a listing parameter; the verdict comes from the factor scores (see Verdict derivation). CONDITIONAL is for real quality reservations (a factor at 2, mild artefacts, AI-upscaling), not for a clean photo that simply prints large only up to a point.

When to invoke

  • "quality review these photos"
  • "are these good enough to sell"
  • "check the photos before legal review"
  • "editorial gate"
  • "print-ready check"
  • "quality check on the inbox"
  • Any photo intake run after Photo-Metadata-Helper completes

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.