Name: create-issue
Rating: 72 (1 reviews)
Author: camunda

create-issue

Create a GitHub issue in camunda/camunda with the correct template, component label, and parent link. Use when asked to create, file, or open an issue — for bugs, features, tasks, tech debt, or CVEs.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced procedural skill with strong validation gates around an external create operation. Its main weaknesses are a padded prerequisites paragraph and a monolithic structure with no reference-file offloading.

Suggestions

Tighten the Prerequisites MCP paragraph to a sentence or two; drop the enumeration of MCP failure modes that Claude can infer.

Move the component-label mapping table and the Zeebe label-split guidance into a references/ file (e.g. COMPONENT_LABELS.md) and link to it from Step 3 to reduce inline bulk.

Consider extracting the GraphQL issue-type and sub-issue registration snippets in Step 7 into a scripts/ helper so the core flow stays scannable.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and commands, but the Prerequisites MCP paragraph over-explains credential and failure semantics ('not immune to failures of their own (their own rate limits, service-side restrictions)') that could be trimmed.	3 / 5
Actionability	Provides copy-paste-ready gh and gh api graphql commands, a mktemp body-file pattern, and explicit template/label mapping tables covering the common cases.	5 / 5
Workflow Clarity	Steps 1–7 are clearly sequenced with explicit validation checkpoints: duplicate search (1.5), an approval gate before creation ('Do NOT call gh issue create yet'), redaction, and a change-revision feedback loop.	5 / 5
Progressive Disclosure	Well-sectioned single file with one clearly signaled one-level reference (AGENTS.md) and the grill-me skill, but at ~240 lines it inlines mapping tables that could be split into reference files and ships no bundle.	4 / 5
	Total	17 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both purpose and trigger conditions with concrete, natural keywords. It is specific to a single repo and task, making it highly distinct.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('correct template, component label, and parent link') but does not enumerate the full create/label/register lifecycle, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states both what it does (create a GitHub issue with template/label/parent link) and when to use it ('Use when asked to create, file, or open an issue').	5 / 5
Trigger Term Quality	Covers natural synonyms ('create, file, or open an issue') plus concrete issue types ('bugs, features, tasks, tech debt, or CVEs') that users would actually say.	5 / 5
Distinctiveness Conflict Risk	Pinned to a specific repo ('camunda/camunda') and a distinct GitHub-issue-creation niche with explicit triggers, giving minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: camunda/camunda
Path: .claude/skills/create-issue/SKILL.md
Commit: dfaeeff

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.