CtrlK
BlogDocsLog inGet started
Tessl Logo

plugin-security-release-targets

Given a Mattermost priority/severity level and a plugin repository, resolve the target plugin release-X.Y branches by cross-referencing the platform release policy with the plugin versions declared in each platform Makefile. Returns only branches that exist on the plugin's origin.

66

Quality

80%

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 ./plugins/cursor-automations/skills/plugin-security-release-targets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a tight, well-sequenced read-only resolution workflow with explicit gating checkpoints and executable commands, requiring only a literal fetch command to be fully copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and efficient throughout — no padding explaining what a Makefile, git, or a release branch is; every line (including the boundary statement about not touching PRs/Jira) earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides concrete, mostly copy-paste-ready commands (raw.githubusercontent Makefile URL, grep-with-exclusion, `git ls-remote --heads`), but the Makefile fetch is given as a URL rather than a literal curl/gh command, leaving a minor gap.

4 / 5

Workflow Clarity

Clear three-step sequence with explicit validation checkpoints: empty PLATFORM_BRANCHES returns immediately, missing Makefiles are skipped, and branches are filtered to those existing on origin — gating at each stage.

5 / 5

Progressive Disclosure

Well-organized into Inputs / Steps / Output with one-level-deep delegation to a named sibling skill and no nested references; appropriately self-contained for a skill of this size.

5 / 5

Total

19

/

20

Passed

Description

67%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, distinct, and uses correct third-person voice, but it lacks an explicit 'Use when...' trigger clause and natural synonyms a user would voice, which cap completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause naming the triggering situations (e.g. needing to cherry-pick a security fix to plugin release branches).

Include natural synonyms users actually say — 'security release', 'cherry-pick', 'CVE', 'plugin backport' — alongside the technical terms.

Keep the concrete action list as-is; it already scores well on specificity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'resolve the target plugin release-X.Y branches', 'cross-referencing the platform release policy with the plugin versions declared in each platform Makefile', 'Returns only branches that exist on the plugin's origin' — with comprehensive coverage of its niche.

5 / 5

Completeness

The 'what' is clear, but there is no explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 3 even though the capability description is strong.

3 / 5

Trigger Term Quality

Contains relevant domain keywords ('Mattermost priority/severity level', 'plugin repository', 'release-X.Y branches') but misses natural user phrasings like 'security release', 'cherry-pick', or 'CVE' that a requester would actually say.

3 / 5

Distinctiveness Conflict Risk

Occupies a very specific niche (Mattermost plugin release-branch resolution by severity) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

16

/

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.