agent-adaptive-coordinator

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

1.51x

Quality

28%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

50%

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-sectioned and includes concrete MCP commands, but it is verbose, dominated by non-executable pseudocode, and lacks validation checkpoints for its stateful topology-switching workflows. With no bundle files and a monolithic structure, progressive disclosure is only partially realized.

Suggestions

Replace the pseudocode classes with compact, executable MCP command examples or move the algorithm detail into a reference file, keeping the SKILL.md overview lean.

Add explicit validation checkpoints to the topology transition protocol (e.g., 'validate predicted improvement before initiating switch; monitor for rollback triggers after migration').

Split the body into referenced files (e.g., TOPOLOGIES.md, MCP_REFERENCE.md) and keep SKILL.md as a concise overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	The ~360-line body is organized into sections but padded with ASCII-art diagrams and conceptual elaboration (e.g., the 'ADAPTIVE INTELLIGENCE LAYER' diagram and lengthy KPI bullet lists) that could be tightened, fitting the 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean anchor.	2 / 3
Actionability	Concrete MCP bash commands (e.g., 'mcp__claude-flow__neural_patterns analyze --operation=...') provide some executable guidance, but the bulk of the body is Python pseudocode classes with undefined methods (self.predict_performance, self.collect_performance_metrics) and missing imports — incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	Sequences exist (Topology Transition Protocols Phase 1-4), but topology switching is a stateful/batch operation with no explicit validation checkpoints before committing a switch, and the described rollback mechanism is not framed as a validate->fix->retry loop, capping the score at 2.	2 / 3
Progressive Disclosure	No bundle files exist and all content lives inline in a single ~360-line monolithic file that arguably should be split (algorithms, KPIs, MCP reference), matching the 'some structure but content that should be separate is inline' anchor rather than a clear overview pointing to one-level-deep references.	2 / 3
	Total	8 / 12 Passed

Description

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 generic boilerplate that names no concrete capabilities and provides no natural usage triggers, failing to communicate what the skill does or when to use it. Only the niche coordinator name provides marginal distinctiveness.

Suggestions

Replace the boilerplate with a concrete list of what the skill does, e.g. 'Dynamically switches swarm topology (hierarchical/mesh/ring) based on real-time performance metrics and trains adaptive coordination models.'

Add an explicit 'Use when...' clause with natural trigger terms such as 'swarm coordination', 'topology switching', 'agent load balancing', or 'adaptive orchestration'.

Drop the 'invoke with $agent-adaptive-coordinator' invocation token and use third-person action verbs describing the skill's behavior.

Dimension	Reasoning	Score
Specificity	The description only states it is an 'Agent skill for adaptive-coordinator' and 'invoke with $agent-adaptive-coordinator', naming no concrete actions — matching the 'vague or no actions; abstract language' anchor.	1 / 3
Completeness	It neither concretely says what the skill does nor provides any 'Use when...' trigger guidance, so both 'what' and 'when' are very weak or missing.	1 / 3
Trigger Term Quality	'invoke with $agent-adaptive-coordinator' is a technical invocation token, not a natural keyword a user would say, with no coverage of natural trigger terms.	1 / 3
Distinctiveness Conflict Risk	The named 'adaptive-coordinator' niche gives some distinctiveness, but the surrounding boilerplate is generic enough that it could overlap with other coordinator skills rather than having clearly distinct triggers.	2 / 3
	Total	5 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: ruvnet/ruflo
Path: .agents/skills/agent-adaptive-coordinator/SKILL.md
Commit: 26c35b5

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.