flow-trace
Trace data flow across files from source to sink. Use for cross-file taint analysis, understanding how user input reaches dangerous sinks, and documenting vulnerability paths.
Discover Development skills, compare source repositories and read the instructions for each workflow.
Trace data flow across files from source to sink. Use for cross-file taint analysis, understanding how user input reaches dangerous sinks, and documenting vulnerability paths.
MATLAB and GNU Octave numerical computing for matrix operations, data analysis, visualization, and scientific computing. Use when writing MATLAB/Octave scripts for linear algebra, signal processing, image proce...
Find denial of service vulnerabilities through resource exhaustion, algorithmic complexity, memory exhaustion, and file/network resource abuse. Use when auditing code for availability issues.
This skill should be used when the user asks to "test for insecure direct object references," "find IDOR vulnerabilities," "exploit broken access control," "enumerate user IDs or object references," or "bypass...
Hunt for hardcoded secrets, API keys, tokens, credentials, private keys, and sensitive configuration. Use when auditing code for credential exposure or before committing code.
QFAI: Create specs, contracts, and scenarios
QFAI: Implement acceptance tests from scenarios
QFAI: Create requirements artifacts
QFAI: Run quality gates and produce evidence
QFAI: Configure qfai.config.yaml based on the repository
QFAI: Discuss an idea and clarify requirements
QFAI: Implement unit tests from specs/scenarios
QFAI: Implement code changes with tests
SOLID design principles for .NET. Use when designing classes, interfaces, and object relationships. Ensures maintainable, testable, and extensible code.
Clean code principles including DRY, KISS, and YAGNI for .NET. Use when writing or reviewing code to ensure maintainability and simplicity.
Test-Driven Development workflow for .NET. Use when implementing features, fixing bugs, or writing new code. Guides RED-GREEN-REFACTOR cycle with proper test design.
Requirements clarification for TDD. Use BEFORE RED phase to understand WHAT to test. Asks targeted questions to uncover ambiguities, edge cases, and acceptance criteria.
Captures valuable insights and documents them in CLAUDE.md. Auto-triggers when: discovering gotchas or unexpected behavior, completing significant features, fixing complex bugs, making architectural decisions,...
Analyzes how user-facing use cases map to data access patterns and architecture. Auto-triggers when: implementing new features that need existing pattern understanding, explaining how a feature works in the dat...
Creates Architecture Decision Records for significant choices. Auto-triggers when: evaluating technology options (database, framework, library), making foundational decisions (architecture patterns, infrastruct...
Orchestrate multiple AI agents across Vers VMs for parallel task execution
This skill should be used when the user asks about "token efficiency", "compress responses", "reduce token usage", "minimize context", "compact format", "token optimization", or discusses reducing token consump...
This skill should be used when the user asks to "design MCP tool", "create tool schema", "tool best practices", "input validation", "output schema", "error handling for tools", or discusses designing individual...
This skill should be used when the user asks about "error messages", "did you mean", "similar tools", "parameter suggestions", "schema hints", "MCP error handling", "guide the client", "helpful errors", "fuzzy...
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.