Agent skill

Todos To GitHub Project

by rome-os in rome-os/rome

Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies.

MITAuto-check passed

Install Todos To GitHub Project

skills CLI
$ npx skills add rome-os/rome --skill todos-to-github-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install rome-os/rome todos-to-github-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/rome-os/rome.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/todos-to-github-project .claude/skills/todos-to-github-project && rm -rf skills-src

Use ~/.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/

Facts

Skill name
todos-to-github-project
GitHub stars
737
Token cost
~1k tokens
SKILL.md length
551 words
Files
1
Skills in repo
18
Repo updated
First seen
Licence
MIT

At a glance

Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies.

  • Works in 5 steps: Harvest → Draft → Approve → …
  • SKILL.md covers 1. Harvest, 2. Draft, 3. Approve and 4. Create, plus 1 more section
  • Calls gh

What it does

Todos To GitHub Project is an agent skill from rome-os/rome. Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub. The repository describes itself as: A compounding agent OS for recursive agents. Also an open source alternative to Grok Bot and Meta's Muse. The licence is MIT.

Example prompts

  • “/todos-to-github-project”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Harvest
  2. Draft
  3. Approve
  4. Create
  5. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit f187f45. 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

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Todos To GitHub Project loads about 1k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 551 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~40
When it runs · the whole SKILL.md, loaded when a task matches
~1k

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 rome-os/rome at commit f187f45, republished under its MIT licence (© rome-os). 551 words, ~1,017 tokens.

