using-superhackers

Route security tasks to sub-skills and enforce the engagement workflow.

6|1|Updated Mar 1, 2026

Search Tags:#routing #orchestration #state-persistence #security-engagement #pentest-flow #recon-enumeration

Ready to run

npx skills add https://github.com/narlyseorg/superhackers --skill using-superhackers

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: using-superhackers
Source: https://github.com/narlyseorg/superhackers/tree/main/skills/using-superhackers
Command: npx skills add https://github.com/narlyseorg/superhackers --skill using-superhackers

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as the entry point for security engagements, routing tasks to the correct sub-skills and enforcing the overall workflow to ensure a disciplined, repeatable pipeline from recon to reporting.

Core Features & Use Cases

Orchestration: determines the applicable security skill chain and loads them in the correct order.
State Management: maintains engagement state and passes findings between skills to preserve context.
Guardrails: ensures recon precedes testing and verification before reporting, reducing misrouting and scope creep.

Quick Start

Load this skill first to route your security task to the appropriate sub-skills and enforce the engagement workflow.

Frequently Asked Questions about using-superhackers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I orchestrate a pentest flow from recon to reporting?▼

Orchestrate a pentest flow by loading this skill first to route security tasks to correct sub-skills, enforcing a pipeline from recon to reporting. It coordinates phases and passes findings between them to maintain context.

What is the best way to maintain state persistence across security engagement phases?▼

Maintain state persistence across security engagement phases by persisting engagement state and routing outputs between sub-skills. This preserves context and ensures findings from recon are available during testing, verification, and reporting.

Can I enforce guardrails so recon precedes testing in my security workflow?▼

Yes, you can enforce guardrails so recon precedes testing in your security workflow. This skill enforces the engagement workflow, ensuring recon happens before testing and verification before reporting to reduce misrouting and scope creep.

How does task routing work for complex security engagements with multiple phases?▼

Task routing for security engagements works by determining the applicable security skill chain and loading sub-skills in the correct order. It acts as the entry point, routing tasks and passing outputs between recon, testing, verification, and reporting phases.

Do I need to load sub-skills manually before executing a security engagement?▼

No, you do not need to load sub-skills manually. This skill determines the applicable security skill chain, ensures skills are loaded and read before execution, and enforces the engagement workflow automatically.

Why does my security engagement lose context between recon and reporting phases?▼

Security engagements lose context between recon and reporting phases without state persistence. This skill solves that by maintaining engagement state and passing findings between skills to preserve context across the entire workflow.