Threat Detection
alirezarezvani/claude-skills
A skill your agent uses when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification.
MITAuto-check passed
Install Request Analyzer
$ npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-cto-team request-analyzer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/request-analyzer .claude/skills/request-analyzer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "request-analyzer" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer into .claude/skills/request-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-analyzer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-cto-team request-analyzer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/request-analyzer .agents/skills/request-analyzer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "request-analyzer" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer into .agents/skills/request-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-analyzer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-cto-team request-analyzer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/request-analyzer .cursor/skills/request-analyzer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "request-analyzer" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer into .cursor/skills/request-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-analyzer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-cto-team.git --path skills/request-analyzer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-cto-team request-analyzer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/request-analyzer .gemini/skills/request-analyzer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "request-analyzer" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer into .gemini/skills/request-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-analyzer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-cto-team request-analyzerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/request-analyzer .github/skills/request-analyzer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "request-analyzer" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer into .github/skills/request-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-analyzer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-cto-team request-analyzer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-cto-team.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/request-analyzer .opencode/skills/request-analyzer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "request-analyzer" agent skill from https://github.com/alirezarezvani/claude-cto-team/tree/main/skills/request-analyzer into .opencode/skills/request-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "request-analyzer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
request-analyzer- GitHub stars
- 117
- Token cost
- ~1.3k tokens
- SKILL.md length
- 462 words
- Files
- 3
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification.
- Works in 5 steps: Detect Intent → Classify Request Type → Assess Complexity → …
- Cto-orchestrator receives new requests that need classification before routing to specialist agents
- SKILL.md covers When to Use, Analysis Framework, Output Format and Examples, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Request Analyzer is an agent skill from alirezarezvani/claude-cto-team. Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification. Use when cto-orchestrator receives new requests that need classification before routing to specialist agents.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `buzzword-dictionary.md` and `classification-criteria.md`).
The repository describes itself as: Your personal CTO Team for Claude Code . These Subagents will help you challenging yourself while you plan and execute. The licence is MIT.
When your agent uses it
- Cto-orchestrator receives new requests that need classification before routing to specialist agents
Example prompts
- “/request-analyzer”
Requirements
- Node.js
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a5bbb78. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Request Analyzer loads about 1.3k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 462 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from alirezarezvani/claude-cto-team at commit a5bbb78, republished under its MIT licence (© alirezarezvani). 462 words, ~1,291 tokens.
Download SKILL.mdSave it as
.claude/skills/request-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- request-analyzer
- description
- Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification. Use when cto-orchestrator receives new requests that need classification before routing to specialist agents.
Request Analyzer
Classifies incoming requests to enable intelligent routing and identify clarification needs before delegating to specialist agents.
When to Use
- When receiving a new user request that needs classification
- When determining which specialist agent should handle a request
- When identifying if requirements are too vague to proceed
- When detecting buzzwords that need to be challenged
Analysis Framework
Step 1: Detect Intent
Classify the primary intent:
| Intent | Indicators | Route |
|---|---|---|
| Strategic | "roadmap", "strategy", "plan", "prioritize", "decide" | May need validation |
| Implementation | "build", "create", "implement", "design", "architect" | Design work |
| Debugging | "fix", "broken", "error", "slow", "not working" | Debug/investigate |
| Documentation | "document", "explain", "describe", "write docs" | Documentation |
Step 2: Classify Request Type
| Type | Key Phrases | Primary Agent |
|---|---|---|
| Design | "How should I build...", "What architecture...", "Design a system..." | cto-architect |
| Validate | "Is this plan solid?", "Thoughts on...", "Review my roadmap..." | strategic-cto-mentor |
| Debug | "Why is X slow?", "Fix this error...", "Troubleshoot..." | debug-helper |
| Document | "Write documentation for...", "Explain how..." | docs-writer |
| Review | "Review this code...", "Check for issues..." | code-reviewer |
Step 3: Assess Complexity
| Complexity | Characteristics | Execution Pattern |
|---|---|---|
| Single | Clear scope, one domain, obvious routing | Direct to one agent |
| Sequential | Multiple phases, depends on previous output | Agent chain |
| Parallel | Independent domains, can run simultaneously | Multiple agents in parallel |
Step 4: Identify Vague Terms
Scan for buzzwords that require clarification. See buzzword-dictionary.md for the complete list.
Common red flags:
- "AI-powered" - What specific AI capability?
- "scale" - What numbers? From what to what?
- "fast" / "soon" - What timeline exactly?
- "simple" - Simple for whom? What constraints?
- "modern" - What specific technologies?
Step 5: Detect Missing Context
Check for required context based on request type:
For Design Requests:
- Expected user/traffic scale
- Budget constraints
- Timeline requirements
- Team size and expertise
- Existing infrastructure
For Validation Requests:
- Current state or existing plan
- Business goals and constraints
- Timeline and resources
- Success criteria
Show full SKILL.md (173 more words)Show less
Output Format
Provide analysis in this structure:
## Request Analysis
**Intent**: [strategic | implementation | debugging | documentation]
**Type**: [design | validate | debug | document | review]
**Complexity**: [single | sequential | parallel]
### Vague Terms Detected
- "[term]" - needs clarification: [what to ask]
### Missing Context
- [missing information item]
### Suggested Routing
**Primary Agent**: [agent name]
**Rationale**: [why this agent]
### Clarification Needed
[yes/no] - [brief explanation]
### Recommended Next Step
[what to do next - clarify or delegate]Examples
Example 1: Vague Request
User: "I want to add AI capabilities to my app"
Analysis:
- Intent: Implementation
- Type: Design
- Complexity: Unknown (needs clarification)
- Vague Terms: "AI capabilities" - What specific problem are we solving?
- Missing Context: Scale, budget, timeline, team, existing stack
- Clarification Needed: Yes
- Next Step: Use clarification-protocol before routing
Example 2: Clear Design Request
User: "Design a real-time notification system for 100K users, using our existing PostgreSQL database and Node.js backend"
Analysis:
- Intent: Implementation
- Type: Design
- Complexity: Single
- Vague Terms: None
- Missing Context: Timeline, budget (nice to have but not blocking)
- Suggested Routing: cto-architect
- Clarification Needed: No (can proceed with optional clarification)
Example 3: Validation Request
User: "Here's my Q2 roadmap - migrate to microservices, add real-time features, and launch mobile app. Thoughts?"
Analysis:
- Intent: Strategic
- Type: Validate
- Complexity: Single
- Vague Terms: None
- Missing Context: Team size, current architecture state
- Suggested Routing: strategic-cto-mentor
- Clarification Needed: Mild (some context helpful but not blocking)
References
- Classification Criteria - Detailed routing logic
- Buzzword Dictionary - Common vague terms to challenge
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in skills/request-analyzer of alirezarezvani/claude-cto-team.
- SKILL.md
- buzzword-dictionary.md
- classification-criteria.md
Open the folder on GitHubat commit a5bbb78
Compare with similar skills
Request Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Request Analyzer this skillalirezarezvani/claude-cto-team | 117 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Threat Detectionalirezarezvani/claude-skills | 28k | — | ~3.5k | Automated safety check: Pass | MIT | |
| Resemble Detectgithub/awesome-copilot | 40k | 3 repos | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Analyzing Network Packets With Scapymukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~626 | Automated safety check: Pass | Apache-2.0 | |
| Detecting Modbus Protocol Anomaliesmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.7k | Automated safety check: Pass | Apache-2.0 | |
| Intent Analyzeraiskillstore/marketplace | 430 | 1 repos | ~4.6k | Automated safety check: Pass | None |
Similar skills
- Official
Resemble Detect
github/awesome-copilot
Deepfake detection and media safety — detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using…
Analyzing Network Packets With Scapy
mukul975/Anthropic-Cybersecurity-Skills
Use Scapy to craft, send, sniff, and dissect TCP/UDP/ICMP/DNS packets, analyze pcap files, implement SYN scans, and detect anomalous traffic such as fragmented or malformed packets.
Detecting Modbus Protocol Anomalies
mukul975/Anthropic-Cybersecurity-Skills
Detect anomalies in Modbus/TCP and Modbus RTU industrial traffic via function code monitoring, register range validation, timing analysis, and deep packet inspection, using Zeek's Modbus analyzer…
Intent Analyzer
aiskillstore/marketplace
Advanced intent interpretation system that analyzes user requests using cognitive science principles and extrapolates logical volition.
Analyzing Cloud Storage Access Patterns
mukul975/Anthropic-Cybersecurity-Skills
Detect abnormal access in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics for after-hours bulk downloads, new-IP access, and…
More from alirezarezvani/claude-cto-team
All 12 skills in this repoAntipattern Detector
alirezarezvani/claude-cto-team
Detect common technical and organizational anti-patterns in proposals, architectures, and plans.
Architecture Pattern Selector
alirezarezvani/claude-cto-team
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints.
Assumption Challenger
alirezarezvani/claude-cto-team
Identify and challenge implicit assumptions in plans, proposals, and technical decisions.
Cost Estimator
alirezarezvani/claude-cto-team
Infrastructure and development cost estimation for technical projects.
ML Cv Specialist
alirezarezvani/claude-cto-team
Deep expertise in ML/CV model selection, training pipelines, and inference architecture.
Roadmap Generator
alirezarezvani/claude-cto-team
Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints.
Questions about Request Analyzer
What does Request Analyzer do?
Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification. Request Analyzer is an agent skill from alirezarezvani/claude-cto-team. Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification.
When should I use Request Analyzer?
Request Analyzer fits situations like: cto-orchestrator receives new requests that need classification before routing to specialist agents.
How do I install Request Analyzer in Claude Code?
Run `npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a claude-code`. Or copy the skill folder (skills/request-analyzer in alirezarezvani/claude-cto-team) into .claude/skills/request-analyzer in your project. Claude Code loads it when a task matches its description.
How do I install Request Analyzer in Codex?
Run `npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a codex`. Or copy the skill folder (skills/request-analyzer in alirezarezvani/claude-cto-team) into .agents/skills/request-analyzer in your project. Codex loads it when a task matches its description.
Can I use Request Analyzer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-cto-team --skill request-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/request-analyzer, .gemini/skills/request-analyzer, .github/skills/request-analyzer and .opencode/skills/request-analyzer in your project.
What does Request Analyzer need to run?
SKILL.md names no scripts, command-line tools or credentials: Request Analyzer is instructions for the agent only. Our summary lists: Node.js.
Does Request Analyzer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Request Analyzer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Request Analyzer use?
Request Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Request Analyzer use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Request Analyzer?
Skills that share tags, products or a category with Request Analyzer: Threat Detection (alirezarezvani/claude-skills, 28k stars), Resemble Detect (github/awesome-copilot, 40k stars), Analyzing Network Packets With Scapy (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Detecting Modbus Protocol Anomalies (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Request Analyzer?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-cto-team, which has 117 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on December 18, 2025.
Source: alirezarezvani/claude-cto-team on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.