Wiki:Packs

From WFM Labs

A pack is a deployable set for a Claude project, published as a wiki page. It contains one instruction block — pasted into a project's custom instructions — and one or more reference blocks, each saved as a Markdown file and uploaded as project knowledge.

Packs contain no installable skill. See Wiki:Skills for those, and the section below for why the distinction matters.

How to use a pack

  1. Open the pack page and read When to use it to confirm it fits the work
  2. Create a project in Claude. Name it for the work, not the method
  3. Copy Block 1 into the project's custom instructions
  4. Save each remaining block as the filename given in its heading, then upload them as project knowledge
  5. Start a conversation

About two minutes. Nothing is installed, nothing persists outside the project, and deleting the project removes the whole set.

Inventory

ID Pack Domain Blocks Version
CP-ANL-001 Causal Inference ANL 1 instruction + 2 reference 1.0
CP-WFM-001 Planning Under Demand Volatility WFM 1 instruction + 3 reference 1.0
CP-WFM-002 Agent Capability Ontology WFM 1 instruction + 4 reference 1.0
CP-WFM-003 Service Quality Comparability WFM 1 instruction + 5 reference 1.0
CP-WFM-004 Content Delivery Under Capacity Constraint WFM 1 instruction + 5 reference 1.0
CP-WFM-005 Leadership Transition Planning for Workforce and Supplier Operations WFM 1 instruction + 6 reference 1.1
CP-WFM-006 Demand Variance Decomposition WFM 1 instruction + 5 reference 1.1

Packs and skills

The two are deployed differently and suit different purposes.

Pack Skill
Deployed as Project instructions + uploaded knowledge Installed capability
Scope One project The whole account
Applies Whenever you are in that project When its description matches the request
Removed by Deleting the project Uninstalling
Cost when idle None Its description loads with every message, everywhere

A Claude skill is account-global: installing one means its description is carried in every conversation, and it cannot be limited to a single workstream. Project instructions do everything a skill's router does, apply reliably because being in the project is itself the trigger, and disappear cleanly when the work ends.

Reserve a skill for the rare capability that must act without being asked, in contexts that cannot be anticipated. Everything else should be a pack.

Domains

Packs share the domain codes used by Wiki:Skills, with a CP- prefix in place of CS-.

Code Domain
META Skill and prompt engineering
WFM Workforce management
ANL Analysis and statistics
RES Research and evidence
CNT Content and publishing
OPS Operations and automation
DEV Code and development

Structure of a pack page

Every pack follows the same layout. Wiki:Packs/Causal Inference is the reference implementation.

  • Infobox — ID, domain, version, and the source articles it derives from
  • When to use it — and when not to
  • How to deploy — numbered, four steps
  • Block 1 — the instruction block, 350–500 words, since it loads with every message in the project
  • Blocks 2–n — reference files, each headed with the filename to save it as
  • Usage notes — sizing, drift warning, scope
  • Change history and See also

Adding a pack

A pack is justified when three or more related articles form a workflow someone would use together, and knowing which to reach for is itself part of the skill. A single article does not justify one.

Write or augment the supporting articles first. Reference blocks are derived from articles — condensed and restructured for a model — not copied from them. An article and its block serve different readers and should not be identical.

Because blocks are derived, they drift. Each pack names its source articles in the infobox; treat that as a dependency list, and regenerate the pack when a source article changes materially.

See also