From ops
Inspect the shared Ops Ledger — what's awaiting owner, what was handled autonomously, what claude-ops or Perplexity did in the last 24h. Always the single source of truth between the two systems.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ops:ledgerThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Single source of truth shared between claude-ops (Mac) and Perplexity (off-Mac).
Single source of truth shared between claude-ops (Mac) and Perplexity (off-Mac).
Stored at ~/.claude-ops/ledger.jsonl and mirrored to Notion DB "Ops Ledger".
# Default: human digest of last 24h
/ops:ledger
# What needs owner's attention right now?
/ops:ledger awaiting
# What did Perplexity do while I was at the gym?
/ops:ledger query --source perplexity --since -PT4H
# What's been touched on this Gmail thread?
/ops:ledger query --claim-key gmail:thread:19e690a55d213f52
Wraps ~/.claude-ops/bin/ledger (the CLI from this skill). Always reports:
Before doing real work, run:
~/.claude-ops/bin/ledger query --claim-key "$CLAIM_KEY" --since -PT24H
If result has any entry with status in (in_progress, done, drafted, awaiting_sam),
SKIP — the other system already handled it. Don't duplicate.
After doing work:
~/.claude-ops/bin/ledger claim --claim-key "$CLAIM_KEY" --kind <kind> --brand <brand> \
--title "<title>" --source claude-ops
# ... do work ...
~/.claude-ops/bin/ledger resolve <id> --status done|drafted|awaiting_sam
npx claudepluginhub lifecycle-innovations-limited/claude-ops --plugin opsCreates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.