skills.rest
sohamda
sohamdaCOMMUNITY
Explore all skills by this author →
Website𝕏@iamsohamGitHub

count-registry

Provides canonical entity counts from count-manifest.json to prevent hard-coded numbers in documentation.

Updated May 12, 2026
Search Tags:#documentation#validation#drift detection#registry#manifest#single source of truth#entity counts
One-click install
npx skills add https://github.com/sohamda/apex-try-out-demo-repo --skill count-registry-sohamda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: count-registry
Source: https://github.com/sohamda/apex-try-out-demo-repo/tree/main/.archive/_archived_skills/count-registry
Command: npx skills add https://github.com/sohamda/apex-try-out-demo-repo --skill count-registry-sohamda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation and generated artifacts often hard-code entity counts (agents, skills, validators) that drift out of sync with the actual repository, causing stale and inconsistent numbers across files. ## Core Features & Use Cases - Single Source of Truth: All entity counts live in tools/registry/count-manifest.json, which validators auto-compute from filesystem globs. - Canonical Phrasing Guide: Provides approved descriptive phrases like "specialized agents and subagents" so prose avoids brittle numbers. - Drift Detection Support: Works with the validate-no-hardcoded-counts.mjs validator that compares documented counts against actual filesystem values. - Use Case: When an agent generates a README section mentioning how many skills exist, it reads the manifest and cites the number with its source instead of hard-coding a value. ## Quick Start Ask the agent how many agents or skills exist in this project and have it read the count manifest rather than guessing a number.

Frequently Asked Questions about count-registry

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

FAQPage Schema
How do I find how many agents or skills exist in this project?▼

Read the count-manifest.json file in the tools/registry directory, which is the single source of truth for entity counts. Validators auto-compute these values from filesystem globs, so the manifest always reflects the actual repository state.

How should documentation reference entity counts without going stale?▼

Prefer descriptive canonical phrases like "specialized agents and subagents" or "the skill catalog" instead of numbers. When an exact count is required, read count-manifest.json and cite it parenthetically as the source.

Why are hard-coded counts in documentation a problem?▼

Hard-coded counts drift out of sync as agents, skills, and validators are added or removed, producing inconsistent documentation. The validate-no-hardcoded-counts.mjs validator detects this drift by resolving manifest globs against the filesystem.

Are any fixed numbers allowed to be hard-coded?▼

Yes, entities with a static value field in the manifest, such as the ten golden principles, are genuinely fixed and exempt from the no-hard-coding rule. Only counts computed from filesystem globs must avoid hard-coding.

When should I use exact numbers versus descriptive phrasing?▼

Use descriptive phrasing by default in committed prose, since numbers become stale. Reserve exact counts for cases where precision is required, and always state the manifest as the source alongside the number.

Related Skills

Explore More Software Engineering Skills→
qprjack86qprjack86

count-registry

Read .github/count-manifest.json to provide authoritative repository entity counts.

Community
Basic
cassm199-mitacassm199-mita

count-registry

Manage project entity counts stored in a JSON manifest.

Community
Basic
friedbotstudiofriedbotstudio
5

audit-baseline

Detect drift between on-disk baseline implementations and their specifications.

Official
Advanced
yonatangrossyonatangross
217

validate-counts

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

Community
Intermediate