agent-topology-optimizer

Agent skill for topology-optimizer - invoke with $agent-topology-optimizer

1.58x

Quality

Does it follow best practices?

Impact

92%

1.58x

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-topology-optimizer/SKILL.md

Quality

Content

0%Scale 1-3

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

This skill is an aspirational architecture document rather than an actionable skill. It presents hundreds of lines of non-executable pseudocode referencing undefined classes and methods, with no clear workflow, no validation steps, and no grounding in real tools or APIs. It reads like a design spec or wishlist rather than instructions Claude can follow to perform topology optimization.

Suggestions

Replace the aspirational class hierarchies with actual executable code or concrete CLI commands that Claude can run, grounded in real tools (e.g., actual claude-flow commands with verified flags).

Add a clear step-by-step workflow: 1) Analyze current topology, 2) Generate recommendations, 3) Validate changes, 4) Apply optimization — with explicit validation checkpoints.

Reduce content to under 100 lines by removing redundant code blocks and focusing on the specific actions this agent should take, not the internal architecture of imaginary systems.

Split detailed algorithm implementations (genetic algorithm, simulated annealing) into separate reference files and keep SKILL.md as a concise overview with links.

Dimension	Reasoning	Score
Conciseness	Extremely verbose at ~600+ lines. The content is filled with illustrative but non-executable pseudocode for classes that don't exist (HierarchicalTopology, MeshTopology, etc.), explaining optimization concepts Claude already understands. Most code is aspirational architecture rather than actionable instruction.	1 / 3
Actionability	The code examples are not executable — they reference numerous undefined classes (GeneticPlacementAlgorithm, PatternAnalyzer, CompressionEngine, etc.) and MCP methods that may not exist. The bash commands at the end reference 'npx claude-flow' subcommands without verifying they exist. Nothing is copy-paste ready or grounded in real tooling.	1 / 3
Workflow Clarity	There is no clear step-by-step workflow for performing topology optimization. The content describes what various classes and methods would do conceptually but never sequences actual steps, provides validation checkpoints, or defines error recovery. An agent reading this would not know what to do first.	1 / 3
Progressive Disclosure	The content is a monolithic wall of code blocks with no references to external files, no bundle files to support it, and no clear navigation structure. All content is inline with no separation of overview from detail. The sections are just increasingly long code dumps.	1 / 3
	Total	4 / 12 Passed

Description

0%Scale 1-3

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

This description is essentially a label with an invocation command, providing no information about what the skill does, what actions it performs, or when it should be selected. It fails on every dimension of the rubric, offering neither concrete capabilities nor trigger guidance for skill selection.

Suggestions

Describe what the topology optimizer actually does with specific actions (e.g., 'Optimizes material distribution in structural designs to minimize weight while maintaining strength constraints').

Add an explicit 'Use when...' clause with natural trigger terms users might say (e.g., 'Use when the user asks about structural optimization, material layout, FEA-based design, or topology optimization').

Remove the invocation instruction ('invoke with $agent-topology-optimizer') from the description, as it is operational detail that doesn't help Claude decide when to select this skill.

Dimension	Reasoning	Score
Specificity	The description provides no concrete actions whatsoever. 'Agent skill for topology-optimizer' is entirely vague—it doesn't describe what the skill actually does, only names itself.	1 / 3
Completeness	Neither 'what does this do' nor 'when should Claude use it' is answered. The description only states how to invoke the agent, not what it does or when to use it.	1 / 3
Trigger Term Quality	The only keyword is 'topology-optimizer,' which is a technical/internal term unlikely to match natural user language. There are no natural trigger terms a user would say.	1 / 3
Distinctiveness Conflict Risk	While 'topology-optimizer' is a unique name, the description is so vague that Claude cannot determine when to select it versus any other skill. The lack of any functional description makes it indistinguishable in practice.	1 / 3
	Total	4 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (813 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: ruvnet/claude-flow
Path: .agents/skills/agent-topology-optimizer/SKILL.md
Commit: 913f9ea

Reviewed: 3 days 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.