transilienceai/communitytools

hackthebox

HackTheBox platform operations and automations to solve challenges, machines and capture the flags hacking competitions

First seen Mar 21, 2026

Installation

$ npx skills add transilienceai/communitytools --skill hackthebox

Also in this package

Other skills from transilienceai/communitytools · top by installs.

npx skills add transilienceai/communitytools

Browse all from transilienceai/communitytools

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 516
License LICENSE
Default branch main
Open issues 8
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,817 B
  • docs SUMMARY.md 137 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 130 installs

SKILL.md

Workflow

  • [workflow.md](reference/workflow.md) — Complete workflow with commands. Read this for each step

Steps

  1. Get Credentials — python3 .claude/tools/env-reader.py HTBUSER HTBPASS HTBTOKEN ANTHROPICAPIKEY SLACKBOTTOKEN HTBSLACKCHANNELID
  2. Only for "Machine" kind of competition -> Verify vpn is running, otherwise download the vpn file from the platform and instruct the user on how to enable it
  3. Generate output dirs — mkdir -p YYMMDD_<name>/{recon,findings,logs,artifacts,tools,reports} for each challenge. Do not seed attack-chain.md or experiments.md from the orchestrator — those are the coordinator subagent's first action (see skills/coordination/reference/spawning-recipes.md).
  4. To achieve the tasks given by the user, when possible use the HTBTOKEN, otherwise login to the platform using playwright at https://account.hackthebox.com/login and fill the login form with the HTBUSER and HTB_PASS
  5. If necessary, start the machines
  6. If necessary, check network connectivity to the machines
  7. Spawn coordinator subagent per target — Agent(name="coordinator-{tag}", runinbackground=True, ...) per spawning-recipes.md. Never run the P0-P6 coordinator workflow inline in the orchestrator session — the bookkeeping discipline (attack-chain.md, experiments.md, goal_attempts counting, mandatory skeptic at experiments 5/15/25) requires the subagent boundary. Max N concurrent agents, queue-based spawning.
  8. Post-solve Phase 3 — parent orchestrator (not coordinator) always runs /skill-update + Slack after each coordinator returns its PHASE3_SUMMARY (see workflow.md step 8)

References

  • [workflow.md](reference/workflow.md) — Workflow overview with credentials, VPN, setup, and coordinator spawn
  • [spawning-recipes.md](../coordination/reference/spawning-recipes.md) — Coordinator agent spawn prompt templates (exploitation, flag submission, completion report, stats)
  • [completion-report-schema.md](../../formats/htb-completion-report.md) — Challenge completion report structure & template
  • [slack-notifications.md](reference/slack-notifications.md) — Slack completion notification format & examples
  • [platform-navigation.md](reference/platform-navigation.md) — Platform site navigation guide
  • [vpn-pool-routing.md](reference/vpn-pool-routing.md) — VPN pool isolation. Pre-flight check before spawning any machine (releasearena vs dediviplab vs others)
  • [vpn-setup.md](reference/vpn-setup.md) — VPN connectivity troubleshooting
  • [anti-bot-bypass.md](../reconnaissance/reference/anti-bot-bypass.md) — Cloudflare/Turnstile detection evasion