Security & Testing Agent Skills for Claude Desktop

Verify an Obsidian plugin with Node unit tests, typecheck, production build, and Selenium E2E against real Obsidian.

Verify, inspect, discharge, or waive CbC claims for cbc=mandatory artifacts using the evidence ledger

A behavioral skill that forces every claim the agent makes to be evidence-gated and honestly labeled.

Select and execute the verification that actually proves the change works, based on what type of change it is.

Multi-AI validation, scoring, and review using available external providers (Double Diamond Deliver phase)

Extracts and verifies the runnability and code coverage of all Python code blocks inside a Markdown file.

Use for a technical incident, disputed diagnosis, bug fix, or claim that a change works.

Verify a claim with fresh local evidence: restate it falsifiably, capture baseline and treatment, compare artifacts, and return VERIFIED…

Concrete, per-area proof that a change actually works before reporting it fixed, done, or "should work now" — which dev server, test…

Use when about to run tests/builds for ctsnetwork-event, after editing any file in event/backend or event/frontend, or before reporting…

Use when applying web best practices — security headers, modern APIs, error handling.

Use when stakes are high — adversarial fresh-context review of every non-trivial decision.

Use when handling user input, auth, secrets, or external integrations — prevent OWASP Top 10, enforce auth patterns, secrets management…

Use when auditing web quality — orchestrate performance, a11y, SEO, best-practices across Lighthouse categories.

Audit rapidly generated or AI-produced code for structural flaws, fragility, and production risks.

Independently evaluate supplied technical and perceptual evidence for an immutable identified render.

4-phase root cause investigation methodology for bugs and unexpected behavior.

Structure descriptive evidence about already identified media assets or immutable renders.

Pixel-perfect visual testing with auto-fix loop.

Use after frontend, UI, UX, visual polish, responsive layout, design-to-code, dashboard, website, app-screen, or TUI changes when the…

MUST USE after building/changing any UI or when asked whether a page, component, or TUI looks right.