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.
Create, evaluate, and triage GitHub issues for CausalPy. An agent skill from pymc-labs/CausalPy.
Apache-2.0Auto-check passed
Install GitHub Issues
$ npx skills add pymc-labs/CausalPy --skill github-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pymc-labs/CausalPy github-issues --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/pymc-labs/CausalPy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/github-issues .claude/skills/github-issues && 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 "github-issues" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/github-issues into .claude/skills/github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issues", 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/pymc-labs/CausalPy/tree/main/.agents/skills/github-issuesType 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 pymc-labs/CausalPy --skill github-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pymc-labs/CausalPy github-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/github-issues .agents/skills/github-issues && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "github-issues" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/github-issues into .agents/skills/github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issues", 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 pymc-labs/CausalPy --skill github-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pymc-labs/CausalPy github-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/github-issues .cursor/skills/github-issues && 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 "github-issues" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/github-issues into .cursor/skills/github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issues", 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/pymc-labs/CausalPy.git --path .agents/skills/github-issues--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 pymc-labs/CausalPy --skill github-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pymc-labs/CausalPy github-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/github-issues .gemini/skills/github-issues && 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 "github-issues" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/github-issues into .gemini/skills/github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issues", 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 pymc-labs/CausalPy github-issuesInstalls 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 pymc-labs/CausalPy --skill github-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/github-issues .github/skills/github-issues && 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 "github-issues" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/github-issues into .github/skills/github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issues", 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 pymc-labs/CausalPy --skill github-issues -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install pymc-labs/CausalPy github-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pymc-labs/CausalPy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/github-issues .opencode/skills/github-issues && 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 "github-issues" agent skill from https://github.com/pymc-labs/CausalPy/tree/main/.agents/skills/github-issues into .opencode/skills/github-issues/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "github-issues", 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
github-issues- GitHub stars
- 1.2k
- Token cost
- ~254 tokens
- SKILL.md length
- 90 words
- Files
- 5
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create, evaluate, and triage GitHub issues for CausalPy. An agent skill from pymc-labs/CausalPy.
- Proposing an enhancement
- SKILL.md covers When to use, References and Important behavior
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Analyzing existing issues
What it does
GitHub Issues is an agent skill from pymc-labs/CausalPy. Create, evaluate, and triage GitHub issues for CausalPy. Use when filing a bug, proposing an enhancement, analyzing existing issues, or splitting large work into parent-child sub-issues.
Its SKILL.md is about 250 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `reference/bug-report.md`, `reference/issue-creation.md` and `reference/issue-evaluation.md`).
It works with GitHub. The repository describes itself as: A Python package for causal inference in quasi-experimental settings. The licence is Apache-2.0.
When your agent uses it
- Proposing an enhancement
- Analyzing existing issues
- Splitting large work into parent-child sub-issues
Example prompts
- “/github-issues”
What it can do on your machine
Read from SKILL.md and the folder at commit f17b30f. 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
GitHub Issues loads about 254 tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 90 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 pymc-labs/CausalPy at commit f17b30f, republished under its Apache-2.0 licence (© pymc-labs). 90 words, ~254 tokens.
Download SKILL.mdSave it as
.claude/skills/github-issues/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- github-issues
- description
- Create, evaluate, and triage GitHub issues for CausalPy. Use when filing a bug, proposing an enhancement, analyzing existing issues, or splitting large work into parent-child sub-issues.
GitHub Issues
This skill covers issue creation, bug reporting, and issue evaluation workflows.
When to use
- Filing a new issue (bug, enhancement, or task)
- Evaluating an existing issue and proposing next steps
- Preparing issue content for user review before posting
- Breaking large work into one parent issue with sub-issues
References
- Issue creation workflow
- Bug report workflow
- Issue evaluation workflow
- Parent-child sub-issues workflow
Important behavior
- If native sub-issues are not available, do not silently switch to fallback.
- Explain the limitation and ask the user whether to proceed with markdown tracking links.
© pymc-labs, 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 4 other files in .agents/skills/github-issues of pymc-labs/CausalPy.
- SKILL.md
- reference/bug-report.md
- reference/issue-creation.md
- reference/issue-evaluation.md
- reference/parent-child-issues.md
Open the folder on GitHubat commit f17b30f
Compare with similar skills
GitHub Issues 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 |
|---|---|---|---|---|---|---|
| GitHub Issues this skillpymc-labs/CausalPy | 1.2k | — | ~254 | Automated safety check: Pass | Apache-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Diagnosing Superpowers Sessionsobra/superpowers | 296k | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 83k | 5 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT | |
| Update V8 Versionopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
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.
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
More from pymc-labs/CausalPy
All 12 skills in this repoExample Datasets
pymc-labs/CausalPy
Load built-in CausalPy example datasets for demos, tutorials, tests, and quick causal-analysis prototypes.
Review PR
pymc-labs/CausalPy
Review CausalPy pull requests end-to-end by classifying PR type, checking branch freshness, mergeability, remote CI, correctness, security, tests, docs, and maintainer concerns.
Causal Detective
pymc-labs/CausalPy
Challenge causal claims through structured threat assessment, counterfactual reasoning, and CausalPy falsification checks.
Running Placebo Analysis
pymc-labs/CausalPy
Performs placebo-in-time sensitivity analysis with hierarchical null model and optional Bayesian assurance.
Python Environment
pymc-labs/CausalPy
Detect, configure, and use the project's Python environment (uv by default, conda-compatible tool as a fallback).
Feature Exploration
pymc-labs/CausalPy
Explore unfamiliar APIs, libraries, or implementation behavior with minimal reproducible examples and documented findings.
Related
Works with
Questions about GitHub Issues
What does GitHub Issues do?
Create, evaluate, and triage GitHub issues for CausalPy. An agent skill from pymc-labs/CausalPy. GitHub Issues is an agent skill from pymc-labs/CausalPy. Create, evaluate, and triage GitHub issues for CausalPy.
When should I use GitHub Issues?
GitHub Issues fits situations like: proposing an enhancement; analyzing existing issues; splitting large work into parent-child sub-issues.
How do I install GitHub Issues in Claude Code?
Run `npx skills add pymc-labs/CausalPy --skill github-issues -a claude-code`. Or copy the skill folder (.agents/skills/github-issues in pymc-labs/CausalPy) into .claude/skills/github-issues in your project. Claude Code loads it when a task matches its description.
How do I install GitHub Issues in Codex?
Run `npx skills add pymc-labs/CausalPy --skill github-issues -a codex`. Or copy the skill folder (.agents/skills/github-issues in pymc-labs/CausalPy) into .agents/skills/github-issues in your project. Codex loads it when a task matches its description.
Can I use GitHub Issues 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 pymc-labs/CausalPy --skill github-issues -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/github-issues, .gemini/skills/github-issues, .github/skills/github-issues and .opencode/skills/github-issues in your project.
What does GitHub Issues need to run?
SKILL.md names no scripts, command-line tools or credentials: GitHub Issues is instructions for the agent only.
Does GitHub Issues 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 GitHub Issues 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 GitHub Issues use?
GitHub Issues 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 GitHub Issues use?
About 254 tokens (SKILL.md is roughly 1k 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 GitHub Issues?
Skills that share tags, products or a category with GitHub Issues: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains GitHub Issues?
pymc-labs (a GitHub organization) maintains it in pymc-labs/CausalPy, which has 1,200 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on October 6, 2026.
Source: pymc-labs/CausalPy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.