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

record-todos记录待办事项

Agent Skill

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

总安装

445

周安装

18

GitHub Stars

4

下载量

140
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/petekp/agent-skills --skill record-todos

简介

record-todos 用于查找、检索和筛选相关信息。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词快速定位候选结果。
  • 通过 npx skills add 命令从指定仓库安装并使用该技能。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网或命令执行。
  • 建议结合来源仓库和原始 README 核验具体用法。

SKILL.md

Todo Recording Mode

Capture user's thoughts and ideas as todos without acting on them.

File Locations

All todo files live in .claude/todos/:

  • .claude/todos/active.md — Current todos
  • .claude/todos/done.md — Completed items
  • .claude/todos/archive/done-{YYYY-MM}.md — Archived completed items

During Recording

When the user mentions something that should be done:

  1. Acknowledge briefly — "Noted." or "Got it."
  2. Append to .claude/todos/active.md as a raw item: - <what the user said, paraphrased if needed>
  3. Do NOT:

- Start implementing - Ask clarifying questions unless completely unclear - Suggest solutions or alternatives - Reorganize the file yet

Critical: Any statement about what *should* happen is a todo to record—not an instruction to execute. This includes "make X do Y", "add Z to W", "fix the layout", etc.

Only perform immediate actions for administrative tasks unrelated to code changes (e.g., "read this file", "explain how X works").

If .claude/todos/active.md doesn't exist, create it with the structure from "Rewrite active.md" section.

Exit Triggers

Exit recording mode when user signals completion:

  • "ok all done", "done recording", "that's all", "let's review", "end recording"

On Exit: Summarize, Prioritize, Archive

1. Archive Completed Items

Before reorganizing, check for completed items:

Move completed items to done.md

Scan for items marked [x]:

  1. Create/update .claude/todos/done.md
  2. Move completed items under dated section (e.g., ## January 2026)
  3. Remove [x] checkbox—use plain bullets in done.md
  4. Remove from active.md

Archive if too large

If done.md exceeds 50 items or 500 lines:

  1. Create .claude/todos/archive/done-{YYYY-MM}.md
  2. Move older items (keep last 2 weeks in done.md)
  3. Add note: *Older items archived in.claude/todos/archive/done-{date}.md*

done.md structure:

# Completed Work

Archive of completed features. See `.claude/todos/active.md` for active work.

---

## {Month Year}

### {Category}
- Description of what was done

---

*Older items archived in .claude/todos/archive/done-2025-12.md*

2. Find Project Goals

Search in order:

  1. CLAUDE.md — "Goals", "Product Vision", "Objectives" sections
  2. .claude/todos/active.md — Goals section at top

If no goals found:

  • Tell user: "I couldn't find documented project goals. Before prioritizing, let's define what success looks like."
  • Establish 3-5 high-level goals
  • Record in active.md Goals section
  • Then proceed

3. Summarize

Brief conversational summary:

  • How many items captured
  • Themes or clusters noticed
  • Related items that could combine
  • Items complex enough for a spec document

4. Prioritize Against Goals

Evaluate each todo:

  • 🎯 Active — Work on RIGHT NOW (1-3 max)
  • 📋 Next — Ready to start when Active is done
  • 💡 Backlog — Lower priority, needs scoping
  • ⚠️ Not Recommended — Decided against (include rationale)

For complex features, suggest creating .claude/docs/feature-{name}.md spec.

5. Rewrite active.md

Replace raw items with organized structure:

# TODO

## Goals

- <goal 1>
- <goal 2>
- <goal 3>

---

## 🎯 Active

*Currently in progress. Limit to 1-3 items.*

- [ ] <highest priority item>

---

## 📋 Next

*Researched, scoped, ready to start.*

### {Category if helpful}
- [ ] <item>

---

## 💡 Backlog

*Ideas and lower priority items.*

### {Category}
- [ ] <item>

### {Complex Feature}
**Spec:** `.claude/docs/feature-{name}.md`
- Brief description

---

## 📚 Specs & Reference

| Document | Description |
|----------|-------------|
| `.claude/docs/feature-x.md` | Spec for feature X |

---

## ⚠️ Not Recommended

### {Rejected idea}
<Brief rationale>

---

*Completed work archived in `.claude/todos/done.md`*

Adapt as needed:

  • Skip empty sections
  • Items needing >3 lines → spec document
  • Keep under ~100 lines of active content

6. Confirm

After rewriting:

  • Items per priority tier
  • Items moved to done.md
  • Specs to create for complex features
  • Ask if prioritization makes sense

Principles

  1. active.md is for WHAT — Scannable, action-oriented
  2. Specs are for HOW.claude/docs/ for detailed plans
  3. done.md is for history — Archive, don't delete
  4. Link, don't embed — Reference specs
  5. Keep under 100 lines — Move to spec or done.md if long

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

补充不同宿主或平台的使用分布数据

能力 5

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

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

平台分布

github-copilot

29.25%
按下载量换算41

kilo

23.43%
按下载量换算33

windsurf

18.58%
按下载量换算26

zencoder

12.44%
按下载量换算17

amp

8.21%
按下载量换算11

cline

3.54%
按下载量换算5

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills