CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/vex-author

Authors and validates OpenVEX documents - produces `not_affected`, `affected`, `fixed`, and `under_investigation` statements with justification codes using `vexctl create`; attaches VEX assertions to container images; outputs `.openvex.json` files consumed on a downstream VEX-filter / vulnerability-prioritization path. Use when a scanner flags a CVE that analysis confirms is not exploitable in your deployment, and a machine-readable `not_affected` assertion is needed to suppress false positives without discarding the finding from the audit trail.

74

Quality

93%

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

Overview
Quality
Evals
Security
Files

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable and well-sequenced with validation feedback loops, but carries minor verbosity in the conceptual Overview that a competent model doesn't need.

Suggestions

Trim the Overview's definition of OpenVEX/VEX to one sentence; Claude already understands the VEX standard, so lead with the downstream-prioritization contract instead.

The '# vex-author' H1 duplicates the skill name from frontmatter; drop it or fold it into the Overview to save tokens.

Move the spec field tables (Steps 2–3) into a references/ file and link to it, keeping SKILL.md as an overview that points one level deep.

DimensionReasoningScore

Conciseness

Mostly lean (numbered steps, command blocks, tables) but the Overview over-explains what OpenVEX/VEX is — a concept a competent model largely knows — and some prose could be trimmed.

2 / 3

Actionability

Provides fully executable commands (go install, vexctl create/merge/attest with concrete flags), jq validation queries, a CI YAML block, and a copy-paste-ready worked example with an exact purl.

3 / 3

Workflow Clarity

A clear 9-step sequence with an explicit Step 7 validation checklist plus a jq feedback loop, a CI fail-on-missing-justification gate, and a vexctl filter preview step before committing.

3 / 3

Progressive Disclosure

A single self-contained SKILL.md with well-organized sections (When to use, Steps 1–9, Example, Anti-patterns, Limitations, References) and a flat one-level reference list — no nested reference chains and no bundle files needed.

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, complete, and distinctive: it names concrete actions, an explicit Use-when trigger, and natural keywords, all in third person with no over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: produces not_affected/affected/fixed/under_investigation statements with justification codes via vexctl create, attaches VEX assertions to container images, and outputs .openvex.json files — matching the score-3 anchor for multiple specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (authors/validates OpenVEX docs, attaches, outputs) and when via a concrete 'Use when a scanner flags a CVE…' trigger clause.

3 / 3

Trigger Term Quality

Uses natural trigger terms a user would say ('scanner flags a CVE', 'not exploitable', 'false positives', 'not_affected assertion', 'VEX') with good coverage, beyond just 'some relevant keywords'.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (OpenVEX/vexctl VEX assertions for CVE false-positive suppression) with distinct triggers unlikely to overlap with other skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents