What is create-tickets?

A workflow for turning ideas from a brainstorming discussion into GitHub issues, which are tracked work items in a code repository. It breaks large ideas into appropriately sized tasks and prepares their project metadata.

Use it to extract features and bugs, split large changes into smaller issues, and create approved issues with labels, milestones, and project-board placement.

It turns an unstructured discussion into actionable work that a development team can review and track.

How Destrayon/Connapse configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Destrayon/Connapse. 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/Destrayon/Connapse/main/.claude/skills/create-tickets/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Destrayon/Connapse

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/destrayon/connapse/create-tickets/github.svg)](https://agentmods.dev/skills/destrayon/connapse/create-tickets)

Your own site

<a href="https://agentmods.dev/skills/destrayon/connapse/create-tickets"><img src="https://agentmods.dev/badge/skills/destrayon/connapse/create-tickets/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/destrayon/connapse/create-tickets"><img src="https://agentmods.dev/badge/skills/destrayon/connapse/create-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,891 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.00062	$0.01891
Opus 5.5	$0.00025	$0.00756
Sonnet 5.5	$0.00012	$0.00378
Haiku 4.5	$0.00006	$0.00189

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

Security

Grade A, and why

create-tickets 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/create-tickets/SKILL.md · 223 lines

How it starts

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

Create Tickets

Turn a brainstorming conversation into well-structured, properly-sized GitHub issues.

Overview

After a discussion about features, improvements, or bugs, this skill:

Extracts every idea from the conversation
Decomposes large features into PR-sized sub-issues
Presents a structured plan for user review
Batch-creates all approved issues with proper metadata
Adds them to the project board

Step 1: Extract Ideas from Conversation

Read the full conversation history. For each distinct idea, feature, bug, or task mentioned, capture:

What it is (feature, bug fix, enhancement, refactor, docs, test, infrastructure)
Why it matters (the user's stated motivation)
Rough scope (how many files/areas it touches)

Group related ideas together. If the user discussed a large feature with multiple parts, keep those parts linked.

Step 2: Size and Decompose

Apply these sizing rules strictly:

Size	Lines Changed	Files	Target
XS	< 50	1-2	Ideal for config, typos, small fixes
S	50-150	2-4	Target size for most issues
M	150-300	3-6	Acceptable for focused features
L/XL	300+	6+	MUST be decomposed — never create as single issue

For any idea estimated at L or larger, decompose by layer:

Data layer: models, migrations, interfaces (S)
Service layer: business logic implementing interfaces (S-M)
Endpoint layer: API endpoints wired to service (S)
UI layer: Blazor components consuming endpoints (S-M)
Test layer: unit + integration tests (S-M)

Not every layer applies to every feature. Only create sub-issues for layers that are relevant.

Step 3: Structure Each Issue

For each issue, determine all metadata:

Title

Concise, actionable, imperative voice
Good: "Add multi-prefix OR-clause to cloud scope search"
Bad: "Cloud scope search improvements"

Labels (one type, one or more area labels, and a size label)

Type labels (exactly one): type: feature, type: bug, type: enhancement, type: refactor, type: docs, type: test, type: infrastructure

Read the full file on GitHub · 223 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/project-metadata.md 2.0 KB

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 · 223 lines · 62 tokens per session scan A 17bda450fd01

Subscribe to this mod's changes

create-tickets is a skill published in the GitHub repository Destrayon/Connapse (22 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,891 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-08-30.

Project management blazor dotnet hybrid-search model-context-protocol ollama pgvector

create-tickets next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
create-ticketsDestrayon/Connapse	Skill	22	today	MIT	A	62	Claude Code
mapsuiznlgis/opengis-skills	Skill	76	10d ago	MIT	A	107	Claude Code, Codex
rag-expertpersonamanagmentlayer/pcl	Skill	44	11d ago	Apache-2.0	A	97	Claude Code
weasley-deepmindpotatohoney-p/weasley-deepmind	Skill	5	yesterday	Apache-2.0	A	0	Claude Code
collatticeMrBildo/collattice	Skill	8	11d ago	MIT	A	111	Claude Code, Codex
wpfvisualtreemcpfaze79/WPFVisualTreeMcp	Skill	21	11d ago	MIT	A	85	Claude Code, Codex
veladbhq-uk/vela-skill	Skill	6	11d ago	MIT	A	213	Claude Code

Connapse: Skill for Claude Code