CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

attack-path-analysis

Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

Quality

78%

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/codex-security/skills/attack-path-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A disciplined, actionable instruction-only skill: concrete tool calls, an ordered checkpointed workflow, and proper externalization of the large severity and facts material. Its weaknesses are redundancy of the compact-diff-mode rules across four sections and — more seriously — hard dependencies on '../../references/' files that are not part of the bundle.

Suggestions

Resolve or inline the shared-path conventions: either ship '../../references/scan-artifacts.md' and '../../references/artifact-storage.md' with the bundle, or inline the concrete default paths in SKILL.md so the required threat-model input does not depend on unresolvable files.

State the compact-diff-mode rules once (e.g., in the Output Contract) and reference them elsewhere with one-line pointers instead of repeating 'record a nested decision for every eligible candidate' and 'do not create per-finding reports or receipts' in four sections.

Add one short worked example of a rendered attack-path fact block or receipt so the output contract's bullets are demonstrable rather than inferable.

DimensionReasoningScore

Conciseness

Dense, rule-oriented content with zero padding: it never explains security concepts Claude already knows, and heavy material (severity policy, facts templates) is externalized. Not a 5 because the compact-diff-mode rules are stated three to four times across Artifact Resolution, Workflow, Output Contract, and Hard Rules ('record a nested attack-path decision for every eligible candidate', 'do not create per-finding reports or receipts'), and '../../references/scan-artifacts.md' is repeated where one authoritative pointer would do.

4 / 5

Actionability

Largely executable guidance: a concrete copy-paste tool call ('record_candidate_attack_paths({ scanId, attackPaths: [{ candidateId, attackPath }] })'), exact fields to record in receipts, explicit stopping conditions ('If a required input is still missing, stop and ask'), and point-of-use references for facts rendering and severity policy. Not a 5 because there is no worked example of a rendered attack path or receipt — the reader must assemble the output shape from the bullet contract and the external references.

4 / 5

Workflow Clarity

An 8-step numbered workflow with explicit checkpoints: the counterevidence challenge before finalizing scope/reportability (step 4), a checklist to run 'before finalizing the attack-path facts or policy decision', and enforced separation of facts, calibration, and policy adjustment. Not a 5 because there is no validate-and-retry feedback loop for this batch operation — if counterevidence overturns a fact mid-run there is no instruction to revisit earlier steps or re-run the checklist.

4 / 5

Progressive Disclosure

Local references are real and well signaled ('references/severity-policy.md', 'references/attack-path-facts.md' both resolve), but the two most-cited paths — '../../references/artifact-storage.md' and '../../references/scan-artifacts.md', the latter holding the required threat-model path convention — do not resolve anywhere in the actual bundle, leaving the skill's core input/output conventions dangling on out-of-bundle files. Combined with long inline checklists that could live in references, this sits between 'minor organization gaps' (4) and the structurally compromised case (3); the unresolved required references pull it to 3.

3 / 5

Total

15

/

20

Passed

Description

73%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.

A strong, well-bounded trigger description: explicit and specific 'when' guidance with effective anti-conflict scoping, written in third person without fluff. Its main weakness is that the 'what' is thin — only trace-and-calibrate is named, so the skill's broader transformation work is implicit.

Suggestions

Add one clause naming the remaining core actions, e.g. 'Turns validated findings into structured attacker stories with counterevidence and a final reportability decision' — this would lift both specificity and completeness.

Include a common synonym such as 'attack chain' or 'exploit path' in the trigger phrase so users who do not say 'source to sink' still match naturally.

DimensionReasoningScore

Specificity

Names the domain ('attack-path-analysis phase of a security scan') and 1-2 concrete actions ('trace a security finding from source to sink and calibrate severity'), matching the anchor for 1-2 concrete actions without comprehensive coverage — it omits the skill's other stated functions such as building attacker stories, counterevidence, and reportability decisions. Not a 4 because 'several specific actions' would require listing more of the actual capabilities.

3 / 5

Completeness

Both 'what' and 'when' are present: the trigger phrase 'trace a security finding from source to sink and calibrate severity' conveys the core actions, and the 'when' is explicit and highly specific ('Use when Codex is already in the attack-path-analysis phase ... or the user explicitly asks to ...'). Not a 5 because the full 'what' (attacker stories, structured facts, counterevidence pass, final reportability decision) is only implied; the description leans on the 'when' clauses to carry the 'what'.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'attack-path-analysis', 'security scan', 'security finding', 'trace ... from source to sink', 'calibrate severity', plus scan-scope terms ('PR, commit, branch, patch, or repository scans'). Not a 5 because common synonyms a user might say — 'attack chain', 'exploit path', 'vulnerability triage' — are absent; not a 3 because the present terms are natural and well-chosen rather than merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers and minimal conflict risk: it positively scopes to a specific phase or explicit user request, and the negative boundary ('Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans') actively prevents collision with the broader scan skills it could otherwise be confused with.

5 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

openai/plugins

Path

plugins/codex-security/skills/attack-path-analysis/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.