CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-sort

Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

59

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-sort/SKILL.md

The canonical home for this skill is agent-sort in affaan-m/ECC

SKILL.md
Quality
Evals
Security

Quality

Content

68%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, concise, and actionable with concrete commands and a clear workflow. Its main weakness is the absence of an explicit validation feedback loop in the install workflow, which caps workflow clarity.

Suggestions

Add an explicit validate→fix→retry loop in the Verify step (e.g., 'if a DAILY file is missing or a stale rule is active, fix and re-verify') to lift workflow clarity above 3.

Merge the redundant Outputs and Output Format sections into one to remove the minor conciseness drag.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, with concrete commands and a tight evidence-table format; only minor redundancy (the Outputs and Output Format sections overlap) keeps it from a 5.

4 / 5

Actionability

It provides executable commands (rg, cat of package manifests), a concrete evidence-table format with a worked example, and explicit file paths, giving mostly ready-to-run guidance with minor gaps.

4 / 5

Workflow Clarity

A clear six-step Core Workflow exists with a Verify step and report format, but the batch install operation lacks an explicit validate→fix→retry feedback loop, so the cap for missing validation feedback applies.

3 / 5

Progressive Disclosure

Content is organized into well-labeled sections within a single SKILL.md with no nested or buried references; with no bundle files, structure is good but the skill is not minimal enough for a 5.

4 / 5

Total

15

/

20

Passed

Description

67%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concrete and complete, covering both capability and trigger, but relies on the specialized 'ECC' term and could use more natural synonyms. It is distinctive and well above the vague baseline.

Suggestions

Add a user-natural synonym or plain-language gloss for 'ECC' (e.g., 'agent skill/config bundle') so the trigger matches how users actually phrase the need.

Tighten the 'Use when' clause with one or two concrete trigger phrases like 'Use when a repo needs only part of the ECC bundle' to lift trigger quality.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes' — naming the domain and multiple specific operations with only minor coverage gaps.

4 / 5

Completeness

Both 'what' (build an evidence-backed install plan by sorting ECC components) and 'when' (the explicit 'Use when' clause) are present, though the trigger could be more specific.

4 / 5

Trigger Term Quality

It includes a 'Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle' trigger, but leans on the jargon term 'ECC' and misses natural synonyms a user would say.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche — project-specific ECC trimming via DAILY/LIBRARY sorting — with mostly distinct triggers and only minor overlap risk against general install/config skills.

4 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/ECC
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.