Verifier Skill Generator

Use when a project needs one or more verifier skills for web, CLI, or API runtime checks that the Verify agent can discover automatically.

Security Scan

This instruction-only skill coherently describes generating repository-specific verifier skills and asks the agent to inspect the project; it does not request extra credentials or installs, but you should review any generated code before running it.

Purpose & Capability

The name/description match the SKILL.md: the skill's purpose is to inspect a project and generate verifier skill folders for web/CLI/API surfaces. There are no unexpected dependencies, binaries, or credentials declared.

Instruction Scope

The runtime instructions direct the agent to 'inspect the project' and detect stacks, layouts, and tooling availability — which reasonably implies reading repository files and configs. The instructions do not tell the agent to read unrelated system files or exfiltrate data, but reviewing repo files is inherent to the stated purpose and should be expected.

Install Mechanism

No install spec or code is included; this is instruction-only, so nothing will be written to disk by an installer as part of skill installation.

Credentials

The skill declares no required environment variables, credentials, or config paths. The SKILL.md does ask generated verifiers to include 'setup, authentication, cleanup, and self-update behavior' — but that applies to generated artifacts, not this skill's own runtime requirements.

Persistence & Privilege

always is false and there are no indications the skill modifies other skills or system-wide agent settings. The skill is user-invocable and can be invoked autonomously by the agent (platform default), which is expected for a generator.

Assessment

This skill is an instruction-only template for generating repository-specific verifier skills and appears internally consistent. Before installing or running it: (1) be prepared that the agent will scan your repository files and configs to detect stacks and tooling; (2) carefully review any verifier folders or code the skill generates (especially 'authentication' or 'self-update' code) before executing them or supplying secrets; and (3) if provenance matters to you, note the skill's source/homepage are unspecified—ask for author or repository details if you need stronger trust guarantees.

Use this skill to create project-specific verifier skills.

Workflow

1. Detect project areas and application types.
2. Decide whether each area needs web, CLI, or API verification.
3. Identify available automation tools and setup gaps.
4. Ask only the project-specific questions needed to finalize each verifier.
5. Generate verifier skill folders in the repo so verification can be repeated later.

Guardrails

• Focus on functional verification, not unit tests or type checks.
• Use names discoverable by downstream verification tooling.
• Include setup, authentication, cleanup, and self-update behavior in each verifier.

Example Requests

• Generate verifier skills for this frontend and API.
• Inspect the project and create runtime verifier skills the Verify agent can find.

Inputs

• Project layout
• Detected stacks
• Verification tooling availability

Outputs

• One or more verifier skill folders
• Project-specific setup guidance

Success Criteria

• Relevant project areas were detected correctly.
• Generated verifiers match web, CLI, or API needs.
• Each verifier is discoverable and reusable.

Non-Goals

• Unit-test-only verification setup
• Generic verifier templates with no project specifics

Source Provenance

Derived from src/commands/init-verifiers.ts.