Skip to content
TrustedSkillsbeta
Back to all skills

Github Issues

Checked
epicenterhq·vlatest·backend

Automatically create GitHub issues from EpicenterHQ data, streamlining workflows and ensuring comprehensive tracking.

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 epicenterhq/epicenter --skill github-issues -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

epicenterhq

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 epicenterhq/epicenter at f9441c8f6d.

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

Commit
f9441c8f6d
Manifest
.agents/skills/github-issues/SKILL.md
Scanned
1 file, 158 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

github-issues

What it does

This skill enables AI agents to interact directly with GitHub Issues, allowing them to create, update, and manage issue tickets within a repository. It streamlines the workflow by automating administrative tasks related to bug tracking and feature requests on GitHub.

When to use it

  • Automatically generating new issues from code analysis or user feedback logs.
  • Updating issue statuses or adding comments based on resolved pull requests.
  • Triage workflows where an agent categorizes incoming reports into specific labels.
  • Closing stale issues after a defined period of inactivity.

Key capabilities

  • Create new GitHub Issues with custom titles and descriptions.
  • Update existing Issue metadata such as status, priority, or assignees.
  • Add comments to threads within an Issue to provide context or updates.
  • Manage labels to organize and filter issues effectively.

Example prompts

  • "Create a high-priority issue for the login failure bug reported in the latest logs."
  • "Update issue #42 to 'In Progress' and assign it to the backend team."
  • "Add the label 'security-critical' to all open issues containing the word 'vulnerability'."

Tips & gotchas

Ensure your AI agent has valid GitHub API credentials with write permissions for the target repository. The skill relies on the current state of the repository, so ensure the connection is active before attempting batch operations.