ledger

Solid

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.

AI & Automation 20 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 79/100

Stars 20%
44
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
70
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /ops:ledger 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". ## Usage ```bash # 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 ``` ## Behavior Wraps `~/.claude-ops/bin/ledger` (the CLI from this skill). Always reports: 1. Awaiting owner (top of digest, sorted newest first) 2. Drafted by either system (needs send / merge / approve) 3. Done autonomously in last 24h, grouped by source (claude-ops, Perplexity) 4. Skipped or expired claims ## Conventions every command in this plugin follows Before doing real work, run: ```bash ~/.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: ```bash ~/.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 ```

Details

Author
Lifecycle-Innovations-Limited
Repository
Lifecycle-Innovations-Limited/claude-ops
Created
3 months ago
Last Updated
today
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

sdlc-ledger

The team coordination ledger — set it up, read it, leave a note, or hand work off, all through the plugin instead of raw python paths. Use when the user runs /sdlc-ledger, wants to turn the ledger on or initialise it, check what's addressed to them, see who's done what, hand a blocker to a teammate, answer a hand-off, or regenerate TEAM.md. Do NOT use it to log claimed/done for a normal goal — the loop does that automatically.

6 Updated today
swapnil-agrim
Code & Development Listed

stats

Query or render the state of the scattered kit/tide/tg-cleanup/learned ledgers (the dwarves-kit gate/proof/telemetry corpus, tide file-move state, tg-cleanup snapshots, the learning ledger), and detect + propose backlog rows off anomalies in that state. Use when the operator asks to SEE ledger state -- "show me the ledger state", "my debt", "understanding debt", "telemetry", "token cost" / "how much am I spending on tokens", "kit runs" / "kit lane telemetry", "ledger status", "render the ledger", "ledger dashboard", "share this as an artifact" (mid-ledger-conversation) -- or to check/propose off it -- "any ledger anomalies", "is my debt over threshold", "propose a backlog row from the ledger state". Drives the read-only `stats` CLI (dwarves-kit/lib/stats) and renders the result as EITHER an in-terminal reply (bot-reply-formatting , tables + bar-fills) or a shareable web Artifact, both from the same one query; `stats anomalies` is the feedback-loop path, PROPOSE-only (stages a cc-backlog candidate, never files

8 Updated yesterday
dwarvesf
AI & Automation Listed

using-the-ledger

Use the shared decisions ledger correctly from any task — read pins, add a finding, run the compressed interview, record a decision with flip_criteria, and never let an agent commit a decision the human did not elect. The spine both codebase-rescue and greenfield-forge run on.

0 Updated 3 days ago
r3vs