New: 97,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

Issueflow Build

by jepegit in jepegit/cellpy

Run the /build slash command: rebuild the graphify knowledge graph for the project (graphify-out/graph.html, GRAPHREPORT.md, graph.json) by shelling out to issue-flow build (or graphify directly).

MITAuto-check passedKnowledge Management

Install Issueflow Build

skills CLI
$ npx skills add jepegit/cellpy --skill issueflow-build -a claude-code

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

GitHub CLI
$ gh skill install jepegit/cellpy issueflow-build --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/issueflow-build .claude/skills/issueflow-build && 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
issueflow-build
GitHub stars
109
Token cost
~977 tokens
SKILL.md length
449 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Run the /build slash command: rebuild the graphify knowledge graph for the project (graphify-out/graph.html, GRAPHREPORT.md, graph.json) by shelling out to issue-flow build (or graphify directly).

  • Works in 5 steps: Prefer issue-flow build from the project… → Fallback to graphify directly when… → If graphify exits with "no LLM API key… → …
  • Tasks that involve Knowledge graphs
  • SKILL.md covers When to use, Instructions and Constraints
  • Calls uv, pipx and pip; needs GEMINI_API_KEY and GOOGLE_API_KEY

What it does

Issueflow Build is an agent skill from jepegit/cellpy. Run the /build slash command: rebuild the graphify knowledge graph for the project (graphify-out/graph.html, GRAPHREPORT.md, graph.json) by shelling out to issue-flow build (or graphify directly). Off-path: never auto-dispatched by /iflow. Forwards trailing args verbatim to graphify.

Its SKILL.md is about 980 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 Knowledge Management, covering Knowledge graphs and Hooks and plugins. It works with Ollama. The repository describes itself as: extract and tweak data from electrochemical tests of cells. The licence is MIT.

When your agent uses it

  • Tasks that involve Knowledge graphs
  • Tasks that involve Hooks and plugins

Example prompts

  • “/issueflow-build”

Requirements

  • Python 3
  • A credential in GEMINI_API_KEY
  • A credential in GOOGLE_API_KEY

Workflow steps

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

  1. Prefer issue-flow build from the project root
  2. Fallback to graphify directly when issue-flow is unavailable
  3. If graphify exits with "no LLM API key found", the user picked extract (or another semantic subcommand) without configuring a backend…
  4. Handle missing graphify gracefully. If the run reports graphify is not on PATH, do not retry blindly. Tell the user to install it once
  5. Verify and report.

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:

    • uv
    • pipx
    • pip

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

  • Network

    Links to these hosts (documentation or services it may open):

    • graphify.net
    • ollama.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • GEMINI_API_KEY
    • GOOGLE_API_KEY
    • ANTHROPIC_API_KEY
    • OPENAI_API_KEY
    • MOONSHOT_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Issueflow Build loads about 977 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 449 words of instructions outside code blocks.

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

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). 449 words, ~977 tokens.

Download SKILL.mdSave it as .claude/skills/issueflow-build/SKILL.md (or your agent's skills folder).
name
issueflow-build
description
Run the /build slash command: rebuild the graphify knowledge graph for the project (graphify-out/graph.html, GRAPH_REPORT.md, graph.json) by shelling out to `issue-flow build` (or `graphify` directly). Off-path: never auto-dispatched by /iflow. Forwards trailing args verbatim to graphify.
disable-model-invocation
true

issue-flow — graph rebuild (/build)

Follow this skill when the user wants to refresh the project's graphify knowledge graph. Matches .cursor/commands/build.md.

When to use

  • The user runs /build, mentions "rebuild the graph", "refresh graphify", "regenerate GRAPH_REPORT.md", or similar.
  • The project has a graphify-out/ folder that is stale (large refactor, new modules, new docs/papers added) and the user asks to update it.
  • The user installed graphifyy for the first time and wants to produce the initial graph.

Do not use this skill from /issue-start, /issue-close, or /iflow. /build is opt-in only.

Instructions

  1. Prefer issue-flow build from the project root:

    bash
    issue-flow build

    With no extra args this runs graphify update <project> — AST-only, no LLM API key required, produces the full graphify-out/. To pick a different graphify subcommand, pass it as the first arg: issue-flow build extract (adds the slower semantic LLM pass for richer relationships — needs an API key), issue-flow build watch (live), issue-flow build cluster-only --no-viz, etc. Use -C <dir> to scan a project other than the current directory. Trailing flags pass through verbatim. Do not invent new wrapper flags.

  2. Fallback to graphify directly when issue-flow is unavailable:

    bash
    graphify update .

    graphify is subcommand-based — graphify . on its own is not valid (graphify reports unknown command '.'). Always pick a subcommand: update for the no-LLM AST build, extract for the full semantic pass, watch for a long-running watcher, etc.

  3. If graphify exits with "no LLM API key found", the user picked extract (or another semantic subcommand) without configuring a backend. Cursor's own LLM is not available to subprocesses, so graphify cannot reuse it. Suggest one of:

    • Set an API key for GEMINI_API_KEY / GOOGLE_API_KEY, ANTHROPIC_API_KEY, OPENAI_API_KEY, or MOONSHOT_API_KEY.
    • Run issue-flow build extract --backend ollama to use a local LLM via Ollama (requires Ollama installed with a model pulled).
    • Drop the extract arg and use the default issue-flow build (AST-only, no LLM).

  4. Handle missing graphify gracefully. If the run reports graphify is not on PATH, do not retry blindly. Tell the user to install it once:

    bash
    uv tool install graphifyy   # recommended
pipx install graphifyy
pip install graphifyy

    graphifyy (double-y) is the official PyPI package; the CLI is still graphify. After installing, suggest issue-flow update so graphify cursor install registers the graphify Cursor skill alongside this one.

  5. Verify and report.

    • Confirm graphify-out/graph.json, graphify-out/graph.html, and graphify-out/GRAPH_REPORT.md exist after a successful run.
    • Surface non-zero exit codes verbatim; do not silently retry.
    • When the user asks "what changed?", skim GRAPH_REPORT.md (god nodes, surprising connections) for a short summary.
Show full SKILL.md (52 more words)Show less

Constraints

  • Never auto-dispatch /build from another slash command. The user opts in explicitly.
  • Never commit graphify-out/cost.json or graphify-out/manifest.json; they are local-only.
  • Long-running modes (watch) keep the process alive; ask the user before launching them in an agent context.
  • Forward extra arguments verbatim. Do not translate or rewrite graphify's flag set inside issue-flow.

© 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/issueflow-build of jepegit/cellpy.

Open the folder on GitHubat commit ff2c665

Compare with similar skills

Issueflow Build 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.

Issueflow Build compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Issueflow Build this skilljepegit/cellpy109—~977Automated safety check: PassMIT
Crush Configurationcharmbracelet/crush29k—~3.7kAutomated safety check: PassCustom licence
Ontology1mancompany/OneManCompany4382 repos~1.5kAutomated safety check: PassApache-2.0
Install and Run Cogneetopoteretes/cognee32k—~1kAutomated safety check: NotesApache-2.0
HypatiaMarchLiu/hypatia239—~7.9kAutomated safety check: NotesMIT
KapsoLeeroo-AI/kapso120—~3.6kAutomated safety check: NotesMIT

Similar skills

  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed

  • Ontology

    1mancompany/OneManCompany

    Typed knowledge graph for structured agent memory and composable skills.

    438 GitHub starsUsed in 2 repos~1.5k tokens
    Knowledge ManagementAuto-check passed

  • Install and Run Cognee

    topoteretes/cognee

    Installs the cognee AI memory library in a Python environment, sets the LLM key and gets a first remember and recall script running with the Python SDK.

    32k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check: notes

  • Hypatia

    MarchLiu/hypatia

    Interact with the Hypatia AI memory system using natural language.

    239 GitHub stars~7.9k tokensUpdated 8 days ago
    Knowledge ManagementAuto-check: notes

  • Kapso

    Leeroo-AI/kapso

    Operate Kapso (PyPI leeroo-kapso), the long-running agents that optimize AI and Data systems, from a coding session — verify the install with kapso doctor, launch and follow an evolve campaign…

    120 GitHub stars~3.6k tokensUpdated yesterday
    Knowledge ManagementAuto-check: notes

  • Graph

    xwtro0tk1t-cloud/harness

    Manage code knowledge graphs via code-review-graph (CRG). An agent skill from xwtro0tk1t-cloud/harness.

    265 GitHub stars~1.1k tokensUpdated 5 mo ago
    Knowledge ManagementAuto-check passed

More from jepegit/cellpy

All 31 skills in this repo

  • Gh CI

    jepegit/cellpy

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

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

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

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

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

  • Iflow Capture

    jepegit/cellpy

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

    109 GitHub stars~2k 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.

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

Works with

Categories

Questions about Issueflow Build

What does Issueflow Build do?

Run the /build slash command: rebuild the graphify knowledge graph for the project (graphify-out/graph.html, GRAPHREPORT.md, graph.json) by shelling out to issue-flow build (or graphify directly). Issueflow Build is an agent skill from jepegit/cellpy.json) by shelling out to issue-flow build (or graphify directly).

When should I use Issueflow Build?

Issueflow Build fits situations like: tasks that involve Knowledge graphs; tasks that involve Hooks and plugins.

How do I install Issueflow Build in Claude Code?

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

How do I install Issueflow Build in Codex?

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

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

What does Issueflow Build need to run?

Going by SKILL.md and its folder, Issueflow Build needs the command-line tools its instructions call (uv, pipx and pip) and credentials named GEMINI_API_KEY, GOOGLE_API_KEY, ANTHROPIC_API_KEY and OPENAI_API_KEY. Our summary lists: Python 3; A credential in GEMINI_API_KEY; A credential in GOOGLE_API_KEY.

Does Issueflow Build access the network?

SKILL.md names 2 domains. As links in the text: graphify.net and ollama.com. This is read from the text; nothing was executed.

Is Issueflow Build 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 Issueflow Build use?

Issueflow Build 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 Issueflow Build use?

About 977 tokens (SKILL.md is roughly 3.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 Issueflow Build?

Skills that share tags, products or a category with Issueflow Build: Crush Configuration (charmbracelet/crush, 29k stars), Ontology (1mancompany/OneManCompany, 438 stars), Install and Run Cognee (topoteretes/cognee, 32k stars) and Hypatia (MarchLiu/hypatia, 239 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issueflow Build?

jepegit (a GitHub user) maintains it in jepegit/cellpy, which has 109 GitHub stars. The repository holds 31 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.