CC building-c2-infrastructure-with-sliver-framework
Deploy and harden a Sliver C2 team server (BishopFox's Go-based adversary emulation framework) with multi-protocol listeners (mTLS, HTTP/S, DNS, WireGuard), redirectors, domain fronting, and multi-operator support for authorized red-team operations. Use when standing up resilient C2 for a red-team engagement or generating beacon/session implants that must survive blue-team detection.
Deploy and harden a Sliver C2 team server (BishopFox's Go-based adversary emulation framework) with multi-protocol listeners (mTLS, HTTP/S, DNS, WireGuard)…
As a process C 58/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 9
✓ No critical or high findings
Medium and low: 9
-
low Risky intent
intent-offensive-securityreferences/api-reference.md:1Offensive-security / dual-use content (legitimate for authorised testing; review intended use)# API Reference: Sliver C2 Framework
-
low Risky intent
intent-offensive-securityreferences/standards.md:7Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| T1071.001 | Application Layer Protocol: Web Protocols | Command and Control |
-
low Risky intent
intent-offensive-securityreferences/standards.md:8Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| T1071.004 | Application Layer Protocol: DNS | Command and Control |
-
low Risky intent
intent-offensive-securityreferences/standards.md:9Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| T1573.002 | Encrypted Channel: Asymmetric Cryptography | Command and Control |
-
low Risky intent
intent-offensive-securityreferences/standards.md:10Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| T1090.002 | Proxy: External Proxy | Command and Control |
-
low Risky intent
intent-offensive-securityreferences/standards.md:11Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| T1105 | Ingress Tool Transfer | Command and Control |
-
low Risky intent
intent-offensive-securitySKILL.md:51Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Familiarity with red teaming concepts and tools
-
low Dangerous commands
cmd-pipe-to-shellSKILL.md:83Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill; the skill's own vendor host)curl https://sliver.sh/install | sudo bash
security skillvendor-host -
low Dangerous commands
cmd-privilegeSKILL.md:83Privilege escalation / world-writable permissions (documentation of a security skill)curl https://sliver.sh/install | sudo bash
security skill
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "d3fend_techniques" - note
frontmatter-keyunknown frontmatter key "nist_csf" - note
frontmatter-keyunknown frontmatter key "mitre_attack"
Process rating: all ten parameters 58/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 53 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1805 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 386: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 53 items
- +4Has examples (17 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.