CtrlK
BlogDocsLog inGet started
Tessl Logo

markstream-migration

Audit and migrate existing Markdown rendering to Markstream, or upgrade a markstream-vue 1.x integration to 2.x. Use when Codex needs to replace another renderer, classify direct vs custom vs plugin-heavy adoption, preserve behavior during adoption, migrate custom renderers into scoped Markstream overrides, decide when `nodes` streaming is worth adopting, or replace removed 1.x code-block dependencies, APIs, preview payloads, and parser types.

70

Quality

85%

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 well-structured, actionable migration skill that routes work clearly and defers detail to genuinely existing reference files. The main improvement opportunity is making the validation steps in both routes explicit feedback loops rather than implied checkpoints.

Suggestions

Convert Route A step 7 and Route B step 4 validation into explicit validate→fix→retry loops (e.g. 'If checks fail: fix and re-run; only proceed when they pass') to strengthen feedback-loop clarity for a destructive/batch migration.

Tighten the streaming-vs-history paragraph in Route A step 6 into a compact table or bulleted mode/props mapping to reduce prose density.

Consider one small copy-paste-ready manifest snippet (e.g. the coordinated beta family install command) in Route B step 2 to raise actionability from concrete-instruction to fully executable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no preamble explaining what Markdown or a renderer is), but a few prose-heavy bullet groups such as the streaming/history paragraph could be tightened further.

4 / 5

Actionability

Highly concrete, instruction-level guidance with specific props, package names, and modes (e.g. 'Rename monacoOptions / codeBlockMonacoOptions ... to codeBlockOptions', 'prefer renderer-local streamingComponents ... and htmlComponents ...'); as an instruction-only migration skill the absence of code blocks is justified, with only minor gaps.

4 / 5

Workflow Clarity

Both routes are clearly sequenced with numbered steps and validation/rollback checkpoints ('Run the smallest relevant tests or build', 'Validate the migrated behavior and leave a rollback path'), though some validation is implicit rather than framed as an explicit validate→fix→retry loop.

4 / 5

Progressive Disclosure

SKILL.md acts as a concise overview with well-signaled, one-level-deep references to real bundle files ([references/vue-1x-to-2x.md] and [references/adoption-checklist.md]), and the detailed migration content is correctly deferred to those references.

5 / 5

Total

17

/

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 strong, specific description that clearly states both the capability and the trigger conditions in third person. It is comprehensive and highly distinct; the only minor gap is that trigger phrasing leans technical rather than mirroring the exact words a user would say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Audit and migrate', 'upgrade a markstream-vue 1.x integration to 2.x', 'classify direct vs custom vs plugin-heavy adoption', 'migrate custom renderers into scoped Markstream overrides', 'replace removed 1.x code-block dependencies, APIs, preview payloads, and parser types' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both 'what' (audit/migrate/upgrade) and 'when' via a detailed 'Use when Codex needs to...' clause enumerating concrete trigger situations, matching the top anchor.

5 / 5

Trigger Term Quality

Good coverage of domain terms ('Markdown rendering', 'Markstream', 'markstream-vue 1.x...2.x', 'renderer'), but the phrasing is fairly technical and a few natural user phrasings (e.g. 'migrate to Markstream', 'upgrade markstream-vue') are implicit rather than surfaced as synonyms.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Markstream adoption and 1.x→2.x upgrade) with distinct, specific triggers and minimal realistic 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.