Agent skill

Do

by srid in srid/emanote

Do a task end-to-end — implement, PR, CI loop, ship. An agent skill from srid/emanote.

Custom licenceAuto-check passedTesting & QA

Install Do

skills CLI
$ npx skills add srid/emanote --skill do -a claude-code

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

GitHub CLI
$ gh skill install srid/emanote do --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/srid/emanote.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/do .claude/skills/do && 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
do
GitHub stars
963
Token cost
~12k tokens
SKILL.md length
6,645 words
Files
4 (incl. scripts)
Skills in repo
25
Repo updated
First seen
Licence
Custom licence

At a glance

Do a task end-to-end — implement, PR, CI loop, ship. An agent skill from srid/emanote.

  • Works in 5 steps: Apply the fix narrowly — only the lines… → Run the project's format command (from… → git add — stage only the files this fix… → …
  • Explicitly types /do
  • SKILL.md covers Arguments, Results Tracking, Progress tracking and Steps, plus 2 more sections
  • Calls git, gh and tsc; reaches github.com and kolu.dev

What it does

Do is an agent skill from srid/emanote. Do a task end-to-end — implement, PR, CI loop, ship. ONLY invoke when the user explicitly types /do or $do; never auto-select from a natural-language request, even one that sounds like an end-to-end task.

Its SKILL.md is about 12k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts.

It sits in Testing & QA, covering End-to-end testing. It works with Git. The repository describes itself as: Emanate a structured view of your plain-text notes.

When your agent uses it

  • Explicitly types /do
  • Never auto-select from a natural-language request
  • Even one that sounds like an end-to-end task

