app-design-thinking
Design the app mechanism and build pipeline for the produced app — the app-phase analog of [[schema-design]]. Use this skill whenever the knowledge phases are…
Generate John's process scorecard, auditor manifests, and shareable run report from a Codex project using John's provider-neutral scripts. Use when the user asks for a John report, run report, scorecard, provenance manifest, self-evaluation manifest, or evidence for template
$ npx -y skills add kitchen-engineer42/joharnessburg --skill codex-run-report --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/codex-run-reportContext preview
The summary Claude sees to decide when to auto-load this skill.
Generate John's process scorecard, auditor manifests, and shareable run report from a Codex project using John's provider-neutral scripts. Use when the user asks for a John report, run report, scorecard, provenance manifest, self-evaluation manifest, or evidence for template
name: codex-run-report description: Generate John's process scorecard, auditor manifests, and shareable run report from a Codex project using John's provider-neutral scripts. Use when the user asks for a John report, run report, scorecard, provenance manifest, self-evaluation manifest, or evidence for template evolution while working in Codex.
Run the deterministic report pipeline from the initialized project root:
python3 "<john-plugin>/scripts/process_scorecard.py" python3 "<john-plugin>/scripts/emit_manifests.py"
Then follow the shared report scrub-and-generalize contract in John's `skill-evolution` guidance before writing a shareable Markdown report under `.john/reports/`. Do not infer Codex skill-invocation counts: the scorecard marks Claude Skill-tool telemetry as unsupported on Codex while still counting both `.claude/skills/` and `.agents/skills/` outputs.
Use the JSON fields for evidence. Keep provider execution details separate from the provider-neutral event, checkpoint, lesson, and produced-skill results.
中文版: README_ZH.md John turns unstructured source material into a working knowledge-dense app. It keeps knowledge engineering and app building in one durable run, coordinates large per-entry fan-outs, and leaves auditable events and checkpoints on disk.
Design the app mechanism and build pipeline for the produced app — the app-phase analog of [[schema-design]]. Use this skill whenever the knowledge phases are…
Bundle a finished John workspace from Codex. Use when the user wants to archive, package, hand off, or preserve a John project, or wants the Claude command…
Break parsed markdown into a tree of progressively-disclosed chunks for downstream extraction. Use this skill whenever a phase needs to work on per-chunk…
Apply deterministic quality checks to the code John produces — catch the 80% of issues (leaked API keys, hardcoded prod URLs, broken imports, missing…
Activate a Hamster-built or otherwise applied John template for Codex in the current project. Use when a merged template plugin already exists, when the user…
Execute John's high-volume vertical phases with native Codex subagents over the durable `.john/runs` and event contracts. Use for per-chunk extraction,…