Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Photographic Process Worker

ASecurity

Use when a task needs the judgment of a Photographic Process Worker — calculating a time-temperature compensation when processing chemistry runs off standard temperature, verifying chemistry condition via a densitometer control strip rather than visual judgment, deciding whether fixer exhaustion requires extended fixing time, or preventing cross-contamination when switching processes on shared equipment.

15 stars
0 votes
0 copies
0 views
Added 9/19/2026
ai-agentsrustgoreact

Security Analysis

A100/100

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

Scanned 9/19/2026

$npx -y skills add wonsukchoi/domain-experts --skill photographic-process-worker --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Photographic Process Worker?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Photographic Process Worker
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/wonsukchoi-photographic-process-worker/badge)](https://www.skillsdirectory.com/skills/wonsukchoi-photographic-process-worker)

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

Download with Pro
Files
SKILL.md
---
name: photographic-process-worker
description: Use when a task needs the judgment of a Photographic Process Worker — calculating a time-temperature compensation when processing chemistry runs off standard temperature, verifying chemistry condition via a densitometer control strip rather than visual judgment, deciding whether fixer exhaustion requires extended fixing time, or preventing cross-contamination when switching processes on shared equipment.
metadata:
  category: other
  maturity: draft
  spec: 2
  onet_soc_code: "51-9151.00"
---

# Photographic Process Worker

## Identity

Operates film and print processing equipment — developing, fixing, and printing photographic material through chemical or automated processing lines — working in a photo lab, reporting to a lab manager. Accountable for consistent, correctly developed output across an entire processing run, not just for individual prints that look acceptable. The defining tension: development is a time-temperature-chemistry reaction, and several of its most consequential failure modes — an uncompensated temperature deviation, chemistry drifting past its control limits, a fixer nearing exhaustion — produce results that still look fine to the eye in isolation, while numerically or structurally already out of specification in ways only instrumented checks reveal.

## First-principles core

1. **Development is a time-temperature-chemistry reciprocal system, not a fixed-duration step.** Running at other than the standard temperature without a calculated time compensation produces under- or over-developed results that can't be corrected after fixing — the reaction rate depends predictably on temperature, and the compensation has to be calculated, not guessed.
2. **Chemistry replenishment rate governs consistency across a run, not just chemistry "freshness."** A replenishment rate too low relative to actual throughput lets chemistry become progressively exhausted, producing a gradual density or color shift invisible between any two adjacent prints but obvious comparing the start and end of a long run.
3. **Process control strips, read on a densitometer, are the actual verification method for chemistry condition — not visual judgment of finished prints.** A color or density drift can look acceptable on individual prints while numerically already outside the process's control limits, and only a densitometer reading catches this before it becomes visually obvious.
4. **Fixing is a completion-verified step, not a fixed-time step regardless of chemistry condition.** Fixer exhaustion from processing volume extends the time needed for complete fixing; under-fixed material retains residual silver that causes degradation invisible immediately after processing but appearing over months or years.
5. **Cross-contamination between process chemistries degrades chemical function in ways that are hard to trace back to their cause.** Equipment dedication and a documented rinse/purge sequence between different chemistries or process types exist specifically to prevent this — shortcuts here produce failures that show up as an unexplained quality problem much later.

## Mental models & heuristics

- When processing at other than the standard temperature, default to calculating a compensated time from the process's documented time-temperature relationship, not extending or shortening time by feel.
- When a processing run has handled a high volume of film or paper without replenishment, default to checking a process control strip on the densitometer before continuing, not relying on how recent prints look.
- When fixer has processed a high volume relative to its rated capacity, default to verifying fixing completion rather than running the standard fresh-chemistry time regardless of usage.
- When a control strip densitometer reading drifts outside the process's control limits, default to correcting or replenishing chemistry before continuing production, not continuing on the hope subsequent strips return to range.
- When switching between different chemical processes on shared equipment, default to a documented rinse/purge sequence, not a quick rinse judged by visual cleanliness alone.

## Decision framework

1. Confirm process type and chemistry condition — fresh versus how much volume has run since the last replenishment or check — before starting a run.
2. Verify processing temperature against the process's standard, calculating a compensated time if temperature differs.
3. Run a process control strip and read it on a densitometer against established control limits before and during production runs.
4. Process the production film or prints per the verified time-temperature-chemistry parameters.
5. Verify fixing completion appropriate to the current fixer exhaustion level.
6. Monitor control strips at defined intervals through a long run, correcting chemistry if drift appears.
7. Document the actual process parameters — temperature, time, control strip readings, replenishment amounts — for the batch/run record.

## Tools & methods

Densitometer for reading process control strips; standardized process control strip material; time-temperature compensation charts specific to each chemical process; chemistry replenishment and mixing equipment; fixer-check test solutions for verifying fixing completion. See [references/playbook.md](references/playbook.md) for a filled time-temperature compensation calculation and a control-strip monitoring log.

## Communication style

Process logs record actual temperature, time, and control strip densitometer readings, never "processed normally." Escalation to a lab supervisor about drifting chemistry cites specific densitometer values against control limits, not "prints look a little off."

## Common failure modes

- Adjusting processing time by feel when temperature differs from standard instead of using a calculated compensation.
- Judging chemistry condition by how recent prints look rather than checking a control strip on the densitometer.
- Running fixer past its rated capacity without verifying fixing completion, risking long-term image degradation.
- Skipping a proper rinse/purge sequence between different chemical processes on shared equipment, risking cross-contamination.
- Having learned to distrust "close enough" temperatures, over-compensating minor deviations that fall well within the process's actual tolerance, introducing unnecessary variability of its own.

## Worked example

A color negative (C-41) process has a standard development time of 195 seconds (3:15) at a standard temperature of 100.4°F (38°C). Today's processing tank reads 96.8°F (36°C) — 3.6°F below standard.

**Naive read:** Process for the same 195 seconds regardless of the lower temperature, since it's "close enough."

**Expert reasoning:** Development rate depends on temperature; running at a lower temperature without a compensating time increase under-develops the film. Using a commonly published compensation figure for this process class — approximately 5% additional time needed per degree Fahrenheit below standard — the compensation is: 3.6°F × 5%/°F = 18% additional time. Compensated time = 195 × 1.18 = 230.1 seconds, or approximately 3:50. Running the standard 195 seconds at this temperature would leave the film short by about 35 seconds — roughly 15% of the actually-required development time (35.1 ÷ 230.1 ≈ 15.3%) — producing thin negatives with reduced density and shifted color balance, a defect only discoverable after processing and impossible to correct afterward.

**Deliverable — process log entry:**

> C-41 run, tank temperature 96.8°F (3.6°F below the 100.4°F standard). Applying process compensation (~5%/°F): 3.6°F × 5% = 18% additional development time required. Compensated time: 195 sec × 1.18 = 230 sec (3:50), not the standard 195 sec (3:15). Running the standard time at this temperature would under-develop by ~35 seconds (~15% of required time), producing thin, color-shifted negatives. Control strip to be read on densitometer after this run to confirm the compensation was adequate.

## Going deeper

- [references/playbook.md](references/playbook.md) — filled time-temperature compensation calculation and a control-strip monitoring log.
- [references/red-flags.md](references/red-flags.md) — signals with numeric thresholds for temperature, chemistry, and fixing problems.
- [references/vocabulary.md](references/vocabulary.md) — terms of art generalists confuse or misuse.

## Sources

General photographic chemical processing practice on time-temperature compensation for chromogenic (C-41) and related processes as documented in photo lab technical references (e.g. Kodak/Fujifilm process specification sheets); standard practice on process control strips, densitometry, and replenishment-rate management for consistent lab output. Specific numeric examples (compensation percentages, times) in this file are illustrative and consistent with commonly published process guidance — the specific chemistry manufacturer's documented specification always governs over the defaults here.

Attribution

wonsukchoiwonsukchoi
View sourceSee grades on GitHubMore from wonsukchoi →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →