Repository
jepegit/cellpy agent skills
- skills
- 31
- GitHub stars
- 109
GitHub description: “extract and tweak data from electrochemical tests of cells”
- Stars
- 109 (39 forks)
- Licence
- MIT
- Last push
- Oct 2026
- Created
- Dec 2015
- chemistry
- electrochemistry
- physics
- data-analysis
- opensource
- battery
Install all skills
npx skills add jepegit/cellpyAdd --skill <name> for a single skill and -a <agent> to choose the agent (see the agent guides).
Skills in jepegit/cellpy, ranked
Ranked by score. Sort bymost stars,trending,newest,recently updated
| # | Skill | Repository | Stars | Used in | Tokens | Auto-check | Licence | Updated |
|---|---|---|---|---|---|---|---|---|
| 1 | 1.Gh CI Use GitHub CLI to snapshot or wait on CI for a pull request or workflow run. | jepegit/ | 109 | — | ~667 | Automated safety check: Pass | MIT | yesterday |
| 2 | 2.Caveman Respond in a terse "smart caveman" style that keeps all technical substance but drops filler, articles, and pleasantries. | jepegit/ | 109 | — | ~725 | Automated safety check: Pass | MIT | yesterday |
| 3 | 3.Grill Me 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. | jepegit/ | 109 | — | ~676 | Automated safety check: Pass | MIT | yesterday |
| 4 | Condense old solved issue groups into one dated summary file, then delete the originals. | jepegit/ | 109 | — | ~1.3k | Automated safety check: Pass | MIT | yesterday |
| 5 | Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status. | jepegit/ | 109 | — | ~2k | Automated safety check: Pass | MIT | yesterday |
| 6 | Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md. | jepegit/ | 109 | — | ~1.4k | Automated safety check: Pass | MIT | yesterday |
| 7 | 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. | jepegit/ | 109 | — | ~3.3k | Automated safety check: Pass | MIT | yesterday |
| 8 | Rebuild the graphify knowledge graph (graphify-out/) by shelling out to issue-flow graphify or graphify directly. | jepegit/ | 109 | — | ~960 | Automated safety check: Pass | MIT | yesterday |
| 9 | Update the changelog when landing an issue: append a bullet to [Unreleased], or promote it to a release section after a version bump. | jepegit/ | 109 | — | ~1.6k | Automated safety check: Pass | MIT | yesterday |
| 10 | Refresh open PR heads onto the default branch after another merge left them DIRTY (usually HISTORY.md). | jepegit/ | 109 | — | ~1.2k | Automated safety check: Pass | MIT | yesterday |
| 11 | 11.Iflow Split Split one over-large GitHub issue into linked child issues (native sub-issues), then optionally start the first child. | jepegit/ | 109 | — | ~1.8k | Automated safety check: Pass | MIT | yesterday |
| 12 | Bump the project version following the project's release strategy: static pyproject versions via uv, or tag-derived versions via a planned git tag. | jepegit/ | 109 | — | ~1.6k | Automated safety check: Pass | MIT | yesterday |
| 13 | 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). | jepegit/ | 109 | — | ~977 | Automated safety check: Pass | MIT | yesterday |
| 14 | 14.Iflow Smart dispatcher: detect where the focus issue stands and dispatch to /iflow-capture, /iflow-plan, /iflow-build, or /iflow-close. | jepegit/ | 109 | — | ~2.3k | Automated safety check: Pass | MIT | yesterday |
| 15 | 15.Iflow Auto Unattended large-change orchestrator over a confirmed epic: cycle a stage, adversarial review, loop budget, next-epoch gate when the queue is clear. | jepegit/ | 109 | — | ~2.3k | Automated safety check: Pass | MIT | yesterday |
| 16 | 16.Iflow Build Implement the confirmed plan for the focus issue using the project's documented conventions. | jepegit/ | 109 | — | ~2.5k | Automated safety check: Pass | MIT | yesterday |
| 17 | Post-merge branch hygiene: switch to the default branch and delete landed local branches (reachable via -d; squash-landed via -D behind its own confirm). | jepegit/ | 109 | — | ~3.6k | Automated safety check: Pass | MIT | yesterday |
| 18 | 18.Iflow Cycle Process many issues hands-off in a row: resolve a queue, then run each through the yolo chain under one up-front confirm. | jepegit/ | 109 | — | ~3.5k | Automated safety check: Pass | MIT | yesterday |
| 19 | 19.Iflow Doctor Audit .issueflows/ for dirty conditions and optionally apply safe repairs. | jepegit/ | 109 | — | ~1.6k | Automated safety check: Pass | MIT | yesterday |
| 20 | 20.Iflow Drive Compose-only orchestrator: draft an epic from an existing issue, publish every stage, run /iflow-auto each epoch, final review, then local -d cleanup and /iflow-status. | jepegit/ | 109 | — | ~2.3k | Automated safety check: Pass | MIT | yesterday |
| 21 | 21.Iflow Fix Interactive session: one long-lived branch + GitHub issue for a stream of small iterative fixes, landed together via /iflow-close. | jepegit/ | 109 | — | ~2k | Automated safety check: Pass | MIT | yesterday |
| 22 | 22.Iflow Init Cold-start or check the issue-flow harness: guide issue-flow init when the scaffold is missing; bootstrap a parent folder of git siblings; point at update / doctor / iflow-capture when a project… | jepegit/ | 109 | — | ~2.1k | Automated safety check: Pass | MIT | yesterday |
| 23 | 23.Iflow Issue Create one well-specified normal GitHub issue, then optionally branch and run /iflow-capture into the standard lifecycle. | jepegit/ | 109 | — | ~1.9k | Automated safety check: Pass | MIT | yesterday |
| 24 | 24.Iflow Ops Run ops / no-PR work for the focus issue (staging→prod, flag flips, external deploys), then finish via /iflow-close ops. | jepegit/ | 109 | — | ~1.1k | Automated safety check: Pass | MIT | yesterday |
| 25 | 25.Iflow Pause Park work on the current issue without closing it: update status, move the group to 02-partly-solved-issues/, optional WIP commit. | jepegit/ | 109 | — | ~1.2k | Automated safety check: Pass | MIT | yesterday |
| 26 | 26.Iflow Pick Front door: choose the next issue, create the issue branch, and run /iflow-capture. | jepegit/ | 109 | — | ~3k | Automated safety check: Pass | MIT | yesterday |
| 27 | 27.Iflow Plan Draft a structured plan in issue<Nplan.md and get explicit user confirmation before any implementation starts. | jepegit/ | 109 | — | ~1.9k | Automated safety check: Pass | MIT | yesterday |
| 28 | 28.Iflow Review Review open GitHub issues and apply labels (extendable kinds; v1: yolo). | jepegit/ | 109 | — | ~1.7k | Automated safety check: Pass | MIT | yesterday |
| 29 | 29.Iflow Setup Guide a new user from an empty folder or an unprepared existing project to a working issue-flow setup: uv project, git repo, GitHub remote, and scaffold. | jepegit/ | 109 | — | ~2.1k | Automated safety check: Notes | MIT | yesterday |
| 30 | 30.Iflow Status Read-only snapshot of where every issue stands, locally and on GitHub. | jepegit/ | 109 | — | ~1.4k | Automated safety check: Pass | MIT | yesterday |
| 31 | 31.Iflow Yolo Chain capture → plan → build → close yolo for a small, low-risk issue under one consolidated confirm. | jepegit/ | 109 | — | ~1.6k | Automated safety check: Pass | MIT | yesterday |
Questions, answered from the data.
What is the best skill in jepegit/cellpy?
Gh CI from jepegit/cellpy ranks first of the 31 skills in jepegit/cellpy listed here, with the highest score: its repository has 109 GitHub stars, its SKILL.md loads about 667 tokens and it passes the automated safety check with no findings. Next come Caveman and Grill Me.
Are the skills in jepegit/cellpy official?
None yet. All 31 skills in jepegit/cellpy listed here come from community repositories; a skill counts as official when the product's own GitHub organization publishes it.
How do I install all skills from jepegit/cellpy?
Run npx skills add jepegit/cellpy in your project: the open-source skills CLI installs the repository's skills into your coding agent's skills folder. To install a single skill, open its page here for the exact command.
How are these skills ranked?
By Skill Navigator score, which combines the GitHub stars of the skill's repository (shared across that repo's skills and discounted for large collections), how many other GitHub owners carry a copy of the skill, and automated SKILL.md quality checks, minus penalties for safety-check warnings and for each further skill from the same repository. Skills that fail the safety check are not listed.