stream-chain

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

1.00x

Quality

50%

Does it follow best practices?

Impact

100%

1.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/stream-chain/SKILL.md

Quality

Content

50%

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

The body is highly actionable with concrete commands and config, but it is far too verbose for a SKILL.md — redundant example sections and marketing fluff inflate it to ~560 lines with no progressive disclosure to bundle files. Workflow sequencing is clear but lacks built-in validation checkpoints.

Suggestions

Cut redundant sections ("Pipeline Examples", "Examples Repository", "Conclusion") and remove marketing adjectives; keep one canonical example per mode to roughly halve the length.

Split the pipeline catalog and advanced integrations into referenced files (e.g. PIPELINES.md, ADVANCED.md) and link to them one level deep so SKILL.md stays a lean overview.

Add an explicit validate-then-proceed checkpoint to the chain workflow (e.g. verify each step's output before passing it on, and a retry-on-failure loop) to lift workflow clarity toward the 3-anchor.

Dimension	Reasoning	Score
Conciseness	At ~560 lines the body is heavily padded: "Pipeline Examples" repeat commands already shown, "Examples Repository" duplicates earlier chains, "Conclusion" restates the overview, and marketing phrasing ("sophisticated", "battle-tested", "powerful modes") adds no actionable value.	1 / 3
Actionability	It provides concrete, copy-paste-ready commands ("claude-flow stream-chain run ..."), a syntax form, options tables with defaults, and a complete config JSON block for custom pipelines.	3 / 3
Workflow Clarity	Step sequencing is illustrated ("How Context Flows") and a "Verification Steps" best practice exists, but there are no explicit validate-then-fix-then-retry checkpoints built into the chains, so validation is suggested rather than enforced.	2 / 3
Progressive Disclosure	No references/scripts/assets bundle files exist and the entire 560-line doc is inline; section structure is present, but content that should be split out (pipeline catalog, examples, advanced integrations) is not separated into one-level-deep referenced files.	2 / 3
	Total	8 / 12 Passed

Description

50%

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 a clear, third-person statement of what the skill does and its domain, but it omits explicit "when to use" trigger guidance and leans on jargon ("Stream-JSON chaining"). It is solid but generic enough to risk overlap with related workflow skills.

Suggestions

Add an explicit "Use when..." clause naming natural user triggers (e.g. "Use when chaining agent outputs into a pipeline, transforming data across sequential steps, or building multi-stage workflows").

Replace or gloss the jargon "Stream-JSON chaining" with terms a user would actually say, such as "chain agent outputs" or "sequence multi-step agent tasks".

Add one or two more concrete actions beyond "chaining" (e.g. "routes each step's output into the next, transforms data between stages") to lift specificity toward the 3-anchor.

Dimension	Reasoning	Score
Specificity	Quotes "Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows" name the domain and one action ("chaining") but do not list multiple concrete actions like the 3-anchor (extract/fill/merge); it reads as domains rather than a comprehensive action set.	2 / 3
Completeness	It states what the skill does but lacks an explicit "Use when..." trigger clause; per the guidelines a missing explicit trigger guidance caps completeness at 2, and the "for ..." clause only implies when.	2 / 3
Trigger Term Quality	"multi-agent pipelines, data transformation, sequential workflows" are reasonably natural terms, but "Stream-JSON chaining" is technical jargon and common user-facing variations (e.g. "chain agents", "pipeline steps") are missing.	2 / 3
Distinctiveness Conflict Risk	"Stream-JSON chaining" is a fairly specific niche, but "data transformation" and "sequential workflows" are generic enough to overlap with other pipeline/workflow skills, so it is not yet a clear distinct trigger set.	2 / 3
	Total	8 / 12 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: ruvnet/agentic-flow
Path: .claude/skills/stream-chain/SKILL.md
Commit: d069fff

Reviewed: about 10 hours 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.