markstream-angular

Integrate the alpha markstream-angular package into an Angular 20+ app. Use when Codex needs standalone component imports, signal-based examples, CSS wiring, custom HTML tags or customComponents setup, or optional peer integration in an Angular repository.

Quality

93%

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

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured integration guide with concrete Angular bindings and CSS paths throughout. Its main weakness is workflow validation: step 7 names no specific command and provides no error-recovery loop, capping workflow clarity.

Suggestions

Replace the vague step 7 with a concrete validation command (e.g., `ng build` or `npm run build`) and add a brief feedback loop: if the build fails on the markstream imports/CSS, re-check the import paths and bindings before retrying.

Give the exact install command in step 2 (e.g., `npm install markstream-angular` plus the requested peer packages) rather than only naming the packages to install.

Tighten the Default Decisions section so it does not restate step 5/6 defaults verbatim; keep it as a one-line quick-reference of defaults to remove the mild redundancy.

Dimension	Reasoning	Score
Conciseness	The body (~45 lines) avoids explaining general Angular concepts and confines prose to markstream-specific rationale ("Smooth pacing handles gradual appearance; fade would flicker"), so tokens earn their place rather than padding general knowledge Claude already has.	3 / 3
Actionability	Concrete, copy-paste-ready guidance dominates: specific bindings like "[smoothStreaming]='auto'", "[htmlPolicy]='safe'", and exact paths "markstream-angular/index.css" and "katex/dist/katex.min.css", with the component name MarkstreamAngularComponent; the two vaguer steps (install, validate) are a minority and do not outweigh this.	3 / 3
Workflow Clarity	The 7-step sequence is clearly ordered, but step 7 ("Validate with the smallest useful Angular dev or build command") is vague with no specific command and no validate→fix→retry feedback loop, matching the anchor where checkpoints are present but implicit or gapped.	2 / 3
Progressive Disclosure	Under 50 lines with no bundle files present, the body is organized into clear sections (Workflow, Default Decisions, Useful Doc Targets) and the doc-target paths are one-level-deep, well-signaled navigation pointers, satisfying the simple-skill allowance for a top score on organization alone.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, third-person description that names a concrete niche (Angular 20+ alpha package integration) and an explicit Use-when trigger listing the specific capabilities it handles. It is specific, complete, and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Quotes "standalone component imports, signal-based examples, CSS wiring, custom HTML tags or customComponents setup, or optional peer integration" — a list of multiple specific concrete capabilities, matching the anchor for listing multiple concrete actions rather than the vaguer score-2 anchor.	3 / 3
Completeness	It states what ("Integrate the alpha markstream-angular package into an Angular 20+ app") and an explicit when ("Use when Codex needs..."), satisfying the anchor that requires both an explicit what and an explicit trigger.	3 / 3
Trigger Term Quality	Terms like "standalone component imports", "CSS wiring", "custom HTML tags", and "customComponents setup" are exactly the feature-level vocabulary a developer integrating this package would naturally say, giving good coverage rather than the sparse score-2 case.	3 / 3
Distinctiveness Conflict Risk	The niche "alpha markstream-angular package into an Angular 20+ app" with feature-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 12 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-angular/SKILL.md
Commit: f25ebd5

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