skills.rest
yonatangross
yonatangrossCOMMUNITY
Explore all skills by this author →
𝕏@yonyonizGitHub

validate-counts

Validate hook, skill, and agent counts across documentation and manifests.

217|20|Updated Dec 31, 2025
Search Tags:#documentation#consistency#validation#manifests#counts#orchestkit
One-click install
npx skills add https://github.com/yonatangross/orchestkit --skill validate-counts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-counts
Source: https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/validate-counts
Command: npx skills add https://github.com/yonatangross/orchestkit --skill validate-counts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and rules (resource) components.

What problem does it solve?

This Skill ensures that the counts of skills, agents, and hooks reported in documentation and manifests precisely match the actual number of components in the codebase, preventing misleading information and ensuring consistency.

Core Features & Use Cases

  • Cross-Source Validation: Compares counts from filesystem sources (src/) against documentation (CLAUDE.md) and configuration files (manifests/ork.json).
  • Drift Detection: Identifies and reports any discrepancies, flagging specific files and fields that are out of sync.
  • Use Case: Before a release, run this Skill to verify that the "89 skills" mentioned in the README accurately reflects the number of skill directories present in src/skills/, and that all other component counts are also consistent.

Quick Start

Run the validate-counts skill from the repository root to check all component counts.

Frequently Asked Questions about validate-counts

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

FAQPage Schema
How do I validate component counts in manifests against source directories?▼

Drift detection identifies discrepancies between filesystem counts and documentation or manifest entries. It flags specific files and fields out of sync, preventing misleading information before a release.

Why does my CLAUDE.md documentation show a different skill count than the src directory?▼

Your CLAUDE.md documentation shows a different skill count because of drift between the filesystem and documentation. Validation compares counts across these sources to identify and report the specific mismatches.

Can I check OrchestKit manifest consistency before a release?▼

You can check OrchestKit manifest consistency before a release by running cross-source validation. This compares counts from filesystem sources against manifests and documentation files to ensure accurate component reporting.

What's the best way to detect configuration drift in hook and agent counts?▼

The best way to detect configuration drift is cross-source validation. It compares hook and agent counts from configuration files like hooks.json against filesystem sources, reporting mismatches with precise file references.

Related Skills

Explore More Software Engineering Skills→
codenamevcodenamev
74

architecture-status

Aggregate ADR counts, reviews, and activity metrics into a Markdown status report.

Community
Basic
jeremylongshorejeremylongshore
2.6k

detecting-infrastructure-drift

Detect infrastructure drift between current state and desired configuration.

Community
Advanced
yonatangrossyonatangross
217

analytics

Query local analytics data to analyze OrchestKit agent performance and token costs.

Community
Intermediate
NinatuziNinatuzi

skill-creator

Generate SKILL.md structures with YAML frontmatter and validate against the manifest.

Community
Intermediate