CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentica-spawn

Spawn Agentica multi-agent patterns

Quality

61%

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 ./.claude/skills/agentica-spawn/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 well-structured and code-forward, giving Claude a usable pattern-to-spawn-method map, but the code examples are not directly executable and the spawn workflow lacks explicit validation checkpoints. Adding imports and a verify-agents-started step would meaningfully raise the actionability and workflow-clarity scores.

Suggestions

Add the missing imports and constructor context so each code block is copy-paste executable (e.g. `from agentica import Swarm, AggregateMode`).

Replace undefined placeholders like `jury.decide(bool, question)` with a concrete call such as `jury.decide(True, "Is the solution correct?")`.

Insert a validation checkpoint after spawning (e.g. confirm `SWARM_ID`/`AGENT_ROLE` are set and agents reported ready) to satisfy the batch-operation feedback-loop expectation.

DimensionReasoningScore

Conciseness

The body is lean with code-forward pattern sections and no padding explaining what multi-agent systems are; the only trimmable redundancy is the 'When to Use' bullets duplicating the pattern-to-method mapping below, matching the 'efficient, minor instances of over-explanation' anchor.

4 / 5

Actionability

Concrete Python snippets are provided for each pattern, but they are not copy-paste executable: imports for Swarm/Hierarchical/Jury/AggregateMode/ConsensusMode are missing and `jury.decide(bool, question)` uses undefined placeholders, fitting the 'concrete but incomplete, missing key details' anchor.

3 / 5

Workflow Clarity

The select-pattern-then-spawn sequence is only implicit and there are no validation or verification checkpoints for what is effectively a batch agent-spawning operation, which per the feedback-loop guidance caps workflow clarity at 3.

3 / 5

Progressive Disclosure

Content is organized into clearly labeled sections (When to Use, Pattern Selection to Spawn Method, Environment Variables) with no external references needed; at ~70 lines it exceeds the under-50-line simple-skill exception, so it sits at 'good structure, minor organization gaps' rather than 5.

4 / 5

Total

14

/

20

Passed

Description

41%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 brief and names a distinct niche, but it is light on concrete actions and lacks any explicit 'when to use' trigger guidance. Adding a Use-when clause and one or two concrete spawn actions would lift the completeness and trigger-term scores.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user has selected an Agentica pattern (swarm, hierarchical, generator/critic, jury) for a multi-agent task.'

Name concrete actions beyond 'Spawn', such as 'configure and spawn swarm, hierarchical, generator/critic, and jury multi-agent patterns'.

Include natural user-facing synonyms (e.g. 'multi-agent', 'agent swarm', 'parallel agents') so the description matches phrases users actually say.

DimensionReasoningScore

Specificity

The description names the domain ("Agentica multi-agent patterns") but offers only a single generic action ("Spawn"), matching the 'names the domain but actions are minimal or generic' anchor rather than the 1-2 concrete actions required for a 3.

2 / 5

Completeness

It gives a clear 'what' (spawning Agentica multi-agent patterns) but no 'when'/Use-when clause, which per the guidelines caps completeness at 3; it cannot reach 4 without explicit trigger guidance.

3 / 5

Trigger Term Quality

"Spawn Agentica multi-agent patterns" is jargon-heavy; "Agentica" and "spawn" are framework terms users rarely say verbatim, and only "multi-agent" is a genuinely natural keyword, so it falls at the 'one or two generic keywords, missing natural phrases' level.

2 / 5

Distinctiveness Conflict Risk

The "Agentica" framework name carves a clear niche with low conflict risk, but "multi-agent patterns" still overlaps slightly with generic orchestration skills, placing it at 'mostly distinct, minor overlap risk' rather than the minimal-conflict 5.

4 / 5

Total

11

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

parcadei/Continuous-Claude-v3

Path

.claude/skills/agentica-spawn/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.