count-registry

Retrieve and validate project entity counts from .github/count-manifest.json.

6|2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/jonathan-vella/azure-smb-rf --skill count-registry-jonathan-vella
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: count-registry
Source: https://github.com/jonathan-vella/azure-smb-rf/tree/main/.github/skills/count-registry
Command: npx skills add https://github.com/jonathan-vella/azure-smb-rf --skill count-registry-jonathan-vella

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The skill unit helps in providing accurate and consistent reference counts for entities such as agents, skills, instructions, or validators within a project. It eliminates hard-coding of counts and promotes descriptive language in documentation.

Core Features & Use Cases

  • Single Source of Truth: Ensures that counts are always derived from a single .github/count-manifest.json file, eliminating discrepancies and ensuring consistency.
  • Descriptive Language: Encourages the use of descriptive language in documentation to reference entities rather than specific numbers.
  • Manual Checking: Informs developers about manually reviewing .github/count-manifest.json when exact counts are required for precise references.

Quick Start

Query the count-registry skill to find the total number of agents and skills in your project.

Frequently Asked Questions about count-registry

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

FAQPage Schema
How do I retrieve entity counts for project documentation without hard-coding numbers?

You can retrieve entity counts by querying a centralized manifest file. The skill automates retrieval and validation using .github/count-manifest.json to provide accurate references for project documentation without hard-coding values.

How does a count manifest file ensure consistent entity inventory references?

A count manifest file acts as a single source of truth for entity inventory. It derives all counts from .github/count-manifest.json, eliminating discrepancies and ensuring consistent references across project documentation.

What is the best way to manage counts for agents, skills, and validators in a project?

The best way to manage entity counts is using a registry skill that automates retrieval. It targets project management by validating counts against .github/count-manifest.json, encouraging descriptive language rather than specific numbers in documentation.

Do I need to manually update .github/count-manifest.json when exact counts are required?

Yes, you need to manually review .github/count-manifest.json when exact counts are required for precise references. The skill informs developers to check this file directly for accurate project entity counts.

Can I use descriptive language in documentation instead of hard-coded entity counts?

Yes, you can use descriptive language in documentation to reference entities. The skill promotes this approach by automating count retrieval from .github/count-manifest.json, eliminating the need to hard-code specific numbers in project documentation.