CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

building-vulnerability-dashboard-with-defectdojo

Deploy DefectDojo as a centralized vulnerability management dashboard that ingests findings from 200+ security scanners, deduplicates results, tracks remediation metrics, and integrates with CI/CD, Jira ticketing, and Slack notifications via its REST API. Use when consolidating scanner output into one dashboard or automating vulnerability ticketing and executive reporting.

Quality

79%

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/building-vulnerability-dashboard-with-defectdojo/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 strong, mostly executable deployment and API-integration guidance, but it is padded with a redundant overview and boilerplate, omits validation around batch scan-import operations, and completely fails to signal its own bundle files — leaving references/, scripts/, and assets/ orphaned while duplicating some of their content inline.

Suggestions

Delete the Overview and generic 'When to Use' sections (the frontmatter description already covers both) and remove the inlined scanner table in favor of a pointer to references/api-reference.md.

Add validation after each API call — check the HTTP status code and verify imported findings (e.g., GET /api/v2/findings/?test=<id>) — especially around batch reimport-scan operations, and include an error-recovery step.

Add a navigation section that links each bundle file with its purpose (e.g., 'Full API endpoints: see references/api-reference.md; ready-made automation: scripts/process.py; hierarchy template: assets/template.md') so the existing reference, script, and asset files are discoverable.

DimensionReasoningScore

Conciseness

The body is mostly dense, useful code, but the Overview paragraph restates the frontmatter description almost verbatim and "When to Use" is generic boilerplate ("When deploying or configuring building vulnerability dashboard with defectdojo capabilities in your environment"), and the Supported Scanner Types table duplicates the table already in references/api-reference.md. These are unnecessary tokens that could be trimmed, matching the 'mostly efficient but could be tightened' anchor rather than the 'several padded sections' anchor at 2, since the bulk of the content is concrete commands and code.

3 / 5

Actionability

Deployment commands ("./dc-up-d.sh", "docker compose logs initializer 2>&1 | grep 'Admin password'"), curl upload commands with real scan_type values, and a GitHub Actions workflow are largely copy-paste ready. It stops short of 5 because the metrics snippets never use the response (findings = resp.json() with no follow-up), the Jira "configuration" is an illustrative dict rather than actual executable configuration, and no API call checks its HTTP status.

4 / 5

Workflow Clarity

Sections follow a sensible sequence (deploy → configure → create hierarchy → import scans → integrate CI/CD and Jira → report metrics) with one checkpoint ("docker compose ps", checking initializer logs), but every API interaction lacks validation — no status-code checks, no verification that findings were imported or deduplicated. Because reimport-scan is a batch operation on existing findings with no validation or feedback loop, workflow clarity is capped at 3 per the rubric's scoring notes.

3 / 5

Progressive Disclosure

The body itself is well-sectioned, but none of the six bundle files (references/api-reference.md, standards.md, workflows.md, scripts/agent.py, scripts/process.py, assets/template.md) are referenced anywhere in the body — the References section lists only external URLs — and the scanner table and API query details that belong in references/api-reference.md are inlined instead. This matches 'references present but not clearly signaled; content that should be separate is inline'; it is not 2 because the body is clearly structured rather than a minimal or monolithic dump.

3 / 5

Total

13

/

20

Passed

Description

92%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: concrete, third-person, comprehensive action list paired with an explicit 'Use when' trigger clause naming the tool and its ecosystem. The only weakness is that a handful of natural synonym phrases (e.g., 'scan results', 'vulnerability findings') are absent from the trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Deploy DefectDojo", "ingests findings from 200+ security scanners", "deduplicates results", "tracks remediation metrics", "integrates with CI/CD, Jira ticketing, and Slack notifications via its REST API" — covering the full capability set. This matches the anchor for comprehensive concrete actions; it is not score 4 because there are no noticeable coverage gaps in what the skill's body actually delivers.

5 / 5

Completeness

Explicitly answers both questions: the "what" is the deploy/ingest/deduplicate/track/integrate action list, and the "when" is the concrete trigger clause "Use when consolidating scanner output into one dashboard or automating vulnerability ticketing and executive reporting". This mirrors the score-5 anchor example's structure; score 4 would require the 'when' to be less explicit, which it is not.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "vulnerability management dashboard", "consolidating scanner output", "vulnerability ticketing", "executive reporting", plus tool/ecoystem names (DefectDojo, CI/CD, Jira, Slack) users would actually say. It falls short of the score-5 anchor because a few common variants are missing (e.g., "scan results", "vulnerability findings", "AppSec/DevSecOps metrics").

4 / 5

Distinctiveness Conflict Risk

Naming the specific tool (DefectDojo) with its distinctive trigger activities (scanner consolidation, dedup, Jira/Slack integration) establishes a clear niche with minimal conflict risk — it would only collide with another DefectDojo-specific skill. It is not score 4 because there is no meaningful overlap with generic dashboard or reporting skills.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/building-vulnerability-dashboard-with-defectdojo/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.