CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

postexploit-specialist-methods

Evidence-led postexploit technical methods and evidence interpretation for the relevant environment.

Quality

71%

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 ./packages/decepticon/decepticon/skills/standard/post-exploit/specialist-methods/SKILL.md
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.

The body is a lean, high-signal evidence standard: it states exactly what to record for each class of postexploit claim (shells, credentials, file transfers, C2 callbacks, cleanup) and what does not count as proof, with no over-explanation and no padding. Its main gaps are the absence of a worked example of a recorded evidence entry and its reliance on sibling technique skills for implementation details.

DimensionReasoningScore

Conciseness

The ~38-line body assumes Claude's competence — it drops "a ticket's SPN, realm and delegation constraints" without explanation — and every sentence is directive (what to record, what counts as proof, e.g. "A successful TCP connection or a shell-like banner is not proof of code execution"). This matches 'Lean and efficient; assumes Claude's competence; every token earns its place'; nothing reads as padding to trim.

5 / 5

Actionability

The guidance is concrete and specific for an instruction-only skill — "record protected artifact paths, source identity, credential type, validity window and the service where use was actually validated" and "record source/destination paths, hash and byte count" are near-checklist directives. It stops short of anchor 5 because there is no worked example of a recorded evidence entry and implementation details are deferred to sibling technique skills ("Use the relevant existing technique skills for implementation details").

4 / 5

Workflow Clarity

Content is organized by claim type with explicit evidentiary checkpoints ("Privilege and lateral-access claims require before/after identity and a concrete observable at each claimed hop") and explicit handling of missing information ("Separate attempted actions, observed defender events and unavailable telemetry"). It is not anchor 5 because no sequence or validate-fix-retry loop is given — the skill deliberately disclaims defining "an engagement stage order" — leaving the workflow implicit.

4 / 5

Progressive Disclosure

The body is under 50 lines, self-contained, and organized into two clear sections ("Access and credential evidence", "State changes and transport") with no external file references needed, matching the rubric exception where short simple skills score 5 on well-organized sections alone. No bundle files exist and none are referenced, so there is no buried or nested content.

5 / 5

Total

18

/

20

Passed

Description

45%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 identifies a real niche (evidence-led postexploit methods) but reads as a domain label rather than a capability statement: no concrete actions, no trigger clause, and vague filler. Adding an explicit 'Use when...' sentence with natural trigger terms would address its weakest dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when making or verifying post-exploitation claims (shells, credential validity, lateral movement, file transfers, C2 callbacks) or deciding what counts as proof of access.'

Replace the filler 'for the relevant environment' with 1-2 concrete capabilities, e.g. 'Defines what evidence substantiates shells, credential use, privilege changes, lateral movement, file transfers, and C2 callbacks.'

Include natural trigger variations users would actually say — 'post-exploitation', 'post-exploit', 'evidence handoff', 'proof of access' — to improve trigger matching and distinguish it from sibling technique skills.

DimensionReasoningScore

Specificity

The description names the postexploit domain but its action phrases are generic — "Evidence-led postexploit technical methods and evidence interpretation" names no concrete capability, and "for the relevant environment" is filler. This matches anchor 2 ('Names the domain but actions are minimal or generic') rather than 3, which would require 1-2 concrete stated actions.

2 / 5

Completeness

The 'what' is stated ("Evidence-led postexploit technical methods and evidence interpretation") but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 4 because the 'when' is wholly absent rather than merely imprecise, and not 2 because the 'what' is domain-clear rather than vague.

3 / 5

Trigger Term Quality

"postexploit" and "evidence" are relevant terms a user might say, but natural variations and synonyms — "post-exploitation", "post-exploit", "evidence handoff", "proof of access" — are entirely missing, matching anchor 3 ('Some relevant keywords but missing common variations or synonyms'). It is not 4 because coverage is thin: only two meaningful terms appear and no natural trigger phrases.

3 / 5

Distinctiveness Conflict Risk

"postexploit ... evidence interpretation" carves out a somewhat specific niche, but the broad phrase "technical methods" invites overlap with the closely related credential, privilege, and lateral-movement technique skills that the body itself references. This matches anchor 3 ('Somewhat specific but could still overlap with similar skills'); it is not 4 because no distinct trigger phrases differentiate it from those sibling skills.

3 / 5

Total

11

/

20

Passed

Validation

87%

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

Validation — 14 / 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

Total

14

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/post-exploit/specialist-methods/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.