Skills are knowledge packages that inject specialized security expertise into agent context. Each skill provides advanced testing techniques, practical examples, and validation methods for specific vulnerability types, technologies, or frameworks.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/usestrix/strix/llms.txt
Use this file to discover all available pages before exploring further.
Overview
From the skills documentation:Skills are specialized knowledge packages that enhance Strix agents with deep expertise in specific vulnerability types, technologies, and testing methodologies. Each skill provides advanced techniques, practical examples, and validation methods that go beyond baseline security knowledge.Agents can load up to 5 skills at creation time, selecting the most relevant ones for their specific task.
How Skills Work
Dynamic Injection
When an agent is created, skills are loaded and injected into the system prompt:Agent Creation with Skills
Skills are not additional tools. They’re knowledge injected into the agent’s system prompt to guide reasoning and testing strategies.
Skill Categories
Skills are organized by domain:Vulnerabilities
Path:strix/skills/vulnerabilities/
Core vulnerability classes for web applications and APIs:
Authentication & Authorization
Authentication & Authorization
Injection Attacks
Injection Attacks
sql_injection- SQLi detection, exploitation, and validationxss- Cross-Site Scripting (reflected, stored, DOM-based)xxe- XML External Entity attacksrce- Remote Code Execution vulnerabilitiesssrf- Server-Side Request Forgerypath_traversal_lfi_rfi- File path attacks, Local/Remote File Inclusion
Business Logic & Data
Business Logic & Data
business_logic- Application logic flaws, race conditions, state manipulationrace_conditions- TOCTOU, parallel request attacksinformation_disclosure- Sensitive data exposure, verbose errorsinsecure_file_uploads- File upload bypasses, malicious content
Web-Specific
Web-Specific
csrf- Cross-Site Request Forgeryopen_redirect- Unvalidated redirectssubdomain_takeover- DNS and hosting misconfigurations
Frameworks
Path:strix/skills/frameworks/
Framework-specific testing techniques:
fastapi- FastAPI security patterns, Pydantic bypasses, async vulnerabilitiesnextjs- Next.js API routes, SSR/SSG security, middleware bypasses
Technologies
Path:strix/skills/technologies/
Third-party service and platform-specific knowledge:
- Authentication providers (Auth0, Firebase, Supabase)
- Payment gateways (Stripe, PayPal)
- Cloud services (AWS, Azure, GCP)
- Databases and storage systems
Protocols
Path:strix/skills/protocols/
Protocol-specific testing patterns:
graphql- GraphQL introspection, batching attacks, depth limitswebsocket- WebSocket security, message injectionoauth- OAuth2 flows, PKCE, redirect_uri validationgrpc- gRPC reflection, metadata manipulation
Cloud
Path:strix/skills/cloud/
Cloud provider security testing:
aws- AWS-specific misconfigurations, IAM issuesazure- Azure security, Managed Identity exploitationgcp- GCP metadata service, service account abusekubernetes- K8s API security, pod escapes
Reconnaissance
Path:strix/skills/reconnaissance/
Advanced information gathering:
- Subdomain enumeration techniques
- Technology fingerprinting
- API discovery methods
- Attack surface mapping
Custom
Path:strix/skills/custom/
Community-contributed and specialized skills for:
- Industry-specific testing (healthcare, finance, IoT)
- Regional compliance requirements
- Proprietary technology stacks
Skill Structure
Anatomy of a Skill
Let’s examine the JWT authentication skill:- Frontmatter metadata: Name and description
- Attack surface: Where vulnerabilities commonly appear
- Reconnaissance: How to discover potential issues
- Key vulnerabilities: Specific weaknesses to test for
- Advanced techniques: Non-obvious attack vectors
- Special contexts: Platform or environment-specific considerations
Best Practices for Skills
A good skill should: ✅ Focus on actionable techniques - Not just theory, but specific testing methods ✅ Include practical examples - Real payloads, commands, and test cases ✅ Provide validation methods - How to confirm findings and avoid false positives ✅ Cover edge cases - Non-obvious scenarios and configuration-dependent behavior ✅ Be concise - Focus on high-value information, avoid redundancySkill Selection Strategy
Automatic Selection
The root agent analyzes the target and automatically creates sub-agents with relevant skills:Manual Selection
You can guide skill selection through instructions:graphql skill and related vulnerability skills.
Skill Limits
Agents can load maximum 5 skills to balance:- Context window size: More skills = larger prompts
- Focus: Too many skills dilute attention
- Relevance: Each skill should apply to the task
Skill Discovery
List available skills:Creating Custom Skills
Skill Template
Create a new skill file in~/.strix/skills/custom/:
Vulnerability Class 2
…Advanced Techniques
Non-obvious attack vectors and edge cases.Special Contexts
Platform-specific considerations:Mobile Applications
- Mobile-specific attack surfaces
Microservices
- Service mesh security considerations
Skill Examples
Combining Skills Effectively
API Testing:Skill Inheritance
Sub-agents don’t inherit parent skills:Internal Skills
Some skills are used internally by Strix:Scan Modes
Path:strix/skills/scan_modes/
Define high-level testing strategies:
quick- Fast vulnerability discoverythorough- Comprehensive testingstealth- Low-noise testing
Coordination
Path:strix/skills/coordination/
Multi-agent orchestration patterns:
root_agent- Loaded by root agents for coordination strategies
Internal skills are excluded from user-facing skill selection but are automatically applied when appropriate.
Contributing Skills
Share your skills with the community:- Create skill file following the structure above
- Test thoroughly with real applications
- Submit pull request to Strix repository
- Document use cases in the PR description
Contribution Guidelines
- Accuracy: Techniques must be practical and effective
- Completeness: Cover attack surface, reconnaissance, and exploitation
- Examples: Include working payloads and commands
- Validation: Explain how to confirm findings
- Originality: Add value beyond existing skills
Skill Limitations
Not a Replacement for Tools
Skills provide knowledge, not capabilities. Agents still need appropriate tools:Context Window Constraints
More skills = larger prompts = higher costs and latency:- Each skill adds ~1-5K tokens
- 5 skills can add 5-25K tokens
- Monitor LLM costs if using many skills
Specificity vs. Generalization
Skills should be:- Specific enough to provide actionable techniques
- General enough to apply across multiple targets
- Overly generic skills that duplicate baseline knowledge
- Hyper-specific skills that only apply to one application
Next Steps
Agents
Learn how agents use skills
Tools
Explore available tools
Vulnerability Detection
See skills in action
Contributing
Create and share your own skills