Skip to content
TrustedSkillsbeta
Back to all skills

Next Issue Number

Checked
oocx·vlatest·frontend·MIT

Automatically generates the next sequential issue number based on existing oocx frontend tickets.

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 oocx/tfplan2md --skill next-issue-number -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

oocx

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 oocx/tfplan2md at e422e9f9c0.

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

Commit
e422e9f9c0
Manifest
.agents/skills/next-issue-number/SKILL.md
Scanned
4 files, 528 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

What it does

This skill, next-issue-number, automatically determines and provides the next available issue number within a specified project. It analyzes existing issues to identify gaps in numbering sequences, ensuring new issues are assigned unique identifiers. This prevents conflicts and maintains organizational clarity within issue tracking systems.

When to use it

  • When creating a new issue manually and needing to ensure proper sequencing.
  • In automated workflows that generate new issues programmatically.
  • To quickly verify the next available number when migrating or re-organizing existing issues.
  • During audits of an issue tracking system to identify potential numbering errors.

Key capabilities

  • Analyzes existing issue numbers.
  • Identifies gaps in numbering sequences.
  • Determines the next available issue number.

Example prompts

  • "What's the next issue number for project 'Acme Project'?"
  • "Find the next available ticket ID in repository 'MyRepo'."
  • "Give me the next sequential issue number."

Tips & gotchas

The accuracy of this skill depends on the consistency of existing issue numbering. If there are significant irregularities or missing numbers, the calculated "next" number might be inaccurate.