New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Iflow Capture

by jepegit in jepegit/cellpy

Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status.

MITAuto-check passedDevelopment

Install Iflow Capture

skills CLI
$ npx skills add jepegit/cellpy --skill iflow-capture -a claude-code

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

GitHub CLI
$ gh skill install jepegit/cellpy iflow-capture --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/jepegit/cellpy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/iflow-capture .claude/skills/iflow-capture && 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
iflow-capture
GitHub stars
110
Token cost
~2k tokens
SKILL.md length
908 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
MIT

At a glance

Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status.

  • Works in 6 steps: Explicit hints in slash input — root:,… → CLI fast path — issue-flow agent resolve… → Branch context — exactly one workspace… → …
  • Development work in your project
  • SKILL.md covers Instructions and Constraints
  • Calls git, gh and uv

What it does

Iflow Capture is an agent skill from jepegit/cellpy. Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status.

Its SKILL.md is about 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. It works with GitHub and Git. The repository describes itself as: extract and tweak data from electrochemical tests of cells. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/iflow-capture”

Workflow steps

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

  1. Explicit hints in slash input — root:, repo: (directory name, e.g. cellpy-core), or repo:owner/name.
  2. CLI fast path — issue-flow agent resolve [-C ] [--from-file ] [--json]. Use the returned project_root and repo; pass -C to other…
  3. Branch context — exactly one workspace repo whose branch matches ^\d+- → that root.
  4. Single scaffold — exactly one .issueflows/ tree visible in the workspace → that root.
  5. Workspace default — an issueflow-workspace.toml at the workspace root (created with issue-flow workspace init) may name a default member…
  6. Ambiguous → stop and ask; never guess between sibling repos.

What it can do on your machine

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

    • git
    • gh
    • uv

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

  • Network

    No URLs in SKILL.md. Its commands use git, gh and uv, 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

Iflow Capture loads about 2k tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 908 words of instructions outside code blocks.

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

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 jepegit/cellpy at commit ff2c665, republished under its MIT licence (© jepegit). 908 words, ~1,969 tokens.

Download SKILL.mdSave it as .claude/skills/iflow-capture/SKILL.md (or your agent's skills folder).
name
iflow-capture
description
Capture a GitHub issue locally as issue<number>_original.md and archive other current issues by done status.
disable-model-invocation
true
issue-flow-version
0.4.2a4

issue-flow — issue capture (/iflow-capture)

Follow this skill to capture a GitHub issue locally under .issueflows/01-current-issues/.

Invoke: type iflow capture in chat, or /iflow-capture from the slash menu (iflow-capture also works).

MODEL & EXECUTION DIRECTIVE

Profile: economy — Prioritize speed and token economy over deep reasoning.

In Cursor: use Auto or a fast model before invoking this step.

Keep scope tight to what this step requires.

Resolve project root (multi-root workspaces)

Before any git, gh, or .issueflows/ path operation in this workflow:

Resolution order (stop when unambiguous):

  1. Explicit hints in slash input — root:<path>, repo:<folder-basename> (directory name, e.g. cellpy-core), or repo:owner/name.
  2. CLI fast path — issue-flow agent resolve [-C <start>] [--from-file <active-file>] [--json]. Use the returned project_root and repo; pass -C <project_root> to other issue-flow agent … subcommands. When the answer came from the workspace registry, the payload sets resolved_via_workspace_default: true.
  3. Branch context — exactly one workspace repo whose branch matches ^\d+- → that root.
  4. Single scaffold — exactly one .issueflows/ tree visible in the workspace → that root.
  5. Workspace default — an issueflow-workspace.toml at the workspace root (created with issue-flow workspace init) may name a default member repo; use it when no scaffold matched above. Tell the user the default was used.
  6. Ambiguous → stop and ask; never guess between sibling repos.

After resolution, treat the result as <project_root> and <owner/repo>:

  • Git: git -C <project_root> … (or issue-flow agent … -C <project_root> for supported ops).
  • GitHub: pass an explicit repo on every gh call — never rely on gh's implicit cwd default. For most commands use --repo <owner/repo>; exception: gh repo view takes the repo as a positional arg (gh repo view <owner/repo> …) and rejects --repo.
  • Paths: all .issueflows/… paths are under <project_root>.

When .issueflows/04-designs-and-guides/multi-repo-workspaces.md exists, read it for layout and cross-repo guidance.

Instructions

CLI fast path (optional). If the issue-flow CLI is on PATH:

  • Resolve root + repo (step 0): issue-flow agent resolve [--from-file <active-file>] [--json] — use project_root and repo for all steps below.
  • Fetch + write (steps 3 & 5): issue-flow agent capture <N> -C <project_root> (use --repo owner/repo to override the resolved remote, --force to overwrite). It writes the ## Original issue text body deterministically and prints the comments payload — you still triage comments (step 3a) and add the curated section yourself.
  • Archive (step 4): issue-flow agent sweep --except <N> -C <project_root> (add --dry-run to preview).

The CLI is optional: if it is missing or errors, fall back to the manual instructions below. (issue-flow is only present when the user installed it, e.g. uv tool install issue-flow.)

  1. Folders — Ensure .issueflows/00-tools/, .issueflows/01-current-issues/, .issueflows/02-partly-solved-issues/, and .issueflows/03-solved-issues/ exist (create only if the user allows; never delete issue markdown).

  2. Resolve the reference

    • URL — Parse owner, repo, issue number.
    • Number only — After resolving <project_root>, run git -C <project_root> remote get-url origin (HTTPS or SSH) to derive owner/repo. If parsing fails, ask for a full URL or owner/repo.
    • Empty / whitespace — Run git -C <project_root> branch --show-current. If empty or main/master (case-insensitive), stop and ask for a number, URL, or owner/repo/#n. If the branch is an issue-style branch matching ^\d+-.+, ask: "You have not provided an issue reference. Should I use issue #NN from the current branch <branchname>?" Do not proceed without a clear yes/no.
    • Archived-issue guard — Before writing, check .issueflows/02-partly-solved-issues/ and .issueflows/03-solved-issues/ for existing issue<n>_* files. If the issue is already archived, warn and require a second explicit confirmation before re-opening it in .issueflows/01-current-issues/.

  3. Fetch — gh issue view <n> --repo owner/repo --json title,body,url,number,comments. The comments field returns an array of {author.login, body, createdAt, ...} that step 3a consumes. On failure, report the error and suggest gh auth login. After confirming owner/repo, change the chat/agent tab title to reflect the issue topic on the form "Issue <issue number> <short description of issue>" (e.g. "Issue 74 cell info").

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

3a. Triage comments (skip if comments is empty). Follow the iflow-comments skill — it owns the triage rules (chronological precedence, three buckets, noise filtering) and the exact shape of the ## Comments (curated summary) section.

3.5 Branch status preflight (report only) — Run git fetch --prune. Report current branch, clean/dirty working tree, and ahead/behind counts vs origin/<default> (detect default via gh repo view --json defaultBranchRef -q .defaultBranchRef.name, else git symbolic-ref --quiet --short refs/remotes/origin/HEAD, else main). If the current branch matches ^(\d+)-.+ and files for that issue already live in .issueflows/02-partly-solved-issues/ or .issueflows/03-solved-issues/, note that the branch looks stale. Never delete or move anything at this step.

  1. Archive — In .issueflows/01-current-issues/, group files by issue number (issue121_*). For each group other than the issue being created: move the whole group to .issueflows/03-solved-issues/ only if a status file for that issue contains a checked Done line matching - [x] Done (case-insensitive on "done"). Otherwise move to .issueflows/02-partly-solved-issues/. If no status file or checkbox is unclear, treat as not done.

  2. Write — Create .issueflows/01-current-issues/issue<number>_original.md with:

    markdown
    # Issue #<number>: <title>

Source: <url>

## Original issue text

<body exactly as returned by GitHub>

## Comments (curated summary)

- **Additional tasks**: <bullets distilled from comments that add real work>
- **Clarifications / constraints**: <bullets the agent should honour>
- **Superseded / retracted**: <earlier points later contradicted or walked back>

_Note: this section is an interpretive summary of the comment thread, not a verbatim dump. Source comments: <count>, last comment by @<login> on <date>._

    Preserve the body text faithfully as returned by GitHub — don't paraphrase or edit it, but don't waste effort on trailing newlines or CRLF vs LF either (no second-pass byte-diffing). The ## Comments (curated summary) section is optional — include it only when step 3a produced at least one bullet, and drop any of the three bullet groups that have no content.

  3. Conflicts — If issue<number>_original.md already exists, do not overwrite silently; ask the user.

  4. Report — Summarize number, owner/repo, branch inference (if used), path written, comment triage counts (fetched vs surfaced vs superseded, or "section omitted" when skipped), archive moves (source → destination), and success or failure.

Constraints

  • Allowed file operations: create/update the target *_original.md, and move pre-existing issue groups per the archive rules. Do not modify unrelated project files.

© jepegit, 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 .cursor/skills/iflow-capture of jepegit/cellpy.

Open the folder on GitHubat commit ff2c665

Compare with similar skills

Iflow Capture 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.

Iflow Capture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Iflow Capture this skilljepegit/cellpy110—~2kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
PR Review State Fetchprisma/orm48k—~767Automated safety check: PassApache-2.0

Similar skills

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • PR Review State Fetch

    prisma/orm

    Official

    Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.

    48k GitHub stars~767 tokensUpdated today
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from jepegit/cellpy

All 13 skills in this repo

  • Gh CI

    jepegit/cellpy

    Use GitHub CLI to snapshot or wait on CI for a pull request or workflow run.

    110 GitHub stars~667 tokensUpdated yesterday
    Auto-check passed

  • Caveman

    jepegit/cellpy

    Respond in a terse "smart caveman" style that keeps all technical substance but drops filler, articles, and pleasantries.

    110 GitHub stars~725 tokensUpdated yesterday
    Auto-check passed

  • Grill Me

    jepegit/cellpy

    Interview the user relentlessly about a plan or design until every branch of the decision tree is resolved, then feed the conclusions into the issue plan.

    110 GitHub stars~676 tokensUpdated yesterday
    Auto-check passed

  • Iflow Archive

    jepegit/cellpy

    Condense old solved issue groups into one dated summary file, then delete the originals.

    110 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Iflow Comments

    jepegit/cellpy

    Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md.

    110 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Iflow Epic

    jepegit/cellpy

    Plan a larger change as a staged epic: draft epic<Nplan.md with stages of manageable issue specs, then publish confirmed stages as GitHub issues.

    110 GitHub stars~3.3k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Iflow Capture

What does Iflow Capture do?

Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status. Iflow Capture is an agent skill from jepegit/cellpy.md and archive other current issues by done status.

When should I use Iflow Capture?

Iflow Capture fits situations like: development work in your project.

How do I install Iflow Capture in Claude Code?

Run `npx skills add jepegit/cellpy --skill iflow-capture -a claude-code`. Or copy the skill folder (.cursor/skills/iflow-capture in jepegit/cellpy) into .claude/skills/iflow-capture in your project. Claude Code loads it when a task matches its description.

How do I install Iflow Capture in Codex?

Run `npx skills add jepegit/cellpy --skill iflow-capture -a codex`. Or copy the skill folder (.cursor/skills/iflow-capture in jepegit/cellpy) into .agents/skills/iflow-capture in your project. Codex loads it when a task matches its description.

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

What does Iflow Capture need to run?

Going by SKILL.md and its folder, Iflow Capture needs the command-line tools its instructions call (git, gh and uv).

Does Iflow Capture access the network?

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

Is Iflow Capture 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 Iflow Capture use?

Iflow Capture 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 Iflow Capture use?

About 2k tokens (SKILL.md is roughly 7.9k 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 Iflow Capture?

Skills that share tags, products or a category with Iflow Capture: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Iflow Capture?

jepegit (a GitHub user) maintains it in jepegit/cellpy, which has 110 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 6, 2026.

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