CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worker-integration

Worker-Agent integration for intelligent task dispatch and performance tracking

50

Quality

63%

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/worker-integration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 well-organized, mostly lean reference with concrete CLI commands, mappings, and config, but it is documentation rather than a workflow: no sequenced integration procedure, no validation steps, and several code paths corrupted ('$' instead of '/'). It functions as an overview but would not reliably guide a user through an end-to-end integration.

Suggestions

Fix the corrupted paths: '.claude$settings.json' should be '.claude/settings.json' and the import 'agentic-flow$workers$worker-agent-integration' should use '/' separators so code is copy-paste executable.

Add a numbered integration workflow with validation checkpoints (enable config → dispatch a trigger → recordFeedback → checkBenchmarkCompliance → verify stats), rather than presenting topics as disconnected sections.

Move the full agent-mappings table and per-agent benchmark thresholds into a reference file (e.g., references/mappings.md) and keep a summary inline, tightening the main file.

DimensionReasoningScore

Conciseness

Mostly lean: command blocks, a mapping table, and config examples with little over-explanation of concepts Claude already knows. Minor filler remains (e.g., 'Workers provide feedback for continuous improvement', explanatory comments in the selection example), so it falls short of anchor 5.

4 / 5

Actionability

The 'npx agentic-flow workers' commands and config JSON are concrete, but key code is not executable as written: the import path 'agentic-flow$workers$worker-agent-integration' and the file path '.claude$settings.json' use '$' where '/' belongs, and the selectBestAgent snippet is illustrative without imports — matching the anchor for incomplete guidance with non-executable code.

3 / 5

Workflow Clarity

Content is organized by topic rather than a sequenced workflow: there is no ordered integration procedure (e.g., enable config → dispatch → record feedback → check compliance) and no validation checkpoints, matching the anchor of steps present but checkpoints missing. It is not a 2 — sections are coherent and the Quick Start gives an entry point.

3 / 5

Progressive Disclosure

A single-file, well-sectioned overview with no external references to go wrong; navigation is easy. Minor gap: bulkier reference material (the full agent-mappings table and per-agent benchmark thresholds) is inlined and could live in separate reference files, keeping it below anchor 5.

4 / 5

Total

14

/

20

Passed

Description

50%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 identifies its domain and two core actions but reads like a product tagline: no usage triggers, a buzzword ('intelligent'), and no synonyms or concrete tool names. It answers 'what' adequately but never 'when'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when dispatching background worker tasks to specialized agents, or when tracking agent performance/quality metrics.'

Drop the buzzword 'intelligent' and enumerate the concrete capabilities (agent selection, benchmark compliance checks, feedback recording, integration stats).

Include natural user phrasings and synonyms — 'background workers', 'assign agents to tasks', 'agent metrics', 'npx agentic-flow workers' — so the skill triggers on realistic requests.

DimensionReasoningScore

Specificity

Names the domain ('Worker-Agent integration') and two actions ('task dispatch and performance tracking'), but 'intelligent' is buzzword and coverage is not comprehensive — matching the anchor for domain plus 1-2 concrete actions.

3 / 5

Completeness

It has a clear 'what' (task dispatch and performance tracking) but no 'when should Claude use it' guidance — a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

'Worker', 'Agent', 'task dispatch', and 'performance tracking' are relevant keywords, but natural user phrasings and synonyms (e.g., 'background tasks', 'assign agents', 'agent metrics') are missing.

3 / 5

Distinctiveness Conflict Risk

'Worker-Agent integration' names a specific subsystem, but generic action phrasing ('task dispatch', 'performance tracking') could overlap with other agent-orchestration or monitoring skills.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

ruvnet/ruflo

Path

.agents/skills/worker-integration/SKILL.md

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.