Skip to content
TrustedSkillsbeta
Back to all skills

Issue Create

Checked
terrylica·vlatest·testing·MIT

Automatically generates well-formatted bug reports with context from conversations and system data.

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 terrylica/cc-skills --skill issue-create -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

terrylica

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 terrylica/cc-skills at 3a1dc29965.

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

Scanned
5 files, 712 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

This skill enables AI agents to programmatically create new issues within a repository management system. It automates the workflow of logging bugs, feature requests, or tasks directly into the project's issue tracker without manual intervention.

When to use it

  • Automatically generating bug reports when an automated test suite fails.
  • Creating task cards for developers based on user feedback collected from a chat interface.
  • Initiating security vulnerability reports upon detecting suspicious code patterns.
  • Logging recurring maintenance tasks identified during routine system health checks.

Key capabilities

  • Instantly creates new issue entries in supported repositories.
  • Captures detailed descriptions, titles, and priority levels for each log entry.
  • Integrates seamlessly into existing CI/CD pipelines to trigger immediate responses.

Example prompts

  • "Create a high-priority issue titled 'Login timeout error' describing the 503 response observed in the staging environment."
  • "Log a new feature request for dark mode support based on the latest community feedback summary."
  • "Generate an issue to track the migration of legacy database schemas scheduled for next quarter."

Tips & gotchas

Ensure your AI agent has the necessary write permissions configured for the target repository before attempting to create issues. Be specific in your descriptions to avoid vague tickets that require extensive clarification from human maintainers.