markstream-nuxt

Integrate markstream-vue into a Nuxt 3 or Nuxt 4 app. Use when Codex needs client-only boundaries, SSR-safe setup, browser-only peer gating, worker-aware initialization, renderer `mode` selection, or a safe `MarkdownRender` integration inside pages, components, or Nuxt plugins.

Quality

81%

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

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

The body is a lean, action-oriented overview with a sequenced workflow, concrete API/prop specifics, and clearly signaled one-level references. It could be tightened by removing minor repetition and adding complete code examples plus an explicit validation command.

Suggestions

Remove the duplicated "mode='minimal' for lightweight non-chat surfaces" guidance (steps 5 and the streaming sub-section) to tighten conciseness.

Add at least one copy-paste MarkdownRender snippet showing the streaming vs. recovered-history prop set to lift actionability.

Make the validation step concrete (e.g., name the exact `nuxi typecheck`/`nuxi build` command) and add a brief validate-fix-retry note for error recovery.

Dimension	Reasoning	Score
Conciseness	The body is dense and operational, assuming Vue/Nuxt competence without explaining SSR, and nearly every line earns its place; minor repetition (e.g., "mode='minimal' for lightweight non-chat surfaces" restated) keeps it just below a 5.	4 / 5
Actionability	It gives concrete, executable guidance with exact import paths ("markstream-vue/utils", "markstream-vue/index.css"), exact prop values (mode="chat"/"docs"/"minimal", :fade="false"), and named APIs (useStickToBottom, setStreamDiffsWorkerPool); it lacks copy-paste fenced code blocks, which caps it below 5.	4 / 5
Workflow Clarity	A clear numbered 1-6 workflow ends with an explicit validation step ("Validate with the smallest relevant Nuxt dev, build, or typecheck command"), giving most checkpoints; the validation command is generic rather than specific and there is no explicit error-recovery feedback loop, so it is not a 5.	4 / 5
Progressive Disclosure	Content is split into well-organized sections (Workflow, Default Decisions, Useful Doc Targets) with one-level-deep doc references clearly signaled; the doc targets are listed as bare paths without per-file annotations, a minor organization gap below 5.	4 / 5
	Total	16 / 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.

The description is specific, uses third-person voice, and cleanly separates what the skill does from when to invoke it, with concrete and distinctive triggers. Keyword coverage is strong though a few natural synonyms are absent.

Dimension	Reasoning	Score
Specificity	"Integrate markstream-vue into a Nuxt 3 or Nuxt 4 app" names the domain plus a concrete action, and the trigger list enumerates several specific capabilities (client-only boundaries, SSR-safe setup, browser-only peer gating, worker-aware initialization, renderer mode selection, MarkdownRender integration). It stops short of the exhaustive, multi-action coverage of a 5.	4 / 5
Completeness	It explicitly answers "what" (integrate markstream-vue into a Nuxt 3/4 app) and "when" via a concrete "Use when Codex needs ..." clause listing explicit triggers, matching the anchor for clearly answering both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Phrases like "client-only boundaries", "SSR-safe setup", "Nuxt plugins", and "MarkdownRender" are natural terms a Nuxt developer would voice, giving good keyword coverage; a few common synonyms or file extensions are missing, so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	The pairing of markstream-vue with Nuxt 3/4 plus narrow SSR/client-only triggers carves a clear niche with minimal overlap against other skills, fitting the distinct-triggers anchor.	5 / 5
	Total	18 / 20 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-nuxt/SKILL.md
Commit: 3ffa399

Reviewed: 4 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.