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.
Fetch and manage GitHub issues via the API. An agent skill from profbernardoj/everclaw-community-branches.
MITAuto-check passed
Install GitHub Issues
$ npx skills add profbernardoj/everclaw-community-branches --skill github-issues -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install profbernardoj/everclaw-community-branches 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/profbernardoj/everclaw-community-branches.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/skillguard/test-fixtures/legit-api-skill .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/profbernardoj/everclaw-community-branches/tree/main/skills/skillguard/test-fixtures/legit-api-skill 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/profbernardoj/everclaw-community-branches/tree/main/skills/skillguard/test-fixtures/legit-api-skillType 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 profbernardoj/everclaw-community-branches --skill github-issues -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install profbernardoj/everclaw-community-branches github-issues --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/profbernardoj/everclaw-community-branches.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/skillguard/test-fixtures/legit-api-skill .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/profbernardoj/everclaw-community-branches/tree/main/skills/skillguard/test-fixtures/legit-api-skill 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 profbernardoj/everclaw-community-branches --skill github-issues -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install profbernardoj/everclaw-community-branches github-issues --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/profbernardoj/everclaw-community-branches.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/skillguard/test-fixtures/legit-api-skill .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/profbernardoj/everclaw-community-branches/tree/main/skills/skillguard/test-fixtures/legit-api-skill 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/profbernardoj/everclaw-community-branches.git --path skills/skillguard/test-fixtures/legit-api-skill--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 profbernardoj/everclaw-community-branches --skill github-issues -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install profbernardoj/everclaw-community-branches github-issues --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/profbernardoj/everclaw-community-branches.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/skillguard/test-fixtures/legit-api-skill .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/profbernardoj/everclaw-community-branches/tree/main/skills/skillguard/test-fixtures/legit-api-skill 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 profbernardoj/everclaw-community-branches 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 profbernardoj/everclaw-community-branches --skill github-issues -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/profbernardoj/everclaw-community-branches.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/skillguard/test-fixtures/legit-api-skill .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/profbernardoj/everclaw-community-branches/tree/main/skills/skillguard/test-fixtures/legit-api-skill 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 profbernardoj/everclaw-community-branches --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 profbernardoj/everclaw-community-branches github-issues --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/profbernardoj/everclaw-community-branches.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/skillguard/test-fixtures/legit-api-skill .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/profbernardoj/everclaw-community-branches/tree/main/skills/skillguard/test-fixtures/legit-api-skill 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
- 112
- Used in
- 1 other repo
- Token cost
- ~119 tokens
- SKILL.md length
- 48 words
- Files
- 2
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Fetch and manage GitHub issues via the API. An agent skill from profbernardoj/everclaw-community-branches.
- Tasks that involve Test data and fixtures
- SKILL.md covers Usage and Configuration
- Runs JavaScript scripts from its folder; needs GITHUB_TOKEN
What it does
GitHub Issues is an agent skill from profbernardoj/everclaw-community-branches. Fetch and manage GitHub issues via the API
Its SKILL.md is about 120 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `github.js`).
It works with GitHub. The repository describes itself as: Decentralized AI inference for OpenClaw agents. Powered by Morpheus AI. Stake MOR, access Kimi K2.5 + 10 models, never run out of inference. The licence is MIT.
When your agent uses it
- Tasks that involve Test data and fixtures
Example prompts
- “/github-issues”
Requirements
- Node.js
- A credential in GITHUB_TOKEN
What it can do on your machine
Read from SKILL.md and the folder at commit 0b30b36. 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 script files (JavaScript), 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 these keys or tokens, usually read from environment variables:
GITHUB_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
GitHub Issues loads about 119 tokens when it runs. Until then it costs about 14 tokens; SKILL.md has 48 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 profbernardoj/everclaw-community-branches at commit 0b30b36, republished under its MIT licence (© profbernardoj). 48 words, ~119 tokens.
Download SKILL.mdSave it as
.claude/skills/github-issues/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- github-issues
- description
- Fetch and manage GitHub issues via the API
GitHub Issues
This skill lets you list, create, and manage GitHub issues.
Usage
- "Show me open issues for repo X"
- "Create a new issue titled Y in repo Z"
Configuration
Set GITHUB_TOKEN in your environment with a personal access token.
The token needs repo scope for private repositories.
© profbernardoj, MIT. 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 1 other file in skills/skillguard/test-fixtures/legit-api-skill of profbernardoj/everclaw-community-branches.
- SKILL.md
- github.js
Open the folder on GitHubat commit 0b30b36
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in profbernardoj/everclaw-community-branches, which our catalogue first saw on October 7, 2026.
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 skillprofbernardoj/everclaw-community-branches | 112 | 1 repos | ~119 | Automated safety check: Pass | MIT | |
| 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 profbernardoj/everclaw-community-branches
All 12 skills in this repoMemory Upgrade
profbernardoj/everclaw-community-branches
Diagnose and fix broken memory search in OpenClaw. An agent skill from profbernardoj/everclaw-community-branches.
Relationships
profbernardoj/everclaw-community-branches
Relationship CRM for tracking people, connections, and context.
Agent Chat
profbernardoj/everclaw-community-branches
XMTP real-time agent-to-agent and user-to-agent encrypted messaging daemon for EverClaw.
Bagman
profbernardoj/everclaw-community-branches
Secure key management for AI agents. An agent skill from profbernardoj/everclaw-community-branches.
Night Shift
profbernardoj/everclaw-community-branches
Automated overnight task planning and execution engine for EverClaw.
Pii Guard
profbernardoj/everclaw-community-branches
Personally identifiable information (PII) leak prevention for EverClaw.
Related
Works with
Questions about GitHub Issues
What does GitHub Issues do?
Fetch and manage GitHub issues via the API. An agent skill from profbernardoj/everclaw-community-branches. GitHub Issues is an agent skill from profbernardoj/everclaw-community-branches.
When should I use GitHub Issues?
GitHub Issues fits situations like: tasks that involve Test data and fixtures.
How do I install GitHub Issues in Claude Code?
Run `npx skills add profbernardoj/everclaw-community-branches --skill github-issues -a claude-code`. Or copy the skill folder (skills/skillguard/test-fixtures/legit-api-skill in profbernardoj/everclaw-community-branches) 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 profbernardoj/everclaw-community-branches --skill github-issues -a codex`. Or copy the skill folder (skills/skillguard/test-fixtures/legit-api-skill in profbernardoj/everclaw-community-branches) 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 profbernardoj/everclaw-community-branches --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?
Going by SKILL.md and its folder, GitHub Issues needs JavaScript for the scripts in its folder and credentials named GITHUB_TOKEN. Our summary lists: Node.js; A credential in GITHUB_TOKEN.
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 MIT 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 119 tokens (SKILL.md is roughly 476 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?
profbernardoj (a GitHub user) maintains it in profbernardoj/everclaw-community-branches, which has 112 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 2, 2026.
Source: profbernardoj/everclaw-community-branches on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.