3.5K skills · sorted by relevance
Automate Emaillistverify operations through Rube MCP, a connection for agent tools. Discover available actions and their required inputs, check the service connection, and execute individual or bulk operations through Composio.
Verify a qwen-code pull request in an isolated environment by comparing its behavior with a control build and running focused tests. Produce a report and machine-readable verdict that distinguish measured results from areas left untested.
This skill should be used when the user asks to "dev-verify", "実装の検証", "完了チェック", "verify implementation", "全テスト実行", "run all tests", "dev-verify auth". Plan単位で全タスクの完了状態とテスト・ビルド・Lintの整合性を検証し、レポートを出力する。
The English summary is being prepared. Showing the original description.
Verify that an application works correctly using `stably verify`. Use when an AI agent has made code changes and needs to validate the feature works in a real browser. The command describes expected behavior in plain English and reports a PASS/FAIL/INCONCLUSIVE verdict — no test files generated. Triggers on: "verify this works", "stably verify", "check if this works", "validate my changes", "verify my feature", "does this work", "check the app", "verify the feature".
The English summary is being prepared. Showing the original description.
Use when you need to verify Java performance optimizations by comparing profiling results before and after refactoring — including baseline validation, post-refactoring report generation, quantitative before/after metrics comparison, side-by-side flamegraph analysis, regression detection, or creating profiling-comparison-analysis and profiling-final-results documentation. This should trigger for requests such as Verify performance fix; Verify the performance; Verify the memory; Verify the threading; Compare before and after profiling results; Check for performance regressions after refactoring. Part of Plinth Toolkit
The English summary is being prepared. Showing the original description.
Verify RuView changes with Rust and Python tests, output hashes that detect processing changes, and firmware hash records. Packages test logs and audit evidence into a witness bundle that recipients can check with a single command.
Reproduce and verify Weave Router behavior locally with Docker Compose and Claude CLI. Test model routing, response conversion, and streaming against real APIs or a mock service, then inspect logs without changing global Claude Code settings.
Verify completed code changes in six stages: build, type checks, lint, tests with coverage, searches for possible secrets, and diff review. Produces a pass/fail report with issues to fix and readiness for a pull request.
Verify Paperclip through real browser or command-line journeys across source checkouts, published npm installations, or existing hosted environments. Record the exact version, platform, starting data, observed behavior, and supporting evidence for each tested journey.
Verify RuView pipeline output against a reference hash, package evidence for others to check, and review accuracy statements. The skill distinguishes measured, claimed, and synthetic results and requires real device logs for hardware validation.
Verify WorldMonitor dashboard behavior using existing browser tests or focused manual interactions. Check panels, map layers, settings, search, and country briefs, while collecting screenshots, logs, and persisted-state evidence to document the results.
Verify the witness chain, a linked record of evidence, for a Cognitum Seed device. Check for missing recording periods and broken hash links, report an integrity score, and save detected gaps for auditing.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.
Compare an implementation with its OpenSpec specifications, tasks, and design decisions before archiving the change. Get a report on completion, requirement coverage, and consistency, with prioritized issues, actionable recommendations, and explicit limits where evidence is missing.
Test the Senpi adapter and task engine against the real senpi binary in an isolated environment. Check task and team behavior, record evidence in a consistent location, and verify that the existing agent directory remains untouched.
Test omo Codex Light edition in an isolated environment using real Codex and a local mock model. Verify installation, plugin hooks, and terminal startup, with captured evidence and no calls to a real model API.
Configure a Claude Code hook that checks shell commands before execution and blocks flags that skip Git checks or commit signing. It helps preserve existing commit quality checks while documenting the guard's limits.
Check AI agent plugins and tools for changed, missing, or untracked files using SHA-256 file fingerprints. Generate integrity records, review dependency version settings, and check requirements before promoting a plugin to production.
Use the CopilotKit CLI to check app connections, credentials, and agent responses before investigating code. It also guides project creation, integration into existing apps, hosted project selection, typed agent identifier generation, and thread history imports.
Verify a local OpenSEO MCP server, which exposes tools to AI agents, through real DataForSEO calls and a headless Claude trial. Check protocol correctness alongside tool discovery, input rules, response size, errors, and asynchronous task recovery.
Test a released archon binary through Homebrew or curl installation on macOS or a Linux VPS. Check version information, bundled workflows, Claude execution, and sensitive environment key removal, then clean up and report the results.
Verify a code change by running the app and checking that it works as expected. Use it after a fix or other change to confirm the intended behavior in the running application.
Verify whether a reported vulnerability is fixed in the current code without changing repository files. Trace the original attack path, examine possible bypasses and legitimate behavior, and return an evidence-based verdict for each supplied finding.
Verify whether a reported vulnerability is fixed in the current code without changing repository files. Trace the original attack path, examine possible bypasses and legitimate behavior, and return an evidence-based verdict for each supplied finding.