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

daily-done每日完成

Agent Skill

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

总安装

303

周安装

13

GitHub Stars

2

下载量

106
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/benjaming/ai-skills --skill daily-done

简介

daily-done 标记今日任务文件中的已完成项,并显示剩余工作量概览。

  • 适用于配合 Jira 或其他任务系统使用的日常进度管理工具,强化闭环意识。
  • 可通过任务 ID、Jira key 或序号指定目标,灵活适应不同用户的引用习惯。
  • 依赖 ~/.claude/daily-tasks/ 目录下的 JSON 格式任务文件,格式错误将导致解析失败。
  • 若无今日任务文件,则直接返回提示并终止流程,避免误判或空操作。

SKILL.md

Done — Complete Current Task

Mark a task as completed in today's task file and show remaining work.

Configuration

persistence:
  tasksDir: "~/.claude/daily-tasks"

Execution Steps

1. Load Task File

Read today's task file:

cat ~/.claude/daily-tasks/$(date +%Y-%m-%d).json 2>/dev/null

If no file exists: "No task file for today. Nothing to mark as done." Stop here.

Parse the JSON.

2. Identify Task to Complete

If $ARGUMENTS is a number: target that task ID.

If $ARGUMENTS matches a Jira key pattern (e.g., RGI-265): find the task with matching jira_key.

If $ARGUMENTS is empty: find the task with status: "in_progress".

  • If multiple tasks are in_progress, list them and ask which one to complete.
  • If no task is in_progress: "No task currently in progress. Specify a task ID: /daily-done 3"
  • Stop here if unable to identify a single task.

Validation:

  • If the selected task has status: "done": "Task #N is already done."
  • If the selected task ID doesn't exist: "Task #N not found. Today has tasks 1-M."
  • If the selected task has status: "pending" (never started): Mark as done anyway, but note: "Task #N was never started — marking as done directly."
  • If the selected task has status: "standby": Warn but proceed: "⚠️ Task #N is on standby (waiting on: {waiting_on}). Marking as done anyway."

3. Mark as Done

Read the current task file, update the target task:

  • Set status to "done"
  • Set completed_at to current ISO timestamp (use date -u +%Y-%m-%dT%H:%M:%SZ)
  • Set waiting_on to null and paused_at to null (clean up any standby fields)
  • Update updated_at on the root object

Write the updated JSON back using the Write tool.

4. Show Completion Summary

Display:

✅ Task #N done: $JIRA_KEY — $SUMMARY

If started_at exists, calculate and show duration:

   ⏱️  Duration: Xh Ym

Show overall progress:

📋 Progress: N/M tasks done today

5. Show Next Task

List remaining actionable tasks (pending or in_progress only — exclude standby):

Remaining:
  #N. [TIER] $JIRA_KEY — $SUMMARY
  #N. [TIER] $JIRA_KEY — $SUMMARY

If any standby tasks exist, add a note:

⏸ N task(s) on standby — run /daily-unblock to activate when ready

Suggest the next task:

👉 Next up: Task #N ($JIRA_KEY) — $SUMMARY
   Run /daily-next to pick it up, or /daily-next M for a different task.

6. All Done State

If no pending or in-progress tasks remain (standby tasks don't count):

🎉 All tasks for today are done!

📋 Final: M/M complete
⏱️  Total tracked time: Xh Ym (sum of all tasks with started_at and completed_at)

Consider:
  - Running /daily-standup to refresh and check for new items
  - Checking Jira backlog for new work

Edge Cases

  • Multiple in_progress tasks, no argument: List all in-progress tasks with IDs and ask which to complete. Do not guess.
  • Task is skipped: Allow marking as done — change status from skipped to done.
  • Task is standby: Warn about standby state but allow marking as done. Clear waiting_on and paused_at.
  • File write fails: Report error, do not silently lose the update.
  • Concurrent modification: Read-then-write is sufficient for single-user workflow. If the file was modified between read and write, the latest write wins.

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.66%
按下载量换算36

Claude

29.6%
按下载量换算31

Cursor

18.64%
按下载量换算20

Gemini CLI

9.6%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

权限需确认

当前来源未能明确判断权限范围,默认进入异常复核队列。

安装前确认

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

来源信息

继续浏览同类 Skills