Loading...
Loading...
Found 3,942 Skills
Author, scaffold, and run coding-agent-driven tests: Markdown case files executed by a coding agent against a live environment (browser, API, DB, logs, cloud, telemetry) with an auditable PASS/FAIL/BLOCKED report. Use when a deterministic test would be premature, brittle, too expensive, or too narrow.
Submit a transaction to Sumsub Transaction Monitoring (KYT) via the ApplicantResource API. TRIGGER when the user asks to "submit / create / send / record a transaction", "test a KYT rule with a transaction", post a fiat or crypto payment for monitoring, attach Travel Rule data to a transfer, log a user-platform event (signup / login / password-reset / 2FA-reset) for monitoring, or submit a transaction for an applicant that does not exist yet (the request creates them). SKIP for editing arbitrary fields on an existing transaction, for bulk import (`/kyt/misc/txns/import`), for fetching / approving / rejecting transactions, for KYT rule management, or for Travel Rule data-exchange flows that are not transaction creation.
2. Create Feature Design Document
Identify and fix flaky E2E tests by running them repeatedly and investigating failures.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, PRDs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Use when implementing any feature or bugfix, before writing implementation code
Run comprehensive accessibility audit (WCAG 2.1) on Webflow pages - checks buttons, forms, links, focus states, headings, keyboard navigation, and generates detailed reports with fixes. Requires Webflow Designer connection. Excludes image alt text (covered by asset-audit skill).
Test Plan - creates a manual test plan with traceable test cases from specification documents. Use when preparing to verify a feature implementation.
Facilitates the third step of a proven customer-interview method: translating hypotheses into open-ended, unbiased interview questions — each a miniature experiment designed to test one hypothesis without leading the witness. Two modes: given a single hypothesis, it grills the question into shape and outputs the final question in chat; given a HYPOTHESES.md file, it iterates the whole list, grouping related hypotheses, and maintains a QUESTIONS.md file (numbered Q1, Q2, … mapped to H-numbers) as a live, resumable artifact. Load when the user has hypotheses and wants interview questions, asks how to phrase a question for customers without biasing the answer, or says 'turn my hypotheses into questions' or 'help me ask about X without leading.' Do NOT load for writing goal questions or hypotheses (earlier steps), for conducting or analyzing the interviews themselves, for survey/questionnaire design, or for job interviews.
Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end. Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic minimal repro (fixed seeds, frozen time, stubbed network), writing the failing regression test BEFORE the fix (red) and confirming the fix flips it green, and writing repro evidence back into the ticket. Distinguishes flaky-not-reproducible from environment-specific. Use when: "reproduce this bug," "minimal reproduction," "repro steps," "find the commit that broke it," "git bisect," "make the repro deterministic," "write a failing test for this bug," "regression test for a defect," "can't reproduce this bug." Not for: Classifying/deduplicating/severity-routing existing failures without reproducing them — that is ai-bug-triage. Generating tests from specs rather than from a defect — that is ai-test-generation. Related: ai-bug-triage, ai-test-generation, test-reliability, systematic-debugging, qa-project-context.