CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recon-workbench

Run, audit, and design authorized Recon Workbench workflows when scoped target interrogation needs evidence artifacts, redaction, validation, and safe reporting.

Quality

72%

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/security-ops/recon-workbench/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An extremely disciplined, token-efficient runbook body whose safety constraints and failure handling are exemplary. Its weaknesses are operational concreteness — the rwb entrypoint and its subcommands are never named, so nothing in the body is directly executable — and a Progressive Disclosure section that points at several paths missing from the bundle.

Suggestions

Name the actual entrypoint and at least the primary commands inline (e.g., the literal `rwb doctor` / `rwb run` invocations) instead of "the documented rwb entrypoint", so the workflow steps are executable without consulting external docs.

Fix the dangling references: either include the Infrastructure/references/ lens-pack, expertise-map, and deferred-skill-context files in the bundle or re-point those lines to files that exist (e.g., under references/).

Reorder the Workflow section so authorization confirmation is step one and number the steps (authorize → plan → run read-only → escalate → summarize/validate), making the sequence and its checkpoints explicit.

DimensionReasoningScore

Conciseness

The body is uniformly terse directive bullets ("Start read-only and escalate only when permitted and justified", "Fail fast: stop at first failed gate") with zero concept explanations, filler, or padding — every token is a rule or constraint Claude does not already know. It matches the 5 anchor: lean, efficient, assumes Claude's competence.

5 / 5

Actionability

The body gives concrete policy guidance (exact section titles, redaction targets, stop conditions) but the executable mechanics are missing: it says "Use the documented rwb entrypoint inside a Recon Workbench checkout" without ever naming the command, and the Validation section demands "exact commands, outcomes, and blockers" without providing any. This fits the 3 anchor (some concrete guidance but incomplete, missing key details) better than 4, whose guidance is mostly executable.

3 / 5

Workflow Clarity

The Workflow section lists real steps and the Failure Mode/Validation sections supply checkpoints ("stop with a blocked result instead of probing", fail-fast rerun loop), so validation is not absent. But the sequence is unnumbered and partially unordered — "Start with 2-3 focused surfaces before expanding scope" appears before "Confirm authorization, target, scope" — and no command-level step ordering exists, matching the 3 anchor (sequence present but checkpoints/sequence implicit) rather than the cleanly sequenced 4.

3 / 5

Progressive Disclosure

The bundle's references (contract.yaml, evals.yaml, task-profile.json) are all real and clearly signaled in a dedicated "Progressive Disclosure" section, which is good. However, three of the referenced paths — "Infrastructure/references/software-literature-expert-lens-pack.md", ".../software-literature-skill-expertise-map.md", and ".../deferred-skill-context/security-ops-recon-workbench/" — do not exist in the bundle, leaving dangling navigation. That is more than the "minor organization gaps" of the 4 anchor, fitting the 3 anchor (references present but with structural problems).

3 / 5

Total

14

/

20

Passed

Description

67%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 solid, third-person description that answers both what and when with a distinct named-tool niche. Its main weakness is trigger phrasing written in internal jargon rather than the terms users actually type (rwb, doctor, manifest, probe plan), which costs trigger-term quality.

Suggestions

Include the natural invocation terms users would type, e.g. append "Use when the user asks to run rwb doctor, authorize, plan, run, summarize, manifest, validate, or reconcile" or mention the "rwb" abbreviation.

Rewrite the when-clause in user voice rather than internal jargon: replace "when scoped target interrogation needs evidence artifacts" with concrete situations like "when running authorized recon probes or producing evidence-backed findings reports".

Make "safe reporting" concrete (e.g., "produce redacted, validation-checked findings reports") so the capability reads as an action rather than an abstraction.

DimensionReasoningScore

Specificity

"Run, audit, and design authorized Recon Workbench workflows" names the domain and three concrete actions, and the conditional clause adds further capabilities ("evidence artifacts, redaction, validation, and safe reporting"). It falls short of the 5 anchor because several of those capabilities are stated abstractly (e.g., "safe reporting") without the concrete operations behind them.

4 / 5

Completeness

Both what ("Run, audit, and design authorized Recon Workbench workflows") and when ("when scoped target interrogation needs evidence artifacts, redaction, validation, and safe reporting") are present, satisfying the requirement of an explicit trigger clause. The when-clause is conditional and jargon-heavy ("scoped target interrogation") rather than user-phrased, matching the 4 anchor where "when" could be more explicit.

4 / 5

Trigger Term Quality

Terms like "Recon Workbench", "audit", "validation", and "redaction" are relevant, but the description omits the natural variations users of this tool would actually say — the "rwb" abbreviation and the subcommands surfaced in the body (doctor, authorize, plan, run, summarize, manifest, validate, reconcile). It matches the 3 anchor (some relevant keywords, missing common variations) rather than 4, which requires good coverage of natural terms.

3 / 5

Distinctiveness Conflict Risk

The named tool ("Recon Workbench") plus the authorization-scoped recon framing carves a clear niche with minimal conflict risk. Broad terms like "audit" and "validation" give minor overlap with general security/code-audit skills, so it fits the 4 anchor rather than the fully distinct 5.

4 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

Skills/security-ops/recon-workbench/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.