agent sort

AI Community

Skill notes

When to Use

A project only needs a subset of ECC and full installs are too noisy The repo stack is clear, but nobody wants to hand-curate skills one by one A team wants a repeatable install decision backed by grep evidence instead of opinion You need to separate always-loaded daily workflow surfaces from searchable library/reference surfaces A repo has drifted into the wrong language, rule, or hook set and needs cleanup

Non-Negotiable Rules

Use the current repository as the source of truth, not generic preferences Every DAILY decision must cite concrete repo evidence LIBRARY does not mean "delete"; it means "keep accessible without loading by default" Do not install hooks, rules, or scripts that the current repo cannot use Prefer ECC-native surfaces; do not introduce a second install system

Outputs

Produce these artifacts in order: DAILY inventory LIBRARY inventory install plan verification report

Classification Model

Use two buckets only: DAILY should load every session for this repo strongly matched to the repo's language, framework, workflow, or operator surface LIBRARY

Evidence Sources

Use repo-local evidence before making any classification: file extensions package managers and lockfiles framework configs CI and hook configs

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
@affaan-m · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
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.

Output preview agent-sort.preview
# 6. Verify the result

- every DAILY file exists where expected
- stale language rules were not left active
- incompatible hooks were not installed
- the resulting install actually matches the repo stack
- DAILY count
- LIBRARY count

Discussion

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