CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

c2

Framework-agnostic C2 orchestration — listener types, implant modes, redirector architecture, malleable profiles, jitter strategy, OPSEC guidance.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/post-exploit/c2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 well-organized operational knowledge base with genuinely concrete artifacts — executable NGINX config, specific jitter parameters, explicit checklists, and a clear decision gate. Its main weaknesses are padding with concepts Claude already knows (including a MITRE table duplicating frontmatter metadata), the absence of an end-to-end C2 setup workflow with verification steps, and a monolithic single-file structure where reference material is inlined rather than split into bundle files.

Suggestions

Trim the concept-explanation padding: drop the opening "C2 infrastructure enables persistent, covert communication..." paragraph and the "### Concept" sentence under Malleable Profiles, and remove or shrink the MITRE ATT&CK table since the same technique IDs already appear in the frontmatter metadata.

Split reference-grade material into one-level-deep bundle files — e.g. references/redirector.md for the full NGINX config and references/detection.md for the signature table — keeping SKILL.md as the overview with clearly signaled links.

Add verification/feedback steps to the workflow: how to confirm a listener is reachable and a callback is received before proceeding, and what to do when the callback fails (e.g., fall back to DNS channel), turning the decision gate into a loop rather than a one-way tree.

DimensionReasoningScore

Conciseness

The bulk is dense, high-value operational content (jitter value tables, detection-signature/mitigation pairs, checklist), but it includes concept explanation Claude already knows — "C2 infrastructure enables persistent, covert communication between the operator and implants..." and "Malleable profiles shape C2 traffic to mimic legitimate application traffic..." — plus a MITRE table that duplicates the mitre_attack tags already in the frontmatter. Mostly efficient with some unnecessary explanation matches the 3 anchor; not a 4 because the intro/Concept padding and duplication are exactly the penalized pattern.

3 / 5

Actionability

Provides mostly executable guidance: a copy-paste-ready NGINX redirector config (only <TEAMSERVER_IP> needs substitution), concrete jitter values (60-120s / 50-70%), docker compose profile commands, and an explicit pre-lateral-movement checklist. Not a 5 because there is no end-to-end listener/beacon workflow with commands — that is deferred to sibling skills — and the channel-type and malleable-profile sections are informational rather than instructive.

4 / 5

Workflow Clarity

The decision gate gives a clearly sequenced tree (C2 active → credential access / lateral movement / evasion / persistence) and the pre-lateral-movement checklist supplies explicit validation checkpoints ("Stable C2 callback with appropriate jitter", "OPSEC review: no alerts triggered, implant stable"). Minor gaps: no feedback loop for error recovery (e.g., what to do when a callback never arrives) and no listener-reachability verification step.

4 / 5

Progressive Disclosure

A single ~200-line file with no bundle files at all: the full NGINX redirector config, the detection-signature table, and the output-file tree are inlined where they would naturally live in one-level-deep reference files (e.g. references/redirector.md, references/detection.md). Section structure is good and in-file navigation is easy, so above a 2, but content that should be separate is inline and the under-50-line simple-skill exception does not apply.

3 / 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, domain-distinct description that clearly states what the skill covers, but it omits the "when to use" trigger guidance entirely from the description itself (delegating it to metadata.when_to_use) and misses several natural trigger synonyms. Adding a "Use when..." clause with terms like "command and control", "beacon", and "teamserver" would lift it to the top band.

Suggestions

Append a trigger clause to the description itself, e.g. "Use when the user mentions C2, command and control, beacons, listeners, redirectors, teamserver setup, or implant callback issues" — currently the when-to-use guidance lives only in metadata.when_to_use, capping completeness at 3.

Add natural synonyms to the description that users would actually say: "command and control" spelled out, "beacon", "teamserver", and "payload delivery".

State the relationship to sibling skills explicitly (e.g. "overview skill — see c2-sliver or c2-havoc for framework specifics") to further reduce overlap risk with the framework-specific skills.

DimensionReasoningScore

Specificity

Names several concrete, distinct capability areas — "listener types, implant modes, redirector architecture, malleable profiles, jitter strategy, OPSEC guidance" — with only minor gaps in coverage. Not a 5 because it enumerates topics rather than the comprehensive concrete actions of the top anchor; well above the 1-2 concrete actions of a 3.

4 / 5

Completeness

The "what" is clear (framework-agnostic C2 orchestration across six named areas), but the description contains no "Use when..." clause or equivalent trigger guidance — the explicit trigger list lives in metadata.when_to_use, not the description field, so completeness is capped at 3 per the rubric guideline. Not a 2 because the "what" is specific rather than vague.

3 / 5

Trigger Term Quality

Includes natural terms an operator would actually say — "C2", "implant", "listener", "redirector" — but misses common synonyms like "command and control" spelled out, "beacon", and "teamserver", which appear only in the metadata when_to_use field rather than the description. Good coverage with a few natural terms missing matches the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

"Framework-agnostic C2 orchestration" carves a clear niche (the overview layer above framework-specific siblings), and terms like "malleable profiles" and "jitter" are C2-specific. Minor overlap risk remains with the closely related c2-sliver/c2-havoc skills, which the description does not explicitly distinguish itself from.

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/post-exploit/c2/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.