CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cyber-evidence

Captures redacted, provenance-aware cybersecurity observations with shared status fields, independent ground truth, and honest limitations. Use when recording exercise evidence, findings, validation results, or security-review handoffs.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 tight, well-structured instructional skill: concrete enums, field contracts, and guardrail rules make it actionable, and the heavy schema is properly pushed to a single one-level reference. Main weaknesses are mild redundancy between Workflow and Rules, no inline example record, and two declared/referenced paths that do not resolve.

Suggestions

Consolidate the finding_status and outcome enum guidance, which currently appears in both Workflow steps 4-5 and the Rules section, into one location to remove restatement.

Add one short, fully filled-in example evidence record (with redaction applied) inline so the field contract is unambiguous without opening the reference file.

Fix the structural references: either include the declared evals/evals.json in the bundle or remove it from the Structure section, and verify the ../../common/common-security-audit/references/trust-review-policy.md path resolves.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no basic-concept explanations, every rule carries domain-specific substance (e.g., "Correlation key (run_id, attempt_id, test_id) is immutable per attempt"). It is not anchor 5 because finding-status guidance is restated between Workflow steps 4-5 and the Rules section, which could be consolidated.

4 / 5

Actionability

Guidance is concrete and executable for an instruction-only skill: exact field names, closed enums ("confirmed, suspected, blocked, not-tested, false-positive"), and precise guardrails ("never false-positive without independent invalidating evidence"). The gap versus anchor 5 is that no complete filled-in example record appears inline — the canonical schema is deferred to the reference file.

4 / 5

Workflow Clarity

The 7-step workflow is clearly sequenced with paired/unpaired branching (step 3) and supporting guardrails (rejected conflicting correlation keys, independent-review promotion). It falls short of anchor 5 because validation checkpoints live in the Rules section rather than being explicit validate-then-proceed steps inside the workflow itself.

4 / 5

Progressive Disclosure

The overview is well-organized with clearly signaled one-level-deep references, and the bulk canonical schema is correctly split into references/evidence-record.md, which exists. It is not anchor 5 because the declared structure lists evals/evals.json which is absent from the bundle, and the referenced ../../common/common-security-audit/references/trust-review-policy.md path is unresolvable from the skill directory.

4 / 5

Total

16

/

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: it states a concrete, differentiated capability in third person and pairs it with an explicit 'Use when' trigger clause covering the main use cases. The only improvement space is broader trigger-term coverage (synonyms like pen test or red team evidence) and slightly fuller enumeration of distinct actions.

DimensionReasoningScore

Specificity

Names concrete, well-modified actions and objects — "Captures redacted, provenance-aware cybersecurity observations", "recording exercise evidence, findings, validation results, or security-review handoffs" — with only minor coverage gaps. It falls short of anchor 5 because the core capability is a single capture/record verb rather than a comprehensive list of distinct actions.

4 / 5

Completeness

Explicitly answers both questions: the first sentence states clearly what the skill does ("Captures redacted, provenance-aware cybersecurity observations with shared status fields...") and the second gives an explicit "Use when" clause with concrete trigger phrases. This matches anchor 5 exactly, and is not anchor 4 since the 'when' guidance is fully explicit rather than merely adequate.

5 / 5

Trigger Term Quality

The "Use when recording exercise evidence, findings, validation results, or security-review handoffs" clause contains natural phrases users in this domain would say. Common variations like "pen test results", "red team evidence", or "security assessment" are missing, so it matches anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — redacted, provenance-aware cybersecurity evidence records with status fields — and its triggers (exercise evidence, validation results, security-review handoffs) are unlikely to fire for unrelated skills. Minimal conflict risk matches anchor 5.

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: 1 suspicious

Warning

Total

12

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

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