CtrlK
BlogDocsLog inGet started
Tessl Logo

markstream-install

Install and wire markstream-vue, markstream-react, markstream-vue2, markstream-angular, or markstream-svelte into an existing repository. Use when Codex needs to choose the right package, install the smallest framework-specific peer-dependency set, fix CSS/reset order, choose Vue 3 renderer mode and built-in, plain, or custom code-block paths, decide between `content`, `nodes`, and Vue 3 virtual-scroll coordination, or add a minimal working renderer example.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/markstream-install/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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-organized, lean install skill with a clear validated workflow and a real bundled reference. Its main weakness is the absence of an executable renderer example despite naming that as a core task, and some repeated streaming guidance.

Suggestions

Add one minimal copy-pasteable renderer example per framework (or at least for Vue 3) so the 'add a minimal working renderer example' trigger is directly actionable.

De-duplicate the 'streaming vs recovering history' guidance that appears in both step 4 and Default Decisions, keeping the fuller version in one place and linking from the other.

Make the feedback loop explicit in the Validate step — if the build/typecheck fails, fix peers or CSS order and re-run.

DimensionReasoningScore

Conciseness

Dense and lean — it assumes Claude's competence and never explains basics — but the 'streaming vs recovering history' guidance is repeated across Workflow step 4 and Default Decisions, so a little could be trimmed.

4 / 5

Actionability

Gives concrete prop values and named APIs ('mode="chat"', 'fade=false', 'setCustomComponents(customId, { code_block: ... })', 'useMarkstreamVirtualAdapter()'), but for a skill whose own trigger is 'add a minimal working renderer example' there is no actual copy-pasteable code example, only prop guidance.

3 / 5

Workflow Clarity

A clear six-step sequence (Detect → Install → Fix CSS → Add example → Scope customization → Validate) with an explicit validation step ('Run the smallest relevant build, typecheck, test, or docs build command'), though without a fix-and-retry feedback loop.

4 / 5

Progressive Disclosure

Overview body with a clearly signaled one-level-deep reference ('Read references/scenarios.md before making dependency choices') that resolves to a real bundled file, plus a 'Useful Doc Targets' list; minor gap that those targets are external doc paths rather than bundled files.

4 / 5

Total

15

/

20

Passed

Description

91%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 pairs a clear 'what' with an explicit multi-condition 'when' clause. It is comprehensive and distinct, with only minor room to broaden plain-language trigger synonyms.

DimensionReasoningScore

Specificity

Lists multiple concrete install actions — 'choose the right package', 'install the smallest framework-specific peer-dependency set', 'fix CSS/reset order', 'choose Vue 3 renderer mode', 'decide between content, nodes, and virtual-scroll coordination', 'add a minimal working renderer example' — with comprehensive coverage across install sub-decisions.

5 / 5

Completeness

Explicitly answers both 'what' (install and wire the markstream packages into an existing repository) and 'when' (an explicit 'Use when Codex needs to...' clause enumerating concrete trigger conditions).

5 / 5

Trigger Term Quality

Natural trigger phrases appear ('Use when Codex needs to...') alongside framework package names as synonyms, but it leans on the 'markstream' token and omits some plain-language variants a user might say.

4 / 5

Distinctiveness Conflict Risk

A clear markstream-install niche with package-specific triggers; minimal risk of firing for an unrelated skill.

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.