CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cyber-engagement-planning

Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates. Use when preparing an exercise or assessment plan before execution.

Quality

81%

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

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.

The content is a lean, guardrail-oriented planning skill with a clear eight-step workflow, concrete field and role enumerations, and a properly linked reference template. It falls short of top marks due to duplication between Workflow and Rules sections, no inline example or revision feedback loop, and a Structure tree that does not match the actual bundle contents.

Suggestions

Deduplicate the positive-continuation and restart-gate guidance: state it once (either in the Workflow or the Rules section) instead of repeating nearly identical text in steps 7-8 and Rules bullets 3-4.

Fix the Structure tree to match the actual bundle: evals/evals.json is listed but does not exist, which misleads about the bundle layout.

Add a brief filled-in example engagement brief (or a final pre-issue review checklist step) so the workflow closes with an explicit validation checkpoint before the plan is handed off.

DimensionReasoningScore

Conciseness

The body is dense and directive with no explanations of concepts Claude already knows, but Workflow steps 7-8 ("Positive continuation: When required runtime support is absent..." and "Restart requires both current authorization and verified host enforcement") nearly duplicate Rules bullets on the same topics, and the AC-CLV-09/AC-CLV-19 codes are repeated without explanation — minor trimming is possible, matching anchor 4 rather than the every-token-earns-its-place anchor 5.

4 / 5

Actionability

As an instruction-only planning skill it provides concrete enumerations (per-step modes, six named roles, explicit evidence fields like `engagement_scope_ref` through `accountable_owner`, and named exclusions) backed by a real one-level-deep template in references/engagement-brief.md, but it offers no inline filled example of a completed plan, leaving minor gaps versus fully executable anchor-5 guidance.

4 / 5

Workflow Clarity

The eight steps are clearly sequenced from objective through restart gates and include explicit checkpoints ("cycles or missing producer IDs reject before dispatch", restart prerequisites, `blocked/unsupported-runtime` marking), but there is no feedback loop for revising a rejected plan or a final review checklist before the plan is issued, fitting anchor 4 rather than anchor 5.

4 / 5

Progressive Disclosure

The ~45-line body is well organized with clearly signaled references, and references/engagement-brief.md verifiably exists one level deep; however, the Structure tree lists `evals/evals.json` which is absent from the actual bundle, and three of four reference links point to sibling skills outside the bundle that cannot be verified, matching anchor 4's minor organization gaps rather than anchor 5.

4 / 5

Total

16

/

20

Passed

Description

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

The description is strong: it answers both what and when explicitly, uses third person, and enumerates comprehensive, concrete plan components without fluff. Its only weaknesses are a single action verb limiting the specificity ceiling and omission of common synonyms (rules of engagement, pentest, red team) that users might naturally say.

DimensionReasoningScore

Specificity

"Drafts bounded cybersecurity engagement plans with objectives, scope, exclusions, roles, authorization, runtime controls, evidence, stop criteria, and restart gates" enumerates nine specific deliverable components with comprehensive domain coverage, but centers on a single action verb (drafting) rather than the multiple distinct concrete actions of the anchor-5 example.

4 / 5

Completeness

"Drafts bounded cybersecurity engagement plans with..." clearly states what the skill does, and "Use when preparing an exercise or assessment plan before execution" explicitly states when to use it with concrete trigger phrases, matching the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

"engagement plans", "exercise", "assessment plan", and "cybersecurity" are natural phrases users would say, matching good keyword coverage; common synonyms such as "rules of engagement", "penetration test", or "red team" appear only in the frontmatter triggers, not the description, keeping it below comprehensive anchor-5 coverage.

4 / 5

Distinctiveness Conflict Risk

"bounded cybersecurity engagement plans" and the pre-execution planning framing establish a clear niche with distinct triggers, but "assessment plan" and "exercise" carry minor overlap risk with closely related security-assessment and lab-validation skills, fitting anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

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

Warning

Total

12

/

16

Passed

Repository

HoangNguyen0403/agent-skills-standard

Path

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