2406 个 · 按相关度排序
Guide a development team from an assigned user outcome through implementation, testing, and handoff. It covers reproducing defects, checking behavior against requirements, involving design when needed, and reporting the exact changes, verification results, and remaining uncertainty.
中文简介正在准备中。当前显示英语简介。
Design tests for charts, dashboards, and interactive diagrams. Combine data checks, component tests, screenshot comparisons, and end-to-end workflows to catch incorrect values, broken interactions, and visual changes while keeping tests stable.
中文简介正在准备中。当前显示英语简介。
Design workflows for completing business lead records, verifying contact details, and ranking prospects against an ideal customer profile. Plan provider sequences in Clay, scoring rules, and data quality checks around lead volume, existing tools, and budget.
中文简介正在准备中。当前显示英语简介。
Guide feature development from a human-reviewed plan to testable requirements, implementation, and independent verification. Record each requirement with a concrete proof, then have a separate agent check the work and produce a verification report.
中文简介正在准备中。当前显示英语简介。
Organize substantial tasks into a cycle of creation, independent review, and revision while preserving the original request. Turn broad quality goals into observable checks, collect evidence, and finish with verified results or a clearly identified blocker.
中文简介正在准备中。当前显示英语简介。
Look up a company's Trustpilot profile using its domain to collect ratings, review counts, verification status, and contact details. Optional metrics show how the business responds to negative reviews, supporting company comparisons and reputation research.
中文简介正在准备中。当前显示英语简介。
Retrieve Instagram profile details from a username, including the bio, follower and following counts, post count, verification status, and external link. Use the collected information to review an account’s profile and audience size.
中文简介正在准备中。当前显示英语简介。
Check background type checks, tests, and builds in a Git worktree, a separate working directory. Read verification logs to see results, failure counts, and errors, with suggested next actions while development continues.
中文简介正在准备中。当前显示英语简介。
Checks code changes before a pull request by reviewing builds, types, coding rules, tests, potential secrets, and changed files. Produces a report showing results, test coverage, and issues that need fixing.
中文简介正在准备中。当前显示英语简介。
This skill should be used when the user asks to "verify code", "run verification", "check quality", "validate changes", or before creating a PR. Provides comprehensive verification including build, type check, lint, tests, security scan, and diff review.
中文简介正在准备中。当前显示原文说明。
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
中文简介正在准备中。当前显示原文说明。
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
中文简介正在准备中。当前显示原文说明。
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
中文简介正在准备中。当前显示原文说明。
[omh] Proof a change is done before merge: define and record build, lint, typecheck, test, security, docs, generated-output, and CI evidence before completion or merge. Use when the user says: verification-gate, verification gate, quality gate, release gate, test gate, build lint test, lint typecheck tests, verify before merge.
中文简介正在准备中。当前显示原文说明。
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", "make a driver skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
中文简介正在准备中。当前显示原文说明。
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
中文简介正在准备中。当前显示原文说明。
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
中文简介正在准备中。当前显示原文说明。
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
中文简介正在准备中。当前显示原文说明。
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
中文简介正在准备中。当前显示原文说明。
Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.
中文简介正在准备中。当前显示原文说明。
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.
中文简介正在准备中。当前显示原文说明。
Detect 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.
中文简介正在准备中。当前显示原文说明。
Set a repo up to prove engineering-task work actually works before it ships. Investigates the repo, ensures a one-command dev stack (`dev-local`) exists, asks whether verification runs locally or in a sandbox (crabbox), confirms/installs the driver (the `playwright-cli` skill for web by default). Outputs three artifacts: a committed `/verify` skill (per-task verification SOP — spawn a verifier sub-agent → drive the app → screenshot/video proof → open a PR with the proof embedded), the `/dev-local` skill + script, and the installed driver skill. Use when someone says "set up verification", "make this repo verifiable", "scaffold a verify skill", "set up the verifier".
中文简介正在准备中。当前显示原文说明。
Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
中文简介正在准备中。当前显示原文说明。