Download SKILL.mdSave it as .claude/skills/todos-to-github-project/SKILL.md (or your agent's skills folder).
name
todos-to-github-project
description
Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies.
disable-model-invocation
true

Todos to GitHub project

Goal end-state: every remaining todo of the conversation is one task-spec issue, the issues sit in one GitHub project, every dependency is a blocked-by edge on GitHub, and each in-scope issue carries ready-for-agent.

The issue format — title, body sections, the ready-for-agent bar — is defined in docs/authoring/github-issues.md and docs/authoring/github-issues-task-spec.md. Prose in titles and bodies follows docs/authoring/WRITING.md. This skill covers what to file, in which order, and with which gh calls.

1. Harvest

  1. Collect every remaining todo from the conversation: open task-list items, deferred follow-ups, and work the user parked for later.
  2. Search the tracker for each todo with gh issue list --search "<keywords>". If an existing issue already tracks it, drop the todo from the set.
  3. Write one sentence per todo stating the outcome its issue must deliver. If the sentence only makes sense with the conversation open, ask the user what the todo means.

2. Draft

  1. Name the project after the outcome the set delivers, not after the conversation.
  2. Split the todos into in-scope and out-of-scope. An out-of-scope todo files under its issue type with the type label, stays out of the project, and never carries ready-for-agent.
  3. Draft each in-scope issue as a task spec in the github-issues-task-spec.md format, title included.
  4. Wire the dependencies. Issue X is blocked by issue Y when X cannot start before Y merges. Record each edge as a Blocked by line in X's body.
  5. Check the edge graph for cycles. A cycle is a decomposition error — re-split the todos until the graph is acyclic.
  6. Apply the label bar from github-issues-task-spec.md: every in-scope issue gets task, and an issue implementable from its body alone also gets ready-for-agent. An issue still waiting on a user decision files without ready-for-agent.

3. Approve

The draft stays out of chat. Ask for the go-ahead in one line — the project title and the issue count — and write nothing to GitHub before the user gives it. Present issue titles or bodies only when the user asks to see them.

Show full SKILL.md (219 more words)Show less

4. Create

If gh label list does not show task or ready-for-agent, create the missing label with gh label create.

  1. Resolve the repo and owner: gh repo view --json nameWithOwner.

  2. Create the project: gh project create --owner <owner> --title "<title>".

  3. Link the project to the repo so it shows up under the repo's Projects tab: gh project link <project-number> --owner <owner> --repo <owner>/<repo>.

  4. Create the issues in dependency order, blockers first, so every Blocked by line names a real issue number: gh issue create --title "<title>" --body "<body>" --label task --label ready-for-agent. Drop ready-for-agent where step 2.6 withheld it.

  5. Add each in-scope issue to the project: gh project item-add <project-number> --owner <owner> --url <issue-url>.

  6. Mirror every edge into GitHub's native relation. The issue_id is the blocking issue's numeric REST id (gh api repos/<owner>/<repo>/issues/<number> --jq .id), not its issue number:

    bash
    gh api -X POST repos/<owner>/<repo>/issues/<blocked-number>/dependencies/blocked_by -F issue_id=<blocking-id>

5. Verify

  1. Confirm the link with gh repo view --json projectsV2. The new project must appear in the list.
  2. List the project items with gh project item-list <project-number> --owner <owner>. The count must match the in-scope set.
  3. Read back each issue's edges with gh api repos/<owner>/<repo>/issues/<number>/dependencies/blocked_by. Every drafted edge must appear.
  4. Report the project URL and each issue number with its blockers.

© rome-os, 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 .claude/skills/todos-to-github-project of rome-os/rome.

Open the folder on GitHubat commit f187f45

Compare with similar skills

Todos To GitHub Project 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.

Todos To GitHub Project compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Todos To GitHub Project this skillrome-os/rome737—~1kAutomated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Diagnosing Superpowers Sessionsobra/superpowers297k3 repos~1.7kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    297k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed
  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes

More from rome-os/rome

All 18 skills in this repo
  • Color Audit

    rome-os/rome

    Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…

    737 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • Audit the subordinate copy in a UI — section descriptions, field helper text, hints, card subtitles, empty-state body copy, tooltip bodies — against the secondary-text ruleset, and emit a per-string…

    737 GitHub stars~2.8k tokensUpdated today
    Auto-check passed
  • UX Semantics Audit

    rome-os/rome

    Audit an existing UI/UX design (React/JSX/TSX components, HTML, or generated app code) against a tiered ruleset of verifiable UX principles, and produce structured, evidence-cited findings that a…

    737 GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Add a new Rome-managed OAuth integration for a third-party service so a user can delegate access by clicking Connect, and Rome can act on the service with the delegated token (the GitHub/Slack model…

    737 GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Composio CLI

    rome-os/rome

    Help users operate the published Composio CLI to find the right tool, connect accounts, inspect schemas, execute tools, subscribe to trigger events with composio listen, script workflows with…

    737 GitHub stars~2.7k tokensUpdated today
    Auto-check passed
  • File Issue

    rome-os/rome

    File one GitHub issue from a description the user gives — classify it as a bug report, feature request, or task spec, gather what the body needs from the tracker and the code, ask the user only for…

    737 GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Questions about Todos To GitHub Project

What does Todos To GitHub Project do?

Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies. Todos To GitHub Project is an agent skill from rome-os/rome. Turn the remaining todos of the current conversation into a GitHub project of task-spec issues wired with native blocked-by dependencies.

How do I install Todos To GitHub Project in Claude Code?

Run `npx skills add rome-os/rome --skill todos-to-github-project -a claude-code`. Or copy the skill folder (.claude/skills/todos-to-github-project in rome-os/rome) into .claude/skills/todos-to-github-project in your project. Claude Code loads it when a task matches its description.

How do I install Todos To GitHub Project in Codex?

Run `npx skills add rome-os/rome --skill todos-to-github-project -a codex`. Or copy the skill folder (.claude/skills/todos-to-github-project in rome-os/rome) into .agents/skills/todos-to-github-project in your project. Codex loads it when a task matches its description.

Can I use Todos To GitHub Project 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 rome-os/rome --skill todos-to-github-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/todos-to-github-project, .gemini/skills/todos-to-github-project, .github/skills/todos-to-github-project and .opencode/skills/todos-to-github-project in your project.

What does Todos To GitHub Project need to run?

Going by SKILL.md and its folder, Todos To GitHub Project needs the command-line tools its instructions call (gh).

Does Todos To GitHub Project access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Todos To GitHub Project 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 Todos To GitHub Project use?

Todos To GitHub Project 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 Todos To GitHub Project use?

About 1k tokens (SKILL.md is roughly 4.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 Todos To GitHub Project?

Skills that share tags, products or a category with Todos To GitHub Project: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 297k stars), Greploop (onyx-dot-app/onyx, 32k stars) and GitHub Deep Research (bytedance/deer-flow, 84k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Todos To GitHub Project?

rome-os (a GitHub organization) maintains it in rome-os/rome, which has 737 GitHub stars. The repository holds 18 skills in this directory. The repository was last updated on October 9, 2026.

Source: rome-os/rome on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.