CtrlK
BlogDocsLog inGet started
Tessl Logo

security-release-targets

Given a Mattermost priority/severity level (Critical/High/Medium/Low), resolve the target release-X.Y branches to cherry-pick onto by parsing the Mattermost release policy (ESR/active/upcoming) and keeping only branches that exist on mattermost/mattermost. Use when you need the list of release branches a fix must be backported to for a given severity.

70

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-sequenced instruction skill that gives exact parsing rules, a concrete validation gate, and clean output handling without explaining anything Claude already knows. The only soft spot is that the live-page parsing logic is algorithmic prose rather than executable code, which keeps actionability just under full marks.

DimensionReasoningScore

Conciseness

Lean and efficient: it jumps straight into the parsing algorithm with no padding or explanation of concepts Claude already knows, and every directive (regex, status markers, integer comparison, dedup) earns its place.

5 / 5

Actionability

Provides concrete executable elements (exact fetch URL, regex `^\s*(v\d+\.\d+)\b`, status marker `:(crit|active|done),`, and a copy-paste `git ls-remote` command), but the mermaid-block parsing is described algorithmically rather than as runnable code, leaving a minor gap.

4 / 5

Workflow Clarity

Clear three-step sequence (parse policy -> map priority -> filter to existing branches) with input validation ('If the value is missing or unrecognised, return an empty result') and an existence-check gate via git ls-remote; no validate->fix->retry loop is needed for this read-only resolution, so it sits just below 5.

4 / 5

Progressive Disclosure

A single-purpose skill under 50 lines with no bundle files (references/scripts/assets absent) and well-organized sections (Input, Step 1-3, Output), matching the simple-skill exception for a top score on organization alone.

5 / 5

Total

18

/

20

Passed

Description

87%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 precise, well-scoped description that cleanly states what it does and when to use it, with strong natural trigger terms and low conflict risk. The only blemish is second-person voice in the trigger clause, which costs it one specificity point.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('resolve the target release-X.Y branches to cherry-pick onto', 'parsing the Mattermost release policy (ESR/active/upcoming)', 'keeping only branches that exist on mattermost/mattermost') with comprehensive coverage, but reduced by 1 per the third-person-voice guideline because the trigger clause uses second person ('Use when you need...').

4 / 5

Completeness

Explicitly answers both what ('resolve the target release-X.Y branches... by parsing the Mattermost release policy... and keeping only branches that exist') and when ('Use when you need the list of release branches a fix must be backported to for a given severity') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('release branches', 'cherry-pick', 'backported', 'severity', and the Critical/High/Medium/Low enum), with a few common variations absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Mattermost release-branch backport resolution for a given severity) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
mattermost/mattermost-ai-marketplace
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.