CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-security-issue

Review an authorized security issue for validity, severity, and a remediation plan.

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/review-security-issue/SKILL.md
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.

The body is an exemplary lean, instruction-only skill: concrete commands, explicit authorization checkpoints, conditional handling of actionable vs non-actionable findings, and clear boundaries on what the agent must not decide. The only refinements would be a severity scale reference and a fuller example of the posted review comment.

DimensionReasoningScore

Conciseness

The body is lean and efficient with zero padding: every sentence encodes a non-obvious constraint Claude could not infer (e.g. 'Do not file or expand a vulnerability in a public issue; follow SECURITY.md', 'Do not introduce agent:* workflow labels'). No concept explanations are present, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Mostly executable guidance: a copy-paste-ready command ('gh issue view <id> --json title,body,state,labels,comments'), a concrete comment marker ('> **🔒 security-review-agent**'), and explicit routing to fix-security-issue. Minor gaps keep it below 5 — the severity step says only 'give a severity with rationale' with no scale or example, and only the comment's opening marker is specified rather than a full comment skeleton.

4 / 5

Workflow Clarity

A clear four-step sequence with explicit validation checkpoints ('Verify that this is an authorized security issue and that a prior review does not already answer the request') and conditional branches ('If actionable... If not actionable...', 'Post the review only when the request authorizes posting'). It falls short of the anchor 5 example only in lacking an explicit error-recovery path stating what to do when authorization cannot be verified.

4 / 5

Progressive Disclosure

A simple sub-50-line skill with a well-organized intro plus '## Assess' numbered workflow and clearly signaled one-level references to SECURITY.md and CONTRIBUTING.md; per the rubric's simple-skill note, no external reference files are needed and the structure earns a 5.

5 / 5

Total

18

/

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 is concise, in third person, and specific about the three review deliverables, but it omits any 'Use when...' trigger guidance and lacks the most common synonyms such as 'vulnerability' or 'CVE'. It is a solid but incomplete trigger description rather than a comprehensive one.

Suggestions

Add an explicit trigger clause, e.g. 'Use when asked to review or validate a reported security issue, vulnerability, or CVE in this repository' — this would raise completeness above its current cap of 3.

Include natural synonyms such as 'vulnerability', 'CVE', and 'security advisory' alongside 'security issue' so the description matches the phrases users actually say.

Briefly distinguish the review scope from the sibling fix workflow (e.g. 'assessment only; fixes are routed separately') to reduce overlap risk with fix-security-issue.

DimensionReasoningScore

Specificity

Names the domain ('security issue') plus three concrete deliverables ('validity, severity, and a remediation plan'), matching the 'several specific actions with minor gaps' anchor; it is not comprehensive enough for a 5 since the authorization-verification and posting aspects of the workflow are absent.

4 / 5

Completeness

The 'what' is clear (review for validity, severity, and a remediation plan) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like 'security issue', 'severity', and 'remediation plan' are present, but the most natural synonyms a user would say — 'vulnerability', 'CVE', 'exploit', 'security advisory' — are missing, matching the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Review an authorized security issue for validity, severity, and a remediation plan' carves a fairly distinct review-only niche (remediation proposal, not fixing), with only minor overlap risk against the sibling fix-security-issue skill and generic security/code review skills.

4 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 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

Total

14

/

16

Passed

Repository

NVIDIA/OpenShell

Path

.agents/skills/review-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.