CtrlK
BlogDocsLog inGet started
Tessl Logo

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 code block choices limited to `stream-diffs` or plain `<pre>`.

72

Quality

89%

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

86%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 compact, well-structured integration skill that assumes Claude's competence and gives concrete configuration guidance with a clear workflow. The main gap is a soft validation step that could be made into an explicit feedback loop, and a couple of executable commands (install/import) are implied rather than shown.

Suggestions

Make step 6 an explicit feedback loop: name a concrete command (e.g. `npm run build`) and add 'If it fails, fix and re-run before proceeding'.

Add the concrete install command (e.g. `npm i markstream-vue2`) and the exact CSS import line in the workflow steps so guidance is copy-paste ready.

Confirm the three `docs/guide/*.md` paths exist in the host repo, or note them as targets to look up rather than guaranteed files.

DimensionReasoningScore

Conciseness

Lean and token-efficient with no padding or explanation of concepts Claude already knows; every line carries actionable configuration detail.

5 / 5

Actionability

Provides concrete, specific guidance with exact function names, prop values, and config snippets (e.g. `:smooth-streaming="isStreaming ? 'auto' : false"`), with minor gaps such as the missing exact install command and import line.

4 / 5

Workflow Clarity

A clearly sequenced 6-step workflow with a validation checkpoint in step 6 ('Validate with the smallest useful local dev or build command'), but the validation is soft and lacks an explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, and well-organized into Workflow / Default Decisions / Useful Doc Targets with one-level-deep doc references, fitting the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

92%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 tight, concrete, third-person description that states both what it does and when to use it, with a well-scoped niche that minimizes conflict risk. Only minor: a few natural synonyms/file extensions are absent from the trigger terms.

DimensionReasoningScore

Specificity

Names the integration domain and enumerates multiple concrete capabilities (Webpack 4 setup, CDN worker fallbacks for Mermaid/KaTeX, `dist/index.css` imports, composition-api shims, `stream-diffs`/`<pre>` code block choices) for comprehensive coverage.

5 / 5

Completeness

Explicitly answers both 'what' (integrate markstream-vue2 into a Vue 2 Vue CLI/Webpack 4 app) and 'when' ('Use when Codex needs...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural trigger terms (Vue 2, Vue CLI, Webpack 4, Mermaid, KaTeX, `dist/index.css`), with a few common variations or file extensions (e.g. `.vue`) missing.

4 / 5

Distinctiveness Conflict Risk

A clear narrow niche (Vue 2 + Vue CLI/Webpack 4 + markstream-vue2) with distinct, specific triggers and minimal overlap with other skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Simon-He95/markstream-vue
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.