Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

recoverrecover 搜索

Agent Skill

recover 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

780

周安装

34

GitHub Stars

6

下载量

280
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:recover(recover 搜索)
来源仓库:https://github.com/duc01226/easyplatform
仓库路径:skills/recover
安装命令:
npx skills add https://github.com/duc01226/easyplatform --skill recover
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/duc01226/easyplatform --skill recover

简介

recover 在会话中断后恢复断点任务与待办清单状态。

  • 读取 checkpoint 文件还原上次中断时的执行进度。
  • 立即调用 TaskCreate 重建工作流避免重复劳动。
  • 依赖定期保存检查点否则无法有效恢复上下文。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。
  • recover 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

SKILL.md

[IMPORTANT] Use TaskCreate to break ALL work into small tasks BEFORE starting — including tasks for each file read. This prevents context loss from long files. For simple tasks, AI MUST ATTENTION ask user whether to skip.

Quick Summary

Goal: Restore workflow state and todo items from checkpoint files after context loss or session interruption.

Workflow:

  1. Find Checkpoint — Locate latest memory-checkpoint-*.md in reports directory
  2. Read Metadata — Extract JSON block with session ID, active plan, current step, pending todos
  3. Restore Todos — Immediately call TaskCreate with pending items from checkpoint
  4. Resume Workflow — Continue from the interrupted step using restored context

Key Rules:

  • Always restore TaskCreate items before resuming any work
  • Check both plans/reports/ and plan-specific report directories
  • Use timestamp to find the checkpoint closest to the interruption

Be skeptical. Apply critical thinking, sequential thinking. Every claim needs traced proof, confidence percentages (Idea should be more than 80%).

Recover Workflow Context

Restore workflow state and todo items from checkpoint files after context compaction or session loss.

Usage

Use this command when:

  • Context was compacted and you've lost track of the workflow
  • Session was interrupted and needs to resume
  • Todo items need to be restored from a checkpoint
  • The automatic recovery didn't trigger

Recovery Process

Step 1: Find Latest Checkpoint

Look for checkpoint files in the reports directory:

ls -la plans/reports/memory-checkpoint-*.md | tail -5

Or search for all recent checkpoints:

find plans -name "memory-checkpoint-*.md" -mmin -60 | head -5

Step 2: Read Checkpoint File

Read the most recent checkpoint to understand the saved state:

Read the checkpoint file at: plans/reports/memory-checkpoint-YYMMDD-HHMMSS.md

Step 3: Extract Recovery Metadata

The checkpoint file contains a JSON metadata block at the end:

{
  "sessionId": "...",
  "activePlan": "plans/YYMMDD-slug/",
  "workflowType": "feature",
  "currentStep": "cook",
  "remainingSteps": ["test", "code-review"],
  "pendingTodos": [...]
}

Step 4: Restore Todo Items

IMMEDIATELY call TaskCreate with the pending todos from the checkpoint:

[
    { "content": "[Workflow] /cook - Implement", "status": "in_progress", "activeForm": "Executing /cook" },
    { "content": "[Workflow] /test - Run tests", "status": "pending", "activeForm": "Executing /test" },
    { "content": "[Workflow] /code-review - Review code", "status": "pending", "activeForm": "Executing /code-review" }
]

Step 5: Read Active Plan (if exists)

If activePlan is set in the metadata, read the plan file:

Read: {activePlan}/plan.md

Step 6: Continue Workflow

Resume from the currentStep identified in the metadata. Execute the remaining workflow steps in order.

Recovery Checklist

  • Located most recent checkpoint file
  • Read checkpoint content
  • Extracted recovery metadata JSON
  • Restored todo items via TaskCreate
  • Read active plan (if applicable)
  • Identified current workflow step
  • Ready to continue from interrupted step

Automatic vs Manual Recovery

ScenarioRecovery TypeTrigger
Session resume after compactAutomaticpost-compact-recovery.cjs hook
New session in same directoryManualThis /recover command
Explicit user requestManualThis /recover command
No workflow state foundManualThis /recover command

Checkpoint Locations

Checkpoints are saved to different locations based on context:

  1. Active plan exists: {plan-path}/reports/memory-checkpoint-*.md
  2. No active plan: plans/reports/memory-checkpoint-*.md

Tips

  1. Check multiple locations - Plans may have their own reports directories
  2. Use timestamp - Checkpoints are timestamped, find the one closest to when you were working
  3. Verify todo status - Compare checkpoint todos with current TaskCreate state
  4. Read incrementally - Don't try to restore everything at once

Related Commands

  • /checkpoint - Create a manual checkpoint (before expected loss)
  • /compact - Manually trigger context compaction
  • /context - Load project context
  • /watzup - Generate progress summary

Example Recovery Flow

User: /recover

Claude: Let me find and restore your workflow context.

1. Finding latest checkpoint...
   Found: plans/reports/memory-checkpoint-260110-143025.md

2. Reading checkpoint metadata...
   - Workflow: feature
   - Current step: /cook
   - Remaining: /test, /code-review
   - Active plan: plans/260110-1430-new-feature/

3. Restoring TaskCreate items...
   [Calling TaskCreate with 3 pending items]

4. Reading active plan...
   [Reading plans/260110-1430-new-feature/plan.md]

5. Ready to continue from /cook step.
   Shall I proceed with the implementation?

Closing Reminders

  • IMPORTANT MUST ATTENTION break work into small todo tasks using TaskCreate BEFORE starting
  • IMPORTANT MUST ATTENTION search codebase for 3+ similar patterns before creating new code
  • IMPORTANT MUST ATTENTION cite file:line evidence for every claim (confidence >80% to act)
  • IMPORTANT MUST ATTENTION add a final review todo task to verify work quality

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.83%
按下载量换算103

Claude

26.21%
按下载量换算73

Cursor

19.81%
按下载量换算55

Gemini CLI

8.91%
按下载量换算25

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills