Skip to content
TrustedSkillsbeta
Back to all skills

Cli Gh

Listed
paulrberg·vlatest·backend·MIT

Cli Gh helps you quickly execute Git commands directly from GitHub, streamlining your workflow and boosting productivity.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add paulrberg/agent-skills --skill cli-gh -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

paulrberg

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    SKILL.md frontmatter is missing description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned paulrberg/agent-skills at 2d4f4a6e5d.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
3 files, 63 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The cli-gh skill allows AI agents to interact with GitHub repositories using the GitHub CLI. It can be used to list files, create pull requests, and perform other common Git operations directly from within an agent's workflow. This enables automation of tasks related to code management and collaboration on GitHub.

When to use it

  • Automated Code Review: An agent could automatically review changes in a branch and create a pull request with suggested improvements.
  • Repository File Listing: Retrieve a list of files within a specific repository for documentation or analysis purposes.
  • Pull Request Creation: Generate a new pull request based on changes made by the agent, including descriptions and assignee selection.
  • Automated Issue Management: Automatically label or close issues in a GitHub repository based on predefined criteria.

Key capabilities

  • GitHub CLI interaction
  • File listing within repositories
  • Pull request creation
  • Git operations automation

Example prompts

  • "List all files in the 'docs' directory of the 'my-org/my-repo' repository."
  • "Create a pull request from my branch to main, with title 'Fix: typo in README'."
  • "Find and label any open issues tagged as 'bug' in the 'my-org/my-repo' repository."

Tips & gotchas

The agent requires access to a GitHub token with appropriate permissions (e.g., repo) to perform actions on repositories. Ensure the token is securely stored and managed within the agent’s environment.