CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

netexec

NetExec (CrackMapExec successor) — unified SMB/LDAP/MSSQL/WinRM/RDP/SSH/FTP/VNC protocol auth + post-auth modules. 200+ modules incl. BloodHound auto-ingest, ESC1-15 scanning, PrintNightmare, LDAP relay.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/ad/netexec/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 dense, highly actionable command playbook that respects Claude's intelligence with minimal conceptual explanation. Its main weaknesses are absent validation/verification checkpoints for batch and destructive operations (capping workflow clarity) and a padded 'Known exemplars' section with dated, unverifiable claims.

Suggestions

Add explicit validation checkpoints around batch/destructive operations, e.g., verify JSON output was written before parsing, confirm lockout policy before spraying, and re-check failed hosts — this lifts the workflow-clarity cap.

Remove or relocate the 'Known exemplars' statistics ('~80% of OSCP-style engagements') and isolate version/date-sensitive details (pinned commit, 'archived 2023') into a clearly labeled version note.

Either complete the Decepticon integration snippet (missing shlex/json/Path imports, no error handling) or move it to scripts/ as an executable file referenced from the body.

DimensionReasoningScore

Conciseness

The core is lean — command blocks with one-line comments — but several sections could be trimmed: 'Known exemplars' pads with unverifiable statistics ('used in ~80% of OSCP-style Windows engagements'), 'The Swiss-army knife of Windows / AD pentest' is fluff, and time-sensitive details (pinned commit hash, 'archived 2023', '2023-2024') are not isolated in a deprecated/old-patterns section as the rubric prefers. Not a 2 because the majority of tokens are actionable commands.

3 / 5

Actionability

Nearly all guidance is copy-paste ready: full nxc invocations with flags, hashcat modes (-m 13100, -m 18200), and an nxcdb session transcript. Minor gaps keep it below 5: the Python 'skeleton' uses shlex, Path, and json without importing them and has no real error handling, and placeholders like $DC/$PW are never defined.

4 / 5

Workflow Clarity

Numbered sections (install → sweep → modules → output) give a recognizable sequence and §6 offers a verification grep ('(Pwn3d!)'), but there are no explicit validation checkpoints or feedback loops. Because the skill's core operations are batch and potentially destructive (subnet sweeps, NTDS dump, password spray), the rubric caps workflow clarity at 3 without validation steps.

3 / 5

Progressive Disclosure

No bundle files exist, and the ~170-line body is well organized under numbered headers appropriate for a command playbook. Minor gaps: the Decepticon Python skeleton is content that could live in scripts/, and cross-references point to sibling skills outside this bundle rather than to navigable reference files.

4 / 5

Total

14

/

20

Passed

Description

66%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 specific, tool-scoped description with strong capability naming and good natural keywords, but it omits any explicit 'when to use' trigger guidance, which the rubric treats as a completeness cap. Moving the trigger terms from metadata.when_to_use into the description itself would address the main weakness.

Suggestions

Append a 'Use when...' clause to the description with concrete triggers, e.g., 'Use when running nxc/cme/crackmapexec commands, spraying or sweeping credentials across SMB/LDAP/WinRM, or enumerating AD.

Include the natural abbreviations users actually type — 'nxc' and 'cme' — in the description text, not only in metadata.when_to_use.

Trim technique names that overlap sibling skills (e.g., keep 'BloodHound auto-ingest' but rely on cross-references for ESC1-15) to reduce conflict risk with dedicated ADCS/BloodHound skills.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities — 'unified SMB/LDAP/MSSQL/WinRM/RDP/SSH/FTP/VNC protocol auth + post-auth modules', 'BloodHound auto-ingest', 'ESC1-15 scanning', 'PrintNightmare', 'LDAP relay' — with only minor coverage gaps (e.g., output formats, credential dumping). Not a 5 because the capabilities are named mostly as noun phrases rather than actions and coverage is not comprehensive.

4 / 5

Completeness

The 'what' is clearly answered (protocol auth + post-auth modules with named techniques), but the description contains no 'Use when...' clause or equivalent explicit trigger guidance — the trigger keywords are relegated to a separate metadata field. Per the rubric guideline, a missing 'when' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'NetExec', 'CrackMapExec', protocol names (SMB, LDAP, WinRM, RDP, SSH), 'BloodHound', 'PrintNightmare'. A few natural terms users would say are missing from the description itself — the abbreviations 'nxc'/'cme' and phrases like 'password spray' or 'sweep' appear only in metadata.when_to_use, not the description.

4 / 5

Distinctiveness Conflict Risk

The NetExec/CrackMapExec tool naming gives a clear, distinct niche unlikely to trigger the wrong skill. Minor overlap risk remains with closely related dedicated skills: 'BloodHound auto-ingest' and 'ESC1-15 scanning' could pull triggers meant for standalone BloodHound or ADCS skills.

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

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/ad/netexec/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.