CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cyber-detection-validation

Validates defensive controls with paired authorized action and observation evidence, distinguishing blocked, prevented, detected, responded, and telemetry-gap outcomes. Use for purple-team validation design or offline fixture review; not unsanctioned testing or production efficacy claims.

Quality

87%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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.

A lean, highly operational governance skill: dense rules, a sequenced workflow with gates, and clean structure with one-level references. The only gaps are the absence of a worked evidence-record example and an explicit error-recovery loop, which keep actionability and workflow clarity at 4.

DimensionReasoningScore

Conciseness

The ~40-line body is dense and operational throughout — binding chains, mode definitions, enum semantics, teardown states — with zero padding and no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Guidance is concrete for an instruction-only skill (named modes, correlation key '(run_id, attempt_id, test_id)', full enum definitions, CleanupResult states), but there is no worked example of a filled ActionReceipt/ObservationRecord and some mechanics defer to external files, leaving minor gaps.

4 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced with real checkpoints (fresh host gate before dispatch, transitive binding enforcement, teardown with recorded CleanupResult), but an explicit error-recovery feedback loop (e.g., what to do when the binding chain is rejected) is only implied.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections (Priority, Input/Process/Output, Workflow, Rules, Anti-Patterns, References) and clearly signaled one-level-deep references in a dedicated section; the simple-skill exception applies and no bundle files are needed inline.

5 / 5

Total

18

/

20

Passed

Description

87%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 capability statement, explicit use-when guidance with boundary exclusions, and natural domain trigger terms. It is slightly narrower in action coverage and keyword variation than the best examples, but well above the midpoint on every dimension.

DimensionReasoningScore

Specificity

The description names a concrete action ('Validates defensive controls with paired authorized action and observation evidence') plus a precise five-outcome taxonomy (blocked, prevented, detected, responded, telemetry-gap), but centers on a single core action rather than the comprehensive multi-action coverage of the top anchor.

4 / 5

Completeness

It explicitly answers both what ('Validates defensive controls with paired authorized action and observation evidence, distinguishing... outcomes') and when ('Use for purple-team validation design or offline fixture review') with concrete trigger phrases and explicit boundary exclusions ('not unsanctioned testing or production efficacy claims').

5 / 5

Trigger Term Quality

'purple-team validation design', 'offline fixture review', and 'telemetry-gap' are terms a user would naturally say in this domain, giving good keyword coverage, though common variations like 'detection testing' or 'control testing' are absent.

4 / 5

Distinctiveness Conflict Risk

The paired-evidence purple-team validation framing carves a clear niche with distinct triggers; the negative boundary clause further reduces the risk of firing for adjacent security skills.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 5 suspicious

Warning

Total

12

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

.agents/skills/cybersecurity/cyber-detection-validation/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.