CtrlK
BlogDocsLog inGet started
Tessl Logo

landscape-jira

Creates well-formed Jira issues in the LNDENG project (warthogs.atlassian.net) — stories, epics, objectives, tasks, spikes, bugs, and more — with correct field mappings, sprint assignment, and acceptance criteria.

87

1.79x
Quality

85%

Does it follow best practices?

Impact

86%

1.79x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

87%Weight 40%Scale 1-3

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

The body is a tight, highly actionable reference with exact IDs, templates, and queries, organized into clear sections. Its main gap is the absence of an explicit end-to-end creation workflow with validation checkpoints, which caps workflow clarity at 2.

Suggestions

Add a short numbered 'Creating an issue' workflow (lookup sprint → build issuetype/parent/AC payload → create → verify the returned key/status) with an explicit verification step before declaring done.

Include a validation/checkpoint note for batch or parent-linked creation, e.g. confirm the parent key exists before creating children, to add an explicit feedback loop.

DimensionReasoningScore

Conciseness

Lean and efficient — uses tables, exact field IDs, copy-paste ADF templates, and exact error messages without explaining concepts Claude already knows (what Jira/ADF/JQL are), so every token earns its place rather than the mostly-efficient-but-padded anchor at 2.

3 / 3

Actionability

Provides fully executable guidance — exact issuetype/field IDs, a complete ADF JSON template, ready-to-use JQL queries, and the sprint-lookup query plus the integer to read — making it copy-paste ready rather than pseudocode or partial guidance at 2.

3 / 3

Workflow Clarity

The sprint lookup has a clear mini-sequence (run JQL, read customfield_10020[0].id, pass the integer) but the overall issue-creation flow is reference-style with no explicit numbered sequence or validate-then-proceed checkpoint; the Gotchas section is implicit error-avoidance, not a feedback loop, so it sits at 2 rather than 3.

2 / 3

Progressive Disclosure

No bundle files are needed or referenced; the single SKILL.md is well-organized with clearly headed sections (Cloud ID, Issue Type IDs, Key Fields, ADF format, Gotchas), which per the simple-skills note earns a 3 with well-organized sections alone.

3 / 3

Total

11

/

12

Passed

Description

82%Weight 40%Scale 1-3

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

The description is specific, trigger-rich, and highly distinct, but is missing an explicit 'Use when...' clause that would make the invocation trigger unambiguous, which caps completeness at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create, update, or look up Jira issues (stories, epics, bugs, tasks, spikes) in the LNDENG project.'

Optionally mention lookup/reading tasks (JQL search, sprint lookup) if the skill supports them, to broaden the natural trigger terms.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'Creates well-formed Jira issues ... stories, epics, objectives, tasks, spikes, bugs ... field mappings, sprint assignment, and acceptance criteria' — matching the comprehensive-action anchor rather than the partial domain-naming anchor at 2.

3 / 3

Completeness

Clearly states 'what' (creates issues with field mappings, sprint assignment, AC) but lacks an explicit 'Use when...' trigger clause, so 'when' is only implied; per guidelines a missing explicit trigger caps completeness at 2 and rules out 3.

2 / 3

Trigger Term Quality

Covers natural user terms ('Jira issues', 'stories', 'epics', 'objectives', 'tasks', 'spikes', 'bugs') that a user would actually say, matching the good-coverage anchor rather than the some-keywords-missing anchor at 2.

3 / 3

Distinctiveness Conflict Risk

Scoped to a specific project (LNDENG) and cloud instance (warthogs.atlassian.net) with named issue types, giving it a clear niche unlikely to conflict with other skills.

3 / 3

Total

11

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
canonical/copilot-collections
Reviewed

Table of Contents

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.