CtrlK
BlogDocsLog inGet started
Tessl Logo

markstream-custom-components

Override built-in Markstream node renderers and add trusted custom tags across Vue, React, Svelte, and Angular. Use when Codex needs scoped `setCustomComponents`, renderer-local React `streamingComponents` or `htmlComponents`, Angular/Svelte `customComponents`, Vue app-scoped components, node override keys such as `image`, `code_block`, `mermaid`, or `link`, or nested renderers for tags such as `thinking`.

68

Quality

83%

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.

The body is an efficient, well-structured workflow that delegates detail to a real one-level reference and includes a validation step. Its main weakness is the absence of executable code examples, which keeps actionability just below fully copy-paste ready.

Suggestions

Add one small executable code snippet (e.g., a scoped setCustomComponents call with a nested renderer for a custom tag) to lift actionability to copy-paste ready.

Tighten the 'Default Decisions' list by removing items that restate the workflow steps (e.g., 'Scoped overrides first', 'Leaf-node overrides before container-node overrides').

Make the step 6 validation checkpoint concrete by naming a specific check (e.g., a demo command or assertion) rather than only 'prefer a local demo, targeted test, or docs build'.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's knowledge of the frameworks, with no padded concept explanations; a few decision-list items repeat information already implied by the workflow steps and could be trimmed.

4 / 5

Actionability

Concrete guidance with specific function signatures (setCustomComponents(customId, mapping), defineStreamingComponents(...)) and exact props to preserve (node, loading, indexKey, estimatedPreviewHeightPx), but lacks any executable code examples to anchor the API usage.

4 / 5

Workflow Clarity

A clear six-step sequence (Classify → scoped mappings → smallest safe override → nested Markdown → props/cleanup → validate) with an explicit validation checkpoint in step 6; minor gap is that the validation step stays qualitative rather than naming a concrete command or assertion.

4 / 5

Progressive Disclosure

Well-organized sections with a clearly signaled, one-level-deep reference to a real file (references/patterns.md) at the top; detail is appropriately split into the reference while the body stays an overview, making navigation easy.

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.

The description is strong: it clearly states what the skill does and when to use it, with concrete API names and framework-specific triggers that make it highly distinct. Verbosity is well-controlled and the trigger guidance is explicit.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Override built-in Markstream node renderers', 'add trusted custom tags' — across named frameworks with specific override keys, but coverage is API-name-heavy with minor gaps in plain-language action verbs.

4 / 5

Completeness

Explicitly answers both 'what' (override renderers and add trusted custom tags across Vue/React/Svelte/Angular) and 'when' (concrete 'Use when Codex needs...' trigger phrases enumerating specific scenarios).

5 / 5

Trigger Term Quality

Good keyword coverage with natural API names users would cite ('setCustomComponents', 'streamingComponents', 'htmlComponents', 'customComponents') and node keys ('image', 'code_block', 'mermaid', 'link', 'thinking'); a few plain-language synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche scoped to Markstream custom components with triggers tied to specific API names and node override keys, yielding minimal conflict risk with other skills.

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.

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.