CtrlK
BlogDocsLog inGet started
Tessl Logo

calculate-priority-score

Calculate priority score for bugs, issues, or tasks based on severity, impact, and likelihood. Use for bug prioritization, task ordering, or risk assessment.

63

Quality

74%

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 ./.claude/skills/calculate-priority-score/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 instruction skill with concrete scoring tables, formula, category mapping, and error handling. Its main weakness is a dangling, self-referential supporting-file reference that hurts navigation.

Suggestions

Remove or fix the `scoring-matrix.json` reference in the Supporting Files section — the file does not exist in the bundle and the note '(see Supporting Files section)' is circular; either ship the file or drop the section.

Promote the trailing validation checklist into an explicit inline checkpoint (e.g. validate factor values in Step 1 before scoring) to tighten the workflow feedback loop.

Trim two of the four near-duplicate worked examples to reduce token cost while keeping representative P0/P2/P3/P1 coverage.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence: tight tables, a one-line formula, and JSON I/O blocks with no concept padding; the four worked examples add some length that could be trimmed, so it stops just short of 5.

4 / 5

Actionability

Provides fully concrete, executable guidance — exact numeric scoring tables, an explicit formula, score-to-category thresholds, error-handling rules, and copy-ready input/output JSON covering the common cases.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with an error-handling feedback section and a validation checklist; it falls short of 5 because validation is a trailing checklist rather than an explicit inline checkpoint within the calculation flow.

4 / 5

Progressive Disclosure

Sections are well organized and the small scoring matrix is sensibly inlined, but the "Supporting Files" section references a `scoring-matrix.json` that does not exist in the bundle and is described with a circular self-reference, a clear organization gap.

3 / 5

Total

16

/

20

Passed

Description

70%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 clear, well-structured description that explicitly covers both capability and trigger conditions with concrete, natural-language phrases. It is slightly limited by naming only one action and a modest set of synonyms.

DimensionReasoningScore

Specificity

Names the domain and a single concrete action ("Calculate priority score") plus the three input factors, but lists only one action rather than multiple specific actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

Explicitly answers both what (calculate priority score from severity, impact, likelihood) and when ("Use for bug prioritization, task ordering, or risk assessment"), with concrete triggers; the when clause is solid but slightly less expansive than the 5 anchor.

4 / 5

Trigger Term Quality

Includes natural user-facing phrases ("bug prioritization", "task ordering", "risk assessment") with good coverage; a few synonyms (e.g. "triage", "ranking") are missing so it is not a full 5.

4 / 5

Distinctiveness Conflict Risk

"Calculate priority score for bugs, issues, or tasks" carves a clear niche (numeric prioritization) with mostly distinct triggers; minor overlap risk with general task-management skills keeps it just below 5.

4 / 5

Total

15

/

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
maslennikov-ig/claude-code-orchestrator-kit
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.