CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

c2-domain-fronting

Domain fronting and CDN abuse for C2 concealment — CloudFront, Azure CDN, Fastly setup, TLS SNI vs Host header technique, CDN-based redirectors, and integration with Cobalt Strike and Sliver.

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-domain-fronting/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.

An operationally rich, code-dense body with per-provider setup steps, working validation tests, a decision gate with fallbacks, and thorough failure/detection tables. Its weaknesses are duplication between the Quick Reference, the provider sections, and section 8, plus a monolithic structure that inlines full profiles and configs instead of splitting them into reference files.

Suggestions

Move the complete Malleable C2 profile, Sliver profile, CloudFront distribution JSON, nginx config, and Cloudflare Worker into a references/ directory and link them one level deep, keeping SKILL.md as an overview with the Quick Reference and Decision Gate.

Remove the duplicated test commands and the SNI/Host re-explanation in section 8 (already covered by section 1's How It Works) to cut the token cost.

Fix the quoted-heredoc bug (use an unquoted EOF or precompute CallerReference) and add a single end-to-end ordered workflow ending in an explicit C2-callback verification step.

DimensionReasoningScore

Conciseness

The body is dense with operational content, but there is real duplication: the Quick Reference repeats the exact curl/https commands from sections 2-4, and section 8 ("TLS SNI vs Host Header") re-explains the SNI/Host mechanism already covered by section 1's "How It Works" diagram and bullet lists. Not a 2 — there is no library-tutorial-style padding and tables are tight; not a 4 — the duplicated test commands and the repeated mechanism explanation could be trimmed.

3 / 5

Actionability

Nearly everything is copy-paste ready: complete `aws cloudfront create-distribution` JSON config, `az cdn` commands, Fastly API calls, a full Malleable C2 profile, a Sliver profile, nginx config, and a Cloudflare Worker. Minor gaps keep it below 5: the quoted heredoc ('EOF') prevents `$(date +%s)` from expanding in CallerReference, and the Beacon Configuration block is comment-only rather than executable config.

4 / 5

Workflow Clarity

The Decision Gate provides an explicit test-and-branch validation flow ("curl -H Host ... / HTTP 200 → Fronting works ... HTTP 403 → CDN enforces SNI/Host match → redirector / alternate CDN"), each provider setup is numbered with a curl test as a checkpoint, and the failure-mode and error-handling tables give recovery paths. Not a 5 because the overall skill is organized topically rather than as one coherent end-to-end sequence (pick provider → configure → validate → integrate → verify C2 callback), leaving some checkpoints implicit.

4 / 5

Progressive Disclosure

This is a ~475-line monolithic single file with no references/ bundle at all. Large, complete artifacts that belong in reference files are fully inlined: the ~75-line Malleable C2 profile, the CloudFront distribution JSON, the nginx redirector config, and the Cloudflare Worker code. Section headers are clear (better than a 2), but content that should be split into one-level-deep reference files is inline, and the one cross-skill pointer ("see c2-alternative-channels") is bare text rather than a signaled link.

3 / 5

Total

14

/

20

Passed

Description

70%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 highly specific, distinct description that names the technique, the three CDN providers, and the C2 frameworks it integrates with. Its main gap is the absent "Use when..." trigger clause in the description itself (it lives in metadata.when_to_use instead), which caps completeness and slightly weakens trigger discoverability.

Suggestions

Append an explicit trigger clause to the description, e.g., "Use when setting up domain-fronted C2, CDN redirectors, or when the user mentions fronting, SNI/Host mismatch, or CDN-based C2 concealment."

Fold a couple of natural synonyms from metadata.when_to_use (e.g., "fronting profile", "CDN redirector", "SNI mismatch") into the description so trigger matching does not depend on metadata.

Shift phrasing from noun enumeration toward actions ("Set up... Test... Configure...") to strengthen the specificity of what the skill does.

DimensionReasoningScore

Specificity

The description enumerates several concrete capabilities: "CloudFront, Azure CDN, Fastly setup", "TLS SNI vs Host header technique", "CDN-based redirectors", and "integration with Cobalt Strike and Sliver". It is not a 5 because the phrasing is noun-phrase enumeration rather than a fully comprehensive action list (no mention of testing/validating frontability, profile creation, or fallback redirectors as things it does), and not a 3 because it goes well beyond naming 1-2 actions.

4 / 5

Completeness

The "what" is clear and specific ("Domain fronting and CDN abuse for C2 concealment — CloudFront, Azure CDN, Fastly setup..."), but there is no "Use when..." clause or equivalent explicit trigger guidance in the description field. Per the rubric guideline, a missing explicit "when" caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a red-team operator would actually say are present: "domain fronting", "CDN", "CloudFront", "C2", "Sliver", "Azure CDN", "Fastly". It is not a 5 because a few natural synonyms are missing from the description itself (e.g., "redirector", "SNI mismatch", "traffic concealment", "fronting profile" appear only in metadata.when_to_use, not in the description field).

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche — CDN-based C2 concealment via domain fronting with named providers and C2 frameworks ("Cobalt Strike and Sliver") — with distinct triggers that would not plausibly fire a different skill.

5 / 5

Total

16

/

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-domain-fronting/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.