GitHub
vulnerability-analysis
Identify vulnerability class, analyze root cause, and plan exploitation strategy.
☆ 1View skill
Research AI Skills
Discover Research skills, compare source repositories and read the instructions for each workflow.
Categories: Research
Research Clear filters
Browse skills
GitHub
repo-scanning
Scan and document repository structure, patterns, and key components. Use when starting work on unfamiliar codebases.
☆ 1View skill
GitHub
ci-setup
Set up pre-commit hooks and GitHub Actions workflows for testing, linting, security scanning, releases, and deployments. Supports Python, Node.js, Go, Rust, and multi-language projects.
☆ 1View skill
GitHub
performance-principles
Performance guidelines and patterns for this system.
☆ 1View skill
GitHub
dependency-mapping
Map module dependencies and relationships. Use for complex codebases with non-trivial coupling.
☆ 1View skill
GitHub
commit-conventions
Commit message style and structure for this repository.
☆ 1View skill
GitHub
test-planning
Design test strategy with concrete test cases. Use before writing tests.
☆ 1View skill
GitHub
security-baseline
Security requirements, threats, and controls that apply across this system.
☆ 1View skill
GitHub
security-writeup
Document security research, CTF solutions, and malware analysis. Includes REPORT.md and STATUS.md templates.
☆ 1View skill
GitHub
documentation-standards
How user-facing and internal documentation should be written and maintained.
☆ 1View skill
GitHub
reporting-standards
Standards for security documentation and writeups
☆ 1View skill
GitHub
api-design
Design API endpoints, schemas, and contracts. Use when defining public interfaces or data models.
☆ 1View skill
GitHub
design-validation
Cross-check design artifacts for consistency and completeness. Use before implementation.
☆ 1View skill
GitHub
security-scanning
Scan code for security vulnerabilities. Use after implementation changes.
☆ 1View skill
GitHub
code-review
Review code for style, performance, and maintainability. Use before merging changes.
☆ 1View skill
GitHub
worktree
Create isolated git worktrees for ALL coding tasks with issue linking (discovery: implementation-clarity). Evaluate at implementation-clarity when task modifies code files. YOU MUST use for feature development,...
☆ 1View skill
GitHub
conversation-reader
Extract and read Claude conversation JSONL files with composable filters (discovery: rubber-duck). Evaluate at rubber-duck or at any point in the sesssion when task requires reading conversation history, verify...
☆ 1View skill
GitHub
deliverable-tracking
Create GitHub Issues for client deliverables in DaveX2001/deliverable-tracking repo (discovery: rubber-duck). Evaluate at requirements-clarity when user mentions tracking, deliverables, commitments, or 'create...
☆ 1View skill
GitHub
frontend-engineer
Implement or review frontend features in this repo using Next.js App Router, React Server Components by default, Tailwind, and TypeScript. Use when changing UI, components, routes, or frontend architecture unde...
☆ 1View skill
GitHub
repo-orchestrator
Repo-wide rules, task workflow, and quality gates for this portfolio project. Use at the start of any task or when making cross-cutting decisions.
☆ 1View skill
GitHub
tech-lead-reviewer
Architecture and code review guidance for this repo, with RSC boundaries, SOLID, quality gates, and mentoring. Use when reviewing changes or advising design.
☆ 1View skill
GitHub
deploy-devops-lite
Deployment and infra guidance for this repo. Use when deciding deployment strategy, environment setup, or future infra readiness (Vercel now; AWS/K8s later).
☆ 1View skill
GitHub
testing-specialist
Testing strategy and implementation for this repo using Jest and TypeScript. Use when writing, reviewing, or planning unit, integration, or future E2E tests.
☆ 1View skill
GitHub
next-project-structure
Authoritative guide on Next.js 16+ App Router structure. Use this skill to determine where files should be created, how to name them for routing, and how to organize project architecture.
☆ 1View skill
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.