Run any Skill in Manus with one click

validate-counts

Stars193

Forks15

UpdatedJune 22, 2026 at 19:19

Validates hook, skill, and agent counts are consistent across CLAUDE.md, hooks.json, manifests, and source directories. Use when counts may be stale after adding or removing components, before releases, or when CLAUDE.md Project Overview looks wrong.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

yonatangross

yonatangross/orchestkit

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

9 files

SKILL.md

readonly

name	validate-counts
compatibility	Claude Code 2.1.183+
description	Validates hook, skill, and agent counts are consistent across CLAUDE.md, hooks.json, manifests, and source directories. Use when counts may be stale after adding or removing components, before releases, or when CLAUDE.md Project Overview looks wrong.
tags	["validation","consistency","orchestkit"]
version	2.0.0
author	OrchestKit
user-invocable	false
disable-model-invocation	true
context	inherit
allowed-tools	["Read","Bash","Grep","Glob"]
complexity	low
persuasion-type	discipline
effort	low
model	haiku

Validate Counts

Checks that hook, skill, and agent counts are consistent across all authoritative sources in OrchestKit. Outputs a comparison table and flags drift with precise file references.

Quick Start

# Full validation: counts src/ vs CLAUDE.md and manifests (run from repo root)
bash src/skills/validate-counts/scripts/validate-counts.sh

# Just get raw counts from src/
bash src/skills/validate-counts/scripts/count-all.sh

Rules

Category	Rule	Impact	Key Pattern
Count Sources	`rules/sources-authoritative.md` (load `${CLAUDE_SKILL_DIR}/rules/sources-authoritative.md`)	HIGH	Filesystem is authoritative; derived sources must match
Drift Detection	`rules/drift-reporting.md` (load `${CLAUDE_SKILL_DIR}/rules/drift-reporting.md`)	HIGH	Comparison table + flag with file:field references

Total: 2 rules across 2 categories

Workflow

Run scripts/validate-counts.sh for full validation (counts + drift comparison), or scripts/count-all.sh for raw counts only
Read CLAUDE.md — extract counts from Project Overview and Version section
Read manifests/ork.json — check skill/agent/hook array lengths
Build the comparison table (see rules/drift-reporting.md for format)
Flag any mismatches with file + field references; otherwise output "All counts consistent."

References

Load on demand with Read("${CLAUDE_SKILL_DIR}/references/<file>"):

File	Content
`count-locations.md`	Where every count lives and why drift happens

Related Skills

release-checklist — Uses validate-counts as step 5 of the release gate
doctor — Broader health check that includes count validation
audit-skills — Quality audit for skill structure and completeness

Common Mistakes

Counting from plugins/ instead of src/ — plugins/ may be empty after an interrupted build
Comparing against deleted alias manifests — only manifests/ork.json exists in v7
Forgetting the hook breakdown: global + agent-scoped + skill-scoped must sum to total

More from this repository

same repository

doctor

yonatangross/orchestkit

OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned entries, and checks CC version matrix compliance. Use when diagnosing plugin health, troubleshooting configuration issues, or running pre-release checks.

2026-06-23193

mcp-visual-output

yonatangross/orchestkit

Interactive MCP visual output via @json-render/mcp. Upgrade plain JSON tool responses to interactive dashboards rendered in sandboxed iframes inside Claude, Cursor, ChatGPT, VS Code Copilot, Goose, and Postman conversations. Covers createMcpApp(), registerJsonRenderTool(), registerJsonRenderResource(), CSP config, JSON Patch streaming, and dashboard component patterns. Use when building MCP servers that return visual output, upgrading existing MCP tools with interactive UI, or creating eval/monitoring dashboards.

2026-06-22193

multi-surface-render

yonatangross/orchestkit

Multi-surface rendering with json-render — same JSON spec produces React web, Next.js apps, React Native, Ink terminal UIs, PDFs, emails, Remotion videos, OG images, and 3D scenes. Covers renderer target selection, registry mapping, and platform-specific APIs (renderToBuffer, renderToStream, renderToFile). Use when generating output for multiple platforms, creating PDF reports, email templates, demo videos, or social media images from a single component spec.

2026-06-22193

browser-tools

yonatangross/orchestkit

OrchestKit security wrapper for browser automation. Adds URL blocklisting, rate limiting, robots.txt enforcement, and ethical scraping guardrails on top of the upstream agent-browser skill. Use when automating browser workflows that need safety guardrails.

2026-06-22193

dev

yonatangross/orchestkit

One-command dev loop boot. Spins up portless (named HTTPS subdomain), emulate (stateful API mocks), the project's dev server, and an agent-browser session — all using the current git branch as the namespace key. Replaces the 4-terminal manual setup with a single `/ork:dev` invocation. Use when starting a new feature branch, switching worktrees, or returning to a project after a break. Skip silently when prerequisite binaries (portless, emulate, agent-browser) are missing — emits install hints.

2026-06-22193

emulate-seed

yonatangross/orchestkit

Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS (S3/SQS/IAM), Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs. Not mocks — full state machines where create-a-PR-and-it-appears-in-the-list, send-an-email-and-retrieve-from-local-inbox. Use when setting up test environments, CI pipelines, integration tests, or offline development.

2026-06-22193

name	validate-counts
compatibility	Claude Code 2.1.183+
description	Validates hook, skill, and agent counts are consistent across CLAUDE.md, hooks.json, manifests, and source directories. Use when counts may be stale after adding or removing components, before releases, or when CLAUDE.md Project Overview looks wrong.
tags	["validation","consistency","orchestkit"]
version	2.0.0
author	OrchestKit
user-invocable	false
disable-model-invocation	true
context	inherit
allowed-tools	["Read","Bash","Grep","Glob"]
complexity	low
persuasion-type	discipline
effort	low
model	haiku

Validate Counts

Checks that hook, skill, and agent counts are consistent across all authoritative sources in OrchestKit. Outputs a comparison table and flags drift with precise file references.

Quick Start

# Full validation: counts src/ vs CLAUDE.md and manifests (run from repo root)
bash src/skills/validate-counts/scripts/validate-counts.sh

# Just get raw counts from src/
bash src/skills/validate-counts/scripts/count-all.sh

Rules

Category	Rule	Impact	Key Pattern
Count Sources	`rules/sources-authoritative.md` (load `${CLAUDE_SKILL_DIR}/rules/sources-authoritative.md`)	HIGH	Filesystem is authoritative; derived sources must match
Drift Detection	`rules/drift-reporting.md` (load `${CLAUDE_SKILL_DIR}/rules/drift-reporting.md`)	HIGH	Comparison table + flag with file:field references

Total: 2 rules across 2 categories

Workflow

Run scripts/validate-counts.sh for full validation (counts + drift comparison), or scripts/count-all.sh for raw counts only
Read CLAUDE.md — extract counts from Project Overview and Version section
Read manifests/ork.json — check skill/agent/hook array lengths
Build the comparison table (see rules/drift-reporting.md for format)
Flag any mismatches with file + field references; otherwise output "All counts consistent."

References

Load on demand with Read("${CLAUDE_SKILL_DIR}/references/<file>"):

File	Content
`count-locations.md`	Where every count lives and why drift happens

Related Skills

release-checklist — Uses validate-counts as step 5 of the release gate
doctor — Broader health check that includes count validation
audit-skills — Quality audit for skill structure and completeness

Common Mistakes

Counting from plugins/ instead of src/ — plugins/ may be empty after an interrupted build
Comparing against deleted alias manifests — only manifests/ork.json exists in v7
Forgetting the hook breakdown: global + agent-scoped + skill-scoped must sum to total