CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

building-vulnerability-aging-and-sla-tracking

Implement a vulnerability aging dashboard and SLA tracking system that measures time-to-remediation against severity-based deadlines (e.g. 14 days critical, 30 days high, 60 days medium, 90 days low), with automated escalations and compliance metrics reporting. Use when designing SLA policies, building aging/remediation dashboards, or proving compliance with remediation timelines.

Quality

76%

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-aging-and-sla-tracking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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-sectioned with genuinely useful domain tables and executable code, but it operates as a standalone monolith: the existing bundle of references and scripts is completely unlinked, duplicating content and even contradicting it on core SLA values. Workflow steps lack any validation checkpoints. Structural fixes around navigation and consistency would raise most dimensions.

Suggestions

Link the bundle files from the body (e.g. 'Full engine: see scripts/process.py; SLA benchmarks by standard: see references/standards.md; escalation workflows: see references/workflows.md') and remove the duplicated inline code, so progressive disclosure has one-level-deep, well-signaled navigation.

Reconcile the contradictory SLA timelines between the body (14/30/60/90 days) and references/api-reference.md plus scripts/agent.py (7/30/90/180 days) into a single authoritative table, since conflicting numbers undermine both actionability and trust.

Add validation checkpoints to the workflow, such as verifying input scan-data quality before computing aging, and validating that generated escalations and KPI outputs are non-empty and correctly bucketed before publishing dashboards.

DimensionReasoningScore

Conciseness

The domain tables (SLA framework, adaptive modifiers, KPIs) are dense and non-obvious, but the Overview pads with time-sensitive 2024 statistics ('over 30,000 new vulnerabilities identified in 2024 (a 17% increase)'), the 'When to Use' section is generic template boilerplate ('When deploying or configuring building vulnerability aging and sla tracking capabilities in your environment'), and the ~120-line code block duplicates scripts/process.py already present in the bundle. Mostly efficient with several sections that could be tightened, matching the midpoint anchor.

3 / 5

Actionability

The body provides a complete, executable pandas VulnerabilityAgingTracker class, a concrete SLA policy document template, and runnable Elasticsearch aggregation queries. It falls short of fully copy-paste-ready because the body's SLA values (14/30/60/90 days) conflict with the unlinked bundle files (scripts/agent.py and references/api-reference.md use 7/30/90/180), leaving two contradictory authoritative sources.

4 / 5

Workflow Clarity

Steps 1-3 (define SLA policy, build aging engine, dashboard visualization) are clearly sequenced, but there are no validation checkpoints: no data-quality checks on scan input, no policy sign-off gate, and no verification step for escalation or KPI output. The sequence is present but checkpoints are missing, matching the anchor for that level.

3 / 5

Progressive Disclosure

The bundle contains references/api-reference.md, references/standards.md, references/workflows.md, scripts/agent.py, scripts/process.py, and assets/template.md, yet the body never mentions or links any of them — the references are effectively buried and discoverable only by accident. Substantial content (the full aging engine, dashboard queries) is inlined where the bundle already holds equivalent (and conflicting) material, matching the 'references are buried' anchor rather than the merely 'not clearly signaled' one.

2 / 5

Total

12

/

20

Passed

Description

88%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 names concrete capabilities with specific SLA parameters and includes an explicit, well-phrased 'Use when...' clause with natural trigger terms. The only weaknesses are a few missing synonym triggers and mild overlap with a closely related remediation-SLA skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Implement a vulnerability aging dashboard and SLA tracking system that measures time-to-remediation against severity-based deadlines (e.g. 14 days critical, 30 days high, 60 days medium, 90 days low), with automated escalations and compliance metrics reporting' — with concrete parameters covering the skill's full scope. It exceeds the 'several specific actions; minor gaps' anchor because dashboard, SLA measurement, escalation, and compliance reporting are all named specifically.

5 / 5

Completeness

It explicitly answers both what ('Implement a vulnerability aging dashboard and SLA tracking system that measures time-to-remediation... with automated escalations and compliance metrics reporting') and when ('Use when designing SLA policies, building aging/remediation dashboards, or proving compliance with remediation timelines') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

'designing SLA policies, building aging/remediation dashboards, or proving compliance with remediation timelines' provides good natural keyword coverage (SLA, aging, remediation, dashboard, compliance). A few natural terms users might say are missing (e.g. MTTR, patch deadlines, vulnerability backlog), so it does not reach the 'comprehensive coverage including synonyms' anchor.

4 / 5

Distinctiveness Conflict Risk

The vulnerability aging/SLA-tracking niche is distinct with specific triggers, but it has minor overlap risk with the closely related 'implementing-vulnerability-remediation-sla' skill (listed under Related Skills), since 'proving compliance with remediation timelines' could also apply there. It is not fully 5 because of that sibling-skill overlap.

4 / 5

Total

18

/

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-aging-and-sla-tracking/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.