verify-implementation

Discover and run verify-* skills from a manifest, reporting failures with concrete paths.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/zdpk/skills --skill verify-implementation-zdpk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-implementation
Source: https://github.com/zdpk/skills/tree/main/dotfiles/skills/custom/meta/verify-implementation
Command: npx skills add https://github.com/zdpk/skills --skill verify-implementation-zdpk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run centralized, repeatable verification by discovering verify-* skills from a manifest and reporting failures with concrete file paths.

Core Features & Use Cases

  • Discover and execute verify-* skills listed in a central manifest.
  • Generate a consolidated pass/fail report with detailed failure paths for remediation.
  • Use case: run a full verification cycle across all skills in a project to ensure readiness before release.

Quick Start

Run verify-implementation from a project directory to execute the verification workflow and produce a results report.

Frequently Asked Questions about verify-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run automated verification across multiple skills in a local project?▼

Automated verification across multiple skills runs by discovering verify-* skills from a central manifest and executing them sequentially to produce a consolidated pass/fail report.

What is the best way to orchestrate verify-packs and report failures with concrete file paths?▼

Orchestrating verify-packs involves reading the default.yaml manifest to locate verification steps, executing them, and generating a report that lists concrete file paths for any failures.

Does centralized verification work with projects containing .claude/skills and .claude/packs directories?▼

Centralized verification works specifically with local projects containing .claude/skills and .claude/packs directories, requiring access to the verify/default.yaml manifest and per-skill SKILL.md files.

How do I generate a consolidated pass/fail report to ensure project readiness before release?▼

A consolidated pass/fail report for release readiness is generated by running a full verification cycle across all discovered project skills, detailing failure paths for remediation.

Can I execute verification workflows deterministically without modifying source code?▼

Verification workflows execute deterministically without modifying source code, relying solely on reading the manifest and SKILL.md files to validate project readiness.

Why does my verification workflow require access to per-skill SKILL.md files?▼

Verification workflows require per-skill SKILL.md files because the central manifest uses them to identify and execute the specific verification steps needed for each skill.