CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

c2-mythic

Mythic C2 framework operations — multi-agent (Apfell, Apollo, Athena, Poseidon, Medusa), web UI on 7443, RabbitMQ + PostgreSQL backend, JSON-RPC tasking model, building an agent via mythic-cli, profile design (HTTP/SMB/named pipe/peer-to-peer), opsec defaults. Comparison to Sliver: more pluggable, less polished UI.

Quality

77%

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

Quality

Content

76%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 operator reference with excellent token efficiency — commands and tables instead of prose. Its main weaknesses are the missing validation checkpoints in the engagement workflow (capped by the destructive-operations rule) and the JSON-RPC vs GraphQL inconsistency in the tasking section.

Suggestions

Add explicit validation checkpoints to the workflow: confirm callback and task output before lateral movement, verify persistence took hold before moving on, and validate cleanup completeness before teardown.

Reconcile the tasking model claim — pick one of 'JSON-RPC' or the GraphQL API at https://<host>:7443/v1/graphql and describe the actual interface consistently.

Verify the Python scripting example against the current mythic package API (module names and function signatures) so it is genuinely copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and operator-focused: tables (agent matrix, profile matrix, framework comparison), complete CLI commands, and terse opsec bullets ('default 30s/20% is loud'). No sections explain concepts Claude already knows, and every section earns its place. It does not fall to 4 because there is no over-explanation to trim.

5 / 5

Actionability

Mostly executable, copy-paste-ready guidance: install commands, a fully parameterized 'mythic-cli payload create' invocation, and a Python scripting example. Not a 5 because the body claims a 'JSON-RPC tasking model' while also listing a 'Direct GraphQL API' endpoint (an internal inconsistency), and the Python example's imports (mythic_utilities, mythic_callbacks) may not match the real mythic package's API.

4 / 5

Workflow Clarity

The 9-step 'Common workflow' has a clear sequence but validation checkpoints are absent or only implicit (survey after callback, no verify-before-lateral-movement, persistence, or teardown steps). Since the workflow includes destructive and batch-style operations (SMB lateral to peers, persistence, cleanup/teardown), the rubric's cap of 3 for missing validation applies.

3 / 5

Progressive Disclosure

Well-organized single-file skill (no bundle files exist) with clear section headers and navigable tables. Not a 5 because at ~130 lines the agent matrix, comparison table, and scripting API details are inline content that would fit better in one-level-deep reference files if the skill grows, and the 'References' section lists external docs rather than structured bundle navigation.

4 / 5

Total

16

/

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 specific, information-dense description with excellent distinctiveness, but it reads as a feature inventory rather than an action-plus-trigger pair. The missing 'Use when...' clause is the main structural gap, and a few natural synonyms (implant, beacon, callback) would strengthen triggering.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Mythic, C2 framework setup, agent callbacks, implant/tasking operations, or building payloads'.

Include natural synonyms users say in this domain: 'command and control', 'implant', 'beacon', 'callback', 'payload' — not just jargon like 'JSON-RPC tasking model'.

Lead with concrete actions ('Build and task Mythic agents via mythic-cli; configure HTTP/SMB/dns C2 profiles; apply opsec defaults') instead of the generic umbrella 'Mythic C2 framework operations'.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities ('building an agent via mythic-cli', 'profile design (HTTP/SMB/named pipe/peer-to-peer)', 'opsec defaults') plus specific facts like agent names, port 7443, and the RabbitMQ/PostgreSQL backend. Not a 5 because 'Mythic C2 framework operations' is a generic umbrella action and core actions like callback tasking are only implied via the 'JSON-RPC tasking model' fact rather than stated as actions.

4 / 5

Completeness

The 'what' is clear and rich (multi-agent operations, profile design, opsec defaults, mythic-cli builds), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('Mythic C2', agent names Apollo/Poseidon/Athena/Apell/Medusa, 'opsec', 'profile') that an operator would actually say. A few natural terms are missing: 'command and control' spelled out, 'implant', 'beacon', 'callback', and 'payload'.

4 / 5

Distinctiveness Conflict Risk

Highly niche triggers ('Mythic C2', 'web UI on 7443', 'mythic-cli', specific agent names) make conflict with other skills minimal; even the Sliver comparison serves to distinguish rather than blur boundaries.

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/mythic/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.