Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action.
MITAuto-check passed
Install Continue Claude Code Work
$ npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install daymade/claude-code-skills continue-claude-code-work --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/daymade-claude-code/continue-claude-code-work .claude/skills/continue-claude-code-work && rm -rf skills-srcUse ~/.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/
Install the "continue-claude-code-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-claude-code-work into .claude/skills/continue-claude-code-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-claude-code-work", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-claude-code-workType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install daymade/claude-code-skills continue-claude-code-work --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/daymade-claude-code/continue-claude-code-work .agents/skills/continue-claude-code-work && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "continue-claude-code-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-claude-code-work into .agents/skills/continue-claude-code-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-claude-code-work", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install daymade/claude-code-skills continue-claude-code-work --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/daymade-claude-code/continue-claude-code-work .cursor/skills/continue-claude-code-work && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "continue-claude-code-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-claude-code-work into .cursor/skills/continue-claude-code-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-claude-code-work", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/daymade/claude-code-skills.git --path daymade-claude-code/continue-claude-code-work--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install daymade/claude-code-skills continue-claude-code-work --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/daymade-claude-code/continue-claude-code-work .gemini/skills/continue-claude-code-work && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "continue-claude-code-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-claude-code-work into .gemini/skills/continue-claude-code-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-claude-code-work", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install daymade/claude-code-skills continue-claude-code-workInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/daymade-claude-code/continue-claude-code-work .github/skills/continue-claude-code-work && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "continue-claude-code-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-claude-code-work into .github/skills/continue-claude-code-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-claude-code-work", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install daymade/claude-code-skills continue-claude-code-work --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/daymade/claude-code-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/daymade-claude-code/continue-claude-code-work .opencode/skills/continue-claude-code-work && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "continue-claude-code-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-claude-code-work into .opencode/skills/continue-claude-code-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-claude-code-work", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
continue-claude-code-work- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 516 words
- Files
- 1
- Skills in repo
- 102
- Repo updated
- First seen
- Licence
- MIT
At a glance
Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action.
- Works in 5 steps: Obtain a verified read receipt → Rebuild the continuation contract → Reconcile with current reality → …
- Given a Claude Code Session ID
- SKILL.md covers Step 1: Obtain a verified read…, Step 2: Rebuild the…, Step 3: Reconcile with current… and Step 4: Execute the business…, plus 1 more section
- Calls claude
What it does
Continue Claude Code Work is an agent skill from daymade/claude-code-skills. Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without claude --resume. Not for Codex sessions (use continue-codex-work).
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: Professional Claude Code skills marketplace featuring production-ready skills for enhanced development workflows. The licence is MIT.
When your agent uses it
- Given a Claude Code Session ID
- Asked to pick up prior Claude work
- Told a run was interrupted
- Asked to take over without claude --resume
Example prompts
- “Use the continue-claude-code-work skill to continue interrupted Claude Code work after local history is read and reconciled — reconstructs the…”
- “/continue-claude-code-work”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 3c268d6. 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:
claude
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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
Continue Claude Code Work loads about 1.1k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 516 words of instructions outside code blocks.
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 daymade/claude-code-skills at commit 3c268d6, republished under its MIT licence (© daymade). 516 words, ~1,051 tokens.
Download SKILL.mdSave it as
.claude/skills/continue-claude-code-work/SKILL.md (or your agent's skills folder).- name
- continue-claude-code-work
- description
- Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Use when given a Claude Code Session ID, asked to pick up prior Claude work, told a run was interrupted or compacted, or asked to take over without `claude --resume`. Not for Codex sessions (use continue-codex-work).
- argument-hint
- [session-id]
Continue Claude Code Work
Continue means execute the still-unfinished business task. It does not mean summarize the transcript, perfect the history tool, or start a new experiment.
Step 1: Obtain a verified read receipt
Invoke daymade-claude-code:read-claude-code-history for the exact Session. Ask
that Skill for a chronological evidence briefing, not separate “last user” and
“last assistant” buckets. If the Session ID is unknown, use its search/inventory
route first.
Do not act until the receipt states:
- exact Session ID and project;
- sources and time coverage;
- compaction and raw-chronology boundaries;
- every retained human request, including queued prompts;
- end reason, unresolved calls, files touched, and explicit gaps.
If a clipped section could contain the objective or a correction, re-read it with the reader's full mode. If identity, ancestry, or authorship is unresolved, stop; continuing from a guessed Session is worse than asking for the missing evidence.
Step 2: Rebuild the continuation contract
Before the first project-changing tool call, write this compact internal contract from evidence. Do not invent a value to fill a blank.
| Field | Evidence required |
|---|---|
| Original business outcome | Earliest still-governing human request, not a later implementation detail |
| Current explicit request | Latest human request that is not merely “继续” |
| Already completed | Independent current-state verification, not the old Agent's claim |
| Still unfulfilled | Requested result with no completion evidence |
| User corrections / do-not-repeat | Human messages that rejected a route, output, or assumption |
| Proven assets and successful routes | Existing code, docs, Skills, outputs, or commands that previously worked |
| Next direct action | One action whose success visibly reduces the unfulfilled business result |
When the latest message is only “继续,” inherit the objective from the verified chronology. Never treat the cue itself as the specification.
Show full SKILL.md (240 more words)Show less
Step 3: Reconcile with current reality
- Read the target project's current
AGENTS.md/CLAUDE.mdand authoritative project state; historical instructions may be stale. - Confirm the current cwd, branch, working tree, and relevant files.
- Verify whether prior writes, commits, external operations, or background jobs actually landed. A transcript records attempts as well as successes.
- Retrieve the proven asset or prior successful path before authoring a replacement.
- If another process may still complete the same transiently failed work, verify its current result before duplicating it.
Step 4: Execute the business task
Take the next direct action from the contract and verify its result. Skill edits, review expansion, documentation systems, and infrastructure cleanup remain subordinate unless the user explicitly made one of them the business outcome or they are strictly required to unblock it.
Before changing direction, ask mechanically: “If this succeeds, which original unfulfilled result becomes smaller?” If the answer is none, record it as a later proposal and return to the task.
Do not run claude --resume or claude --continue. Do not overwrite unrelated
working-tree changes.
Step 5: Report against the contract
- Recovered goal: Session and original business outcome.
- Executed: actions and independent verification.
- Now complete: contract rows that are actually closed.
- Remaining: unfulfilled rows and exact blockers.
- Not repeated: prior rejected routes deliberately avoided when relevant.
Do not say “continued successfully” when only context extraction or a process step completed; the business result is the completion unit.
© daymade, 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 daymade-claude-code/continue-claude-code-work of daymade/claude-code-skills.
Open the folder on GitHubat commit 3c268d6
Compare with similar skills
Continue Claude Code Work 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Continue Claude Code Work this skilldaymade/claude-code-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Continuetelegramdesktop/tdesktop | 33k | 2 repos | ~9.4k | Automated safety check: Pass | GPL-3.0 | |
| Continuous Learningaffaan-m/ECC | 274k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Continuous Learningaffaan-m/ECC | 274k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Continuityparcadei/Continuous-Claude-v3 | 3.9k | 1 repos | ~292 | Automated safety check: Notes | MIT | |
| Continueudecode/plate | 17k | — | ~2.6k | Automated safety check: Pass | Custom licence |
Similar skills
Continuous Learning
affaan-m/ECC
[DEPRECATED - use continuous-learning-v2] Legacy v1 stop-hook skill extractor.
Continuous Learning
affaan-m/ECC
[OBSOLETO - usar continuous-learning-v2] Extractor de skill por hook Stop v1 heredado.
Continuity
parcadei/Continuous-Claude-v3
Problem-solving strategies for continuity in real analysis. An agent skill from parcadei/Continuous-Claude-v3.
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.
Continuous Learning
affaan-m/ECC
自动从Claude Code会话中提取可重复使用的模式，并将其保存为学习到的技能以供将来使用. An agent skill from affaan-m/ECC.
More from daymade/claude-code-skills
All 102 skills in this repoVideo Comparer
daymade/claude-code-skills
This skill should be used when comparing two videos to analyze compression results or quality differences.
CLI Demo Generator
daymade/claude-code-skills
Generates professional animated CLI demos as GIFs using VHS terminal recordings.
Doc To Markdown
daymade/claude-code-skills
Converts DOCX/PDF/PPTX and saved HTML/HTM to high-quality Markdown with automatic post-processing.
Interaction Design Board
daymade/claude-code-skills
Generates several distinct, clickable HTML interaction prototypes for one product surface into a Design Board and collects selection/remix feedback before implementation.
Auto Repo Setup
daymade/claude-code-skills
Diagnoses and repairs repository setup and guarded Git workflows for Claude Code or Codex — environment repair, startup sync, hook auditing, collaborator handoff.
Bigdata Skill
daymade/claude-code-skills
Pulls Bigdata.com (RavenPack) financial and news data via the official bigdata-client SDK and /v1/ REST endpoints — structured financials, prices, analyst estimates, entity-sentiment series…
Questions about Continue Claude Code Work
What does Continue Claude Code Work do?
Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action. Continue Claude Code Work is an agent skill from daymade/claude-code-skills. Continues interrupted Claude Code work after local history is read and reconciled — reconstructs the original outcome, unfulfilled requests, and the next action.
When should I use Continue Claude Code Work?
Continue Claude Code Work fits situations like: given a Claude Code Session ID; asked to pick up prior Claude work; told a run was interrupted; asked to take over without claude --resume.
How do I install Continue Claude Code Work in Claude Code?
Run `npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a claude-code`. Or copy the skill folder (daymade-claude-code/continue-claude-code-work in daymade/claude-code-skills) into .claude/skills/continue-claude-code-work in your project. Claude Code loads it when a task matches its description.
How do I install Continue Claude Code Work in Codex?
Run `npx skills add daymade/claude-code-skills --skill continue-claude-code-work -a codex`. Or copy the skill folder (daymade-claude-code/continue-claude-code-work in daymade/claude-code-skills) into .agents/skills/continue-claude-code-work in your project. Codex loads it when a task matches its description.
Can I use Continue Claude Code Work 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 daymade/claude-code-skills --skill continue-claude-code-work -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/continue-claude-code-work, .gemini/skills/continue-claude-code-work, .github/skills/continue-claude-code-work and .opencode/skills/continue-claude-code-work in your project.
What does Continue Claude Code Work need to run?
Going by SKILL.md and its folder, Continue Claude Code Work needs the command-line tools its instructions call (claude).
Does Continue Claude Code Work access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Continue Claude Code Work 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 Continue Claude Code Work use?
Continue Claude Code Work 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 Continue Claude Code Work use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 Continue Claude Code Work?
Skills that share tags, products or a category with Continue Claude Code Work: Continue (telegramdesktop/tdesktop, 33k stars), Continuous Learning (affaan-m/ECC, 274k stars), Continuous Learning (affaan-m/ECC, 274k stars) and Continuity (parcadei/Continuous-Claude-v3, 3.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Continue Claude Code Work?
daymade (a GitHub user) maintains it in daymade/claude-code-skills, which has 1,443 GitHub stars. The repository holds 102 skills in this directory. The repository was last updated on October 7, 2026.
Source: daymade/claude-code-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.