c2-sliver

Sliver C2 framework operations — server connection, listener setup, implant generation, BOF/Armory extensions, post-implant operations, HTTP C2 profiles.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/post-exploit/c2-sliver/SKILL.md

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an excellent, executable, well-sequenced operational reference with strong validation checkpoints. Its one weakness is progressive disclosure: the main file is large and partially duplicates content that the existing quickstart reference could carry.

Suggestions

Trim the inline quick-reference command catalogs (e.g., the compact listener/generate listings) and point to references/sliver-quickstart.md for the full command menu, keeping SKILL.md as the procedure-and-OPSEC overview.

Ensure the Bundled Resources reference descriptions each state what content lives there so navigation is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-dense with no padding about concepts Claude already knows; inline comments are operational ('better OPSEC', 'low-and-slow') rather than explanatory fluff.	3 / 3
Actionability	It provides fully executable commands with exact flags, concrete bash(command=...) harness invocations, a complete JSON C2 profile, and tables — copy-paste ready and complete rather than pseudocode.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with checkpoints: a numbered connection procedure, a CRITICAL compilation-timeout rules block with an explicit 'correct' example, and a section-9 validation checklist with feedback expectations.	3 / 3
Progressive Disclosure	Content is well-organized into nine labeled sections with a single, clearly signaled one-level reference (sliver-quickstart.md) that exists on disk, but the ~410-line main file is somewhat monolithic and duplicates quick-reference command material that could be offloaded to the bundled reference.	2 / 3
	Total	11 / 12 Passed

Description

67%

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 is specific and well-scoped to Sliver C2, but it omits any explicit 'Use when...' trigger guidance, capping completeness and limiting natural trigger-term quality.

Suggestions

Add a trailing 'Use when ...' clause naming natural trigger phrases a user would actually say (e.g. 'Sliver', 'sliver-client', 'sliver listener/beacon', 'generate a sliver implant', 'armory/BOF extensions').

Move the most common-natural-language trigger terms from metadata.when_to_use into the description so the 'when' half is explicit within the evaluated field.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'server connection, listener setup, implant generation, BOF/Armory extensions, post-implant operations, HTTP C2 profiles' — matching the score-3 anchor for enumerating specific concrete actions.	3 / 3
Completeness	It clearly answers 'what does this do' but contains no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	It names relevant terms like 'Sliver C2 framework' and 'listener setup' but leans on technical jargon ('BOF/Armory extensions') and lacks the natural common-variation coverage; explicit user-facing trigger terms live only in metadata.when_to_use, outside the description target.	2 / 3
Distinctiveness Conflict Risk	It targets a clearly distinct niche — Sliver C2 specifically — making it unlikely to trigger for or conflict with unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: PurpleAILAB/Decepticon
Path: packages/decepticon/decepticon/skills/standard/post-exploit/c2-sliver/SKILL.md
Commit: e34afba

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

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.