CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hub-init

Create a new AgentHub collaboration session with task, agent count, and evaluation criteria. Use when the user runs /hub:hub-init or asks to start a multi-agent competition on a task.

68

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A tight, command-style skill body that gives executable guidance for both argument and interactive modes with concrete output examples and sensible error handling. Its main weaknesses are the unspecified metric-extraction step in Baseline Capture and the unqualified result_ranker.py reference.

Suggestions

Specify how to extract the metric value from eval output (e.g., a parsing rule like 'read the last JSON object's {metric} field' or a tiny example) so the Baseline Capture step is fully executable.

Fully qualify the result_ranker.py reference (e.g., '{skill_path}/scripts/result_ranker.py') the way hub_init.py is, so the delegation to bundle files is unambiguous.

Add a lightweight verification checkpoint after running hub_init.py (e.g., confirm .agenthub/sessions/{session-id}/config.yaml exists) before reporting success to the user.

DimensionReasoningScore

Conciseness

The body is lean with zero concept over-explanation: 'Pass them to the init script', the six-item interactive checklist, and two compact output blocks each earn their place, and the two output examples are justified because they demonstrate distinct modes (eval vs. LLM judge). It assumes Claude's competence throughout — nothing to trim.

5 / 5

Actionability

Concrete executable invocation ('python {skill_path}/scripts/hub_init.py --task "{task}" --agents {N} ...') plus a fully specified interactive collection list with defaults and required/optional markers. Falls short of 5 because 'Extract the metric value from stdout' in Baseline Capture provides no parsing rule or example, leaving that step under-specified.

4 / 5

Workflow Clarity

Clear branching on args vs. interactive mode, a sequenced baseline procedure (run eval, extract metric, append to config.yaml, display), and explicit error recovery ('If the eval command fails at this stage, warn the user but continue — baseline is optional'). Minor gap: no checkpoint verifying session creation succeeded before the 'After Init' report, and no validation on the metric extraction.

4 / 5

Progressive Disclosure

Well-organized sections (Usage, What It Does, Output, Baseline Capture, After Init) that keep the body an overview while delegating implementation to the referenced script, signaled with a full path ('{skill_path}/scripts/hub_init.py') — one level deep. Minor gaps: 'result_ranker.py --baseline' is mentioned without a path, and no bundle structure or other references are surfaced to orient navigation.

4 / 5

Total

17

/

20

Passed

Description

82%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.

A strong description with explicit what-and-when structure, third-person voice, and precise command-scoped triggers. Its only notable limitation is trigger synonym breadth and single-action capability framing.

Suggestions

Broaden trigger coverage with natural synonyms users might say, e.g., '...or asks to run parallel agents / an agent competition / a multi-agent benchmark on a task'.

Consider naming one more concrete capability (e.g., 'captures a baseline metric') so the description reflects more of what the skill actually does beyond session creation.

DimensionReasoningScore

Specificity

'Create a new AgentHub collaboration session with task, agent count, and evaluation criteria' names the domain and enumerates concrete configuration parameters, but describes a single action rather than the several distinct capabilities of the anchor-4/5 examples. Not 4 because there are not multiple specific actions, just one action with parameter detail.

3 / 5

Completeness

Explicitly answers both questions: 'what' (create an AgentHub collaboration session with task, agent count, and evaluation criteria) and 'when' (running /hub:hub-init or asking to start a multi-agent competition), with concrete trigger phrases — the same structure as the anchor-5 exemplar. Not 4 because the 'when' clause is already explicit and specific.

5 / 5

Trigger Term Quality

'Use when the user runs /hub:hub-init or asks to start a multi-agent competition on a task' includes the exact command name and a natural phrase users would say. Not 5 because natural synonyms and variations ('parallel agents', 'spawn agents', 'agent arena', 'benchmark agents') are missing; clearly above the anchor-3 partial-coverage case.

4 / 5

Distinctiveness Conflict Risk

Scoped to a named command ('/hub:hub-init') and a niche tool ('AgentHub', 'multi-agent competition'), giving it a clear niche with distinct triggers and minimal overlap with any generic skill. Nothing falls in a neighboring anchor.

5 / 5

Total

17

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

engineering/agenthub/skills/hub-init/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.