Back to the marketplace · Skill
GitHub CLI workflow
Manage issues, PRs, CI runs, code reviews, releases, and API queries with the gh CLI; requires the user to have gh installed and authenticated; every write operation needs the owner's explicit approval.
Copy this sentence and send it to any colleague in Teloa:In Teloa, open Marketplace, search for "GitHub CLI workflow" and add it (entry openclaw.github).
- Source
- Teloa official · GitHub openclaw/openclaw
Changes relative to upstream:- Frontmatter keeps only name and description; OpenClaw-specific metadata.openclaw (including emoji, requires.bins, and install brew directive) removed.
- Removed the OpenClaw session footer template from the body (the 'View the OpenClaw team session' paragraph); it depends on OpenClaw Runtime's sessionUrl injection, which is not applicable in Teloa.
- The repository root LICENSE (MIT) and THIRD_PARTY_NOTICES.md are included with the artifact.
- License
- MIT
License files: LICENSE, THIRD_PARTY_NOTICES.md - Review
- Reviewed by Teloa on 2026-09-25
- Compatibility
- Needs configuration · Teloa >=0.2.0-alpha.6 · DSH 0.1.7-rc.1
- Requires the user to install gh CLI and run gh auth login; Teloa does not install gh or log in on the user's behalf.
- Any write operation (creating issues/PRs, pushing code, merging, commenting, etc.) must be explicitly approved by the repository owner before execution.
- Permissions and requirements
- Tools: gh
Runtimes: gh
Network at run time: no - Data flow
- Files ship pinned inside the Teloa release; nothing is downloaded when you add it. This site collects no user information.
Entry openclaw.github · version 1.0.0