What is solo-create-issue?

A workflow for creating fully labelled GitHub issues in the hiero-ledger/solo repository and adding them to the Solo X Team project. It fills in fields such as issue type, status, priority, labels, and parent issue when provided.

It is for turning a task description into a GitHub issue with a clear title, structured body, project placement, and tracking metadata.

It standardizes issue creation so new work arrives with the project information the team needs. It also reduces repeated setup when creating an issue from a natural-language request.

How hiero-ledger/solo configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to hiero-ledger/solo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/hiero-ledger/solo/main/.claude/skills/solo-create-issue/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/hiero-ledger/solo

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-create-issue/github.svg)](https://agentmods.dev/skills/hiero-ledger/solo/solo-create-issue)

Your own site

<a href="https://agentmods.dev/skills/hiero-ledger/solo/solo-create-issue"><img src="https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-create-issue/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hiero-ledger/solo/solo-create-issue"><img src="https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-create-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,534 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00058	$0.02534
Opus 5.5	$0.00023	$0.01014
Sonnet 5.5	$0.00012	$0.00507
Haiku 4.5	$0.00006	$0.00253

Measured 2mo ago against content hash 238af8aa2ac1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

solo-create-issue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/solo-create-issue/SKILL.md · 241 lines

How it starts

The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Solo Create Issue

Parse the user's request and create a GitHub issue in hiero-ledger/solo with full project metadata using one Bash tool call that runs all GraphQL mutations sequentially in a single script. All IDs are pre-resolved — no lookup calls needed.

Step 1 — Parse the user's request

Extract the following from the user's natural-language description:

Field	How to determine
Title	Synthesize a clear, action-oriented title (≤ 80 chars)
Body	Write a structured body (see Body Format below)
Issue Type	Explicit mention or infer from context (default: Task)
Priority	Explicit P0/P1/P2 or infer from urgency language (default: P1)
Status	Explicit mention or default to Ready; use Backlog when the issue has unresolved blockers
Labels	Always include the priority label; add others based on content
Parent issue	If the user mentions a parent epic/initiative, capture its node ID for `addSubIssue`

Body Format

## Overview
<2-4 sentence summary of the goal and motivation>

## Sub-Tasks
- [ ] Sub-task one
- [ ] Sub-task two

## Prerequisites
- [ ] Any blockers or dependencies (omit section if none)

### Dependencies
- [ ] requires #N    ← issues this one depends on
- [ ] required by #N ← issues that depend on this one

## References
- [Link text](url) — one line per reference (omit section if none)

Step 2 — Resolve IDs from the tables below

Repository (fixed)

Name	ID
Repo `hiero-ledger/solo`	`R_kgDOLMTWdQ`

Issue Types

Type	ID
Task	`IT_kwDOCq2Q984BY34v`
Bug	`IT_kwDOCq2Q984BY34w`
Feature	`IT_kwDOCq2Q984BY34x`
Epic	`IT_kwDOCq2Q984BhYEV`

Solo X Team Project

Name	ID
Project	`PVT_kwDOCq2Q984A6EW6`
Status field	`PVTSSF_lADOCq2Q984A6EW6zguwhjU`
Priority field	`PVTSSF_lADOCq2Q984A6EW6zguwhkA`

Status Options

Status	Option ID
Blocked	`d1cbdd71`
New	`ce7fcfc9`
Backlog	`f75ad846`
Ready	`36d4dfb8`
In Progress	`47fc9ee4`
In Review	`9ef22b4d`
Changes Requested	`8220b383`
Done	`98236657`

Read the full file on GitHub · 241 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 241 lines · 58 tokens per session scan A 238af8aa2ac1

Subscribe to this mod's changes

solo-create-issue is a skill published in the GitHub repository hiero-ledger/solo (45 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 2,534 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.

Project management hacktoberfest

solo-create-issue next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
solo-create-issuehiero-ledger/solo	Skill	45	yesterday	Apache-2.0	A	58	Claude Code
oh-my-poshJanDeDobbeleer/oh-my-posh	Skill	24k	2d ago	MIT	A	47	Claude Code, Codex
conventional-commitJanDeDobbeleer/oh-my-posh	Skill	24k	2d ago	MIT	A	26	Claude Code, Codex
researchArindam200/awesome-ai-apps	Skill	17k	yesterday	MIT	A	78	Claude Code, Codex
date-formatterAzure/azure-sdk-for-net	Skill	6.1k	today	MIT	A	13	Claude Code, Codex
keys-and-harmony-with-pytheorykennethreitz/pytheory	Skill	1.7k	7d ago	MIT	A	132	Claude Code
redux-to-swrcockroachdb/cockroach	Skill	33k	2d ago	none	A	53	Claude Code

solo: Skill for Claude Code