CtrlK
BlogDocsLog inGet started
Tessl Logo

review-security-issue

Given a GitHub issue, review the issue for security implications. You'll make a determination if the claim in the issue is legitimate and should be addressed or will be a "won't fix." Trigger keywords - security issue, review security ticket, review security issue.

60

Quality

70%

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

75%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 well-structured, actionable security-review workflow with concrete gh commands, decision branches, and ready-to-post comment templates. Minor gaps are the non-executable Task-tool invocation syntax and some command duplication in the reference table.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, providing commands and templates without explaining basic concepts; the only minor trim is the "Useful Commands Reference" table that duplicates commands already shown inline in the steps.

4 / 5

Actionability

It provides copy-paste ready gh commands and full heredoc comment templates covering both legitimate and not-actionable outcomes; the only gap is the Task-tool invocation described as plain text ("Task tool with subagent_type='principal-engineer-reviewer'") rather than executable syntax.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with explicit gating checks in Step 2 (label presence, prior-review marker) and well-defined stop conditions; there is no validate-fix-retry feedback loop, but the workflow is non-destructive review work so this caps at 4 rather than 5.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-organized sections (Prerequisites, Steps, Commands Reference, Examples) and no nested references; at ~190 lines it exceeds the under-50-line simple-skill exception, so it sits at 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

65%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 clearly communicates a focused security-issue review skill with explicit trigger keywords, covering both what and when. Its main weaknesses are second-person voice ("You'll make") and slightly limited action specificity.

Suggestions

Rewrite in third person to avoid the second-person penalty, e.g. "Reviews a GitHub issue for security implications and determines whether the claim is legitimate...".

Add one or two more concrete actions (e.g., posts a structured review comment, transitions plan-requested to plan-ready labels) to lift specificity.

Consider a standard "Use when ..." clause alongside the trigger keywords for an even more explicit when-trigger.

DimensionReasoningScore

Specificity

The description names the domain ("review the issue for security implications") and one concrete action ("make a determination if the claim ... is legitimate and should be addressed or will be a 'won't fix'") which maps to anchor 3, but it uses second person ("You'll make a determination") so the specificity score is reduced by 1 per the voice guideline.

2 / 5

Completeness

It states both what (review a GitHub issue for security implications and make a determination) and when (explicit "Trigger keywords" guidance), so it is not capped at 3; the when-clause could be more explicit, placing it at 4 rather than 5.

4 / 5

Trigger Term Quality

It lists three natural trigger phrases ("security issue", "review security ticket", "review security issue") giving good keyword coverage, though a few natural synonyms are missing so it is not a 5.

4 / 5

Distinctiveness Conflict Risk

The security-review niche with distinct trigger phrases is mostly distinct with only minor overlap risk against general issue-triage skills, fitting anchor 4.

4 / 5

Total

14

/

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
NVIDIA/OpenShell
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.