CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

c2-alternative-channels

Non-traditional C2 channels — Discord/Telegram bots, DNS-over-HTTPS, blockchain-based C2, email-based C2, and cloud function dead drops for covert command and control.

Quality

72%

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-alternative-channels/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 strong, dense operational reference: highly actionable per-channel code with setup, OPSEC, detection, error-handling, and a well-constructed decision gate. Its main weaknesses are the monolithic single-file layout — six full implementations inlined where per-channel reference files belong — and the absence of explicit validation/verification steps in the operational sequences.

Suggestions

Split each channel's full implant code into one-level-deep reference files (e.g., references/discord-c2.md, references/telegram-c2.md), leaving SKILL.md as an overview with the decision gate, comparison tables, and pointers.

Remove the Quick Reference duplication — either keep it as the only inline snippets or drop it in favor of the per-channel sections.

Add an explicit first-run verification step per channel (e.g., confirm beacon check-in/registration succeeds before entering the main loop) to close the workflow-validation gap.

DimensionReasoningScore

Conciseness

The body is dense operational content — full implant code, setup steps, comparison tables, and a decision tree — with almost no explanation of concepts Claude already knows. Minor redundancy keeps it off anchor 5: the Quick Reference repeats snippets shown verbatim in the channel sections, and the opening paragraph spells out the rationale for evading network monitoring that a C2 audience can infer.

4 / 5

Actionability

Every channel gets concrete setup commands and largely copy-paste-ready Python/Bash/Solidity with realistic error handling. Two gaps hold it below fully-executable anchor 5: "ABI = [...] # ABI from compilation" is an unexplained placeholder, and the Ethereum implant's response posting is a commented-out stub with only a hint to use a side channel.

4 / 5

Workflow Clarity

Each channel follows a coherent Setup → Implant → OPSEC sequence, the Decision Gate tree clearly sequences channel selection by outbound constraints, and the Error Handling & Edge Cases table (issue → symptom → resolution) supplies recovery checkpoints. It falls short of anchor 5 only because there are no explicit verification steps (e.g., confirm the first beacon check-in before relying on a channel) and no validate-then-proceed loops.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so ~480 lines of six complete implant implementations live inline in SKILL.md. In-file structure is good (quick reference, clear headers, tables, decision gate), but the per-channel implementations are exactly the content that should be split into one-level-deep reference files with SKILL.md as an overview — matching anchor 3's "content that should be separate is inline" rather than anchor 4's "most content is appropriately placed".

3 / 5

Total

15

/

20

Passed

Description

61%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 clearly and specifically scopes the skill's coverage across five alternative C2 channel families with natural trigger vocabulary, but it is purely a coverage list: no actions are stated and there is no "Use when..." trigger clause, capping both specificity and completeness at 3.

Suggestions

Add an explicit trigger clause, e.g., "Use when setting up covert command and control over Discord, Telegram, DNS-over-HTTPS, blockchain, email, or serverless cloud services."

State concrete actions, not just channel nouns — e.g., "Set up, deploy, and operate..." so the description answers what the skill does, not only what it covers.

Fold one or two missing natural synonyms ("serverless", "command and control") into the description to raise trigger coverage.

DimensionReasoningScore

Specificity

The description comprehensively enumerates concrete channel types ("Discord/Telegram bots, DNS-over-HTTPS, blockchain-based C2, email-based C2, and cloud function dead drops") but contains no action verbs — it states what is covered, not what the skill does (set up, deploy, implement). Anchor 4 requires several specific actions; this lists specific nouns only, so it sits at anchor 3.

3 / 5

Completeness

The "what" is clear — five named alternative C2 channels — but the "when" is entirely absent: no "Use when..." clause or equivalent trigger guidance. Per the judging guideline this caps completeness at 3, matching the anchor for a clear "what" with missing "when".

3 / 5

Trigger Term Quality

Natural terms users would say are present: "C2", "Discord", "Telegram", "DNS-over-HTTPS", "blockchain", "email", "cloud function", "dead drops", and the spelled-out "covert command and control". A few natural synonyms (e.g., "serverless", "command and control" as a standalone trigger) are absent, keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Non-traditional C2 channels" with platform-specific terms (Discord, Telegram, DoH, blockchain dead drops) carves a clear niche distinct from generic networking or document skills. Minor overlap risk remains with sibling C2 skills (e.g., a domain-fronting C2 skill referenced in the body), so it is mostly distinct rather than a clear niche with minimal conflict.

4 / 5

Total

14

/

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-alternative-channels/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.