Skip to content
TrustedSkillsbeta
Back to all skills

Github Operations

Checked
yonatangross·vlatest·backend·MIT

Automates GitHub tasks like creating pull requests, merging branches, and managing issues via API calls.

Repository

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 yonatangross/orchestkit --skill github-operations -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

yonatangross

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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a 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 yonatangross/orchestkit at 7784b90c05.

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

Commit
7784b90c05
Manifest
src/skills/github-operations/SKILL.md
Scanned
2 files, 614 lines
Copies in repo
2 — all of them scanned
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

The GitHub Operations skill empowers AI agents to interact directly with repositories, enabling them to create, update, and delete code files. It allows agents to manage issues and pull requests, facilitating full-cycle software development workflows within a Git environment.

When to use it

  • Automating the creation of new feature branches based on specific requirements.
  • Resolving merge conflicts by editing conflicting files directly in the repository.
  • Managing project backlogs by creating or updating GitHub Issues and Pull Requests.
  • Deploying code changes by committing updates and pushing them to remote repositories.

Key capabilities

  • Create, update, and delete files within a repository.
  • Manage issues and pull requests.
  • Commit changes and push updates to remote branches.
  • Interact with Git history and branch management.

Example prompts

  • "Create a new issue titled 'Fix login bug' and assign it to the development team."
  • "Update the README.md file to include the latest installation instructions for version 2.0."
  • "Commit the changes made in the current branch and push them to the main repository."

Tips & gotchas

Ensure the AI agent has valid authentication credentials (such as a Personal Access Token) before attempting to modify remote repositories. Be cautious when delegating sensitive operations like deleting files or merging critical branches without human oversight.