New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Continuity Ledger

by parcadei in parcadei/Continuous-Claude-v3

Create or update continuity ledger for state preservation across clears

MITAuto-check passed

Install Continuity Ledger

skills CLI
$ npx skills add parcadei/Continuous-Claude-v3 --skill continuity-ledger -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install parcadei/Continuous-Claude-v3 continuity-ledger --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/parcadei/Continuous-Claude-v3.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/continuity_ledger .claude/skills/continuity-ledger && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
continuity-ledger
GitHub stars
3.9k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
321 words
Files
1
Skills in repo
141
Repo updated
First seen
Licence
MIT

At a glance

Create or update continuity ledger for state preservation across clears

  • Works in 4 steps: Filepath & Metadata → Write YAML handoff (~400 tokens) → Mark Session Outcome (REQUIRED) → …
  • SKILL.md covers Process, When to Use, When NOT to Use and Why Clear Instead of Compact?
  • Calls git and uv

What it does

Continuity Ledger is an agent skill from parcadei/Continuous-Claude-v3. Create or update continuity ledger for state preservation across clears

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Context management for Claude Code. Hooks maintain state via ledgers and handoffs. MCP execution without context pollution. Agent orchestration with isolated context windows. The licence is MIT.

Example prompts

  • “/continuity-ledger”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Filepath & Metadata
  2. Write YAML handoff (~400 tokens)
  3. Mark Session Outcome (REQUIRED)
  4. Confirm completion

What it can do on your machine

Read from SKILL.md and the folder at commit d07ff4b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Continuity Ledger loads about 1.1k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 321 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from parcadei/Continuous-Claude-v3 at commit d07ff4b, republished under its MIT licence (© parcadei). 321 words, ~1,070 tokens.

