Continue
telegramdesktop/tdesktop
Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.
Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage — restores the original outcome, unfulfilled requests, and the next action.
MITAuto-check passed
Install Continue Codex Work
$ npx skills add daymade/claude-code-skills --skill continue-codex-work -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install daymade/claude-code-skills continue-codex-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-codex-work .claude/skills/continue-codex-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-codex-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-codex-work into .claude/skills/continue-codex-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-codex-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-codex-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-codex-work -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install daymade/claude-code-skills continue-codex-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-codex-work .agents/skills/continue-codex-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-codex-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-codex-work into .agents/skills/continue-codex-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-codex-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-codex-work -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install daymade/claude-code-skills continue-codex-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-codex-work .cursor/skills/continue-codex-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-codex-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-codex-work into .cursor/skills/continue-codex-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-codex-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-codex-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-codex-work -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install daymade/claude-code-skills continue-codex-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-codex-work .gemini/skills/continue-codex-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-codex-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-codex-work into .gemini/skills/continue-codex-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-codex-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-codex-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-codex-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-codex-work .github/skills/continue-codex-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-codex-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-codex-work into .github/skills/continue-codex-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-codex-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-codex-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-codex-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-codex-work .opencode/skills/continue-codex-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-codex-work" agent skill from https://github.com/daymade/claude-code-skills/tree/main/daymade-claude-code/continue-codex-work into .opencode/skills/continue-codex-work/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "continue-codex-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-codex-work- GitHub stars
- 1.4k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 844 words
- Files
- 2 (incl. references)
- Skills in repo
- 103
- Repo updated
- First seen
- Licence
- MIT
At a glance
Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage — restores the original outcome, unfulfilled requests, and the next action.
- Works in 5 steps: Obtain a verified Codex read receipt → Rebuild the continuation contract → Reconcile with current reality → …
- Given a Codex Session ID
- SKILL.md covers Entry gate: external takeover,…, Step 1: Obtain a verified…, Step 2: Rebuild the… and Step 3: Reconcile with current…, plus 2 more sections
- Calls codex
What it does
Continue Codex Work is an agent skill from daymade/claude-code-skills. Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage — restores the original outcome, unfulfilled requests, and the next action. Use when given a Codex Session ID, asked to pick up a prior Codex run, told Codex was interrupted, fused, compacted or stuck, or asked to take over without codex resume. Not for a conversation Codex already natively resumed.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/native-goal-reconciliation.md`).
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 Codex Session ID
- Asked to pick up a prior Codex run
- Told Codex was interrupted
- Asked to take over without codex resume
Example prompts
- “Use the continue-codex-work skill to continue interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction…”
- “/continue-codex-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 91bed2b. 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:
codex
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 Codex Work loads about 1.7k tokens when it runs, and up to ~2.4k if it reads all its reference files. Until then it costs about 110 tokens; SKILL.md has 844 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 91bed2b, republished under its MIT licence (© daymade). 844 words, ~1,662 tokens.
Download SKILL.mdSave it as
.claude/skills/continue-codex-work/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- continue-codex-work
- description
- Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage — restores the original outcome, unfulfilled requests, and the next action. Use when given a Codex Session ID, asked to pick up a prior Codex run, told Codex was interrupted, fused, compacted or stuck, or asked to take over without `codex resume`. Not for a conversation Codex already natively resumed.
- argument-hint
- [session-id]
Continue Codex Work
Continue means finish the still-unfulfilled business task. Reading history is a mandatory evidence phase, not the deliverable.
Entry gate: external takeover, not native resume
| Current situation | Action |
|---|---|
| Codex itself natively resumed this same conversation, and the restored turns or compaction state are already in the current context | Do not invoke this Skill or read-codex-history. Continue directly from the retained context, then verify current workspace and external state before changing anything. |
| A new/different Agent context must take over an earlier Codex rollout, or the user identifies another Session ID whose continuity is not already present here | Use this Skill. Step 1's verified history receipt remains mandatory. |
A restart is not enough to choose the second row. The deciding fact is whether the current conversation is the host-restored continuation of the same Session, not whether a Codex process was restarted.
Step 1: Obtain a verified Codex read receipt
Invoke daymade-claude-code:read-codex-history for the exact Session ID and request
the full chronological Session evidence briefing. If the ID is unknown, use that
Skill's inventory or bounded search first.
The receipt must state:
- prompt-ledger, state-index, and rollout sources used;
- selected
session_meta.idand whether it exactly matches the requested ID; - root-to-child fork lineage and exact inherited byte boundaries;
- selected and inherited chronological user/assistant turns;
- compacted context, latest plan, end reason, unresolved calls, files, and gaps.
Fail closed on a mismatched rollout, missing child rollout, ambiguous physical copy, missing parent, broken byte boundary, or continuation cue with no recoverable parent objective. Never continue from the “closest” file.
Step 2: Rebuild the continuation contract
Before the first project-changing tool call, fill this internal contract from the read receipt and current-state verification:
| Field | Evidence required |
|---|---|
| Original business outcome | Earliest still-governing human request across inherited and selected timelines |
| Current explicit request | Latest human request that is not only a continuation cue |
| Current delivery stage / non-goals | Latest human correction narrowing what to deliver now and what to defer; do not promote the original long-term ambition back above it |
| Already completed | Current independent verification, not old Agent narration |
| Still unfulfilled | Requested result without completion evidence |
| User corrections / do-not-repeat | Human messages rejecting a route, assumption, or output |
| Proven assets and successful routes | Existing code, documents, Skills, outputs, commands, and prior successful experiments |
| Next direct action | One action whose success visibly reduces the unfulfilled business result |
If the child contains only “继续,” “continue,” or /fork, inherit the task from the
verified parent snapshot. A local cue is not a standalone goal.
Show full SKILL.md (434 more words)Show less
Step 3: Reconcile with current reality
- Read the current target project's
AGENTS.md/CLAUDE.md. - Confirm cwd, branch, working tree, relevant files, and external state.
- Verify that recorded patches, commits, pushes, downloads, jobs, or Agent outputs actually landed; rollouts record attempted actions too.
- Retrieve and reuse prior successful assets before creating a replacement.
- For transient failures such as usage limits or service errors, verify whether the original process later resumed and finished before duplicating work. For an existing native Goal, use Native Goal reconciliation to distinguish unfinished business, runtime status, supported recovery and observed automatic continuation. An absent recovery tool in one tool menu is not proof that the live host has no recovery control.
- Check what was in flight when the session died. A foreground long task
(remote diagnostic, download, build) dies with its session, and its unpersisted
output dies with the pipe — the rollout records that the task started, never its
result. Treat such a result as not done: probe whether the remote process or its
output file survived, and before re-running, give the rerun a detached
result-to-disk channel (e.g. remote
( cmd > log 2>&1 </dev/null; echo $? > rc ) &polled through the rc file — prefersetsid/nohupwhere the target has them, since a pty-backed session can still SIGHUP a bare subshell) so the next interruption cannot take the result again.
Step 4: Execute the business task
Perform the next direct action and close its feedback loop. Reviews, Skill work, infrastructure cleanup, format polish, and extra safety machinery remain subordinate unless they directly unblock the original result or the user explicitly promoted them.
Before every material branch, ask: “If this succeeds, which unfulfilled result in the current authorized stage becomes smaller?” No answer means the branch is not continuation work. A blocked source, login or provider route blocks only dependent work; execute other necessary authorized work before declaring the whole task blocked.
Verify the result at the user's consumption surface: searchable bytes alone do not prove a readable page, and generated suggestions do not prove saved human decisions. Reuse passed checks for unchanged inputs; expand verification only for new changes, failures or unresolved evidence gaps.
Do not run codex resume or codex --continue. Do not overwrite unrelated changes.
Step 5: Report against the contract
- Recovered goal: exact Session lineage and original business outcome.
- Executed: actions and independent verification.
- Now complete: contract rows actually closed.
- Remaining: unresolved rows and exact blockers.
- Not repeated: relevant rejected routes deliberately avoided.
Context recovery, parser success, a green review, or a finished subprocess is not by itself successful continuation. The user's 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
SKILL.md and 1 other file (references) in daymade-claude-code/continue-codex-work of daymade/claude-code-skills.
- SKILL.md
- references/native-goal-reconciliation.md
Open the folder on GitHubat commit 91bed2b
Compare with similar skills
Continue Codex 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 Codex Work this skilldaymade/claude-code-skills | 1.4k | — | ~1.7k | Automated safety check: Pass | MIT | |
| Continuetelegramdesktop/tdesktop | 33k | 2 repos | ~9.4k | Automated safety check: Pass | GPL-3.0 | |
| Continuous Learningaffaan-m/ECC | 275k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Continuous Learningaffaan-m/ECC | 275k | — | ~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.
Continue PR
ClickHouse/ClickHouse
Continue work on an existing PR - resolve conflicts, fix CI failures, address reviewer feedback, and push updates.
More from daymade/claude-code-skills
All 103 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 Codex Work
What does Continue Codex Work do?
Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage — restores the original outcome, unfulfilled requests, and the next action. Continue Codex Work is an agent skill from daymade/claude-code-skills. Continues interrupted Codex work only after read-codex-history verifies rollout identity and fork/compaction lineage — restores the original outcome, unfulfilled requests, and the next action.
When should I use Continue Codex Work?
Continue Codex Work fits situations like: given a Codex Session ID; asked to pick up a prior Codex run; told Codex was interrupted; asked to take over without codex resume.
How do I install Continue Codex Work in Claude Code?
Run `npx skills add daymade/claude-code-skills --skill continue-codex-work -a claude-code`. Or copy the skill folder (daymade-claude-code/continue-codex-work in daymade/claude-code-skills) into .claude/skills/continue-codex-work in your project. Claude Code loads it when a task matches its description.
How do I install Continue Codex Work in Codex?
Run `npx skills add daymade/claude-code-skills --skill continue-codex-work -a codex`. Or copy the skill folder (daymade-claude-code/continue-codex-work in daymade/claude-code-skills) into .agents/skills/continue-codex-work in your project. Codex loads it when a task matches its description.
Can I use Continue Codex 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-codex-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-codex-work, .gemini/skills/continue-codex-work, .github/skills/continue-codex-work and .opencode/skills/continue-codex-work in your project.
What does Continue Codex Work need to run?
Going by SKILL.md and its folder, Continue Codex Work needs the command-line tools its instructions call (codex).
Does Continue Codex 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 Codex 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 Codex Work use?
Continue Codex 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 Codex Work use?
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 747 tokens, read only when the agent opens those files.
What are the alternatives to Continue Codex Work?
Skills that share tags, products or a category with Continue Codex Work: Continue (telegramdesktop/tdesktop, 33k stars), Continuous Learning (affaan-m/ECC, 275k stars), Continuous Learning (affaan-m/ECC, 275k 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 Codex Work?
daymade (a GitHub user) maintains it in daymade/claude-code-skills, which has 1,444 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 8, 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.