skill-enhanced-llm

Scans skill and cron directories to generate sourced usage reports and verify unmapped directory cleanup.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill skill-enhanced-llm-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-enhanced-llm
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/extended/external-automation/automation-skills/skill-enhanced-llm
Command: npx skills add https://github.com/yakeworld/Synthos --skill skill-enhanced-llm-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a large skill library makes it hard to know which skills are actually used, whether cron-scheduled tasks still run, and which directories are orphaned. This Skill produces auditable skill usage statistics and prevents accidental deletion of directories that are still referenced by active skills. ## Core Features & Use Cases - Sourced Usage Reporting: Scans the skills/ directory and cron task list, then generates usage reports (skill counts, cron task counts, total run counts, archived tasks) where every number carries a traceable collection command. - Consistent v1/v2 Data: Keeps report versions on the same measurement basis, using evolution-state.json as the single data source. - Safe Unmapped Directory Cleanup: Detects directories with no cron references and no invocation records, verifies they are not referenced by live skills before cleanup, and rolls back instead of deleting anything still in use. - Use Case: A repository with 27 skills and 21 cron tasks needs a usage audit. The Skill produces a v2 usage report showing 1352 total runs and 3 archived tasks, and flags skills/old-experiment/ as a candidate for cleanup only after confirming no live skill references it. ## Quick Start Scan the skills directory and cron tasks, then generate a sourced skill usage report and list any unmapped directories safe to clean.

Frequently Asked Questions about skill-enhanced-llm

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

FAQPage Schema
How do I audit skill usage across a skill library?

Scan the skills directory and cron task list, then count skills, cron tasks, and total runs using executable commands such as listing SKILL.md files and parsing crontab entries. Each reported number must include its collection command so the statistics remain reproducible.

How to safely delete unused skill directories?

First mark directories with no cron references and no invocation records as unmapped candidates. Then verify no live skill references them, including cross-references inside other SKILL.md files, before deleting anything. If verification fails, keep the directory and skip cleanup.

What data source should skill usage reports use?

Use evolution-state.json as the single data source for run counts and archived task summaries. Keeping one source ensures v1 and v2 report versions stay on the same measurement basis and remain comparable.

Why does unmapped directory cleanup sometimes delete directories still in use?

It happens when verification only checks cron references and invocation logs but misses references inside other skill files. A directory can appear unused while another skill's SKILL.md still references its helper scripts, so verification must grep across all skill definitions.

What are the limitations of cron-based usage statistics?

Cron-based counts only capture scheduled executions and miss manual or indirect invocations. Skills triggered through other paths may show zero runs, so usage reports should combine cron parsing with invocation records before drawing conclusions.