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

73%

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

Quality

Content

57%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 concrete, runnable commands for all three tools and real-world use cases, but it is undermined by duplicated content, a feature-menu section that adds no instruction, and workflows that lack any validation or feedback checkpoints. With no reference files, everything from tool comparison to troubleshooting is inlined, making the skill heavier than it needs to be.

Suggestions

Add validation checkpoints to the workflows, e.g. after setup: 'Run semgrep --config=auto on the repo and confirm findings render as SARIF before wiring into CI', and in Next Steps: 'Verify the quality gate blocks on critical findings with a test scan'.

Remove the duplicated Quick Start code block under 'New Project Setup' (keep one canonical copy) and drop or compress the 'Overview'/'Core Capabilities' sections that restate the description.

Split per-tool depth (Semgrep rule authoring, SonarQube quality gate config, CodeQL query development) into references/ files linked from a lean overview, and turn vague Troubleshooting bullets into specific commands.

DimensionReasoningScore

Conciseness

The 'Overview' section repeats the frontmatter description almost verbatim, the Quick Start Semgrep commands ('pip install semgrep', 'semgrep --config=auto --error') are duplicated verbatim under 'New Project Setup', and 'Core Capabilities' is a descriptive feature menu rather than instruction. Not 2 because it never explains concepts Claude already knows and the code blocks are tight; not 4 because the duplication and padded bullet lists exceed minor trimming.

3 / 5

Actionability

Mostly executable guidance with concrete, copy-paste commands ('docker run -d --name sonarqube -p 9000:9000 sonarqube:10.8-community', 'gh extension install github/gh-codeql', 'codeql database create mydb --language=python', 'semgrep --config p/pci-dss --json -o pci-scan-results.json') plus a complete custom-rule YAML. Not 5 because Troubleshooting and Best Practices give high-level direction ('Review and tune rule sensitivity', 'Parallelize scans across modules') without specific commands; not 3 because the majority of guidance is directly runnable.

4 / 5

Workflow Clarity

Sequences are present and ordered ('Initial Assessment' steps 1-4, 'Next Steps' 1-6) but contain no validation checkpoints — nothing like verifying scan output, confirming a quality gate blocks on critical findings, or a fix-and-rerun loop. Not 2 because steps are clearly numbered and coherent; not 4 because checkpoints are wholly absent rather than having minor gaps.

3 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), so ~190 lines covering three tools, CI integration, compliance, and troubleshooting all sit inline in SKILL.md. Sections are well-labeled, but per-tool depth belongs in separate reference files and the only file links present are unverifiable cross-skill links. Not 4 because at this breadth the content should be split; not 2 because the document is structured and navigable.

3 / 5

Total

13

/

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: it uses third person, explicitly covers both what the skill does and when to use it, and includes natural trigger phrases. The main gaps are modest specificity (only one core action is stated) and missing tool-name keywords that users would commonly name.

Suggestions

Add the covered actions to the 'what' clause, e.g. 'Configure SAST tools (Semgrep, SonarQube, CodeQL), create custom security rules, and set up scanning in CI/CD pipelines for automated vulnerability detection.'

Include tool names and the synonym 'static analysis'/'code scanning' in the trigger clause so users who name a specific tool or phrase still match.

DimensionReasoningScore

Specificity

Names the domain and one to two concrete actions ('Configure Static Application Security Testing (SAST) tools for automated vulnerability detection in application code') but omits the skill's other actions such as custom rule creation, quality gate configuration, and CI/CD integration. Not 4 because the action list is not comprehensive; not 2 because the stated actions are concrete rather than generic.

3 / 5

Completeness

Explicitly answers both what ('Configure SAST tools for automated vulnerability detection in application code') and when ('Use when setting up security scanning, implementing DevSecOps practices, or automating code vulnerability detection') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('setting up security scanning', 'implementing DevSecOps practices', 'automating code vulnerability detection'). Not 5 because it misses tool names users would mention (Semgrep, SonarQube, CodeQL) and synonyms like 'static analysis' or 'code scanning'; not 3 because keyword coverage is genuinely good with multiple natural trigger phrasings.

4 / 5

Distinctiveness Conflict Risk

'SAST tool configuration' is a clear niche with distinct triggers. Not 5 because broad triggers like 'security scanning' and 'vulnerability detection' overlap with adjacent security skills (the body itself links sibling security skills); not 3 because tool-configuration framing is well differentiated from generic security work.

4 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

wshobson/agents

Path

plugins/security-scanning/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.