CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-adaptive-coordinator

Agent skill for adaptive-coordinator - invoke with $agent-adaptive-coordinator

51

1.51x
Quality

23%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-adaptive-coordinator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%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 with concrete MCP commands and algorithms, but it is heavily padded with conceptual and best-practice material Claude already knows, the Python examples are pseudocode, and risky topology switches lack validation. All content is inlined with no bundle references.

Suggestions

Trim the KPI/best-practice/conceptual sections and keep only the decision matrix, switching conditions, and runnable commands to reduce token bloat.

Replace the pseudocode Python classes with executable snippets or explicitly label them as illustrative pseudocode with justification.

Add explicit validation checkpoints to the topology-switching workflow (verify performance improvement before commit; rollback trigger thresholds with a fix-retry loop).

Move the detailed algorithm bodies and KPI catalogs into reference files and link them one level deep from SKILL.md.

DimensionReasoningScore

Conciseness

At ~400 lines the body is noticeably verbose, with KPI bullet lists, 'Best Practices', and conceptual ML definitions that restate concepts Claude already knows, matching the 'noticeably verbose; several unnecessary padded sections' anchor.

2 / 5

Actionability

Concrete bash MCP commands are executable, but the Python classes call undefined helpers (predict_performance, collect_performance_metrics) and read like pseudocode, matching 'some concrete guidance but incomplete; pseudocode instead of executable code'.

3 / 5

Workflow Clarity

The four-phase transition protocol and rollback class give a rough sequence, but topology switching (a batch/risky operation) lacks explicit validation checkpoints or fix-retry loops, so the destructive/batch cap of 3 applies.

3 / 5

Progressive Disclosure

Sections are well organized, but there are no bundle files and all reference material is inlined into one ~400-line SKILL.md, matching 'some structure but could be better organized; content that should be separate is inline'.

3 / 5

Total

11

/

20

Passed

Description

5%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 a templated placeholder that identifies the skill by name and invocation syntax but describes no capabilities and gives no usage triggers. It fails to answer either what the skill does or when to use it.

Suggestions

Replace the placeholder with concrete actions, e.g. 'Dynamically switches swarm topology, balances agent load, and predicts scaling needs across hierarchical, mesh, and ring patterns.'

Add an explicit 'Use when...' trigger clause naming natural user phrases such as 'swarm coordination', 'topology switching', or 'adaptive agent orchestration'.

Use third-person capability verbs and drop the 'invoke with $...' boilerplate so the description is distinguishable from other agent skills.

DimensionReasoningScore

Specificity

The phrase 'Agent skill for adaptive-coordinator' names the domain but lists zero concrete actions, matching the 'names the domain but actions are minimal or generic' anchor rather than the score-1 'pure abstract language'.

2 / 5

Completeness

It says only that this is an 'Agent skill for adaptive-coordinator'; there is no statement of what it does and no 'Use when...' trigger guidance, so both what and when are missing.

1 / 5

Trigger Term Quality

The only term is the invocation syntax '$agent-adaptive-coordinator'; there are no natural keywords a user would actually say, matching the 'no natural keywords; only technical jargon' anchor.

1 / 5

Distinctiveness Conflict Risk

The boilerplate 'Agent skill for X - invoke with $X' template is generic across all agent skills and would conflict with virtually any similarly templated skill.

1 / 5

Total

5

/

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
ruvnet/ruflo
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.