Github Outside Sandbox
Run Git and GitHub CLI commands on the host when sandboxing blocks Keychain auth, network access, or .git writes. Use for gh auth, repo/PR operations, index.lock, or permission errors; covers execution context only.
Install
npx skills add davidondrej/skills --skill github-outside-sandboxgit clone --depth 1 https://github.com/davidondrej/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/github-outside-sandbox ~/.claude/skills/github-outside-sandboxPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# GitHub Outside Sandbox 1. Start normally. Escalate only the blocked command and only within the user's authorization. 2. If sandboxed `gh auth status` fails, rerun it outside the sandbox before claiming authentication is broken. Never expose or copy tokens. 3. Run GitHub CLI network operations outside the sandbox when required: `gh repo ...`, `gh pr ...`, and related `gh` commands. 4. Run Git writes outside the sandbox when `.git` is outside writable roots or errors mention `index.lock` or `Operation not permitted`: `git add`, `git commit`, and `git push`. 5. Use the harness's official host-execution mechanism. In Codex, set `sandbox_permissions: "require_escalated"`, give a concrete `justification`, and use only a narrow safe `prefix_rule` when appropriate. 6. Never use shell wrappers, credential copying, or broad approval prefixes to bypass the sandbox. 7. Verify from the host context with `git status -sb`, `git remote -v`, and the relevant `gh ... view` command. Ask the user to authenticate only if the host-context check also fails.
Details
- Skill name
github-outside-sandbox- Repository
- davidondrej/skills
- Path
skills/github-outside-sandbox/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Github Outside Sandbox skill do?
Run Git and GitHub CLI commands on the host when sandboxing blocks Keychain auth, network access, or .git writes. Use for gh auth, repo/PR operations, index.lock, or permission errors; covers execution context only.
How do I install the Github Outside Sandbox skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add davidondrej/skills --skill github-outside-sandbox. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Github Outside Sandbox popular?
It lives in davidondrej/skills, which has 4,336 GitHub stars and 628 forks.
Related skills
Browser Harness
4.3kdavidondrej/skills
Direct browser control via CDP. Use when the user wants to automate, scrape, test, or interact with web pages. Connects to the user's already-running Chrome.
4x4
4.3kdavidondrej/skills
Pull 16 fast decisions out of the user with 4 sets of 4 open questions, then present an implementation plan. Only for risky changes, large product decisions, or large refactors. Run when the user types /4x4. Agents may suggest it in one line but never start it on their own.
Adr Verbatim
4.3kdavidondrej/skills
Record concise ADRs that preserve the user's decisions without conversational noise. Use for "adr-verbatim", "new ADR", "document that as an ADR", "record this decision", or supplied ADR wording.
Kimi Review
4.3kdavidondrej/skills
Launch an independent Kimi K3.1 Pro Max code review and return it verbatim, falling back across harnesses and routes until one works. Use for /kimi-review, or when the user or another agent asks for a Kimi review.
Git Worktree
4.3kdavidondrej/skills
Use Git worktrees to isolate parallel coding tasks. Use when setting up a task checkout, working in a shared repo, or managing existing worktrees.
Larp Detector
4.3kdavidondrej/skills
Skeptical review of outside contributions to public repos. Use when reviewing, ranking, or replying to public GitHub pull requests or issues from outside contributors, or when the user says "larp-detector".
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.