aget-check-evolution — community aget-check-evolution, template-worker-aget, aget-framework, community, ai agent skill, ide skills, agent automation, AI agent skills, Claude Code, Cursor, Windsurf

v1.0.0
GitHub

About this Skill

Perfect for AGET Agents needing advanced self-diagnostic capabilities for evolution directory health assessment. Monitor .aget/evolution/ directory health. Validates file counts, naming conventions, disk usage, and returns health status with alerts on anomalies.

aget-framework aget-framework
[0]
[0]
Updated: 3/9/2026

Quality Score

Top 5%
56
Excellent
Based on code quality & docs
Installation
SYS Universal Install (Auto-Detect)
> npx killer-skills add aget-framework/template-worker-aget/aget-check-evolution
Supports 19+ Platforms
Cursor
Windsurf
VS Code
Trae
Claude
OpenClaw
+12 more

Agent Capability Analysis

The aget-check-evolution skill by aget-framework is an open-source community AI agent skill for Claude Code and other IDE workflows, helping agents execute tasks with better context, repeatability, and domain-specific guidance.

Ideal Agent Persona

Perfect for AGET Agents needing advanced self-diagnostic capabilities for evolution directory health assessment.

Core Value

Empowers agents to monitor file counts, types, naming conventions, and disk usage within the `.aget/evolution/` directory, leveraging `find` and `wc` commands for precise filesystem analysis.

Capabilities Granted for aget-check-evolution

Monitoring evolution directory health
Debugging file inventory discrepancies
Optimizing disk usage for efficient agent operation

! Prerequisites & Limits

  • Requires filesystem access to `.aget/evolution/` directory
  • Limited to monitoring specific file types (e.g., `.md` extensions)
Project
SKILL.md
2.9 KB
.cursorrules
1.2 KB
package.json
240 B
Ready
UTF-8

# Tags

[No tags]
SKILL.md
Readonly

/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
1# Count total files 2find .aget/evolution -type f | wc -l 3 4# Count by extension 5find .aget/evolution -type f -name "*.md" | wc -l 6find .aget/evolution -type f -name "*.json" | wc -l 7find .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
1# Count valid L-doc names 2find .aget/evolution -type f -name "L[0-9][0-9][0-9]_*.md" | wc -l 3 4# Find non-conforming files (excluding index.json) 5find .aget/evolution -type f ! -name "L[0-9][0-9][0-9]_*.md" ! -name "index.json" ! -name "README.md"

3. Disk Usage

bash
1du -sh .aget/evolution

4. Index Integrity

Check that index.json exists and is valid JSON:

bash
1test -f .aget/evolution/index.json && jq empty .aget/evolution/index.json 2>/dev/null && echo "valid" || echo "invalid"

Thresholds

MetricOKWARNCRITICAL
Total files<500500-750>750
Non-standard files0-1011-50>50
Disk size<10MB10-25MB>25MB
Index integrityvalid-invalid

Note: Thresholds inherited from supervisor defaults. Research AGET baseline (2026-02-08): 94 files, 800K - well within OK range.

Output Format

Report the following:

=== /aget-check-evolution ===

Directory: .aget/evolution/

File Counts:
  Total:     [count]
  L-docs:    [count] (.md matching L###_*.md)
  Index:     [1 if exists, 0 otherwise]
  Other:     [count] (non-conforming)

Disk Usage: [size]

Index Status: [valid/invalid/missing]

Non-Conforming Files:
  [list any files not matching expected patterns]

Health Status: [OK | WARN | CRITICAL]
Alerts:
  [list any threshold violations]

Health Status Logic

IF index invalid OR index missing:
  CRITICAL
ELIF total_files > 750 OR disk > 25MB OR non_standard > 50:
  CRITICAL
ELIF total_files > 500 OR disk > 10MB OR non_standard > 10:
  WARN
ELSE:
  OK

Constraints

  • C1: Read-only operation. Never modify files.
  • C2: Report ALL findings, even if status is OK.
  • C3: List non-conforming files by name for actionability.

Related Skills

  • /aget-check-sessions - Sessions directory health
  • /aget-check-kb - Knowledge base health
  • /aget-record-lesson - Capture findings as L-docs

Traceability

LinkReference
POCPOC-017
ProjectPROJECT_PLAN_AGET_UNIVERSAL_SKILLS.md
SourceFleet Skill Deployment Report (supervisor)
Baseline94 files, 800K (2026-02-08)

aget-check-evolution v1.0.0 Category: Monitoring POC-017 Phase 1

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is aget-check-evolution?

Perfect for AGET Agents needing advanced self-diagnostic capabilities for evolution directory health assessment. Monitor .aget/evolution/ directory health. Validates file counts, naming conventions, disk usage, and returns health status with alerts on anomalies.

How do I install aget-check-evolution?

Run the command: npx killer-skills add aget-framework/template-worker-aget/aget-check-evolution. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for aget-check-evolution?

Key use cases include: Monitoring evolution directory health, Debugging file inventory discrepancies, Optimizing disk usage for efficient agent operation.

Which IDEs are compatible with aget-check-evolution?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for aget-check-evolution?

Requires filesystem access to `.aget/evolution/` directory. Limited to monitoring specific file types (e.g., `.md` extensions).

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add aget-framework/template-worker-aget/aget-check-evolution. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use aget-check-evolution immediately in the current project.

Related Skills

Looking for an alternative to aget-check-evolution or another community skill for your workflow? Explore these related open-source skills.

View All

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
Design

linear

Logo of lobehub
lobehub

Linear issue management. MUST USE when: (1) user mentions LOBE-xxx issue IDs (e.g. LOBE-4540), (2) user says linear, linear issue, link linear, (3) creating PRs that reference Linear issues. Provides

73.4k
0
Communication

testing

Logo of lobehub
lobehub

Testing guide using Vitest. Use when writing tests (.test.ts, .test.tsx), fixing failing tests, improving test coverage, or debugging test issues. Triggers on test creation, test debugging, mock setup

73.3k
0
Communication

zustand

Logo of lobehub
lobehub

Zustand state management guide. Use when working with store code (src/store/**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.

72.8k
0
Communication