Example prompts

  • “/do”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Apply the fix narrowly — only the lines that address this specific finding.
  2. Run the project's format command (from fmt instructions) on the changed files, if one is configured.
  3. git add — stage only the files this fix touched.
  4. git commit -m "refactor(hickey): " (or refactor(lowy): … depending on the lens). The body of the message should restate the finding in one…
  5. git push — push after each commit so the draft PR (once created) accumulates commits in real time. (The -u flag is only needed on the…

What it can do on your machine

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

    Ships 3 files in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • git
    • gh
    • tsc
    • cargo
    • nix
    • just
    • make

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com
    • kolu.dev

    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

Do loads about 12k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 6,645 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 6,645 words (~11,868 tokens).

“Take a task and do it top-to-bottom: research, branch, implement, pass CI, open a PR, and ship. (Under --no-git, extend the working tree in place — no branch, commit, or PR.)”

— opening of SKILL.md by srid, Custom licence
name
do
argument-hint
<issue-url | prompt> [--review] [--no-git] [--minimal] [--from <step>]

Read the full SKILL.md on GitHub

Files

SKILL.md and 3 other files (scripts) in .agents/skills/do of srid/emanote.

  • SKILL.md
  • scripts/do-results
  • scripts/steps/done
  • scripts/steps/sync

Open the folder on GitHubat commit 9d01037

Compare with similar skills

Do 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.

Do compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Do this skillsrid/emanote963—~12kAutomated safety check: PassCustom licence
Releaselycorp-jp/sim-use1.4k—~1.7kAutomated safety check: PassApache-2.0
Code That Fits In Your HeadCodeAlive-AI/ai-driven-development155—~1.7kAutomated safety check: PassMIT
OpenHarness End-to-End EvalsHKUDS/OpenHarness16k1 repos~2.1kAutomated safety check: NotesMIT
Nemoclaw Maintainer Fix E2E FailuresNVIDIA/NemoClaw23k—~2.6kAutomated safety check: PassApache-2.0
Diff-Driven Smoke TestsSkyvern-AI/skyvern23k—~5.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Release

    lycorp-jp/sim-use

    Cut a sim-use release end-to-end. An agent skill from lycorp-jp/sim-use.

    1.4k GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Code That Fits In Your Head

    CodeAlive-AI/ai-driven-development

    Software-engineering heuristics based on Mark Seemann's Code That Fits in Your Head (2021), updated for agent-driven development.

    155 GitHub stars~1.7k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.

    16k GitHub starsUsed in 1 repo~2.1k tokens
    Testing & QAAuto-check: notes
  • Official

    Continuously maintain automatic NemoClaw main E2E results through coordinated repairs.

    23k GitHub stars~2.6k tokensUpdated today
    Testing & QAAuto-check passed
  • Diff-Driven Smoke Tests

    Skyvern-AI/skyvern

    Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.

    23k GitHub stars~5.2k tokensUpdated today
    Testing & QAAuto-check passed
  • Test Pyramid

    kubernetes-sigs/agent-sandbox

    Official

    Analyze the repo's unit and E2E tests and propose rebalancing toward a test pyramid — which E2E tests (or assertions inside them) can be covered by unit tests, which unit-level gaps genuinely need…

    4.2k GitHub stars~1.6k tokensUpdated today
    Testing & QAAuto-check passed

More from srid/emanote

All 25 skills in this repo
  • Codex Debate

    srid/emanote

    Run an automated codex⇄Claude debate to consensus — no round cap, no deadlock exit.

    963 GitHub stars~8.9k tokensUpdated 2 mo ago
    Auto-check passed
  • Be Review

    srid/emanote

    Run /be's review gauntlet SERIALLY — /lens-debate (lowy ⇄ hickey), then /codex-debate, then /simplify, then code-police, each editing and committing on the live branch in turn.

    963 GitHub stars~4.2k tokensUpdated 2 mo ago
    Auto-check passed
  • CI

    srid/emanote

    Reference for the odu runner — how to invoke a full pipeline, a single recipe, or a platform-pinned node, and how to attach to a live run, from a project whose CI odu runs.

    963 GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed
  • Forge PR

    srid/emanote

    Write engaging PR titles and descriptions for any forge (GitHub today; Bitbucket planned).

    963 GitHub stars~2.6k tokensUpdated 2 mo ago
    Auto-check passed
  • Kolu

    srid/emanote

    Drive one AI agent from another through kolu's terminals: spawn a Claude Code / Codex / opencode session in a PTY, prompt it, watch the screen for its reply, read it, and prompt again — a…

    963 GitHub stars~2.4k tokensUpdated 2 mo ago
    Auto-check passed
  • Lens Debate

    srid/emanote

    Run a structural-review debate between two lenses — lowy (volatility-based decomposition) and hickey (structural simplicity) — on the current diff.

    963 GitHub stars~3.7k tokensUpdated 2 mo ago
    Auto-check passed

Works with

Questions about Do

What does Do do?

Do a task end-to-end — implement, PR, CI loop, ship. An agent skill from srid/emanote. Do is an agent skill from srid/emanote. Do a task end-to-end — implement, PR, CI loop, ship.

When should I use Do?

Do fits situations like: explicitly types /do; never auto-select from a natural-language request; even one that sounds like an end-to-end task.

How do I install Do in Claude Code?

Run `npx skills add srid/emanote --skill do -a claude-code`. Or copy the skill folder (.agents/skills/do in srid/emanote) into .claude/skills/do in your project. Claude Code loads it when a task matches its description.

How do I install Do in Codex?

Run `npx skills add srid/emanote --skill do -a codex`. Or copy the skill folder (.agents/skills/do in srid/emanote) into .agents/skills/do in your project. Codex loads it when a task matches its description.

Can I use Do 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 srid/emanote --skill do -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/do, .gemini/skills/do, .github/skills/do and .opencode/skills/do in your project.

What does Do need to run?

Going by SKILL.md and its folder, Do needs the command-line tools its instructions call (git, gh, tsc, cargo, nix and just).

Does Do access the network?

SKILL.md names 2 domains. In commands or code: github.com and kolu.dev; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Do 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Do use?

Do has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Do use?

About 12k tokens (SKILL.md is roughly 47k 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 Do?

Skills that share tags, products or a category with Do: Release (lycorp-jp/sim-use, 1.4k stars), Code That Fits In Your Head (CodeAlive-AI/ai-driven-development, 155 stars), OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars) and Nemoclaw Maintainer Fix E2E Failures (NVIDIA/NemoClaw, 23k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Do?

srid (a GitHub user) maintains it in srid/emanote, which has 963 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on July 26, 2026.

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