stream-chain

Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows

1.00x

Quality

48%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/stream-chain/SKILL.md

Quality

Discovery

32%

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 a technical domain (Stream-JSON chaining) and use cases (pipelines, workflows) but lacks concrete actions and explicit trigger guidance. The technical jargon may not match natural user language, and the absence of a 'Use when...' clause significantly weakens Claude's ability to select this skill appropriately.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when chaining multiple agents, passing structured data between pipeline stages, or building sequential task workflows'

Include concrete actions such as 'Parse streaming JSON responses, route data between agents, transform records between pipeline stages'

Add natural language variations users might say: 'chain agents', 'pass data between steps', 'streaming output', 'pipeline orchestration'

Dimension	Reasoning	Score
Specificity	Names the domain (multi-agent pipelines, data transformation, sequential workflows) and mentions 'Stream-JSON chaining' as a technique, but lacks concrete actions like 'parse', 'route', 'transform records', or specific operations.	2 / 3
Completeness	Describes what the skill relates to (chaining for pipelines/workflows) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes some relevant terms like 'multi-agent', 'pipelines', 'data transformation', and 'workflows', but uses technical jargon ('Stream-JSON chaining') that users may not naturally say. Missing common variations like 'chain tasks', 'pass data between agents', or 'streaming JSON'.	2 / 3
Distinctiveness Conflict Risk	'Multi-agent pipelines' and 'sequential workflows' could overlap with general orchestration or workflow skills. 'Stream-JSON chaining' adds some specificity but the broad terms 'data transformation' and 'workflows' create potential conflict with other skills.	2 / 3
	Total	7 / 12 Passed

Implementation

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides highly actionable, executable guidance with comprehensive command examples and clear syntax documentation. However, it's overly long for a SKILL.md overview, mixing quick-start content with extensive reference material that should be in separate files. The workflow examples would benefit from explicit validation checkpoints, especially for complex multi-step chains.

Suggestions

Move 'Advanced Use Cases', 'Examples Repository', and 'Troubleshooting' sections to separate reference files, keeping SKILL.md as a concise overview with links

Add explicit validation/verification steps to custom chain examples (e.g., 'Verify implementation works' as a distinct step with expected output)

Remove the 'Conclusion' section entirely - it restates information Claude just processed

Add actual file links to 'Related Skills' section instead of just listing names

Dimension	Reasoning	Score
Conciseness	The skill is moderately verbose with some unnecessary sections like 'Conclusion' that summarize what Claude already read, and explanatory text that could be trimmed. However, it's not egregiously padded and most content serves a purpose.	2 / 3
Actionability	Provides fully executable bash commands throughout, with clear syntax, options tables, and copy-paste ready examples. The JSON configuration format is complete and usable.	3 / 3
Workflow Clarity	Pipeline workflows are clearly sequenced with numbered steps, but the custom chain examples lack explicit validation/verification checkpoints. The 'Best Practices' section mentions verification but doesn't integrate it into the main workflow examples consistently.	2 / 3
Progressive Disclosure	Content is well-structured with clear sections, but it's monolithic - everything is in one file when advanced use cases, troubleshooting, and the examples repository could be separate files. The 'Related Skills' section references other skills but doesn't link to them.	2 / 3
	Total	9 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (564 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: ruvnet/ruv-FANN
Commit: 46f6f8a

Reviewed: about 1 month ago

Table of Contents

Discovery Implementation Validation

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.