Results for “source-validation”

Validates observable behavior of apps, CLIs, APIs, and generated artifacts against a prewritten contract without inspecting source code.

Use this skill for context gathering, file triage, source maps, assumptions, task framing, prompt hygiene. Trigger when the task involves programming work related to Context Engineering, production implementation, audits, debugging, strategy, or validation.

Use this skill for crypto market research, tokens, narratives, liquidity, risks, source verification. Trigger when the task involves crypto work related to Crypto Market Research, production implementation, audits, debugging, strategy, or validation.

Use this skill for search indexing, embeddings, RAG chunking, freshness, retrieval evaluation, source citations. Trigger when the task involves ai engineering work related to Search Indexing RAG, implementation, audits, debugging, strategy, or validation.

Use when incorporating information from research, references, or external sources. This skill provides verification procedures to ensure information used in deliverables is accurate, current, and from authoritative sources, preventing hallucination and misinformation.

Verifies a claim by finding primary sources and rates the evidence as supported, mixed, unsupported, or unverifiable, with citations and what would change the verdict.

Use when sources must stay traceable across sessions and years, when each reference needs a passport recording where it was found, how it was verified, and where it is cited, or when a draft needs a cited-but-unverified sweep before submission.

Centralized JSON validation for AGENT_SUCCESS_CRITERIA with defensive parsing and injection attack prevention (CVSS 8.2)

Verify the article’s factual, product, citation, and link integrity before visual production.

Runs bottom-up type-chain validation across database, hooks, and UI layers, then fixes errors at the failing layer for project health checks before large changes.

Find sources for every numerical claim in the draft, add inline hyperlinks, and add internal links to brand-reference articles. Triggered after /draft.

A validation *boundary* is any point where data crosses from a system you do not

Validates generated SRS documents against IEEE 830-1998, fixing errors and reporting warnings.

Validates generated SRS documents against IEEE 830-1998, fixes errors, and reports compliance verdict.

Validates Claude Ads contracts, bundles, scores, runs, capabilities, repositories, and releases with deterministic checks and recovery steps.

Validate user claims against codebase and git history, trace to root cause, and propose a fix

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

Documents the original sources, licenses, and attribution notes for skills in this collection, including those adapted from HackTricks, OWASP, and community repositories.

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

Assess software supply chain security by generating SBOMs, scanning dependencies, auditing CI/CD pipelines, analyzing container images, and verifying vulnerability reachability.

Verify a code change end-to-end in the current worktree: figure out what changed, run the relevant tests, get the app running, drive a browser to exercise the affected areas, and report a verdict with screenshots. Generic across project types (Laravel/Herd, Node/bun, frontend, CLI, library). Use this skill whenever the user wants to verify/QA/smoke-test a change, check that a PR or branch's changes actually work, validate uncommitted work before pushing, or says "/flow", "flow this", "verify this change", "does this PR work", "check my changes", "test and click through this". Accepts an optional target (a PR number/URL, a branch/ref, or a worktree path); with no argument it verifies the current uncommitted/working changes.

Use for writing, reviewing, debugging, migrating, or testing Python application configuration built with pydantic-settings. Trigger for BaseSettings, SettingsConfigDict, environment names, dotenv, secrets directories, nested settings, CLI sources, custom source precedence, and secret-safe startup configuration. Do not use for ordinary Pydantic model validation, direct os.environ access in a small script, or external secret manager administration.

Writes, audits, and troubleshoots Salesforce validation rules, covering formula best practices, bypass patterns, and integration pitfalls.

Performs authorized source-code security reviews using SAST tools like Semgrep and CodeQL, with manual verification of findings and fix recommendations.

Verifies claims, articles, screenshots, and URLs through source-grounded analysis with an evidence ledger, source credibility evaluation, and manipulation detection. Supports quick checks, full fact-check cards, two-source comparisons, and prebunking in multiple languages and policy contexts.

Validate process JS files for correct SDK patterns, task definitions, syntax, and quality gate implementation.

Define and enforce data schemas and quality checks using pandera, Great Expectations, or manual assertions, with clear error handling and documentation.

`analysis-agent`/`task-agent`/`review-agent`: use for input authority, parsing, canonicalization, bounds, state checks, writable fields, rejection, or external-response changes.

Validates custom dotnet new templates for correctness before publishing, catching missing fields, parameter bugs, shortName conflicts, constraint issues, and common authoring mistakes.

Parse source files to find which ones have no test file referencing their declared types, producing a prioritized worklist of untested files.