count-registry

Name: count-registry
Availability: InStock
Author: crytlig

Count agents, skills, instructions, and validators from filesystem data.

Updated Mar 27, 2026

Search Tags:#documentation #validation #metadata #project-management #counts

Ready to run

npx skills add https://github.com/crytlig/azure-agentic-infraops --skill count-registry

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining accurate and consistent counts of project components, preventing hard-coded values that can drift over time.

Core Features & Use Cases

Entity Counting: Retrieves the total numbers of agents, skills, instructions, and validators from a single source.
Data Consistency: Ensures project documentation and codebase reflect actual component counts without manual updates.
Use Case: Use this Skill to verify the number of available skills before deploying or documenting a new release to ensure accuracy.

Quick Start

Use the count-registry skill to get the current number of skills in the project catalog.

Frequently Asked Questions about count-registry

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

FAQPage Schema

How do I get accurate counts of agents and skills in my project environment?▼

To get accurate counts of agents and skills, you can use a registry tool that reads filesystem data to retrieve the total numbers of agents, skills, instructions, and validators within your project environment.

Why do my project documentation counts keep drifting from the actual codebase?▼

Project documentation counts drift because they rely on hard-coded values that become outdated. Using a filesystem data source prevents this by ensuring documentation and codebase reflect actual component counts without manual updates.

What's the best way to verify the number of available skills before a release?▼

The best way to verify the number of available skills before a release is to retrieve current component totals from a single source using filesystem data, ensuring your deployment documentation is accurate.

Do I need to manually update counts for instructions and validators?▼

You do not need to manually update counts for instructions and validators. By retrieving current totals from filesystem data, you ensure documentation and processes stay synchronized without hard-coded values.

Can I use filesystem data to synchronize project management metadata?▼

Yes, you can use filesystem data to synchronize project management metadata by retrieving authoritative counts of project entities, which ensures data consistency across the codebase.