fix-security-issue

Implement a fix for a reviewed security issue. Takes a directly requested issue number or scans for issues labeled `topic:security` and `agent:implementation-requested`. Reads the security review from the issue comments and implements the remediation plan. Trigger keywords - fix security issue, remediate security, implement security fix, patch vulnerability.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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-sequenced, highly actionable workflow with strong validation checkpoints and copy-paste-ready commands and templates. Its main weakness is mild verbosity from repeated label-handling explanations and a long inline commands/examples reference that could be externalized.

Suggestions

Consolidate the repeated agent:implementation-requested / queue-vs-direct-mode label rules into one location (e.g. the Prerequisites or a single 'Invocation Modes' section) and reference it from Steps 2, 4, and 8 instead of restating it each time.

Move the 'Useful Commands Reference' table and the multi-example 'Example Usage' section into a separate references file (e.g. references/commands.md) and link to it, reducing the inline body length.

Tighten Step 6 test guidance by trimming the prose around test levels and leading with the concrete naming examples and verification commands.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands throughout, but several sections restate workflow-label handling across prerequisites, Step 2, Step 4, and Step 8 that could be consolidated; minor over-explanation of the label-mode rules.	4 / 5
Actionability	Fully executable guidance — copy-paste ready gh/git commands, a complete PR body template, concrete test-naming examples, and a commands reference table covering the common cases.	5 / 5
Workflow Clarity	Clear 9-step sequence with explicit validation checkpoints (label validation, review-determination branching, pre-commit checks, test verification) and feedback loops (fix issues before proceeding, re-validate), plus per-branch stop conditions.	5 / 5
Progressive Disclosure	Well-organized into clearly headed steps plus reference tables and examples with no nested references; since no bundle files exist the body is self-contained, but the commands-reference and example sections are long enough that they could be split into reference files.	4 / 5
	Total	18 / 20 Passed

Description

100%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 concrete, uses third person, and explicitly covers both what the skill does and when to trigger it via natural keyword phrases. It is comprehensive and well-distinguished, though slightly verbose for a description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Takes a directly requested issue number or scans for issues', 'Reads the security review from the issue comments', 'implements the remediation plan' — with comprehensive coverage of the workflow entry points.	5 / 5
Completeness	Clearly answers both 'what' (implement a fix for a reviewed security issue, read review, implement remediation) and 'when' (trigger keywords clause), matching the 5-anchor example structure.	5 / 5
Trigger Term Quality	Provides explicit trigger keywords ('fix security issue, remediate security, implement security fix, patch vulnerability') that are natural phrases a user would say, with several synonyms.	5 / 5
Distinctiveness Conflict Risk	Clear niche — reviewed security issues with specific labels (topic:security, agent:implementation-requested) and a paired review skill — minimal conflict risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NVIDIA/OpenShell
Path: .agents/skills/fix-security-issue/SKILL.md
Commit: 69a05eb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.