CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fix-security-issue

Implement an authorized fix for a reviewed security issue and open a PR that closes its issue.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/fix-security-issue/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 an exemplary lean procedural skill: a numbered workflow with explicit authorization gates, stop conditions, verification scope, and concrete gh/mise commands, with general process detail appropriately delegated to referenced documents. The only minor gap is that a few operational specifics live entirely in external references rather than inline.

DimensionReasoningScore

Conciseness

The body is lean and dense: every sentence carries a workflow rule, an authorization boundary, or a concrete command, and it assumes Claude's competence by deferring general process detail to `CONTRIBUTING.md`, `SECURITY.md`, and the `create-github-pr` skill. There is no padding or explanation of concepts Claude already knows, matching the anchor for every token earning its place.

5 / 5

Actionability

Concrete, executable guidance is present — `gh issue view <id> --json number,title,body,state,labels,comments`, `mise run rust:deny:policy`, the `> **🔧 security-fix-agent**` marker, and `Closes #<id>` — with explicit stop conditions. It stops short of anchor 5 because several specifics (branch naming, verification commands, PR details) are deferred to external documents rather than given inline.

4 / 5

Workflow Clarity

A clear five-step sequence with explicit validation and feedback loops: stop-and-report if the review is missing or not actionable, verify the review against current code and record deviations, run format/lint/type checks plus regression and E2E lanes, and broaden verification when risk remains. This matches the anchor for clear sequencing with explicit validation steps and error-recovery paths.

5 / 5

Progressive Disclosure

The skill is under 50 lines, self-contained with no bundle files, and all external pointers (`CONTRIBUTING.md`, `SECURITY.md`, `create-github-pr`, `openshell-crypto`, CRYPTO.md) are one level deep and clearly signaled inline. Per the simple-skill guideline, well-organized short content with no need for external references merits a 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 states a clear, concrete purpose in third person with a distinct niche in the security-remediation workflow, but it omits any explicit "when to use" trigger guidance and is thin on natural keyword variations. Adding a trigger clause with synonyms like "vulnerability" or "security review" would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to fix a reviewed or authorized security issue, vulnerability, or security-review finding."

Include natural synonyms users would say — "vulnerability", "security finding", "CVE", "security fix" — alongside "security issue" to broaden trigger-term coverage.

Mention one or two more concrete actions (e.g., verifying the review against current code, adding regression tests) to round out capability coverage.

DimensionReasoningScore

Specificity

The description names the domain ("security issue" remediation) and two concrete actions — "Implement an authorized fix" and "open a PR that closes its issue" — which matches the anchor for 1-2 concrete actions. It falls short of anchor 4 because no further actions (e.g., verifying the review, testing the fix) are mentioned.

3 / 5

Completeness

The "what" is clear (implement an authorized fix, open a PR closing the issue), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

Relevant keywords like "security issue", "fix", and "PR" are present, but common natural variations users would say — "vulnerability", "security review", "CVE", "security fix" — are missing. This matches anchor 3 (some relevant keywords, missing common variations) rather than anchor 4's fuller coverage.

3 / 5

Distinctiveness Conflict Risk

"reviewed security issue", "authorized fix", and "closes its issue" carve out a distinct niche tied to a specific review workflow, with only minor overlap risk against a generic fix/PR skill. Not a 5 because the description lacks distinctive trigger phrases that fully separate it from neighboring code-fix skills.

4 / 5

Total

13

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/fix-security-issue/SKILL.md

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.