Download SKILL.mdSave it as .claude/skills/continuity-ledger/SKILL.md (or your agent's skills folder).
name
continuity-ledger
description
Create or update continuity ledger for state preservation across clears

Continuity Ledger

Note: This skill is now an alias for /create_handoff. Both output the same YAML format.

Create a YAML handoff document for state preservation across /clear. This is the same as /create_handoff.

Process

1. Filepath & Metadata

First, determine the session name from existing handoffs:

bash
ls -td thoughts/shared/handoffs/*/ 2>/dev/null | head -1 | xargs basename

This returns the most recently modified handoff folder name (e.g., open-source-release). Use this as the handoff folder name.

If no handoffs exist, use general as the folder name.

Create your file under: thoughts/shared/handoffs/{session-name}/YYYY-MM-DD_HH-MM_description.yaml, where:

  • {session-name} is from existing handoffs (e.g., open-source-release) or general if none exist
  • YYYY-MM-DD is today's date
  • HH-MM is the current time in 24-hour format (no seconds needed)
  • description is a brief kebab-case description

Examples:

  • thoughts/shared/handoffs/open-source-release/2026-01-08_16-30_memory-system-fix.yaml
  • thoughts/shared/handoffs/general/2026-01-08_16-30_bug-investigation.yaml
2. Write YAML handoff (~400 tokens)

CRITICAL: Use EXACTLY this YAML format. Do NOT deviate or use alternative field names.

The goal: and now: fields are shown in the statusline - they MUST be named exactly this.

yaml
---
session: {session-name from ledger}
date: YYYY-MM-DD
status: complete|partial|blocked
outcome: SUCCEEDED|PARTIAL_PLUS|PARTIAL_MINUS|FAILED
---

goal: {What this session accomplished - shown in statusline}
now: {What next session should do first - shown in statusline}
test: {Command to verify this work, e.g., pytest tests/test_foo.py}

done_this_session:
  - task: {First completed task}
    files: [{file1.py}, {file2.py}]
  - task: {Second completed task}
    files: [{file3.py}]

blockers: [{any blocking issues}]

questions: [{unresolved questions for next session}]

decisions:
  - {decision_name}: {rationale}

findings:
  - {key_finding}: {details}

worked: [{approaches that worked}]
failed: [{approaches that failed and why}]

next:
  - {First next step}
  - {Second next step}

files:
  created: [{new files}]
  modified: [{changed files}]

Field guide:

  • goal: + now: - REQUIRED, shown in statusline
  • done_this_session: - What was accomplished with file references
  • decisions: - Important choices and rationale
  • findings: - Key learnings
  • worked: / failed: - What to repeat vs avoid
  • next: - Action items for next session

DO NOT use alternative field names like session_goal, objective, focus, current, etc. The statusline parser looks for EXACTLY goal: and now: - nothing else works.

3. Mark Session Outcome (REQUIRED)

IMPORTANT: Before responding to the user, you MUST ask about the session outcome.

Use the AskUserQuestion tool with these exact options:

Question: "How did this session go?"
Options:
  - SUCCEEDED: Task completed successfully
  - PARTIAL_PLUS: Mostly done, minor issues remain
  - PARTIAL_MINUS: Some progress, major issues remain
  - FAILED: Task abandoned or blocked

After the user responds, mark the outcome:

bash
# Mark the most recent handoff (works with PostgreSQL or SQLite)
PROJECT_ROOT=$(git rev-parse --show-toplevel 2>/dev/null || echo "${CLAUDE_PROJECT_DIR:-.}")
cd "$PROJECT_ROOT/opc" && uv run python scripts/core/artifact_mark.py --latest --outcome <USER_CHOICE>
4. Confirm completion

After marking the outcome, respond to the user:

Handoff created! Outcome marked as [OUTCOME].

Resume in a new session with:
/resume_handoff path/to/handoff.yaml

When to Use

  • Before running /clear
  • Context usage approaching 70%+
  • Multi-day implementations
  • Complex refactors you pick up/put down
  • Any session expected to hit 85%+ context

When NOT to Use

  • Quick tasks (< 30 min)
  • Simple bug fixes
  • Single-file changes

Why Clear Instead of Compact?

Each compaction is lossy compression—after several compactions, you're working with degraded context. Clearing + loading the handoff gives you fresh context with full signal.

© parcadei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/continuity_ledger of parcadei/Continuous-Claude-v3.

Open the folder on GitHubat commit d07ff4b

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in parcadei/Continuous-Claude-v3, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Continuity Ledger next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Continuity Ledger compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Continuity Ledger this skillparcadei/Continuous-Claude-v33.9k1 repos~1.1kAutomated safety check: PassMIT
Continuetelegramdesktop/tdesktop33k2 repos~9.4kAutomated safety check: PassGPL-3.0
Continuous Learningaffaan-m/ECC275k—~1.1kAutomated safety check: PassMIT
Continuous Learningaffaan-m/ECC275k—~1.2kAutomated safety check: PassMIT
Recursive Decision Ledgeraffaan-m/ECC275k1 repos~701Automated safety check: PassMIT
Continueudecode/plate17k—~2.6kAutomated safety check: PassCustom licence

Similar skills

  • Continue

    telegramdesktop/tdesktop

    Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.

    33k GitHub starsUsed in 2 repos~9.4k tokens
    Productivity & AutomationAuto-check passed

  • Continuous Learning

    affaan-m/ECC

    [DEPRECATED - use continuous-learning-v2] Legacy v1 stop-hook skill extractor.

    275k GitHub stars~1.1k tokensUpdated 3 days ago
    Auto-check passed

  • Continuous Learning

    affaan-m/ECC

    [OBSOLETO - usar continuous-learning-v2] Extractor de skill por hook Stop v1 heredado.

    275k GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

  • Recursive Decision Ledger

    affaan-m/ECC

    Run repeated rollouts ("Prime Gauss" style recursive prompting) while keeping an append-only decision ledger of trials, marks, coherence checks, and promotion gates, so recursive confidence never…

    275k GitHub starsUsed in 1 repo~701 tokens
    Business, Finance & HRAuto-check passed

  • Continue

    udecode/plate

    Use after an execution slice to reassess whether the current tactic still serves the user's north star, then keep course, pivot, replan, or stop.

    17k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Continue PR

    ClickHouse/ClickHouse

    Continue work on an existing PR - resolve conflicts, fix CI failures, address reviewer feedback, and push updates.

    50k GitHub stars~5.5k tokensUpdated today
    DevelopmentAuto-check: notes

More from parcadei/Continuous-Claude-v3

All 141 skills in this repo

  • Tldr Deep

    parcadei/Continuous-Claude-v3

    Full 5-layer analysis of a specific function. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 2 repos~677 tokens
    Auto-check passed

  • Compound Learnings

    parcadei/Continuous-Claude-v3

    Transform session learnings into permanent capabilities (skills, rules, agents).

    3.9k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check: notes

  • Gradient Methods

    parcadei/Continuous-Claude-v3

    Problem-solving strategies for gradient methods in optimization

    3.9k GitHub starsUsed in 3 repos~1k tokens
    Auto-check: notes

  • Debug Hooks

    parcadei/Continuous-Claude-v3

    Systematic hook debugging workflow. An agent skill from parcadei/Continuous-Claude-v3.

    3.9k GitHub starsUsed in 1 repo~863 tokens
    Auto-check: notes

  • Math

    parcadei/Continuous-Claude-v3

    Unified math capabilities - computation, solving, and explanation.

    3.9k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check: notes

  • Math Model Selector

    parcadei/Continuous-Claude-v3

    Routes problems to appropriate mathematical frameworks using expert heuristics

    3.9k GitHub starsUsed in 3 repos~841 tokens
    Auto-check passed

Questions about Continuity Ledger

What does Continuity Ledger do?

Create or update continuity ledger for state preservation across clears. Continuity Ledger is an agent skill from parcadei/Continuous-Claude-v3.

How do I install Continuity Ledger in Claude Code?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill continuity-ledger -a claude-code`. Or copy the skill folder (.claude/skills/continuity_ledger in parcadei/Continuous-Claude-v3) into .claude/skills/continuity-ledger in your project. Claude Code loads it when a task matches its description.

How do I install Continuity Ledger in Codex?

Run `npx skills add parcadei/Continuous-Claude-v3 --skill continuity-ledger -a codex`. Or copy the skill folder (.claude/skills/continuity_ledger in parcadei/Continuous-Claude-v3) into .agents/skills/continuity-ledger in your project. Codex loads it when a task matches its description.

Can I use Continuity Ledger in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add parcadei/Continuous-Claude-v3 --skill continuity-ledger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/continuity-ledger, .gemini/skills/continuity-ledger, .github/skills/continuity-ledger and .opencode/skills/continuity-ledger in your project.

What does Continuity Ledger need to run?

Going by SKILL.md and its folder, Continuity Ledger needs the command-line tools its instructions call (git and uv). Our summary lists: Python 3.

Does Continuity Ledger access the network?

SKILL.md contains no URLs. Its commands use git and uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Continuity Ledger safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Continuity Ledger use?

Continuity Ledger is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Continuity Ledger use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Continuity Ledger?

Skills that share tags, products or a category with Continuity Ledger: Continue (telegramdesktop/tdesktop, 33k stars), Continuous Learning (affaan-m/ECC, 275k stars), Continuous Learning (affaan-m/ECC, 275k stars) and Recursive Decision Ledger (affaan-m/ECC, 275k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Continuity Ledger?

parcadei (a GitHub user) maintains it in parcadei/Continuous-Claude-v3, which has 3,940 GitHub stars. The repository holds 141 skills in this directory. The repository was last updated on January 26, 2026.

Source: parcadei/Continuous-Claude-v3 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.