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.

81

1.79x
Quality

75%

Does it follow best practices?

Impact

86%

1.79x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./groups/landscape/skills/landscape-jira/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

The content is highly actionable with concrete field mappings, ADF templates, and JQL patterns, but it reads as a reference rather than a sequenced workflow with validation checkpoints.

Suggestions

Add a numbered end-to-end workflow for creating an issue (look up sprint → build ADF → create issue → verify result → transition out of 'Untriaged') with explicit validation/verification checkpoints.

Consider moving the 'Useful JQL Patterns' and 'Writing Good Acceptance Criteria' sections into separate reference files to tighten the core SKILL.md body.

Tighten the 'Writing Good Acceptance Criteria' section to the most essential rules, removing conceptual framing Claude already knows.

DimensionReasoningScore

Conciseness

The body is mostly lean tables, ADF templates, and JQL patterns that assume Claude's competence; the 'Writing Good Acceptance Criteria' section is somewhat educational and could be trimmed, so not a full 5.

4 / 5

Actionability

Provides exact field IDs, copy-paste-ready ADF JSON templates, concrete JQL queries, and literal error messages — fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

Content is organized as a reference rather than a sequenced create-issue workflow, and there are no explicit validation checkpoints after issue creation; the gotchas flag errors but a clear numbered sequence with verify/transition steps is missing.

3 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and everything one level deep; as a single-file skill over 50 lines it is well structured, though some sections (JQL patterns, AC guide) could be split out.

4 / 5

Total

16

/

20

Passed

Description

75%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.

The description is specific and distinctive, clearly naming the domain, issue types, and capabilities, but it omits an explicit 'Use when...' trigger clause, which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when the user asks to create or update Jira issues, epics, stories, or sprints in the LNDENG project').

Include common synonyms/variations users might say (e.g., 'tickets', 'backlog items', 'sprint planning') to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across issue types ('stories, epics, objectives, tasks, spikes, bugs') plus 'correct field mappings, sprint assignment, and acceptance criteria' — comprehensive coverage matching the score-5 anchor.

5 / 5

Completeness

Has a clear 'what' but no 'when'/'Use when...' trigger clause; per the judging guideline, a missing explicit trigger guidance caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a Jira user would say ('Jira issues', 'stories', 'epics', 'sprint', 'acceptance criteria') with good coverage, but lacks a 'Use when...' clause and synonym variants, so it is not a full 5.

4 / 5

Distinctiveness Conflict Risk

Scoped to the LNDENG project on warthogs.atlassian.net with type-specific triggers, giving a clear niche with minimal conflict risk — matches the score-5 anchor.

5 / 5

Total

17

/

20

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.