{"id":"opslane-verify","name":"verify","homepage":null,"repo_url":"https://github.com/opslane/verify","category":"testing","subcategories":[],"tags":["claude","claude-code","claude-code-plugins","claude-code-skill","verification","playwright","browser-automation","spec-testing","qa","evidence"],"what_it_does":"A Claude Code plugin (“opslane-verify”) that performs spec-driven verification: it interprets an acceptance-spec document, extracts acceptance criteria, runs one browser automation agent per criterion (Playwright) against a local dev server, then a judge step reviews screenshots/traces to produce pass/fail results with evidence (screenshots and session recordings).","use_cases":["Validating web-app behavior against a written set of acceptance criteria before pushing changes","Generating automated evidence (screenshots/video/Playwright traces) for failed acceptance criteria","Reducing manual QA effort for regression checks driven by spec documents"],"not_for":["Use as a general-purpose CI/CD system (README explicitly states “No CI. No infrastructure.”)","High-assurance security testing or compliance validation without human review (it’s an automated verification workflow, not a formal verifier)","Environments where you cannot run browser automation against a local dev server"],"best_when":"You have a local dev server and a stable, testable acceptance-spec format, and you want quick feedback with visual evidence for each acceptance criterion.","avoid_when":"You need strongly controlled, deterministic testing at scale (e.g., large suites in shared CI environments), or you cannot safely run browser agents that interact with the app under test.","alternatives":["Playwright test runner with hand-authored test specs","Cypress + visual diffing","BDD frameworks (Cucumber/Behave) with Playwright/Selenium backends","Contract/spec-based testing tools that integrate into CI pipelines"],"af_score":35.2,"security_score":47.8,"reliability_score":6.2,"package_type":"skill","discovery_source":["openclaw"],"priority":"high","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-03-30T13:47:33.999530+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["claude login (OAuth login for Claude Code)"],"oauth":true,"scopes":false,"notes":"The README mentions Claude Code with OAuth login via `claude login`, but does not describe scopes or plugin-specific authorization beyond requiring that login."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information found in the provided content."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":35.2,"security_score":47.8,"reliability_score":6.2,"mcp_server_quality":35.0,"documentation_accuracy":60.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":70.0,"rate_limit_clarity":0.0,"tls_enforcement":60.0,"auth_strength":60.0,"scope_granularity":20.0,"dependency_hygiene":45.0,"secret_handling":50.0,"security_notes":"The provided content does not describe TLS usage, secret handling, or dependency posture for the plugin itself; it only references Playwright and that Claude Code uses OAuth login. Because the workflow runs browser agents against a local dev server, it may have access to application data visible in the UI—users should ensure test environments and data exposure are appropriate.","uptime_documented":0.0,"version_stability":0.0,"breaking_changes_history":0.0,"error_recovery":25.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Spec interpretation/planning may require the user to provide a testable spec and answer clarifying questions before execution.","Browser-agent runs can be non-deterministic if the app under test is flaky or uses timing-dependent UI behavior.","Parallel execution per acceptance criterion (if implemented) may stress shared dev-server state; without explicit isolation, runs may affect each other.","The workflow is evidence-heavy (screenshots/video/trace), which may be impacted by large sessions or environment limitations."]}}