CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-sona-learning-optimizer

Agent skill for sona-learning-optimizer - invoke with $agent-sona-learning-optimizer

35

Quality

30%

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

The canonical home for this skill is agent-sona-learning-optimizer in ruvnet/claude-flow

SKILL.md
Quality
Evals
Security

Quality

Content

36%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 a feature/marketing overview with one genuinely executable snippet (the hooks), but it lacks an actionable workflow, validation steps, and a real reference file. A duplicate frontmatter block and benchmark figures add noise.

Suggestions

Remove the duplicate YAML block (lines 6-18); it restates the frontmatter and wastes context.

Replace the capability bullet lists with a concrete, sequenced workflow (prepare -> run task -> record outcome -> validate) with explicit checkpoints.

Either create the referenced docs/RUVECTOR_SONA_INTEGRATION.md or drop the dangling reference, and move the benchmark figures into a separate reference file.

DimensionReasoningScore

Conciseness

A redundant duplicate YAML frontmatter block and marketing-style benchmark claims (version numbers, ops/sec, +55%) pad the body with tokens Claude does not need.

2 / 5

Actionability

Provides executable pre/post hook commands, but the bulk of the body is descriptive feature lists with no guidance on how to actually perform learning or routing.

3 / 5

Workflow Clarity

No sequenced multi-step workflow or validation checkpoints are present; only loose pre-task/post-task hook commands are implied without an ordered process.

2 / 5

Progressive Disclosure

Sections are headed and reasonably organized, but the referenced 'docs/RUVECTOR_SONA_INTEGRATION.md' does not exist in the bundle and benchmark detail is inlined rather than split out.

3 / 5

Total

10

/

20

Passed

Description

25%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 an auto-generated placeholder that names the skill but conveys no concrete capabilities or natural trigger phrases. It is distinct thanks to its unique name yet uninformative about what it does or when to use it.

Suggestions

Replace the templated text with the concrete actions the skill performs (e.g., 'Fine-tunes the agent with LoRA, preserves prior knowledge with EWC++, and routes requests across LLMs').

Add an explicit 'Use when...' clause with natural trigger phrases users would say (e.g., 'Use when the user wants the agent to learn from past tasks or optimize model routing').

Drop the '$agent-sona-learning-optimizer' invocation token from the description; it is implementation detail, not a user-facing trigger.

DimensionReasoningScore

Specificity

Names the domain ('sona-learning-optimizer') but states no concrete actions, reading as a templated 'Agent skill for X' label rather than a capability description.

2 / 5

Completeness

Offers only a vague 'what' (an agent skill for a named package) with no 'when' or use-case trigger guidance, so it fails to answer when Claude should invoke it.

2 / 5

Trigger Term Quality

The only trigger is the technical invocation token '$agent-sona-learning-optimizer'; there are no natural keywords a user would actually say when they need this skill.

1 / 5

Distinctiveness Conflict Risk

The unique package name and explicit invocation token make it largely distinct from other skills with minor overlap risk, even though the surrounding phrasing is generic.

4 / 5

Total

9

/

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.