Loading...
Loading...
Found 2,243 Skills
Mandatory incident fix verification with observables. Invoke after: applying production fixes, before declaring incidents resolved, when someone says 'I think that fixed it'. Requires log entries, metric changes, and database state confirmation.
Create effective AI skills. This skill should be used when user wants to create a new skill (or update an existing skill) that extends an AI with specialized capabilities, knowledge, workflows, or tool integrations.
Must always be enabled when writing/reviewing TypeScript code.
Pre-commit code quality review workflow. Use before committing changes to verify code quality, security, testing coverage, and adherence to project conventions. Supports both automated checking and interactive review modes.
Review Code
Generate and prioritize US equity long-side edge research tickets from EOD observations, then export pipeline-ready candidate specs for trade-strategy-pipeline Phase I. Use when users ask to turn hypotheses/anomalies into reproducible research tickets, convert validated ideas into `strategy.yaml` + `metadata.json`, or preflight-check interface compatibility (`edge-finder-candidate/v1`) before running pipeline backtests.
Превращает идею в конкретную задачу, которую агент может выполнить. Проводит через 5 шагов: идея → результат → реальность → задача → план.
Verify a specific claim by searching for evidence across web and academic sources. Use when the user asks to verify, fact-check, or confirm a statement.
When reporting that work is completed, fixed, or ready for use before submitting or creating a PR - you need to run verification commands and confirm the output before making any success claims; evidence always precedes assertion
Write documentation with real, validated examples. Executes commands through the user to capture actual output. Use for any new documentation or major doc updates.
Gauntlet for absolute claims (always/never/guaranteed/optimal); pressure-test, then refine with explicit boundaries. Use when users ask to prove or disprove strong certainty claims, request devil's-advocate challenge rounds, or want the $prove-it gauntlet to run in default autoloop/full-auto style.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing.