aget-check-evolution

Monitor .aget/evolution directory health and validate L-doc naming and index.json integrity.

1|Updated Oct 4, 2025
One-click install
npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-check-evolution-gmelli
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aget-check-evolution
Source: https://github.com/gmelli/public-OpenAI-DeepResearch-aget/tree/main/.claude/skills/aget-check-evolution
Command: npx skills add https://github.com/gmelli/public-OpenAI-DeepResearch-aget --skill aget-check-evolution-gmelli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects and reports anomalies in the .aget/evolution directory so agents and maintainers can quickly identify naming, indexing, file-count, and disk-usage issues without supervisor intervention.

Core Features & Use Cases

  • File inventory: Counts total files and breaks down by extension to surface unexpected file types.
  • Naming convention validation: Identifies non-conforming L-doc filenames and lists them for remediation.
  • Index and disk checks: Verifies index.json integrity and measures directory disk usage against thresholds, producing OK/WARN/CRITICAL status and actionable alerts.
  • Use Case: Run as part of repository health audits or CI checks to ensure L-doc hygiene and index consistency before deployments.

Quick Start

Run the aget-check-evolution skill to scan .aget/evolution and return a complete health report with counts, non-conforming files, index status, disk usage, and alerts.

Frequently Asked Questions about aget-check-evolution

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

FAQPage Schema
How do I check the health of the .aget/evolution directory?▼

Checking the health of the .aget/evolution directory involves scanning for file-count anomalies, non-conforming L-doc filenames, index.json integrity issues, and disk usage thresholds, producing a report with OK/WARN/CRITICAL statuses.

What is the best way to validate index.json integrity in an AGET agent repository?▼

Validating index.json integrity in an AGET agent repository involves using standard Unix tooling like jq to parse and verify the JSON structure, ensuring index consistency before deployments.

How do I detect non-conforming filenames in my agent repository?▼

Detecting non-conforming filenames requires scanning the directory with tools like find to identify L-doc files that violate naming patterns, generating a list of files for remediation.

Can I run filesystem monitoring checks in CI pipelines?▼

Filesystem monitoring checks can be run in CI pipelines to validate file type distributions, index consistency, and disk usage thresholds, ensuring L-doc hygiene before deployment without supervisor intervention.

Do I need write access to measure disk usage and count files?▼

Measuring disk usage and counting files requires only read-only filesystem access and standard Unix tooling such as find, du, and jq to validate the directory, ensuring safe non-destructive audits.

What causes disk usage anomalies in the .aget/evolution directory?▼

Disk usage anomalies in the .aget/evolution directory are caused by unexpected file accumulations or oversized L-doc files, detected by measuring directory disk usage against defined thresholds using the du command.