What makes Daily Workflow notable?

1.3K downloads. Trust evidence available

How should Daily Workflow be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Daily Workflow

Preserve evidence-backed project memory

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.3k

Updated

Oct 10, 2026

Version

4.1.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.3K downloadsadoption · observed Oct 10, 2026
Latest release: 4.1.0release · observed Sep 7, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s1712yyvmw7t8z7nqxpz1ydfad8540a4:daily-workflow

Install using `clawhub skill install s1712yyvmw7t8z7nqxpz1ydfad8540a4:daily-workflow` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/englandtong/daily-workflow before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-englandtong-daily-workflow/snapshot"

Documentation

CLAWHUB

78,129 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: daily-workflow
description: Say 开工啦 or 收工啦 and get a resumable project note written for you, so tomorrow you or another AI can pick up without re-reading everything. Use when a user asks to resume a project, save progress, record a checkpoint, end a work session, prepare a handoff, switch to a new AI session, or reconcile stale working notes. Typical triggers include 开工啦, 中段检查, 吃饭啦, 收工啦, 交接, 记一下进度, 存个档, 明天接着做, 换个 AI 继续, 上下文快满了, start work, checkpoint, wrap up, handoff, save progress, resume tomorrow, and switch to a new agent session. Reads existing project authority first, preserves dirty worktrees and governance evidence, avoids competing state files, archives rather than deletes history, and records commands, final outcomes, blockers, risks, and exact next actions without claiming unverified completion or QA acceptance.
---

# Daily Workflow / 项目记忆工作流

Version: 4.1.0

Use this skill to make work resumable. Record only the compact factual state needed by the user or next agent; do not turn project memory into a second project-management system.

Respond in the user's language. Keep machine-readable status values in English.

## Scope And Ownership

This skill owns session continuity only: orientation, checkpoint summaries, wrap-up records, and handoffs.

- `cms-project-governance` owns formal targets, Programs, Work Orders, Controller/QA decisions, and acceptance state.
- `agent-loop-engineering` owns active coding-loop evidence, stop gates, evaluation, and loop records.
- `project-lifecycle-navigator` owns lifecycle analysis and rebaseline proposals.
- `web-search-rules` owns research intake and source rules.
- `ai-workflow-os` may route here but must not create a parallel memory state.

When another system already owns a field, read and summarize it; do not overwrite it.

## Trigger And Authorization

Use this skill when the user explicitly asks to:

- start or resume work;
- save progress or create a checkpoint;
- wrap up or end work;
- prepare a handoff;
- reconcile or migrate workflow notes.

Common phrases include `开工啦`, `中段检查`, `吃饭啦`, `收工啦`, `交接`, `start work`, `checkpoint`, `wrap up`, and `handoff`.

A casual mention of one phrase is not enough when intent is ambiguous. Inspect read-only first. Persist files only when the request clearly asks to initialize or update project memory, or when an established project workflow already defines the trigger as a write command.

## Read-Only Orientation First

Before writing:

1. resolve the actual workspace and repository root, including nested repositories;
2. inspect Git branch, commit, and dirty state without modifying it;
3. locate governing files and determine current authority precedence;
4. locate product scope, entrypoints, build/test commands, and runtime surfaces relevant to the session;
5. read existing memory files and compatible aliases;
6. identify contradictions, missing evidence, and ownership conflicts.

Do not use `git reset`, `git clean`, broad deletion, or ambiguous

_meta.json

{
  "ownerId": "kn7bjt2sd8f7cq83y0nf33xt19855gv6",
  "slug": "daily-workflow",
  "version": "4.1.0",
  "publishedAt": 1788800774694
}

QUICKSTART.md

# Quickstart / 快速开始

## Install / 安装

```bash
openclaw skills install daily-workflow
```

or / 或

```bash
clawhub install daily-workflow
```

## Try it in 30 seconds / 30 秒验证

Say this to your agent at the end of a work session / 收工时对 agent 说：

```text
收工啦
```

You should get / 你应该得到：

- `Docs/STATUS.md` — current state, latest verification, next action;
- `Docs/NEXT_ACTIONS.md` — the immediate next step, then what follows,
  blockers and Owner decisions;
- a one-line summary of what was written.

Open those two files. That is the entire output — no dashboard, no database.

## Four phrases are enough / 四句话就够

| Say | What happens |
| --- | --- |
| `开工啦` | read existing state, orient for the session |
| `中段检查` | mid-session checkpoint |
| `收工啦` | wrap up, record exact next actions |
| `交接` | package a handoff for another person or another AI |

The point is resumability: tomorrow you, or a fresh AI session, can pick up
without re-reading the whole project.

## Minimum useful path / 最小可用路径

Just use `开工啦` and `收工啦`.

You do **not** need `Docs/PROJECT.md`, `TARGET.md`, `COMPLETED.md` or
`PENDING.md`. Those belong to the governance profile and only appear if your
project already runs one. The default lightweight profile writes two files.

## Privacy and safety / 隐私与安全

- Runs locally. Writes plain Markdown into your project's own `Docs/`.
- Stores no API keys, tokens, passwords or credentials.
- Never deletes history — superseded entries are archived, not removed.
- Read-only orientation first: nothing is written until intent is clear.
- Will not claim work is complete or QA-accepted without evidence.

## Next / 下一步

Full record structure and memory profiles: `SKILL.md`.

SECURITY.md

# Daily Workflow / 项目记忆工作流 - Security Guide

Version: 4.1.0

## Security Statement / 安全说明

This skill may write project-local workflow notes when the user explicitly requests persistence or an established trigger authorizes it. It is designed for resumability and handoff, not for storing secrets, replacing project governance, or recording confidential source bodies.

本 Skill 只应在项目本地 `Docs/` 中写入工作流笔记，用于恢复上下文和交接，不用于保存密钥、账号凭证或完整敏感资料。

## Allowed Storage / 允许写入范围

Default allowed write scope when no project-owned workflow defines a narrower location:

```text
Docs/
```

Do not write global user state. Do not write outside `Docs/` unless the user explicitly asks as part of the broader task.

Before writing, resolve the actual workspace and repository, preserve dirty changes, identify existing governance ownership, and avoid creating competing state files.

## Sensitive Data Rules / 敏感信息规则

Never record:

- API keys, tokens, passwords, private keys, cookies, OAuth refresh tokens, browser sessions.
- `.env` values or credential files.
- Full private customer records.
- Long confidential source excerpts.
- Large unrelated logs.

If sensitive context is relevant, record a safe summary and the non-secret location where the user can find the source.

## Legacy Migration Safety / 旧版迁移安全

Legacy files may be read for migration, but must not be deleted automatically. If both old and new files exist, ask before merging. Do not migrate secret-like fields.

## Archive Safety / 归档安全

Archiving older status history is allowed only by moving content into `Docs/archive/`. Never delete history automatically.

## Release Checklist / 发布检查

- `SKILL.md` and `SECURITY.md` show version `4.1.0`; generated registry snapshots are excluded from the publish bundle.
- The package uses one bilingual skill, not separate English and Chinese packages.
- Legacy file migration is documented.
- `NEXT_ACTIONS.md` is the primary continuation file, with `SCHEDULE.md` treated as compatibility alias.
- Existing project/governance files remain authoritative; the lightweight profile starts with only `STATUS.md` and `NEXT_ACTIONS.md`.
- Completion, verification, and independent acceptance remain separate.
- No example contains real credentials or private data.

skill-card.md

## Description:

Daily Workflow helps agents create evidence-backed project checkpoints, wrap-ups, and handoffs so work can resume without re-reading the whole project.

This skill is ready for commercial/non-commercial use.

## Publisher:

[englandtong](https://clawhub.ai/user/englandtong)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and agent users use this skill to preserve concise project memory at start, checkpoint, wrap-up, and handoff moments. It writes project-local Markdown notes that capture current state, verification evidence, blockers, risks, and exact next actions without replacing existing governance records.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: Checkpoint or handoff notes can contain sensitive project context if shared outside the project.

Mitigation: Review generated Docs/ notes before sharing and avoid recording secrets, credentials, full confidential data, or large private logs.

Risk: Project memory files can conflict with existing governance or acceptance records.

Mitigation: Read existing project authority first, preserve dirty worktrees and governance evidence, and summarize externally owned fields instead of overwriting them.

## Reference(s):

- [ClawHub Skill Page](https://clawhub.ai/englandtong/skills/daily-workflow)
- [Quickstart](artifact/QUICKSTART.md)
- [Security Guide](artifact/SECURITY.md)

## Skill Output:

**Output Type(s):** [Markdown, Files, Guidance]

**Output Format:** [Markdown files and concise user-facing summaries]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Writes project-local workflow notes, normally under Docs/, when persistence is clearly authorized.]

## Skill Version(s):

4.1.0 (source: server release metadata and artifact SKILL.md)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.