count-registry

Maintain entity counts in a project via a manifest file and automated validation.

Updated Apr 11, 2026

Search Tags:#validation #project documentation #project inventory #count management #entity counting

Ready to run

npx skills add https://github.com/jgezelscorp/Apex --skill count-registry-jgezelscorp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: count-registry
Source: https://github.com/jgezelscorp/Apex/tree/main/.github/skills/count-registry
Command: npx skills add https://github.com/jgezelscorp/Apex --skill count-registry-jgezelscorp

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that all counts of entities within the project are up-to-date and consistent, eliminating the need for hard-coded numbers and reducing the risk of errors.

Core Features & Use Cases

Single Source of Truth: All counts are stored in .github/count-manifest.json, providing a reliable reference.
Automated Validation: Validators automatically compute actual values from the filesystem, ensuring accuracy.
Descriptive Language: Encourages the use of descriptive language instead of exact numbers, improving readability and maintainability.
Use Case: When documenting the project or generating reports, this Skill helps maintain accurate statistics about the number of agents, skills, instructions, and validators.

Quick Start

Use the count-registry skill to get the current count of agents in the project.

Frequently Asked Questions about count-registry

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

FAQPage Schema

How do I maintain accurate entity counts in my project documentation?▼

To maintain accurate entity counts, you can use a manifest file to store all counts as a single source of truth, replacing hard-coded numbers with descriptive language to improve readability.

How does automated validation for project inventory work?▼

Automated validation for project inventory works by using validators to compute actual entity values directly from the filesystem, ensuring the counts in your manifest file remain accurate and consistent.

What is the best way to track component counts for project reports?▼

The best way to track component counts is to maintain a central manifest file that records statistics for agents, skills, instructions, and validators, ensuring your project reports stay up to date.

Can I use a manifest file to manage inventories without hard-coded numbers?▼

Yes, you can use a central manifest file to manage inventories without hard-coded numbers, encouraging the use of descriptive language instead of exact figures to improve project maintainability.

Does count management require any external dependencies to validate filesystem data?▼

No, count management does not require external dependencies to validate filesystem data, as it uses internal scripts and references to automatically compute actual values from the project directory.