north-star

Constitutional source of truth for reusable Plate architecture and public API design. Use when introducing or changing reusable public APIs, runtime/service boundaries, builder or factory patterns, extension registration contracts, naming/layering rules, or performance-sensitive architecture.

Quality

71%

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 ./.agents/skills/north-star/SKILL.md

Quality

Content

63%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-structured doctrine skill with concrete workflow, checklist, and reaffirmation mechanics, undermined by repeated routing/ownership sections and by rule-file references that resolve to no actual bundle files. Tightening the redundancy and shipping the referenced rules would lift the weaker dimensions.

Suggestions

Collapse the overlapping Use When / Do Not Use When / Hard Routing Rule / Routing Matrix / Who Owns What sections into a single routing + ownership block to remove roughly four restatements of the same decision logic.

Create the referenced ./rules/ files (laws.md, decision-ladder.md, performance-selection-rules.md, update-policy.md, pattern-catalog.md, anti-patterns.md) or remove the dead links so progressive-disclosure navigation resolves.

Make the workflow steps more self-contained by summarizing the validation criteria from each referenced rule inline, so a reader can pass the Binary Review Checklist without opening every file.

Dimension	Reasoning	Score
Conciseness	The body is dense and free of concept explanations Claude already knows, but the Use When / Do Not Use When / Hard Routing Rule / Routing Matrix / Who Owns What sections restate routing and ownership roughly four times, adding avoidable tokens.	3 / 5
Actionability	Provides concrete guidance: an 8-step workflow with named rule files, exact reaffirmation tag formats ("north-star reaffirmed: laws"), and a binary review checklist; much actionable detail lives behind the referenced files, leaving minor gaps.	4 / 5
Workflow Clarity	An ordered 8-step workflow includes validation checkpoints (decision ladder, anti-patterns check, update policy) plus a review checklist gate; some steps are pointers to external files rather than self-contained validation.	4 / 5
Progressive Disclosure	Structure is well organized with one-level-deep references grouped under Constitutional/Pattern Layer headers, but the referenced ./rules/*.md files do not exist in the bundle, so the disclosure points to dead links.	3 / 5
	Total	14 / 20 Passed

Description

78%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, niche description that answers both what and when with concrete trigger phrases and is clearly distinct from sibling skills. It sits just below the top anchor because its action list is slightly less granular and its trigger wording is less user-mention oriented.

Dimension	Reasoning	Score
Specificity	Lists several concrete design actions ("introducing or changing reusable public APIs, runtime/service boundaries, builder or factory patterns, extension registration contracts, naming/layering rules"), with only minor gaps in granularity compared to a fully exhaustive action list.	4 / 5
Completeness	States a clear "what" ("Constitutional source of truth for reusable Plate architecture and public API design") and an explicit "Use when..." clause; the "when" is concrete but slightly less externally trigger-worded than the top anchor.	4 / 5
Trigger Term Quality	Includes genuine trigger phrases a Plate developer would name ("public APIs", "runtime/service boundaries", "builder or factory patterns", "extension registration contracts"); a few natural synonyms like "plugin" or "registry" are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (reusable Plate architecture doctrine) and is explicitly separated from the plugin-authoring execution companion, giving it minimal conflict risk.	5 / 5
	Total	17 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 12 missing, 6 suspicious	Warning

	Total	13 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/north-star/SKILL.md
Commit: bc7104f

Reviewed: 1 day 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.