CtrlK
BlogDocsLog inGet started
Tessl Logo

fanout-analysis

Use this workflow recipe when a question benefits from several independent perspectives followed by a single evidence-based synthesis.

60

Quality

70%

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 ./examples/dynamicworkflow/skills/skills/fanout-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 content is a tight, well-structured workflow recipe with concrete API guidance and explicit failure handling, scoring high across all dimensions. Its only soft spot is the absence of a strict validate->fix->retry checkpoint and full runnable code, which keep workflow clarity and actionability at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, with no padding explaining what workflows or fan-out means; a few phrases ('do not create roles just to make the workflow look larger') could be trimmed, matching the efficient-with-minor-over-explanation anchor above the mostly-efficient midpoint.

4 / 5

Actionability

It gives concrete, executable guidance tied to real API surfaces ('parallel([...])', 'tools=[]', the Agent result's 'structured' object), which is actionable for an instruction-only workflow skill, but it stops short of full copy-paste-ready code examples, matching the mostly-executable anchor.

4 / 5

Workflow Clarity

The Process section is a clear numbered 6-step sequence, and failure handling is explicit (handle 'None' for failed branches, bounded rerun, keep missing evidence explicit) so the batch-operation cap does not apply; it falls short of a 5 because there is no explicit validate->fix->retry loop, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The body is under 50 lines, needs no external references, and is well-organized into 'Process' and 'Compilation Rules' sections, meeting the rubric's explicit exception that simple self-contained skills score 5 with well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

62%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 well-formed with an explicit 'Use when' clause covering both what the workflow does and when to apply it, placing it solidly above average. Its main weakness is abstract action language and limited trigger-term variety, which keep specificity and trigger quality at the midpoint.

Suggestions

Add concrete trigger phrases users would actually say, e.g. 'Use when the user asks for multiple perspectives, second opinions, or to compare approaches before deciding.'

Replace abstract action terms with more concrete operations, e.g. 'spawns 2-4 parallel analysis branches and merges their findings into one evidence-based recommendation.'

Include common synonyms ('multi-angle analysis', 'parallel review', 'fan-out reasoning') to broaden natural-keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain ('workflow recipe' for fan-out/fan-in) and two actions ('several independent perspectives' and 'evidence-based synthesis'), but those actions are abstract process terms rather than concrete operations, matching the anchor that lists domain plus 1-2 actions without comprehensive coverage.

3 / 5

Completeness

It explicitly answers both 'what' (a fan-out/fan-in workflow of perspectives then synthesis) and 'when' ('Use this workflow recipe when a question benefits from...'), but the 'when' is a general condition rather than concrete user trigger phrases, so it sits above the both-present-but-could-be-more-specific anchor and below the fully-concrete-triggers anchor.

4 / 5

Trigger Term Quality

It includes a few relevant natural phrases ('independent perspectives', 'synthesis', 'question') that a user might echo, but it misses common synonyms and variations like 'multiple angles', 'second opinions', or 'compare approaches', matching the anchor with some relevant keywords but missing common variations.

3 / 5

Distinctiveness Conflict Risk

The multi-perspective-synthesis niche is fairly distinct with minimal conflict risk against most skills, though the somewhat abstract trigger could overlap with general research or analysis skills, matching 'mostly distinct; minor overlap risk with closely related skills' rather than the clear-niche anchor.

4 / 5

Total

14

/

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
trpc-group/trpc-agent-go
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.