Results for “verification”

Solve competition math problems (IMO, Putnam, USAMO, AIME) with adversarial verification that catches the errors self-verification misses. Activates when asked to 'solve this IMO problem', 'prove this olympiad inequality', 'verify this competition proof', 'find a counterexample', 'is this proof correct', or for any problem with 'IMO', 'Putnam', 'USAMO', 'olympiad', or 'competition math' in it. Uses pure reasoning (no tools) — then a fresh-context adversarial verifier attacks the proof using specific failure patterns, not generic 'check logic'. Outputs calibrated confidence — will say 'no confident solution' rather than bluff. If LaTeX is available, produces a clean PDF after verification passes.

The English summary is being prepared. Showing the original description.

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".

The English summary is being prepared. Showing the original description.

Citation format and verification protocol for legal documents that draw on Bates-stamped source records. Defines the bracket citation format, multi-source citation rules, quotation handling, the verification pass that runs before output, and the [UNVERIFIED] flag protocol. Use this skill any time another skill produces a legal work product that cites Bates-stamped pages, including medical chronologies, deposition summaries, demand letters, case briefs, and discovery responses. Also use any time the user asks how to format a citation or verify that a claim is supported by the source.

The English summary is being prepared. Showing the original description.

Audit LLM token cost estimates against actual API usage. Activate on 'cost verification', 'token estimate accuracy', 'API cost audit', 'estimation variance'. NOT for pricing lookups, budget planning, or cost optimization strategies.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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".

The English summary is being prepared. Showing the original description.

Run verification commands and confirm output before claiming success

The English summary is being prepared. Showing the original description.

Verification before delivery: production-level command outputs, build, browser evidence. Use when implementing, reviewing or testing verification before delivery for React, Vite, Next.js or Perfect_AI projects.

The English summary is being prepared. Showing the original description.

Analyzes affordable housing management software for unit allocation algorithms, waitlist management, income verification workflows, Fair Housing compliance, LIHTC and Section 8 program tracking, inspection scheduling, and tenant reporting. USE THIS SKILL WHEN: - You are reviewing housing management software or tenant management systems - Someone asks about Section 8, LIHTC, or public housing program compliance - You need to audit unit allocation algorithms for fairness or bias - A project involves waitlist management, income verification, or rent calculations - You are evaluating HUD compliance (50058, EIV, PIC submissions) - Someone mentions Fair Housing, reasonable accommodation, or protected class handling - You need to review HQS/NSPIRE inspection tracking or abatement workflows - A codebase handles tenant eligibility, subsidy calculations, or housing vouchers TRIGGER PHRASES: "affordable housing", "Section 8", "LIHTC", "public housing", "waitlist management", "income verification", "Fair Housing", "HUD compliance", "rent calculation", "housing voucher", "tenant management", "HQS inspection", "unit allocation", "housing authority"

The English summary is being prepared. Showing the original description.

Audit LLM token cost estimates against actual API usage. Activate on 'cost verification', 'token estimate accuracy', 'API cost audit', 'estimation variance'. NOT for pricing lookups, budget planning, or cost optimization strategies.

The English summary is being prepared. Showing the original description.

Turn verification recordings and pull request videos into captioned MP4 files with zoom and playback speed changes. Preserve the original recording as evidence while adding visual explanations that help viewers follow the demonstrated actions.

• Add explanatory captions to a pull request recording
• Zoom in on controls during a UI demonstration
• Speed up waiting periods in a verification video

Design or change REA investigation tools by defining responsibilities, inputs, results, and CLI or MCP interfaces. Produce a proposal that explains how Evidence records should be interpreted, compares the nearest existing alternative, and outlines verification.

• Designing a new REA investigation tool
• Reviewing CLI or MCP inputs and results
• Defining provider responsibilities and Evidence meaning

Checks whether work is truly complete before reporting success, committing changes, or creating a pull request. It runs the relevant checks, reads their full output, and ties status reports to current evidence.

• Checking results before reporting completion
• Confirming that a bug fix resolves the original problem
• Verifying work before a commit or pull request

Run repository commands, inspect Git state, investigate CI or build failures, and verify focused fixes. Report the commands and results as evidence, clearly distinguishing local changes, local verification, commits, and pushes.

• Inspecting repository and branch state
• Investigating CI or build failures
• Making and verifying a focused fix

Verify Quarkus services before pull requests or deployment through builds, code analysis, tests, coverage reports, and security scans. The workflow also checks native executables, containers, performance, health endpoints, configuration, and documentation.

• Checking a Quarkus service before a pull request
• Verifying refactoring or dependency upgrades
• Checking native executable compatibility

Break an RFC, a written design proposal, into work units with dependencies and acceptance tests for multiple agents. Organize research, implementation, testing, review, queued merges, and final system verification for features too large for one pass.

• Splitting a large design proposal into verifiable work units
• Assigning dependent tasks to multiple agents
• Managing review and queued merges of agent-built branches

Design or review repeating agent workflows with machine-checkable goals, protected boundaries, independent verification, and retry limits. It helps identify endless retries, manipulated checks, and incorrect completion while keeping final judgment with a human.

• Define completion criteria for repeating agent tasks
• Review loops for endless retries and manipulated checks
• Separate planning, building, and independent verification

Check a Laravel project before merging or deploying. Work through environment settings, code checks, tests and coverage, dependency security, database changes, caches, queues, and scheduled tasks, stopping when a required check fails.

• Checking a Laravel project before opening a pull request
• Verifying a major refactor or dependency upgrade
• Checking readiness for staging or production deployment

Organize a real mailbox, draft replies using thread history, and verify sent messages. The workflow identifies the account and recipient, checks commitments and deadlines, and reports whether a message is drafted, sent, blocked, or awaiting verification.

• Sorting an inbox and identifying mail to archive
• Drafting replies based on conversation history
• Sending email and checking the sent copy

Check a Django application before a pull request or deployment. Review its environment, code quality, database changes, tests, vulnerabilities, and configuration, then produce a phased pass/fail report identifying issues that need fixes.

• Checking a Django pull request
• Reviewing database migrations
• Checking test coverage targets

Review Cisco IOS and IOS-XE configurations, choose read-only troubleshooting commands, and plan checks before and after network changes. Examine traffic filtering rules, interface settings, and configuration saving to avoid overlooked operational risks.

• Review router and switch configurations before a change
• Choose read-only commands for troubleshooting
• Check traffic filtering masks and interface direction

Give an AI agent its own email inbox using the AgentMail CLI. Send and receive messages, handle replies and attachments, complete email verification codes, and trigger ongoing workflows when new mail arrives.

• Creating an email address for an AI agent
• Sending messages and handling replies or attachments
• Completing verification with codes received by email

Turn clear requirements into small implementation tasks with acceptance criteria, verification steps, dependencies, and estimated scope. Produce a written plan and ordered task list, with checkpoints and opportunities for parallel work identified before coding begins.

• Breaking a large feature into implementable tasks
• Ordering work by dependencies
• Defining completion criteria and verification steps

Coordinate a complete Paperclip release, from candidate verification and canary testing to stable npm publication and GitHub Release creation. Track release notes, Docker smoke tests, announcement follow-up, and linked content cases when Cases are enabled.

• Coordinating a complete Paperclip release
• Promoting a tested canary to a stable release
• Checking release candidates with Docker smoke tests