CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

building-vulnerability-exception-tracking-system

Build a vulnerability exception and risk acceptance tracking system covering approval workflows, compensating controls documentation, and automatic expiration for vulnerabilities that miss SLA remediation timelines. Use when standing up a governance process for risk acceptance and exception approvals to support PCI DSS, SOC 2, or NIST CSF compliance.

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-exception-tracking-system/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 is well-organized and lean, with a solid data model (category table, SQL schema) and a real helper script, but the implementation section is stub code rather than executable guidance, the multi-step approval workflow lacks explicit sequencing and validation checkpoints, and the existing bundle reference files are completely unsignaled.

Suggestions

Replace the stubbed Flask endpoints with complete implementations (actual DB insert, approver notification, and enforcement of the `max_days` category limits) or point users to the equivalent executable `scripts/process.py` commands (--create/--approve/--reject).

Add an explicit numbered workflow for the exception lifecycle (request → validate category/duration limits → approve → monitor → expire) with validation checkpoints, e.g., verify the exception is pending and approver level matches the category before approving.

Link the existing bundle files from the body — `references/workflows.md` for the approval/expiration workflows, `references/api-reference.md` for GRC integrations, and `assets/template.md` for request templates — so progressive disclosure actually routes readers to them.

DimensionReasoningScore

Conciseness

Mostly concrete artifacts (category table, exception schema dict, SQL DDL, cron commands) with little padding. Minor over-explanation: the Overview paragraph restates the frontmatter description and the "When to Use" section is generic boilerplate — trimmable but not substantial enough to drop to 3.

4 / 5

Actionability

Mixed executability: the SQL DDL and cron commands are runnable, but the Flask API section is stubbed — "# Insert into database and notify approvers" followed by a hardcoded `jsonify({"status": "pending", "id": "exc-12345"})`, and the `max_days` validation is computed but never enforced. This matches the anchor for incomplete guidance with pseudocode-level code rather than the mostly-executable anchor 4.

3 / 5

Workflow Clarity

The request → approve/reject → expiration-check sequence is implied by section order and API routes, but there is no explicit numbered workflow and no validation checkpoints (e.g., verifying an exception exists and is pending before approving). Per the rubric's feedback-loop rule for database/batch operations, workflow clarity is capped at 3; it is not 2 because the endpoints and daily-cron steps are present and coherent.

3 / 5

Progressive Disclosure

The body is well-sectioned and its one script reference is real (`scripts/process.py --check-expirations` / `--report` flags verified), but the bundle's `references/workflows.md`, `references/api-reference.md`, `references/standards.md`, `assets/template.md`, and `scripts/agent.py` are never mentioned or linked, so the reference material is present in the bundle but not signaled. This fits anchor 3 (references present but not clearly signaled) rather than 4, where references would be mostly clear.

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: it concretely states what the skill builds, uses natural domain trigger terms, and includes an explicit 'Use when' clause tied to named compliance frameworks. Its only weakness is missing a few natural keyword synonyms, which slightly limits recall.

DimensionReasoningScore

Specificity

The description lists multiple concrete capabilities — "approval workflows, compensating controls documentation, and automatic expiration for vulnerabilities that miss SLA remediation timelines" — comprehensively covering the system's functions. It is not 4 because the action coverage is complete for this system type, with no notable gaps.

5 / 5

Completeness

Explicitly answers both: what — "Build a vulnerability exception and risk acceptance tracking system covering approval workflows... and automatic expiration" — and when — "Use when standing up a governance process for risk acceptance and exception approvals to support PCI DSS, SOC 2, or NIST CSF compliance" with concrete trigger contexts.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "vulnerability exception", "risk acceptance", "compensating controls", "SLA remediation", "PCI DSS, SOC 2, or NIST CSF". It is not 5 because common variations such as "exception request", "waiver", or "remediation extension" are missing, so keyword coverage is good but not exhaustive.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (exception/risk-acceptance tracking for missed SLA remediation) with framework-specific triggers, making it unlikely to fire for adjacent skills like general vulnerability scanning or remediation. Minor adjacency to generic GRC skills exists, but the triggers ("exception", "risk acceptance", "compensating controls") are distinct, matching the anchor 5 example's clarity rather than anchor 4's overlap risk.

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-exception-tracking-system/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.