Markdown Article Formatter
JimLiu/baoyu-skills
Reformats plain text or Markdown articles with frontmatter, a title, a summary, headings, bold, lists and code blocks, and saves a separate formatted copy.
Convert a selected Markdown plan into clear, dependency-ordered Markdown todos.
Install Write Todos
$ npx skills add HazAT/pi-config --skill write-todos -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HazAT/pi-config write-todos --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/write-todos .claude/skills/write-todos && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "write-todos" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/write-todos into .claude/skills/write-todos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-todos", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/HazAT/pi-config/tree/main/skills/write-todosType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add HazAT/pi-config --skill write-todos -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HazAT/pi-config write-todos --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/write-todos .agents/skills/write-todos && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "write-todos" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/write-todos into .agents/skills/write-todos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-todos", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HazAT/pi-config --skill write-todos -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HazAT/pi-config write-todos --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/write-todos .cursor/skills/write-todos && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "write-todos" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/write-todos into .cursor/skills/write-todos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-todos", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/HazAT/pi-config.git --path skills/write-todos--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add HazAT/pi-config --skill write-todos -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HazAT/pi-config write-todos --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/write-todos .gemini/skills/write-todos && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "write-todos" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/write-todos into .gemini/skills/write-todos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-todos", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install HazAT/pi-config write-todosInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add HazAT/pi-config --skill write-todos -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/write-todos .github/skills/write-todos && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "write-todos" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/write-todos into .github/skills/write-todos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-todos", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add HazAT/pi-config --skill write-todos -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HazAT/pi-config write-todos --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/write-todos .opencode/skills/write-todos && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "write-todos" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/write-todos into .opencode/skills/write-todos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "write-todos", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
write-todos- GitHub stars
- 451
- Token cost
- ~530 tokens
- SKILL.md length
- 149 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Convert a selected Markdown plan into clear, dependency-ordered Markdown todos.
- Breaking plans into tasks
- SKILL.md covers Rules and File Format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Updating execution status from coordinator evidence
What it does
Write Todos is an agent skill from HazAT/pi-config. Convert a selected Markdown plan into clear, dependency-ordered Markdown todos. Use for /todos, breaking plans into tasks, or updating execution status from coordinator evidence.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Documents & Office. The repository describes itself as: My personal pi coding agent configuration - skills and extensions. The licence is MIT.
When your agent uses it
- Breaking plans into tasks
- Updating execution status from coordinator evidence
Example prompts
- “/write-todos”
What it can do on your machine
Read from SKILL.md and the folder at commit 655acd4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Write Todos loads about 530 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 149 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from HazAT/pi-config at commit 655acd4, republished under its MIT licence (© HazAT). 149 words, ~530 tokens.
Download SKILL.mdSave it as
.claude/skills/write-todos/SKILL.md (or your agent's skills folder).- name
- write-todos
- description
- Convert a selected Markdown plan into clear, dependency-ordered Markdown todos. Use for /todos, breaking plans into tasks, or updating execution status from coordinator evidence.
Write Todos
Read the absolute plan path supplied by the caller. Write only the supplied todos path; do not implement work or launch agents.
Rules
- Preserve the plan's architecture, scope, exclusions, and acceptance criteria.
- Use stable sequential IDs (
TODO-001,TODO-002, ...). When updating an existing file, preserve IDs and completed evidence. - Make each source-writing todo fit one focused worker and one commit.
- Source-writing todos must be dependency ordered because workers share one checkout and run sequentially.
- Repeat the constraints a worker needs; do not make it infer critical intent.
- Name target files, useful source references, objective checks, and plausible wrong approaches.
- Only the coordinator updates status, owner, commit, verification, and result fields. Delegated agents read this file but never edit it.
File Format
# Execution Todos
**Status:** Pending | In Progress | Complete | Blocked
**Plan:** `/absolute/path/to/session.plan.md`
**Updated:** [ISO-8601 timestamp]
## TODO-001 — [outcome]
**Status:** Pending | In Progress | Complete | Blocked
**Depends on:** none | TODO-NNN
**Owner:** unassigned | [SC label]
**Commit:** pending | [full SHA] | n/a
### Outcome
[What this produces and why]
### Constraints
- [plan decision to preserve]
- [explicit non-goal or wrong approach]
### Files and References
- `path/to/file` — [expected change]
- `path/to/example:line` — [pattern to follow]
### Acceptance Criteria
- [ ] [observable result tied to a plan criterion]
- [ ] `[verification command]` passes
- [ ] One focused commit contains only this todo's changes and is not pushed
### Verification
- Pending
### Result
- PendingUse Blocked with an objective reason. Mark the top-level status Complete only when every required todo is complete with verified commit/result evidence (or an explicitly justified n/a).
© HazAT, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/write-todos of HazAT/pi-config.
Open the folder on GitHubat commit 655acd4
Compare with similar skills
Write Todos next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Write Todos this skillHazAT/pi-config | 451 | — | ~530 | Automated safety check: Pass | MIT | |
| Markdown Article FormatterJimLiu/baoyu-skills | 26k | 7 repos | ~3.5k | Automated safety check: Pass | MIT | |
| MarkitdownImCa0/just-laws | 781 | 14 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Obsidian MarkdownAtmosphere/atmosphere | 3.8k | 20 repos | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| DOCXrvdbreemen/OTGW-firmware | 207 | 33 repos | ~4.3k | Automated safety check: Pass | Proprietary | |
| Gzh Designisjiamu/gzh-design-skill | 3.9k | 1 repos | ~2.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
Markitdown
ImCa0/just-laws
Convert files and office documents to Markdown. An agent skill from ImCa0/just-laws.
Obsidian Markdown
Atmosphere/atmosphere
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax.
DOCX
rvdbreemen/OTGW-firmware
A skill your agent uses whenever the user wants to create, read, edit, or manipulate Word documents (.docx files).
Gzh Design
isjiamu/gzh-design-skill
微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown…
Word Document Reader and Writer
HKUDS/DeepTutor
Reads, creates and edits Word .docx files with python-docx, and drops to raw OOXML for tracked changes, comments and byte-exact edits.
More from HazAT/pi-config
All 10 skills in this repoSession Reader
HazAT/pi-config
Efficiently read and analyze pi agent session JSONL files. An agent skill from HazAT/pi-config.
Pi Extension Development
HazAT/pi-config
Defines the local standard for standalone Pi extension repositories.
Superconductor
HazAT/pi-config
Operates the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads.
Plan
HazAT/pi-config
Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path.
Review
HazAT/pi-config
Coordinate a model-diverse local code review, automatically repair actionable findings with sequential workers, and re-review to a final verdict.
Setup Superconductor Project
HazAT/pi-config
Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts.
Related
Categories
Questions about Write Todos
What does Write Todos do?
Convert a selected Markdown plan into clear, dependency-ordered Markdown todos. Write Todos is an agent skill from HazAT/pi-config. Convert a selected Markdown plan into clear, dependency-ordered Markdown todos.
When should I use Write Todos?
Write Todos fits situations like: breaking plans into tasks; updating execution status from coordinator evidence.
How do I install Write Todos in Claude Code?
Run `npx skills add HazAT/pi-config --skill write-todos -a claude-code`. Or copy the skill folder (skills/write-todos in HazAT/pi-config) into .claude/skills/write-todos in your project. Claude Code loads it when a task matches its description.
How do I install Write Todos in Codex?
Run `npx skills add HazAT/pi-config --skill write-todos -a codex`. Or copy the skill folder (skills/write-todos in HazAT/pi-config) into .agents/skills/write-todos in your project. Codex loads it when a task matches its description.
Can I use Write Todos in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add HazAT/pi-config --skill write-todos -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/write-todos, .gemini/skills/write-todos, .github/skills/write-todos and .opencode/skills/write-todos in your project.
What does Write Todos need to run?
SKILL.md names no scripts, command-line tools or credentials: Write Todos is instructions for the agent only.
Does Write Todos access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Write Todos safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Write Todos use?
Write Todos is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Write Todos use?
About 530 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Write Todos?
Skills that share tags, products or a category with Write Todos: Markdown Article Formatter (JimLiu/baoyu-skills, 26k stars), Markitdown (ImCa0/just-laws, 781 stars), Obsidian Markdown (Atmosphere/atmosphere, 3.8k stars) and DOCX (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Write Todos?
HazAT (a GitHub user) maintains it in HazAT/pi-config, which has 451 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on August 25, 2026.
Source: HazAT/pi-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.