comark

Comark (Components in Markdown) parser: syntax, AST, Vue/React/Svelte/Angular renderers, plugins, and LLM streaming with auto-close.

Quality

67%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/comark/SKILL.md

Quality

Content

68%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 highly actionable with strong executable examples and a solid reference structure, but it is verbose with redundant summary sections and lacks validation checkpoints in its batch workflow. Fixing the broken AGENTS.md link and trimming repetition would improve it.

Suggestions

Remove or merge the redundant 'Summary', 'Choose Comark when', and 'Next Steps' sections, which repeat the overview and reference links already shown above.

Add a validation/verification step to the 'Batch File Processing' example (e.g. assert node counts or catch parse errors) so the batch workflow clears the workflow-clarity cap.

Resolve the missing ./AGENTS.md reference (create the file or remove the link) to make progressive disclosure fully consistent.

Dimension	Reasoning	Score
Conciseness	The ~530-line body is mostly useful code and API content, but redundant Summary, 'Choose Comark when', and 'Next Steps' sections plus the ASCII architecture diagram and repeated reference links add padding that could be trimmed.	3 / 5
Actionability	Provides fully executable, copy-paste-ready examples across common cases — basic parsing, each framework renderer, static-site generation, real-time editor, and batch processing — plus concrete API signatures.	5 / 5
Workflow Clarity	The guide is well-organized but lacks explicit multi-step workflows with validation checkpoints; the 'Batch File Processing' use case is a batch operation with no verification step, capping this dimension at 3.	3 / 5
Progressive Disclosure	Clear overview with well-signaled one-level-deep references to six real ./references/*.md files, but the referenced ./AGENTS.md does not exist and some inline content (API summary, architecture diagram) could be split out.	4 / 5
	Total	15 / 20 Passed

Description

66%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 and clearly distinguishes the skill's capabilities, but it omits any 'when to use' trigger guidance, which limits its completeness and triggerability. Adding an explicit 'Use when...' clause would meaningfully raise the score.

Suggestions

Append an explicit 'Use when...' clause naming concrete triggers (e.g. 'Use when parsing or rendering markdown with custom components, streaming LLM output, or rendering markdown in Vue/React/Svelte/Angular').

Lead with verb-based actions ('Parses', 'Renders', 'Streams') instead of a noun list to strengthen specificity.

Include natural user phrasing and file extensions (e.g. '.md', 'markdown to HTML') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Comark parser') and lists several concrete capabilities — 'syntax, AST, Vue/React/Svelte/Angular renderers, plugins, and LLM streaming with auto-close' — but frames them as features/nouns rather than verbs, leaving minor coverage gaps.	4 / 5
Completeness	The 'what' is clear and concrete, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('markdown parser', 'Vue/React/Svelte/Angular renderers', 'LLM streaming', 'auto-close'), but a few common phrases users might say (e.g. 'convert markdown to HTML', 'render markdown') are only implied.	4 / 5
Distinctiveness Conflict Risk	The niche (Components-in-Markdown with multi-framework renderers and LLM streaming) is fairly distinct, with only minor overlap risk against general markdown skills; missing explicit triggers prevents a 5.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (535 lines); consider splitting into references/ and linking	Warning
relative_links	Relative link issues: 3 missing, 3 suspicious	Warning

	Total	14 / 16 Passed

Repository: onmax/nuxt-skills
Path: skills/comark/SKILL.md
Commit: bc438e5

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