Context packing with Oracle and PackX: team walkthrough

Skill-backed context packing and Oracle review: scope and evidence selection, preview and bundling, compact evidence, follow-up state tracking, CLAUDE.md exclusion, saved-log inspection, and locally authored project artifacts.

Team Learning Goal

Teach this as a skill-backed workflow, not a PackX flag lecture.

The audience should understand that skills/oracle-packx/SKILL.md is the operational contract. The cheatsheet explains when to use it, what it does, what to ask for, and how to inspect the result.

Walkthrough Depth

Essential Walkthrough

  1. Show the software scenario: saved payment methods, billing webhook bug, or auth/session architecture review.
  2. Show the bundled skill path: skills/oracle-packx/SKILL.md.
  3. Explain that the skill owns PackX command construction and Oracle call shape.
  4. Show the high-level pipeline: preview, bundle, browser Oracle, output.log, local artifact.
  5. Show what the human must provide: outcome, scope, evidence, exclusions, success check.
  6. Show how to know it worked.

Expanded Walkthrough

Add:

  • compact evidence
  • follow-up Oracle calls and prior-state ledger
  • why Oracle-created downloads are not the artifact
  • why CLAUDE.md is excluded

Deep-Dive Walkthrough

Add:

  • skim the PackX quick reference
  • show the common PackX capabilities table
  • discuss when this workflow is too heavy
  • start an exercise where team members write a skill invocation prompt for their own project

Talking Points

Opening:

You are not learning every PackX flag. You are learning when to hand a hard software question to a skill that knows how to build the packet.

When showing the skill:

The skill is the source of truth. The cheatsheet is the mental map.

When showing preview:

Preview is how the skill fails cheaply before spending the Oracle run.

When showing CLAUDE.md exclusion:

Repo instructions can matter, but this workflow excludes CLAUDE.md and prefers deliberately scoped guidance.

When showing compact evidence:

Some evidence should be summarized, not packed raw.

When showing output.log:

The visible answer may be clipped. The skill requires the local agent to read the saved log before summarizing.

Do Not Over-Explain

  • every PackX flag
  • tokenizer internals
  • browser automation implementation details
  • Oracle pricing or product speculation
  • every line of the skill
  • every possible PackX workflow

Essential Points To Preserve

  • oracle-packx is a bundled skill.
  • The skill owns PackX and Oracle execution details.
  • The human supplies scope, evidence, exclusions, and desired software outcome.
  • The output is read from output.log.
  • The local agent writes the project artifact.

Portable Pattern Table

John's local thing Portable pattern
skills/oracle-packx/SKILL.md skill as workflow contract
PackX deterministic context bundler
--preview inspect before sending context
~/.oracle/bundles/{slug}.txt local context packet
Oracle browser mode deliberate deep review surface
output.log saved full answer
compact evidence useful facts from raw material that should not be packed
local artifact write project output owned by the local environment

Bridge To Section 2

Close with:

Section 1 showed a skill that gives the agent the right project context. Section 2 is about making sure the agent can see the same shell environment and tools you expect it to use.

Source references