Agent skill

aget-check-evolution

Monitor .aget/evolution/ directory health. Validates file counts, naming conventions, disk usage, and returns health status with alerts on anomalies.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill aget-check-evolution-aget-framework-template-consultant --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Version: 1.0.0
Path: skills/agent/aget-check-evolution-aget-framework-template-consultant/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /aget-check-evolution Monitor the health of the `.aget/evolution/` directory by checking file counts, types, naming conventions, and disk usage. ## Purpose Provide self-diagnostic capability for AGET agents to assess their evolution directory health without supervisor intervention. ## Execution When invoked, perform these checks: ### 1. File Inventory ```bash # Count total files find .aget/evolution -type f | wc -l # Count by extension find .aget/evolution -type f -name "*.md" | wc -l find .aget/evolution -type f -name "*.json" | wc -l find .aget/evolution -type f ! -name "*.md" ! -name "*.json" | wc -l ``` ### 2. Naming Convention Check Valid L-doc pattern: `L###_*.md` (e.g., `L588_skill_invocation_control_semantics.md`) ```bash # Count valid L-doc names find .aget/evolution -type f -name "L[0-9][0-9][0-9]_*.md" | wc -l # Find non-conforming files (excluding index.json) find .aget/evolution -type f ! -name "L[0-9][0-9][0-9]_*.md" ! -name "index.json" ! -name "README.md" ``` ### 3. Disk Usage ```bash du -sh .aget/evolution ``` ### 4. Index Integrity Check that `index.json` exists and is valid JSON: ```bash test -f .aget/evolution/index.json && jq empty .aget/evolution/index.json

What's inside
Steps it walks through
  1. Purpose
  2. Execution
  3. 1. File Inventory
  4. 2. Naming Convention Check
  5. 3. Disk Usage
  6. 4. Index Integrity
  7. Thresholds
  8. Output Format
  9. Health Status Logic
  10. Constraints
  11. Related Skills
  12. Traceability
Ships with 1 file
  • metadata.json
Commands it runs
Count total files
find .aget/evolution -type f | wc -l
Count by extension
find .aget/evolution -type f -name "*.md" | wc -l
find .aget/evolution -type f -name "*.json" | wc -l
find .aget/evolution -type f ! -name "*.md" ! -name "*.json" | wc -l
Count valid L-doc names
find .aget/evolution -type f -name "L[0-9][0-9][0-9]_*.md" | wc -l
Find non-conforming files (excluding index.json)
find .aget/evolution -type f ! -name "L[0-9][0-9][0-9]_*.md" ! -name "index.json" ! -name "README.md"
More from claude-skill-registry
All skills →
About this skill
What does the aget-check-evolution skill do?

Monitor .aget/evolution/ directory health. Validates file counts, naming conventions, disk usage, and returns health status with alerts on anomalies.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill aget-check-evolution-aget-framework-template-consultant --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going