Spec
getsentry/sentry-react-native
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building.
A skill your agent uses when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo…
Install Run GitHub Project
$ npx skills add chrisbanes/skills --skill run-github-project -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install chrisbanes/skills run-github-project --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/chrisbanes/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/run-github-project .claude/skills/run-github-project && 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 "run-github-project" agent skill from https://github.com/chrisbanes/skills/tree/main/skills/run-github-project into .claude/skills/run-github-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-github-project", 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/chrisbanes/skills/tree/main/skills/run-github-projectType 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 chrisbanes/skills --skill run-github-project -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install chrisbanes/skills run-github-project --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisbanes/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/run-github-project .agents/skills/run-github-project && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "run-github-project" agent skill from https://github.com/chrisbanes/skills/tree/main/skills/run-github-project into .agents/skills/run-github-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-github-project", 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 chrisbanes/skills --skill run-github-project -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install chrisbanes/skills run-github-project --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisbanes/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/run-github-project .cursor/skills/run-github-project && 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 "run-github-project" agent skill from https://github.com/chrisbanes/skills/tree/main/skills/run-github-project into .cursor/skills/run-github-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-github-project", 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/chrisbanes/skills.git --path skills/run-github-project--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 chrisbanes/skills --skill run-github-project -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install chrisbanes/skills run-github-project --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisbanes/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/run-github-project .gemini/skills/run-github-project && 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 "run-github-project" agent skill from https://github.com/chrisbanes/skills/tree/main/skills/run-github-project into .gemini/skills/run-github-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-github-project", 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 chrisbanes/skills run-github-projectInstalls 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 chrisbanes/skills --skill run-github-project -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/chrisbanes/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/run-github-project .github/skills/run-github-project && 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 "run-github-project" agent skill from https://github.com/chrisbanes/skills/tree/main/skills/run-github-project into .github/skills/run-github-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-github-project", 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 chrisbanes/skills --skill run-github-project -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install chrisbanes/skills run-github-project --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chrisbanes/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/run-github-project .opencode/skills/run-github-project && 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 "run-github-project" agent skill from https://github.com/chrisbanes/skills/tree/main/skills/run-github-project into .opencode/skills/run-github-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "run-github-project", 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
run-github-project- GitHub stars
- 1.1k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 656 words
- Files
- 22 (incl. scripts, references)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo…
- Works in 4 steps: Live authority: claims, selection, and… → Controller ownership: only the… → Unknown outcomes: reconcile a failed or… → …
- Asked to set up
- SKILL.md covers Core principle, Select the mode and Final report
- Operate a repositorys GitHub Project workflow
What it does
Run GitHub Project is an agent skill from chrisbanes/skills. Use when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo triage, epics, checkpoints, next-issue execution, or an authorized drain.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 23 other files, including scripts and reference files (for example `agents/openai.yaml`, `references/agent-routing.md` and `references/authority-and-pauses.md`). Compatibility notes: External skill providers are mode-specific: review and setup require none; execution, triage, and Wayfinder lanes use the providers documented in…
It sits in Mobile, covering User stories. It works with GitHub. The repository describes itself as: Skills for Kotlin, Jetpack Compose, and Android development. The licence is Apache-2.0.
When your agent uses it
- Asked to set up
- Operate a repositorys GitHub Project workflow
- Including ready claims
- Role-labelled human work
Example prompts
- “/run-github-project”
Requirements
- Compatibility (from SKILL.md): External skill providers are mode-specific: review and setup require none; execution, triage, and Wayfinder lanes use the providers documented in references/workflow-providers.md.
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Live authority: claims, selection, and finish decisions require complete,
- Controller ownership: only the controller claims, assigns, mutates shared
- Unknown outcomes: reconcile a failed or timed-out remote mutation before
- Preservation: retain blocked, dependency-gated, and role-labelled human work in
What it can do on your machine
Read from SKILL.md and the folder at commit f872f97. 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 1 file in scripts/, which the agent can run.
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.
Compatibility
External skill providers are mode-specific: review and setup require none; execution, triage, and Wayfinder lanes use the providers documented in references/workflow-providers.md.
From compatibility in the SKILL.md frontmatter.
Context cost
Run GitHub Project loads about 1.5k tokens when it runs, and up to ~41k if it reads all its reference files. Until then it costs about 67 tokens; SKILL.md has 656 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); the scripts in this folder are not scanned.
SKILL.md
The full file from chrisbanes/skills at commit f872f97, republished under its Apache-2.0 licence (© chrisbanes). 656 words, ~1,484 tokens.
Download SKILL.mdSave it as
.claude/skills/run-github-project/SKILL.md (or your agent's skills folder). This skill also uses 21 other files; get the full folder from GitHub.- name
- run-github-project
- description
- Use when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo triage, epics, checkpoints, next-issue execution, or an authorized drain.
- compatibility
- External skill providers are mode-specific: review and setup require none; execution, triage, and Wayfinder lanes use the providers documented in references/workflow-providers.md.
- disable-model-invocation
- true
Run GitHub Project
Core principle
Use Backlog → Todo → Ready to implement → In progress → Done as
the default board lanes. Todo queues planning. Resolve lane names in this
procedure and its references through the trusted binding's verified names and
option IDs; preserve existing configured names. Current column membership
supplies ticket authorization; never inspect column transition history for
permission, plan freshness, or a Ready handoff. Backlog is read-only: never
claim, plan, triage, close epics, resume cleanup, or promote its items. Only
humans move items out of Backlog. Continue automatic work only in Todo and
later applicable columns, subject to ownership, dependencies, plan integrity,
and the current run's operation-specific grants.
A verified ticket handoff covers in-scope local implementation, tests and repairs.
The ticket lead may work solo or delegate when justified; retain one independent
integrated-candidate review and reuse valid evidence under deliver-spec.
The Project is the live control plane. Apply these invariants throughout:
- Live authority: claims, selection, and finish decisions require complete, fresh GitHub and Project state; cache and partial reads are hints only.
- Controller ownership: only the controller claims, assigns, mutates shared Project state, merges, closes issues, and reconciles. A ticket agent owns its worktree, branch, and non-merge PR mutations only.
- Unknown outcomes: reconcile a failed or timed-out remote mutation before retrying or reporting success.
- Preservation: retain blocked, dependency-gated, and role-labelled human work in its authoritative frontier or partial-drain report; never change state merely to make the queue appear empty.
Preserve verified plan state through contract-preserving replans, return true
human work to a decision pause, and in drain pair occupied slots with warm worktrees
and persistent ticket agents. Park verified authority pauses and qualifying
terminal required-CI claims outside capacity before refreshing the control plane.
Before dispatch, apply the execution controller's unattended readiness pass. Preserve required qualification and bounded grants while independent runnable work continues.
Show full SKILL.md (350 more words)Show less
Select the mode
review: inspect or explain only; finish under the review contract.setup: configure or validate the binding only; finish under the setup contract. Neither mode dispatches Project work or requires execution dependencies.next: default execution; process at most one selected issue.drain: only on explicit drain/run-all/repeat/until-empty request; no skill-defined ticket cap. A merge pause remains resumable work.
A named Wayfinder child remains next; it grants neither drain authority nor a
claim bypass. Before any mode-specific action, read the matching mandatory lane:
| Mode | Mandatory reference |
|---|---|
review or setup | Review and setup |
next or drain | Review and setup for binding validation, then execution controller and ticket lifecycle |
For execution, read workflow providers
before preconditions; it is authoritative on required, conditional, optional
providers, sources, installation commands, and lane-specific fallback. Never
install a provider implicitly. Read all providers and specialist contracts
required by the execution-controller lane before their relevant action.
Read run authority and ticket pauses.
Use next --auto-merge or drain --auto-merge to grant merge authority for this
invocation. Without it, deliver to ready PRs and pause only their merges while
the board continues.
When the trusted configuration enables agent profiles, read
agent routing before assigning a planner, ticket
agent, or helper.
For drain, read drain scheduler completely
before drain queue work. For next or drain, read
review contracts completely before acceptance
work.
Final report
Use the selected lane's terminal state and report contract. Lead an execution report with the outcome, completed tickets, work still moving, exact blockers, and the user's next action, if any. Link to durable issue, PR, and checkpoint evidence instead of repeating unchanged queries or no-op events. Keep mode, capacity, configuration digest, live-query and authority evidence, routing ledger, frontiers, parked/triage/reconciliation outcomes, and per-ticket selection, lease/plan, branch/commit/PR, verification/review, reconciled mutation/merge, and preserved or cleaned state available in a concise appendix when needed to audit a decision or resume work. Include changed unattended readiness blockers, complete-refresh/invalidation reasons, and observed planning/implementation/repair/review/CI intervals and capacity/resource waits under the timing procedure. Distinguish overlapping phase durations, total wall time and unknown timing; link repeated-cycle diagnosis and the bounded next action without claiming unmeasured savings.
© chrisbanes, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 21 other files (scripts, references) in skills/run-github-project of chrisbanes/skills.
- SKILL.md
- agents/openai.yaml
- references/agent-routing.md
- references/authority-and-pauses.md
- references/behavioral-review.md
- references/drain-scheduler.md
- references/execution-controller.md
- references/human-frontier.md
- references/normalized-ticket.md
- references/project-config.md
- references/remote-reconciliation.md
- references/review-and-setup.md
- references/review-contracts.md
- references/subagent-selection.md
- references/ticket-lifecycle.md
- references/todo-lane.md
- references/triage-lane.md
- references/wayfinder-lane.md
- references/workflow-providers.md
- … and 3 more
Open the folder on GitHubat commit f872f97
Compare with similar skills
Run GitHub Project 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 |
|---|---|---|---|---|---|---|
| Run GitHub Project this skillchrisbanes/skills | 1.1k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Specgetsentry/sentry-react-native | 1.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Execute Issuelbedner/aegis-stack | 143 | — | ~1.1k | Automated safety check: Pass | MIT | |
| GitHub Issue TriageOpenHands/extensions | 157 | — | ~437 | Automated safety check: Pass | MIT | |
| Create Issuetradingstrategy-ai/frontend | 150 | — | ~607 | Automated safety check: Pass | None | |
| Phoenix GitHubArize-ai/phoenix | 12k | — | ~6.5k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
Execute Issue
lbedner/aegis-stack
A skill your agent uses when handed a GitHub issue (number or URL) to execute end to end.
GitHub Issue Triage
OpenHands/extensions
Prioritize open issues and establish acceptance criteria before marking them ready for development.
Create Issue
tradingstrategy-ai/frontend
Creates a new GitHub issue with structured user story format, acceptance criteria, and project integration.
Phoenix GitHub
Arize-ai/phoenix
Manage GitHub issues, labels, project boards, sprint operations, and roadmap health for the Arize-ai/phoenix repository.
Abo Issue Watcher
jeeftor/audiobook-organizer
Inspect Audiobook Organizer GitHub issues, comments, acceptance criteria, linked PRs, and next steps.
More from chrisbanes/skills
All 19 skills in this repoGradle Run
chrisbanes/skills
A skill your agent uses when planning to execute Gradle through gradle, ./gradlew, or a custom gradlew wrapper script, or diagnosing a Gradle build, compact workflow ledger, repeated failure…
Compose Animations
chrisbanes/skills
A skill your agent uses when writing or reviewing Jetpack Compose motion: visibility enter/exit, animating one property toward a target, color or size transitions, multiple properties from one…
Compose UI Testing Patterns
chrisbanes/skills
A skill your agent uses when writing or reviewing Jetpack Compose UI tests, screenshot tests or baseline-recording evidence, previews, semantics assertions, fake image loading, keyboard input, focus…
Release Kotlin Library
chrisbanes/skills
A skill your agent uses when preparing, publishing, or checking readiness for a Kotlin library release, including verifying its gradle-maven-publish-plugin prerequisite, reconciling changelogs and…
Compose Component Design
chrisbanes/skills
A skill your agent uses when designing or reviewing reusable Jetpack Compose component APIs with modifier parameters, root layout placement, caller-provided variable content, primitive content…
Compose Focus Navigation
chrisbanes/skills
A skill your agent uses when writing or reviewing Jetpack Compose UI for TV, keyboard, desktop, accessibility focus, D-pad navigation, FocusRequester, focusProperties, key events, or initial focus…
Related
Works with
Categories
Questions about Run GitHub Project
What does Run GitHub Project do?
A skill your agent uses when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo…. Run GitHub Project is an agent skill from chrisbanes/skills. Use when asked to set up, review, or operate a repository's GitHub Project workflow, including ready claims, role-labelled human work, unknown remote mutation outcomes, Todo triage, epics, checkpoints, next-issue execution, or an authorized drain.
When should I use Run GitHub Project?
Run GitHub Project fits situations like: asked to set up; operate a repositorys GitHub Project workflow; including ready claims; role-labelled human work.
How do I install Run GitHub Project in Claude Code?
Run `npx skills add chrisbanes/skills --skill run-github-project -a claude-code`. Or copy the skill folder (skills/run-github-project in chrisbanes/skills) into .claude/skills/run-github-project in your project. Claude Code loads it when a task matches its description.
How do I install Run GitHub Project in Codex?
Run `npx skills add chrisbanes/skills --skill run-github-project -a codex`. Or copy the skill folder (skills/run-github-project in chrisbanes/skills) into .agents/skills/run-github-project in your project. Codex loads it when a task matches its description.
Can I use Run GitHub Project 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 chrisbanes/skills --skill run-github-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-github-project, .gemini/skills/run-github-project, .github/skills/run-github-project and .opencode/skills/run-github-project in your project.
What does Run GitHub Project need to run?
SKILL.md names no scripts, command-line tools or credentials: Run GitHub Project is instructions for the agent only. Compatibility (from SKILL.md): External skill providers are mode-specific: review and setup require none; execution, triage, and Wayfinder lanes use the providers documented in references/workflow-providers.md..
Does Run GitHub Project 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 Run GitHub Project 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 Run GitHub Project use?
Run GitHub Project is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Run GitHub Project use?
About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 39k tokens, read only when the agent opens those files.
What are the alternatives to Run GitHub Project?
Skills that share tags, products or a category with Run GitHub Project: Spec (getsentry/sentry-react-native, 1.8k stars), Execute Issue (lbedner/aegis-stack, 143 stars), GitHub Issue Triage (OpenHands/extensions, 157 stars) and Create Issue (tradingstrategy-ai/frontend, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Run GitHub Project?
chrisbanes (a GitHub user) maintains it in chrisbanes/skills, which has 1,090 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 4, 2026.
Source: chrisbanes/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.