CtrlK
BlogDocsLog inGet started
Tessl Logo

sast-report

Consolidate all SAST vulnerability results from the sast/ folder into a single final report ranked by severity and confidentiality impact. Reads all *-results.md files and produces sast/final-report.md. Run after all vulnerability detection skills complete. Use when asked to generate a final report, consolidate findings, or summarize security results.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

The canonical home for this skill is sast-report in utkusen/sast-skills

SKILL.md
Quality
Evals
Security

Quality

Content

68%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 actionable, well-structured report-generation skill that avoids over-explaining basics, but its batch workflow lacks an explicit validation checkpoint and the large output template is inlined rather than referenced.

Suggestions

Add an explicit validation checkpoint after Step 4 — e.g., verify all existing sast/*-results.md files were read, every VULNERABLE/LIKELY VULNERABLE finding appears in the report, and no Proof/Remediation/Dynamic Test section was truncated — to lift workflow clarity above the batch-operation cap of 3.

De-duplicate the file list: the 13 result files are enumerated both in Step 1 and again in the Appendix scan-coverage table; reference one from the other to tighten conciseness.

Consider moving the full output-format template (~90 lines) into a references/ file (e.g. REPORT_TEMPLATE.md) referenced from the body, reducing inline weight while keeping the template copy-paste ready.

DimensionReasoningScore

Conciseness

Dense and purposeful with no padding of concepts Claude already knows, but the 13-file discovery list in Step 1 is duplicated by the Appendix scan-coverage table, a minor trim opportunity.

4 / 5

Actionability

Provides a copy-paste output template, explicit classification markers, and an exhaustive severity-tier table, but High/Medium/Low sections use '[Same structure]' shorthand and placeholder rows rather than fully fleshed examples.

4 / 5

Workflow Clarity

The four-step sequence (Discover, Read/extract, Score/sort, Write) is clear, but this batch consolidation over 13 result files lacks an explicit validation checkpoint confirming completeness or output well-formedness, capping the score at 3.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and a self-contained workflow, though the ~90-line output template block could arguably live in a separate reference file; no bundle files are present to offload it.

4 / 5

Total

15

/

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 concise, specific, and complete, clearly stating both the capability and the triggering contexts. It assumes a well-scoped niche with negligible conflict risk.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — consolidate SAST results, rank by severity and confidentiality impact, read *-results.md files, and produce sast/final-report.md — with comprehensive coverage of the task.

5 / 5

Completeness

Explicitly answers both what (consolidate into a final report ranked by severity and confidentiality impact) and when (Use when asked to generate a final report, consolidate findings, or summarize security results) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say — 'generate a final report', 'consolidate findings', 'summarize security results' — with good synonym coverage around reporting and security results.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (consolidating sast/*-results.md files into sast/final-report.md after detection skills run) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

20

/

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
utkusen/sast-skills
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.