CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sast-configuration

Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code. Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection.

Quality

70%

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 ./skills/sast-configuration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%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 delivers genuinely executable commands for all three tools, but suffers from triple-redundant workflow sections, feature-catalog padding, abstract high-level steps with no validation checkpoints, and references to bundle files that are missing. Consolidating the repeated workflow sections and splitting per-tool detail into the referenced files would materially improve it.

Suggestions

Collapse 'Instructions', 'Quick Start > Initial Assessment', and 'Next Steps' into one sequential workflow with concrete commands per step, removing the redundant 'Overview' and 'Use this skill when' restatements.

Add validation checkpoints to the workflow (e.g., verify the baseline scan ran and produced SARIF output, confirm the quality gate blocks a deliberately introduced test finding, re-review suppressions after tuning) so CI gating changes are verified rather than assumed.

Either create the referenced files (references/semgrep-rules.md, scripts/run-sast.sh) or remove the references, and move per-tool capability catalogs, the tool comparison table, and troubleshooting into one-level-deep reference files.

DimensionReasoningScore

Conciseness

The body pads heavily: the 'Overview' section restates the opening line, 'Use this skill when' repeats the frontmatter triggers, and the same workflow appears three times ('Instructions', 'Quick Start > Initial Assessment', 'Next Steps'). The 'Core Capabilities' section is a feature catalog ('Quality gate configuration', 'Security hotspot analysis') that adds no instruction, matching 'noticeably verbose; several unnecessary explanations or padded sections'. It is above a 1 because there is no long tutorial-style explanation of concepts Claude doesn't know.

2 / 5

Actionability

Mostly executable guidance: concrete install/run commands for semgrep, sonarqube, and codeql, a GitHub Actions YAML snippet, a pre-commit config, and a plausible custom-rule YAML. It falls short of 5 because './scripts/run-sast.sh --setup ...' points to a script that does not exist in the bundle, and some snippets (pre-commit rev pin 'v1.45.0', CI fragment) are incomplete or version-fragile rather than copy-paste ready.

4 / 5

Workflow Clarity

A sequence exists ('Identify languages... Choose tools... Integrate scans... Tune rules... Track remediation') but the steps are abstract one-liners with no validation checkpoints — nothing on verifying a scan succeeded, confirming a quality gate blocks correctly, or re-running after suppression changes. This matches 'Steps listed but validation gaps; checkpoints missing or implicit'. It is not a 2 because the ordering is coherent and tool-specific quick-start commands do follow the steps.

3 / 5

Progressive Disclosure

The body has real section structure, but content that belongs in separate files (per-tool capability catalogs, tool comparison table, troubleshooting) is inlined, and the two paths it does cite — 'references/semgrep-rules.md' and './scripts/run-sast.sh' — do not exist in the bundle, so the signaled references are broken. That fits 'some structure but could be better organized; references present but not clearly signaled' territory, kept at 3 rather than 2 because sections are well-organized and the reference is explicitly signaled, not buried.

3 / 5

Total

12

/

20

Passed

Description

78%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 description with explicit 'what' and 'when' coverage and natural trigger phrases. Its main limitation is breadth of specifics — a single concrete action and no tool names or synonyms like 'static analysis' — which slightly caps specificity and trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Configure Static Application Security Testing (SAST) tools') and one concrete action ('automated vulnerability detection in application code'), but stops short of the several specific actions (e.g., custom rule creation, CI/CD integration, false-positive tuning) a 4 would list. It sits above the 'names the domain, minimal actions' anchor of 2 because the action is concrete and purposeful.

3 / 5

Completeness

It explicitly answers both questions: the 'what' ('Configure SAST tools for automated vulnerability detection in application code') and the 'when' with three concrete trigger phrases ('Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection'). This matches the anchor example structure exactly; a 4 would require the 'when' to be weaker or less explicit than it is here.

5 / 5

Trigger Term Quality

Phrases like 'setting up security scanning', 'implementing DevSecOps practices', and 'automating code vulnerability detection' are natural things a user would say. It misses common variations such as 'static analysis', 'code scanning', 'CI/CD', or tool names (Semgrep, SonarQube, CodeQL), keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

SAST tool configuration is a clear niche, distinct from DAST or manual penetration testing. However, 'security scanning' and 'vulnerability detection' are moderately broad terms that could overlap with closely related skills such as dependency scanning or container security, so it does not fully meet the 'minimal conflict risk' bar of a 5.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 3 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

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