markstream-vue2-cli

Integrate markstream-vue2 into a Vue 2 Vue CLI or Webpack 4 app. Use when Codex needs Webpack 4-friendly setup, CDN worker fallbacks for Mermaid or KaTeX, `dist/index.css` imports, Vue 2 composition-api shims, or safer code block defaults that avoid fragile Monaco worker setups.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%Weight 40%Scale 1-3

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

The body is concise, actionable, and well-structured with concrete APIs, attribute values, and clear doc-target navigation. The main gap is workflow validation: step 6 names no concrete validation command and lacks an explicit validate-fix-retry feedback loop.

Suggestions

Replace the generic step 6 validation with a concrete command example (e.g., 'npm run build' or 'npx vue-cli-service build') so the checkpoint is executable rather than implicit.

Add an explicit feedback loop after validation: if the dev/build command fails, fix the worker or import configuration and re-run before proceeding.

Optionally move the detailed streaming-vs-recovering-history attribute triples into a referenced doc target, keeping the overview leaner while preserving the guidance.

Dimension	Reasoning	Score
Conciseness	Lean and directive with no concept-explaining filler; every section is task-specific guidance (named APIs, props, and decisions) that assumes Claude's competence. The streaming/history configuration block is dense but genuinely useful rather than padded.	3 / 3
Actionability	Provides concrete, named APIs and copy-paste-ready attribute values such as createKaTeXWorkerFromCDN(...), MarkdownCodeBlockNode, :smooth-streaming="isStreaming ? 'auto' : false", and html-policy="trusted", giving specific executable guidance.	3 / 3
Workflow Clarity	A clear numbered 6-step sequence with a precondition check (step 1) and a validation step (step 6), but the validation checkpoint is generic ('smallest useful local dev or build command') rather than a concrete command, and there is no explicit error-recovery feedback loop.	2 / 3
Progressive Disclosure	Well-organized into Workflow, Default Decisions, and Useful Doc Targets, with clearly signaled one-level-deep doc references (vue2-quick-start.md, vue2-installation.md, troubleshooting.md) and overview-level inline content appropriately split from detail.	3 / 3
	Total	11 / 12 Passed

Description

85%Weight 40%Scale 1-3

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, complete, and distinct, clearly scoping a narrow Vue 2 / Webpack 4 integration niche with explicit 'what' and 'when' guidance. Trigger phrasing leans somewhat technical and tool-internal rather than reflecting natural user language.

Dimension	Reasoning	Score
Specificity	Names the domain (Vue 2 / Vue CLI / Webpack 4) and enumerates multiple concrete actions: CDN worker fallbacks for Mermaid/KaTeX, dist/index.css imports, composition-api shims, and safer code block defaults.	3 / 3
Completeness	Clearly states what it does ('Integrate markstream-vue2 into a Vue 2 Vue CLI or Webpack 4 app') and provides an explicit 'Use when...' clause listing triggers, answering both what and when.	3 / 3
Trigger Term Quality	Includes relevant niche keywords (Vue 2, Vue CLI, Webpack 4, Mermaid, KaTeX, Monaco) with an explicit 'Use when' clause, but several triggers are tool-internal or technical jargon ('composition-api shims', 'dist/index.css imports') rather than broad natural variations a user would say.	2 / 3
Distinctiveness Conflict Risk	Targets a narrow niche (a specific library on a legacy Vue 2 / Webpack 4 stack) with distinctive triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Simon-He95/markstream-vue
Path: .agents/skills/markstream-vue2-cli/SKILL.md
Commit: f25ebd5

Reviewed: 11 days 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.