Explore skills
Showing 37021–37050 of 48921 skills
Reference for the Tech Lead role in the AID lifecycle.
ilandahan/AID
Stars: 10Claude CodeCodex[OPTIONAL] AI-powered visual generation using Google Nano Banana Pro. For user flows, architecture diagrams, mockups.
ilandahan/AID
Stars: 10Claude CodeCodexAID methodology phase gate enforcement. Ensures work follows correct 6-phase order (Discovery -> PRD -> Tech Spec -> Impl Plan -> Dev -> QA & Ship). Enforces gates, validates transitions. Use before any work to check the current phase and refuse work belonging to a later phase.
ilandahan/AID
Stars: 10Claude CodeCodexDrives the Phase 4-5 dev pipeline state machine with sub-agent reviews and bounded autoresearch gates. Use when running /pipeline or executing an approved plan.
ilandahan/AID
Stars: 10Claude CodeCodexComprehensive code review for commits and pull requests. Covers security, TDD, code quality, and documentation standards.
ilandahan/AID
Stars: 10Claude CodeCodexTDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.
ilandahan/AID
Stars: 10Claude CodeCodexPre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.
ilandahan/AID
Stars: 10Claude CodeCodexAutomatic quality check on significant outputs via isolated sub-agent. Spawns reflection-agent for objective evaluation without conversation context bias.
ilandahan/AID
Stars: 10Claude CodeCodexData Scientist role within the AID methodology. Activate when working on: EDA, feasibility assessment, experiment planning, ML architecture, model development & validation, or production deployment & monitoring. Stack-agnostic — ask the user for their stack at the start of any new project.
ilandahan/AID
Stars: 10Claude CodeCodexDeveloper role in AID methodology. Use for implementation, debugging, technical design, TDD workflow, code review.
ilandahan/AID
Stars: 10Claude CodeCodexPM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.
ilandahan/AID
Stars: 10Claude CodeCodexQA Engineer role in AID methodology. Use for test strategy, BDD scenarios, bug reporting, acceptance testing, flaky test prevention.
ilandahan/AID
Stars: 10Claude CodeCodexTech Lead role in AID methodology. Use for architecture decisions, code reviews, technical direction, operational readiness, team guidance.
ilandahan/AID
Stars: 10Claude CodeCodexSenior System Architect for SaaS specifications. Security-first design with ISO 27001 compliance. Use for system architecture, tech specs, API design, technology choices, distributed systems, cloud infrastructure.
ilandahan/AID
Stars: 10Claude CodeCodexTDD methodology for production-quality tests. Write tests FIRST driven by PRD, Tech Spec, Implementation Plan. Covers minimal mocking, realistic test data, strong assertions, test independence.
ilandahan/AID
Stars: 10Claude CodeCodexFOUNDATIONAL SKILL - Analyze every prompt for underlying motivation using Golden Circle (WHY->HOW->WHAT). Runs BEFORE any other skill. No action without understanding WHY.
ilandahan/AID
Stars: 10Claude CodeCodexHandle the current public TDM DaOS payment contract and recovery guidance. Use when a TDM service returns HTTP 402 from POST /authorize, when the user needs help with Session Gas Tank behavior, or when the user should be guided toward tdm connect, tdm fuel, tdm sweep, or tdm cashout.
ToDealMarket/tdm-daos-agent
Stars: 9Claude CodeCodexUse when the user wants to write, revise or diagnose Korean song lyrics and the matching Suno Style, Exclude and Title fields for any genre, from ballad and trot to rap, K-pop, rock and electronic.
previtlab/suno-lyrics-skill
Stars: 8Claude CodeCodexprevitlab/suno-lyrics-skill
Stars: 8Claude CodeCodexEssential fuzzing payloads: SQL injection, command injection, special characters. Curated essentials for vulnerability testing.
capture0x/YeepForge
Stars: 8Claude CodeCodexSensitive data patterns for security testing: API keys, credit cards, emails, SSNs, phone numbers, IPs, and more. Use for data discovery and validation.
capture0x/YeepForge
Stars: 8Claude CodeCodexEssential exploitation payloads: anti-virus test files, file name exploits, malicious files. Curated for testing.
capture0x/YeepForge
Stars: 8Claude CodeCodexRun a full web-application penetration test by driving YeepForge's MCP tools. Use when the user gives a target URL (with authorization) and wants reconnaissance, OWASP Top 10 testing, exploitation, and a professional report. Requires the 'yeepforge' MCP server to be connected.
capture0x/YeepForge
Stars: 8Claude CodeCodexStatic application security testing (SAST) of a source-code directory using YeepForge's static analyzer. Use when the user provides a local code path and wants a vulnerability review - SQLi, XSS, RCE, SSRF, path traversal, XXE, SSTI, JWT, IDOR, missing auth, business logic, GraphQL. Requires the 'yeepforge' MCP server.
capture0x/YeepForge
Stars: 8Claude CodeCodexPerform codebase analysis and architecture mapping as the first phase of a security assessment. Explores the tech stack, frameworks, entry points, data flows, and trust boundaries. Outputs sast/architecture.md. Run this before any vulnerability detection skill. Use when asked to analyze a codebase for security or when sast/architecture.md does not yet exist.
capture0x/YeepForge
Stars: 8Claude CodeCodexDetect business logic vulnerabilities in a codebase using a three-phase approach: threat modeling (domain analysis and attack scenarios), batched verify (check exploitable gaps in parallel subagents, 3 scenarios each), and merge (consolidate batch results). Covers price manipulation, workflow bypass, limit violations, race conditions, reward abuse, etc. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/businesslogic-results.md. Use when asked to find business logic, logic flaws, or abuse-of-function bugs.
capture0x/YeepForge
Stars: 8Claude CodeCodexDetect insecure file upload vulnerabilities in a codebase using a three-phase approach: discovery (find all upload sites), batched verify (check extension bypass and related issues in parallel subagents, 3 sites each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/fileupload-results.md. Use when asked to find file upload, unrestricted upload, or extension bypass bugs.
capture0x/YeepForge
Stars: 8Claude CodeCodexDetect GraphQL injection vulnerabilities in a codebase using a three-phase approach: recon (confirm GraphQL usage and find unsafe operation document assembly sites), batched verify (trace user input to those sites in parallel subagents, up to 3 candidate sites each), and merge (consolidate batch results). Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/graphql-results.md. If no GraphQL technology is found in Phase 1, later phases are skipped. Use when asked to find GraphQL injection, unsafe GraphQL document construction, or operation string injection bugs.
capture0x/YeepForge
Stars: 8Claude CodeCodexDetect Insecure Direct Object Reference (IDOR) vulnerabilities in a codebase using a three-phase approach: recon (find candidates), batched verify (check authorization in parallel subagents, 3 candidates each), and merge (consolidate batch results). Checks endpoints for missing ownership or authorization checks on user-supplied identifiers. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/idor-results.md. Use when asked to find IDOR or authorization bypass bugs.
capture0x/YeepForge
Stars: 8Claude CodeCodexDetect insecure JWT (JSON Web Token) implementations in a codebase using a two-phase approach: first map all JWT issuance and verification sites to understand the token lifecycle and signing configuration, then check each verification site for exploitable weaknesses such as algorithm confusion, missing signature verification, weak secrets, header injection, and missing claim validation. Requires sast/architecture.md (run sast-analysis first). Outputs findings to sast/jwt-results.md. If no JWT usage is found in Phase 1, Phase 2 is skipped. Use when asked to find JWT, token forgery, or authentication bypass bugs.
capture0x/YeepForge
Stars: 8Claude CodeCodex