Back to catalog
Static reviewDevelopment

Skill dossier

operating-sliver-c2

Source declaration

Stand up a Sliver C2 server and mTLS listeners, generate cross-platform implants and beacons, and run post-exploitation, pivoting, and BOF/.NET tooling via the Armory for adversary emulation. Use during authorized, rules-of-engagement-bound red-team engagements that need a full open-source C2 lifecycle spanning server setup, implant generation, and post-exploitation tradecraft.

The author's original description, preserved in English. It describes intent, not verified performance.

Stand up a Sliver C2 server and mTLS listeners, generate cross-platform implants and beacons, and run post-exploitation, pivoting, and BOF/.NET tooling via the Armory for adversary emulation. Use during authorized, rules-of-engagement-bound red-team engagements that need a full open-source C2 lifecycle spanning server setup, implant generation, and post-exploitation tradecraft.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Stand up a Sliver C2 server and mTLS listeners, generate cross-platform implants and beacons, and run post-exploitation, pivoting, and BOF/.NET tooling via the Armory for adversary emulation. Use during authorized, rules-of-engagement-bound red-team engagements that need a full open-source C2 lifecycle spanning server setup, implant generation, and post-exploitation tradecraft. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L85]
  • Step 1: Start the Sliver server console [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L87]
  • Step 2: (Optional) Configure multiplayer for a team [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L102]
  • Step 3: Start C2 listeners [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L118]
  • Step 4: Generate implants [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L139]
  • Step 5: Stage implants (optional) [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L170]
  • Step 6: Interact with callbacks [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L180]
  • Step 7: Privilege escalation and credential access [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L214]
  • Step 8: Install and run armory extensions [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L227]
  • Step 9: Pivot into segmented networks [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L245]
  • Step 10: Clean up [Source statement; provisional, not tested. Evidence: skills/operating-sliver-c2/SKILL.md:L262]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/operating-sliver-c2/SKILL.md:L1-L22]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
5
Markdown files
3
scripts
1
references
2
Size
33.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/operating-sliver-c2/LICENSEOther11 KB
skills/operating-sliver-c2/references/api-reference.mdReference3.3 KB
skills/operating-sliver-c2/references/standards.mdReference1.4 KB
skills/operating-sliver-c2/scripts/agent.pyScript6.3 KB
skills/operating-sliver-c2/SKILL.mdInstruction11.7 KB

SKILL.md frontmatter

{
  "name": "operating-sliver-c2",
  "description": "Stand up a Sliver C2 server and mTLS listeners, generate cross-platform implants and beacons, and run post-exploitation, pivoting, and BOF/.NET tooling via the Armory for adversary emulation. Use during authorized, rules-of-engagement-bound red-team engagements that need a full open-source C2 lifecycle spanning server setup, implant generation, and post-exploitation tradecraft.",
  "domain": "cybersecurity",
  "subdomain": "red-teaming",
  "tags": [
    "red-team",
    "command-and-control",
    "sliver",
    "adversary-emulation",
    "implant",
    "post-exploitation",
    "pivoting",
    "mtls"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "DE.CM-01"
  ],
  "mitre_attack": [
    "T1071.001"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Objectives

    Source-described action candidate under “Objectives”; not verified execution.

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  6. 06
    Action

    Step 1: Start the Sliver server console

    Source-described action candidate under “Step 1: Start the Sliver server console”; not verified execution.

Inspect all extracted workflow candidates (22 candidate steps)
  1. 07
    Action

    Run the server interactively to get the operator console:

    Source-described action candidate under “Step 1: Start the Sliver server console”; not verified execution.

  2. 08
    Action

    Step 2: (Optional) Configure multiplayer for a team

    Source-described action candidate under “Step 2: (Optional) Configure multiplayer for a team”; not verified execution.

  3. 09
    Action

    Step 3: Start C2 listeners

    Source-described action candidate under “Step 3: Start C2 listeners”; not verified execution.

  4. 10
    Action

    Step 4: Generate implants

    Source-described action candidate under “Step 4: Generate implants”; not verified execution.

  5. 11
    Action

    Generate a session implant pointing at your mTLS endpoint:

    Source-described action candidate under “Step 4: Generate implants”; not verified execution.

  6. 12
    Action

    Generate a beacon with jitter for asynchronous, lower-noise operation:

    Source-described action candidate under “Step 4: Generate implants”; not verified execution.

  7. 13
    Action

    Step 5: Stage implants (optional)

    Source-described action candidate under “Step 5: Stage implants (optional)”; not verified execution.

  8. 14
    Action

    Step 6: Interact with callbacks

    Source-described action candidate under “Step 6: Interact with callbacks”; not verified execution.

  9. 15
    Decision

    When an implant calls back, list and select it:

    Source-described decision candidate under “Step 6: Interact with callbacks”; not verified execution.

  10. 16
    Action

    Step 7: Privilege escalation and credential access

    Source-described action candidate under “Step 7: Privilege escalation and credential access”; not verified execution.

  11. 17
    Action

    Step 8: Install and run armory extensions

    Source-described action candidate under “Step 8: Install and run armory extensions”; not verified execution.

  12. 18
    Action

    Step 9: Pivot into segmented networks

    Source-described action candidate under “Step 9: Pivot into segmented networks”; not verified execution.

  13. 19
    Action

    Step 10: Clean up

    Source-described action candidate under “Step 10: Clean up”; not verified execution.

  14. 20
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  15. 21
    Action

    OPSEC and Detection Considerations

    Source-described action candidate under “OPSEC and Detection Considerations”; not verified execution.

  16. 22
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

75 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

17 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 17 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

54 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 54 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Elevated privileges are referenced

3 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 3 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/operating-sliver-c2/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 5 collected file(s), 3 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/operating-sliver-c2/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/operating-sliver-c2
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.