Vercel Composition Patterns
supabase/supabase
React composition patterns that scale. An agent skill from supabase/supabase.
Walk through a list of items (e.g. An agent skill from jackfranklin/dotfiles.
Install One By One
$ npx skills add jackfranklin/dotfiles --skill one-by-one -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jackfranklin/dotfiles one-by-one --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/jackfranklin/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/skills/one-by-one .claude/skills/one-by-one && 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 "one-by-one" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/one-by-one into .claude/skills/one-by-one/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "one-by-one", 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/jackfranklin/dotfiles/tree/master/claude/skills/one-by-oneType 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 jackfranklin/dotfiles --skill one-by-one -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jackfranklin/dotfiles one-by-one --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/claude/skills/one-by-one .agents/skills/one-by-one && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "one-by-one" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/one-by-one into .agents/skills/one-by-one/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "one-by-one", 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 jackfranklin/dotfiles --skill one-by-one -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jackfranklin/dotfiles one-by-one --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/claude/skills/one-by-one .cursor/skills/one-by-one && 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 "one-by-one" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/one-by-one into .cursor/skills/one-by-one/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "one-by-one", 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/jackfranklin/dotfiles.git --path claude/skills/one-by-one--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 jackfranklin/dotfiles --skill one-by-one -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jackfranklin/dotfiles one-by-one --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/claude/skills/one-by-one .gemini/skills/one-by-one && 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 "one-by-one" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/one-by-one into .gemini/skills/one-by-one/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "one-by-one", 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 jackfranklin/dotfiles one-by-oneInstalls 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 jackfranklin/dotfiles --skill one-by-one -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/claude/skills/one-by-one .github/skills/one-by-one && 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 "one-by-one" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/one-by-one into .github/skills/one-by-one/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "one-by-one", 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 jackfranklin/dotfiles --skill one-by-one -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jackfranklin/dotfiles one-by-one --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jackfranklin/dotfiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/claude/skills/one-by-one .opencode/skills/one-by-one && 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 "one-by-one" agent skill from https://github.com/jackfranklin/dotfiles/tree/master/claude/skills/one-by-one into .opencode/skills/one-by-one/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "one-by-one", 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
one-by-one- GitHub stars
- 255
- Token cost
- ~1.2k tokens
- SKILL.md length
- 717 words
- Files
- 1
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- MIT
At a glance
Walk through a list of items (e.g. An agent skill from jackfranklin/dotfiles.
- Works in 5 steps: Scan the recent conversation for… → Present each finding using the format… → If the user asks a follow-up or you… → …
- The user wants to work through a structured list interactively rather than scan it all at once
- SKILL.md covers Your role, Format for each finding, What to avoid and Flow
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
One By One is an agent skill from jackfranklin/dotfiles. Walk through a list of items (e.g. code review findings, design questions, open decisions) one at a time, giving full context and discussion for each before moving to the next. Use when the user wants to work through a structured list interactively rather than scan it all at once.
Its SKILL.md is about 1.2k 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 Development. The repository describes itself as: My dotfiles for my dev environment, compromising of tmux, vim, zsh and git. The licence is MIT.
When your agent uses it
- The user wants to work through a structured list interactively rather than scan it all at once
Example prompts
- “/one-by-one”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Scan the recent conversation for anything list-like: code review findings, design questions, numbered items, bulleted points, or any set…
- Present each finding using the format above and wait for a decision.
- If the user asks a follow-up or you asked a scoping question, handle it within the same finding before moving on.
- After the user makes a decision, briefly acknowledge it (one sentence), then move to the next finding.
- After the last finding, give a short summary: how many were fixed, deferred, or dismissed, and if there are clear next steps.
What it can do on your machine
Read from SKILL.md and the folder at commit 48208f5. 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.
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
One By One loads about 1.2k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 717 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 jackfranklin/dotfiles at commit 48208f5, republished under its MIT licence (© jackfranklin). 717 words, ~1,185 tokens.
Download SKILL.mdSave it as
.claude/skills/one-by-one/SKILL.md (or your agent's skills folder).- name
- one-by-one
- description
- Walk through a list of items (e.g. code review findings, design questions, open decisions) one at a time, giving full context and discussion for each before moving to the next. Use when the user wants to work through a structured list interactively rather than scan it all at once.
- disable-model-invocation
- true
One-by-One
Guide the user through a list of findings interactively, one at a time. Each finding gets its own focused conversation: context, background, the problem it points to, and options for what to do about it. Do not rush ahead or present the next item until the user is done with the current one.
Your role
- Orient first. At the start, briefly acknowledge how many items you're working through and start with item 1. Don't ask the user if they want to begin — they already invoked the skill.
- One finding at a time. Present each finding fully, then end with the closing prompt and wait for the user to respond before moving on.
- Give real context. Don't just restate the finding. Explain why it matters: what could go wrong, what pattern it violates, what it makes harder to maintain or change. Reference the relevant code if you have it.
- Offer concrete paths forward. Give one option if there is genuinely only one reasonable path — that's a valid answer, not a shortcut. Don't reduce to one option just because you have a preference; if the options represent meaningfully different approaches or trade-offs, present them separately. Give two or three when trade-offs genuinely depend on context or constraints — but only count options that represent meaningfully different paths; don't pad. Beyond three genuinely distinct options, you're doing the user's sorting work for them — collapse them and strengthen your recommendation instead. Be specific — name the function, change, or pattern, not vague advice like "refactor this". If you have questions for the user (e.g. about intent or constraints), ask them before presenting options.
- Handle mid-finding dialogue. If you asked a scoping question and the user answers, or if the user asks a follow-up rather than making a decision, respond and continue the conversation within the same finding. Only advance to the next finding when the user has made a clear decision (fix, defer, or dismiss). Re-present the options in the format block if the scoping answer changes what you'd recommend.
- Honour the user's decision. The user may want to fix it, defer it, dismiss it, or discuss it further. Accept any of these and move on.
- Track position. Always make clear which finding you're on (e.g. "Finding 2 of 7") so the user knows where they are.
Show full SKILL.md (335 more words)Show less
Format for each finding
Present each finding like this:
Finding N of M — [short title]
What's the issue: One or two sentences on what the code is doing and what's wrong with it. Be specific — name the function, variable, or pattern.
Why it matters: The real-world consequence. What breaks, degrades, or becomes painful if this stays as-is?
Options:
- A: [concrete fix or change] — [trade-off or reason to pick this]
My recommendation: [only include when there are multiple options — use it to break the tie and explain why, not to restate the chosen option. Omit this section entirely if there is only one option.]
What do you want to do — fix it, defer it, or move on?
What to avoid
- Listing multiple findings at once
- Vague options like "refactor this" or "improve naming" without saying how
- Skipping the "why it matters" — that's the most important part for building understanding
- Advancing to the next finding before the user has made a decision
- Treating dismissals as failures — if the user waves something off, accept it and move on without re-litigating
- Outputting internal stage directions (anything instructing yourself to wait or stop belongs in your behaviour, not your output)
Flow
- Scan the recent conversation for anything list-like: code review findings, design questions, numbered items, bulleted points, or any set of distinct questions or topics raised in the prior message. If you find one, start directly with item 1 — don't ask the user to share it again. Only ask the user to share a list if there is genuinely nothing list-like in context.
- Present each finding using the format above and wait for a decision.
- If the user asks a follow-up or you asked a scoping question, handle it within the same finding before moving on.
- After the user makes a decision, briefly acknowledge it (one sentence), then move to the next finding.
- After the last finding, give a short summary: how many were fixed, deferred, or dismissed, and if there are clear next steps.
© jackfranklin, 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/one-by-one of jackfranklin/dotfiles.
Open the folder on GitHubat commit 48208f5
Compare with similar skills
One By One 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 |
|---|---|---|---|---|---|---|
| One By One this skilljackfranklin/dotfiles | 255 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Vercel Composition Patternssupabase/supabase | 111k | 58 repos | ~726 | Automated safety check: Pass | MIT | |
| Finishing a Development Branchobra/superpowers | 297k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 25 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
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.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
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.
More from jackfranklin/dotfiles
All 19 skills in this repoGitHub Code Review
jackfranklin/dotfiles
Perform a thorough, read-only review of one GitHub pull request.
Adr
jackfranklin/dotfiles
Capture an Architecture Decision Record (ADR) for a significant decision made in the current project.
Jack References
jackfranklin/dotfiles
Manage Jack's personal technical reference library at ~/git/references.
Later
jackfranklin/dotfiles
Log items to come back to later — bugs found mid-task, feature ideas, project feedback — as GitHub Issues.
New Deno App
jackfranklin/dotfiles
Scaffold a new Deno 2 + Hono + Deno KV + Eta + HTMX app with password auth and PWA support.
Resolve Merge Conflict
jackfranklin/dotfiles
A skill your agent uses when you need to resolve an in-progress git merge/rebase conflict.
Related
Categories
Questions about One By One
What does One By One do?
Walk through a list of items (e.g. An agent skill from jackfranklin/dotfiles. One By One is an agent skill from jackfranklin/dotfiles.g.
When should I use One By One?
One By One fits situations like: the user wants to work through a structured list interactively rather than scan it all at once.
How do I install One By One in Claude Code?
Run `npx skills add jackfranklin/dotfiles --skill one-by-one -a claude-code`. Or copy the skill folder (claude/skills/one-by-one in jackfranklin/dotfiles) into .claude/skills/one-by-one in your project. Claude Code loads it when a task matches its description.
How do I install One By One in Codex?
Run `npx skills add jackfranklin/dotfiles --skill one-by-one -a codex`. Or copy the skill folder (claude/skills/one-by-one in jackfranklin/dotfiles) into .agents/skills/one-by-one in your project. Codex loads it when a task matches its description.
Can I use One By One 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 jackfranklin/dotfiles --skill one-by-one -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/one-by-one, .gemini/skills/one-by-one, .github/skills/one-by-one and .opencode/skills/one-by-one in your project.
What does One By One need to run?
SKILL.md names no scripts, command-line tools or credentials: One By One is instructions for the agent only.
Does One By One 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 One By One 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 One By One use?
One By One 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 One By One use?
About 1.2k tokens (SKILL.md is roughly 4.7k 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 One By One?
Skills that share tags, products or a category with One By One: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 297k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains One By One?
jackfranklin (a GitHub user) maintains it in jackfranklin/dotfiles, which has 255 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.
Source: jackfranklin/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.