CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

markstream-vue2

Integrate markstream-vue2 into a Vue 2.6 or 2.7 app. Use when Codex needs Vue 2-compatible setup, `@vue/composition-api` decisions, CSS wiring, optional peer setup, or scoped Markstream overrides in a Vue 2 repository that is not specifically Vue CLI / Webpack 4 constrained.

Quality

86%

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

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.

A tight, well-structured instruction body: every line carries skill-specific decisions (prop defaults, streaming-vs-history configurations, security defaults) with no filler. The main weaknesses are the unnamed install command and a vague final validation step, plus a couple of rationale sentences that could be trimmed.

Suggestions

Name the concrete validation command(s) in step 6 (e.g., 'npm run build' or 'npm run dev') and add a short failure-handling note so the workflow ends with an explicit checkpoint.

Give the install command for step 2 (e.g., 'npm install markstream-vue2 @vue/composition-api') so the setup path is fully copy-paste ready.

Trim rationale sentences in the streaming-vs-history section (e.g., 'Content is already complete — pacing would slow it down...') to prop configurations alone, moving explanation to a doc target if needed.

DimensionReasoningScore

Conciseness

The body is dense with skill-specific facts Claude cannot know (prop defaults like 'smooth-streaming="auto" is the default and activates when typewriter=true or max-live-nodes <= 0') and contains no generic Vue tutoring. A few rationale sentences ('Content is already complete — pacing would slow it down, but fade gives a polished entry animation') could be trimmed, matching the 'efficient; minor instances of over-explanation' anchor rather than the fully lean score-5 anchor.

4 / 5

Actionability

Prop bindings are concrete and copy-paste ready (':smooth-streaming="isStreaming ? \'auto\' : false"', 'html-policy="safe"', ':mermaid-props="{ isStrict: false }"'), and the starting component ('<MarkdownRender :content="markdown" />') is executable. Not 5 because 'Install markstream-vue2' omits the actual install command and step 6 ('Validate with the smallest useful dev or build command') names no specific command; well above 3 since most guidance is directly executable.

4 / 5

Workflow Clarity

A clear 6-step sequence from repo detection ('Confirm the repo is Vue 2.6 or 2.7') through CSS import order, component adoption, overrides, and validation ('Validate with the smallest useful dev or build command'). This is a score-4 fit: most checkpoints are present but the final validation step is vague, lacking the explicit command and failure-handling loop of the score-5 anchor; no destructive or batch operations apply, so no cap.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (no references/, scripts/, or assets/ directories exist), and the body is cleanly organized into 'Workflow', 'Default Decisions', and 'Useful Doc Targets' with one-level-deep pointers to package docs (e.g., 'docs/guide/vue2-quick-start.md'). Per the simple-skill guideline, well-organized sections alone justify the score-5 anchor here.

5 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description: concrete, in a clearly delimited niche, with an explicit 'Use when' clause containing actionable trigger phrases and a boundary that steers away from sibling skills. The only gaps are a few missing natural synonyms (e.g., markdown rendering, streaming) in the trigger terms.

DimensionReasoningScore

Specificity

Names the domain ('Integrate markstream-vue2 into a Vue 2.6 or 2.7 app') and lists several concrete action areas ('Vue 2-compatible setup, `@vue/composition-api` decisions, CSS wiring, optional peer setup, or scoped Markstream overrides'), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because coverage is not comprehensive (e.g., component usage and streaming configuration are absent), and well above 3 since more than 1-2 actions are enumerated.

4 / 5

Completeness

Explicitly answers both: 'what' ('Integrate markstream-vue2 into a Vue 2.6 or 2.7 app') and 'when' ('Use when Codex needs Vue 2-compatible setup... in a Vue 2 repository that is not specifically Vue CLI / Webpack 4 constrained') with concrete trigger phrases and an explicit boundary condition. This matches the score-5 anchor exactly.

5 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say: 'Vue 2.6 or 2.7', 'Vue 2-compatible setup', '@vue/composition-api', 'CSS wiring', 'Markstream overrides', 'Vue CLI / Webpack 4'. Not 5 because common variations like 'markdown rendering' or 'streaming UI' are missing; not 3 since coverage goes well beyond a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Vue 2.6/2.7 integration of a specific package) with distinct triggers, and it explicitly fences off the Vue CLI / Webpack 4 case that belongs to a sibling skill ('markstream-vue2-cli'). Minimal conflict risk, matching the score-5 anchor.

5 / 5

Total

18

/

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

Simon-He95/markstream-vue

Path

.agents/skills/markstream-vue2/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.