app-design-thinking
Design the app mechanism and build pipeline for the produced app — the app-phase analog of [[schema-design]]. Use 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
Claude Code
$ npx -y skills add kitchen-engineer42/joharnessburg --skill codex-run-report --agent claude-code
Codex
$ npx skills add kitchen-engineer42/joharnessburg --skill codex-run-report -a codex -y
Cursor
$ npx skills add kitchen-engineer42/joharnessburg --skill codex-run-report -a cursor -y
Gemini CLI
$ npx skills add kitchen-engineer42/joharnessburg --skill codex-run-report -a gemini-cli -y
GitHub Copilot
$ npx skills add kitchen-engineer42/joharnessburg --skill codex-run-report -a github-copilot -y
OpenCode
$ npx skills add kitchen-engineer42/joharnessburg --skill codex-run-report -a opencode -y
Windsurf
$ npx skills add kitchen-engineer42/joharnessburg --skill codex-run-report -a windsurf -y
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…
Bundle a finished John workspace from Codex. Use when the user wants to archive, package, hand off, or preserve a John project,…
Break parsed markdown into a tree of progressively-disclosed chunks for downstream extraction. Use this skill whenever a phase…
Apply deterministic quality checks to the code John produces — catch the 80% of issues (leaked API keys, hardcoded prod URLs,…
Activate a Hamster-built or otherwise applied John template for Codex in the current project. Use when a merged template plugin…
Execute John's high-volume vertical phases with native Codex subagents over the durable `.john/runs` and event contracts. Use for…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.