CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-stream-nesting-logic

万悟平台 SSE 子会话递归嵌套与三明治序列渲染架构指南。涵盖 parentId 领养、order 绝对排序、动静 Chunk 分层及 Vue 2 响应式引用协议。

57

Quality

64%

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 ./.agents/skills/agent-stream-nesting-logic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is a concise, well-structured protocol guide that assumes competence and avoids padding, but it functions as a rule set rather than a sequenced, validated workflow with executable examples. Adding an ordered rendering sequence with validation checkpoints and concrete code snippets would lift the weaker dimensions.

Suggestions

Add an ordered, step-by-step rendering sequence (e.g., receive package -> resolve parentId 领养 -> sort by order -> split stable/active chunks -> emit DOM with data attributes) with explicit validation checkpoints.

Provide concrete, copy-paste-ready code or pseudocode for the key rules (parentSub.messageSequence.push, the sseMethod.js id===parentId interception/re-stamp) so guidance is fully executable.

Make the ID self-reference interception an explicit validate->fix->retry feedback loop rather than an isolated rule.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: it states tight protocol rules with concrete field names (parentId, order, stableChunks, activeResponse, data-sub-id) and only explains the one critical reactive-red-line case where the rationale is genuinely necessary, so every token earns its place.

3 / 3

Actionability

It gives some concrete guidance (e.g., `parentSub.messageSequence.push(subConversion)`, intercept in `sseMethod.js` and re-stamp with a `content_` prefix), but as an instruction-only architecture guide it stops short of copy-paste-ready, complete executable examples for each rule.

2 / 3

Workflow Clarity

Rules are organized into clear sections, but the rendering protocol is not presented as an ordered, sequenced workflow with explicit validation checkpoints; the only checkpoint-like item (id === parentId interception) is isolated rather than part of a feedback loop.

2 / 3

Progressive Disclosure

At under 50 lines with no bundle files needed, the body is well-organized into six numbered sections, which per the simple-skill scoring note is sufficient for a top progressive-disclosure score.

3 / 3

Total

10

/

12

Passed

Description

57%

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 specific and clearly occupies a distinct niche, but it lacks an explicit "when to use" trigger clause and relies on technical jargon over natural user phrasing. Adding a Use-when clause with more colloquial trigger terms would raise its score.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should apply this protocol (e.g., when rendering 万悟平台 SSE sub-session streams or debugging nested 打字机 rendering issues).

Soften technical jargon with natural trigger terms users would actually say, alongside the existing domain vocabulary.

Reframe the covered topics as concrete actions Claude performs (e.g., '递归领养子会话、按 order 排序、区分动静 Chunk') instead of describing what the guide 'covers'.

DimensionReasoningScore

Specificity

The description names a concrete domain and several specific mechanisms ("parentId 领养、order 绝对排序、动静 Chunk 分层及 Vue 2 响应式引用协议"), but it frames them as topics a guide "covers" rather than concrete user-facing actions, so it stops short of the multi-action clarity of a level-3 anchor.

2 / 3

Completeness

It clearly states what the skill is (an architecture guide for recursive sub-session rendering) but provides no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It includes some relevant domain keywords (SSE、子会话、Vue 2、嵌套渲染) a maintainer might say, but the phrasing leans heavily on technical jargon (三明治序列、响应式引用协议) rather than the natural, varied terms users would actually invoke.

2 / 3

Distinctiveness Conflict Risk

The niche is highly specific (万悟平台 SSE 子会话递归嵌套渲染架构) with distinct triggers, making it unlikely to be selected for the wrong skill.

3 / 3

Total

9

/

12

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
UnicomAI/wanwu
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.