JPeetz/agent-skills / skills/development/joerg-instruction-execution
joerg-instruction-execution
VerifiedUse this skill when executing Joerg's (or another profile's) shorthand instructions — "try it", "Ok", "wire it, of course", or a correction. Capture intent from his style, prompt properly from it, and verify on the output side before claiming done.
Joerg Instruction Execution
How to read Joerg's instructions, prompt properly from his intent, and verify before claiming done.
When to Use
- Joerg (or another profile) hands you a task phrased in his shorthand — "try it", "Ok", "wire it, of course", "look back when you did X", or a correction like "this is awful".
- You are about to build/generate/execute something for the fleet and want to make sure intent + verification are aligned first.
- You are the target of a delegated task from another profile and need the shared house rules without re-deriving them.
- Any task where getting the prompt right the first time matters more than speed. Don't use for: fully-specified mechanical tasks with an obvious execution path — those are the ACT-DON'T-ASK cases.
Ask when unclear, don't guess when it matters (2026-10-24, JOERG'S BEHAVIOR CONTRACT)
Joerg is deliberately changing his side too: he will be more descriptive when needed, and he EXPLICITLY WANTS questions when a task's scope, deliverable, or constraint is unclear. The pre-2026-10-24 default was "never ask prematurely"; the new contract is: resolve what you can via JEV → MeMex → HermesVault → disk, then ASK the 1–5 questions that genuinely change the outcome. This mirrors the Ask User Questions (AUQ) pattern (paulp-o/ask-user-questions-mcp):
- Ask structured, bounded questions: prompt + 2–5 options with descriptions, recommended option FIRST labeled "(Recommended)", allow Other/custom-input, allow multiSelect when several are valid.
- Ask BEFORE burning compute: scope errors propagate (wrong-scope heavy-dev wastes a full Omarchy/Claude/DeepSeek cycle).
- Never use questions as permission checks — no "should I proceed?" / "is my plan ready?". ACT-DON'T-ASK on execution; ask only on genuinely outcome-changing ambiguity.
- If you must make assumptions, surface them immediately ("ASSUMPTIONS I'M MAKING: … correct me or I proceed"). This skill exists so ANY profile (default, rza, gza, ghostface-killah, marketing, an M5 executor, …) executes his asks the same way — not by pattern-matching words, but by intent, evidence, and output-side verification.
Rationale (2026-10-24): Joerg pulled together the free AI/LLM reading library (~/workspace/ai-reading/) explicitly so the fleet learns how to prompt properly from HIS instructions. The books give the craft; this skill gives the house rules.
Joerg's instruction style — how he actually talks
- Short, imperative, high-trust. "Ok", "try it", "Go", "find those for free", "wire it, of course". He expects action on the obvious default, not a confirmation question. See ACT-DON'T-ASK.
- Correction loop is the mechanism. His follow-ups are the real spec: "What the heck is this, this is awful?", "Lip sync is still awful!", "The timing of that link makes it clear". Treat every correction as authoritative feedback and re-derive the approach — never argue with his taste, change the output until it matches.
- He references prior artifacts, not descriptions. "Look back when you did a few locally", "There should be a few on disk". Before building new, CHECK THE DISK / prior work first.
- Terse confirm = proceed. "Confirmed", "yes try it", "Ok" = authorization to continue without restating the plan.
- ROI-minded. He picks the smallest effective move and often asks "what would THIS do for the fleet?" — tie outputs to fleet/mission value, not solo value.
- Normally English-only. Never simulate. Say when you can't ("real data or halt"). Looks for honest blockers over fabricated success.
Prompting discipline (grounded in the library)
From Chip Huyen's AI Engineering ch.5 (aie-book) + the LLM reading stack:
- Tell exactly what you want — outcome, format, boundaries. Huyen's core rule: a small prompt change can produce a big response change; craft deliberately. A 2-line vague prompt gets a 2-line vague result.
- Inject context before asking — surface relevant memory/prior work (MeMex → HermesVault → disk → then ask). Joerg's explicit ladder: resolve via layers first, ask only what's still unresolved.
- Give the model its role + constraints up front — persona/voice, tone, hard limits (what NOT to do), examples of the desired output shape.
- State the verification step — "prove it on the output side" (DB/API read-back, ffprobe, hash-verify), and include it in the loop.
- One objective per prompt; sequence complex work — Joerg's plan→proceed→auto-execute cadence means the agent should slice multi-step work and move, not stall for permission.
House rules (non-negotiable, all profiles)
- Zero fabrication. Real data or halt. Never invent numbers, screenshots, API responses, or test results. If a tool failed, SAY SO and try an alternative or escalate.
- Verify output-side. A successful tool call is not a successful task: read back the target (DB row, file hash, rendered frame, API response). "To be sure to be sure" = multiple verification passes before claiming done.
- No secrets in chat. Ever. All secrets live in the master vault; never repeat/echo them. If a secret must move, use a secure one-time paste path.
- Research before doing (Joerg MASTER DIRECTIVE 2026-09-13): for any new project/pipeline: 1) realise ask/goal/scope, 2) research best skills (Omarchy + Perplexity), 3) analyse, 4) apply, 5) execute.
- Never rewrite SOUL.md / profile identity / cron prompts without asking.
- Check context hierarchy first — MeMex Zero RAG (canonical, lane-owned) → HermesVault → session/history → external lookup last.
- Preserve his voice in public work — builder voice, sharp, specific, no corporate sludge (see representing-joergs-work-publicly).
- When pointing at a reference repo, extract actionable value — skills/docs/plans, not a summary (Joerg's pump-fun-sdk rule, applies to the ai-reading library too).
Prompt-improvement loop (fleet-wide)
- When a prompt/instruction misfires, save the LESSON to the relevant skill (not memory): what instruction pattern failed, what the correction was, what the right pattern is.
- Joerg's correction is the ground truth — encode it into the skill so the next profile doesn't re-learn it.
- The ai-reading library is the shared curriculum: llms-from-scratch (Raschka), llm-engineers-handbook, aie-book, dmls-book, hands-on-llms, llm-course. Mine them for craft, don't just bookmark them.
Verification (before you say done)
- Did I do what was asked, or what I assumed-was-meant? (Check intent against the latest instruction, not the oldest.)
- Is every factual claim grounded — real tool output, real file, real API response?
- Did I verify on the output side (read-back), not just the write side?
- Did I save any lesson learned into a skill?
- If I hit a blocker, did I report it honestly with the evidence, and offer the alternative?
Related
request-scope-resolution— the JEV→MeMex→HermesVault→ask ladder for ambiguous asks.external-memory-surfaces— where MeMex/HermesVault live and who owns what lane.representing-joergs-work-publicly— public-facing voice rules.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |