Source profileQuality 54/100
nexu-io/open-design/plugins/_official/atoms/todo-write/SKILL.md
todo-write
TodoWrite-driven plan that the agent commits to before generation.
- Source repository stars
- 82,073
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Before writing any artifact files, the agent commits to a numbered plan via the TodoWrite tool. The plan is the audit trail; subsequent turns either tick items off or rewrite the plan. The atom's prompt fragment teaches the agent to:
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
Source-detected install commandSource
npx skills add https://github.com/nexu-io/open-design --skill "plugins/_official/atoms/todo-write"Safe inspection promptEditorial
Inspect the Agent Skill "todo-write" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/plugins/_official/atoms/todo-write/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
The source does not provide enough structured workflow evidence for a step-by-step guide.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
EvidenceSourceComputedTestedEditorial
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 54/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 82,073 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- nexu-io/open-design
- Skill path
- plugins/_official/atoms/todo-write/SKILL.md
- Commit
- 89d6d4ef21baf80f871595abdf6f7de6e941dd44
- License
- Apache-2.0
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
Todo write
Before writing any artifact files, the agent commits to a numbered plan via the TodoWrite tool. The plan is the audit trail; subsequent turns either tick items off or rewrite the plan. The atom's prompt fragment teaches the agent to:
- Keep todos atomic (one verb per todo).
- Reorder freely as the picture sharpens.
- Mark a todo complete only after the matching artifact lands.
- Surface blockers as todos — never silently skip.
The Open Design daemon does not enforce a particular tool name; the agent is free to use TodoWrite (Claude Code) or an in-prompt list. The atom's job is to keep "make a plan first" in the system prompt so non-trivial workflows don't skip the planning step.