skill organizer

AI Community

Skill notes

Why This Exists

Models have a skill selection capacity (kappa) of approximately 50-100 items. Beyond that, selection accuracy degrades. As skills accumulate through log analysis and manual creation, the skill library can cross this threshold. This skill keeps the library organized and the routing guide compact. Reference: Scaling LLM Agents with Skill Libraries

Step 1: Inventory

List all skill directories in the .agent/skills/ folder. Then read each skill's SKILL.md to understand scope, quality, and overlap. Each skill lives in a subdirectory of .agent/skills/ with a SKILL.md file.

Step 2: Identify overlapping or confusable skills

Look for: Skills that do the same thing with slightly different names Skills whose scopes significantly overlap (one is a subset of another) Skills that could be combined into a single broader skill with multiple sections Near-duplicate skills created from different log analysis sessions

Step 3: Merge into hierarchical parent skills

For each group of overlapping or related skills, create a single parent skill with sections covering each sub-capability: Choose a broader parent name and directory (e.g., web-app-dev instead of separate react-frontend, nodejs-backend, web-testing) Write one comprehensive SKILL.md with clearly labeled sections for each

Step 4: Generate SKILLREGISTRY.md

Write .agent/skills/SKILL_REGISTRY.md as a compact routing guide: The registry should: Group skills by purpose/domain (not alphabetically) For each skill, include: what it does, when to read it, and what sections it contains The "Use when" line is critical — it tells agents when to load the full SKILL.md

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@massgen · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Inventory

List all skill directories in the .agent/skills/ folder. Then read each skill's SKILL.md to understand scope, quality, and overlap. Each skill lives in a subdirectory of .agent/skills/ with a SKILL.md file.

02
Step 2: Identify overlapping or confusable skills

Look for: Skills that do the same thing with slightly different names Skills whose scopes significantly overlap (one is a subset of another) Skills that could be combined into a single broader skill with multiple sections Near-duplicate skills created from different log analysis sessions

03
Step 3: Merge into hierarchical parent skills

For each group of overlapping or related skills, create a single parent skill with sections covering each sub-capability: Choose a broader parent name and directory (e.g., `web-app-dev` instead of separate `react-frontend`, `nodejs-backend`, `web-testing`) Write one comprehensive SKILL.md with clearly labeled sections for each

04
Step 4: Generate SKILLREGISTRY.md

Write `.agent/skills/SKILL_REGISTRY.md` as a compact routing guide: The registry should: Group skills by purpose/domain (not alphabetically) For each skill, include: what it does, when to read it, and what sections it contains The "Use when" line is critical — it tells agents when to load the full SKILL.md

05
Step 5: Report

Summarize what you did: How many skills were found Which skills were merged (old names -> new name) Which skills were kept as-is The final registry structure

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.