Published mirror page for the Operator Agent Skills catalog.

This is one pack in the Operator Agent Skills catalog: portable context packs and agent skills for Codex, Claude Code / cowork, OpenClaw, Hermes, and similar operator-agent runtimes.

Source series

The Implementation Economy

Who it is for

Operators, founders, executives, product/revenue/operations leaders, and agents supporting high-stakes operating decisions.

When to use it

Use this pack when you need structured, evidence-backed decisions in the domain of The Implementation Economy. The four skills are sequenced to avoid overlap and produce reusable artifacts.

Included skills

  • Purchase-to-Adoption Gap Diagnosis — Use this workflow when work in this pack specifically requires purchase-to-adoption gap diagnosis and a concrete operator-grade artifact. Use it as one step in the pack progression, not as a generic strategy brainstorm.
  • Implementation Ownership Architecture — Use this workflow when work in this pack specifically requires implementation ownership architecture and a concrete operator-grade artifact. Use it as one step in the pack progression, not as a generic strategy brainstorm.
  • Implementation Economics Model — Use this workflow when work in this pack specifically requires implementation economics model and a concrete operator-grade artifact. Use it as one step in the pack progression, not as a generic strategy brainstorm.
  • Services-to-Product Conversion Plan — Use this workflow when work in this pack specifically requires services-to-product conversion plan and a concrete operator-grade artifact. Use it as one step in the pack progression, not as a generic strategy brainstorm.

How to load in Codex / Claude Code / OpenClaw / Hermes

  1. Start from START_HERE.md, manifest.json, or the main catalog.
  2. Select this pack, then select one skill for the immediate job.
  3. Load only the pack README.md, the selected skill file, and the matching example if a concrete prompt pattern helps.
  4. Preserve the selected skill's output schema, assumptions, failure modes, and human review gates.
  5. Do not treat a skill as permission for autonomous external action; keep external, personnel, financial, legal, security, and high-impact decisions behind explicit human review.

packs/77-implementation-economy