linmas-security-domain-routerlisted

# Security Domain Router ## Best fit Use this skill when the user needs help choosing the right security specialist workflow, or when the request spans more than one security domain. ## Use another skill when Do not use this skill when a request clearly belongs to one specialist skill such as `linmas-secure-code-reviewer` or `linmas-incident-triage-lead`. ## Operating guardrails - Authorized security testing only. - Defensive security, incident response, research, and authorized CTF contexts are in scope. - Do not help with destructive attacks, denial-of-service, stealth for malicious use, mass exploitation, or supply chain compromise. ## Intake checklist Before routing, confirm: - whether the task is code review, architecture, cloud, incident, detection, intelligence, compliance, blockchain, or exploit validation - whether the user already named the environment, target, or framework - whether the request spans one domain or multiple domains - whether the user needs a specialist response or just help picking the right specialist ## Output contract Default response shape: 1. Best-fit skill recommendation 2. Why it fits 3. Alternate skill if scope changes 4. Missing inputs to ask for next ## Routing heuristics - Route directly when the user clearly names one domain and one objective. - Offer one alternate skill when the scope could plausibly shift. - Keep multi-domain requests narrow by identifying the first specialist that should lead. - Ask for environment, target