CtrlK
BlogDocsLog inGet started
Tessl Logo

1k-jira-qa-handoff

Generate Chinese product behavior and QA cases from commits, then sync them to a Jira issue while preserving existing context and Slack links.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.skillshare/skills/1k-jira-qa-handoff/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is highly actionable with concrete commands, a copy-verbatim template, and a clear sequenced workflow with checkpoints. It loses a little on conciseness from restated rules and on workflow clarity from a missing explicit validation retry loop around the Jira write.

DimensionReasoningScore

Conciseness

The body is largely efficient — concrete bash commands, a tight decision table, and a copy-verbatim template — with only minor padding such as restated 'silent default' rules across Hard rules, Path A, and Anti-patterns that could be trimmed.

4 / 5

Actionability

Fully executable: real git commands, exact MCP tool names and ToolSearch queries, a literal Jira URL parsing example, and a copy-paste Chinese output template with concrete OneKey-style title examples.

5 / 5

Workflow Clarity

A clear 5-step sequenced checklist with a preview/approval checkpoint and skip conditions; however, the destructive Jira write has only one confirmation gate and lacks an explicit validate-then-retry feedback loop, capping it just below 5.

4 / 5

Progressive Disclosure

Well-organized into Hard rules, Workflow, Output Template, MCP notes, and Anti-patterns with no bundle files needed; a few inline sections (the MCP notes and decision table) could live in reference files, but structure and navigation are good.

4 / 5

Total

17

/

20

Passed

Description

58%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 concretely states what the skill does and is reasonably distinct, but it omits any 'Use when…' trigger guidance, which caps completeness and weakens trigger-term quality. Adding an explicit trigger clause would lift both dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a PR has merged and the PM needs to hand off QA-visible behavior to a Jira task issue.'

Add natural user phrasings/synonyms such as 'hand off to QA', 'update Jira description', or 'sync commits to Jira' to improve trigger-term coverage.

Mention commit parsing explicitly (e.g., 'reads recent git commits on the branch') so the commit-input action is stated, not implied.

DimensionReasoningScore

Specificity

Names the domain (Jira QA handoff) and several concrete actions — 'Generate Chinese product behavior and QA cases', 'sync them to a Jira issue', 'preserving existing context and Slack links' — with only minor coverage gaps (e.g., commit parsing is implied rather than stated).

4 / 5

Completeness

The 'what' is clearly stated, but there is no explicit 'when to use this skill' trigger guidance, which the rubric caps at 3 for a missing Use-when clause.

3 / 5

Trigger Term Quality

Relevant keywords like 'commits', 'QA cases', 'Jira issue' are present, but it lacks a natural 'Use when…' trigger clause and omits common user phrasings such as 'hand off to QA' or 'update Jira'.

3 / 5

Distinctiveness Conflict Risk

The niche (post-merge Chinese QA handoff synced to a task-type Jira issue while preserving context) is fairly distinct from generic Jira or commit-message skills, with only minor overlap risk against a sibling create-pr skill.

4 / 5

Total

14

/

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
OneKeyHQ/app-monorepo
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.