team-okrs

OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".

Quality

81%

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

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.

A concise, well-structured single-purpose skill with concrete layout guidance and a clear output contract. Its main weakness is a broken reference to DESIGN.md, which the workflow depends on but which is absent from the bundle.

Suggestions

Either provide DESIGN.md in ./references/ or remove the 'Read DESIGN.md' step and inline any required design tokens (palette, accent, spacing) directly in the body.

Add a minimal HTML skeleton or one complete objective-card example so the output contract is copy-paste ready rather than structural-only.

Clarify the output contract by showing the expected progress-bar markup pattern for a key result, not just the artifact wrapper.

Dimension	Reasoning	Score
Conciseness	Lean ~22-line body that assumes Claude's competence, with no over-explanation of known concepts and every line (layout spec, output contract) earning its place.	5 / 5
Actionability	Concrete structural guidance — exact card structure, status pill values ('On track / At risk / Off track'), key-result row fields, and an artifact output contract — but no executable HTML example, leaving minor gaps for a code-producing skill.	4 / 5
Workflow Clarity	A clear three-step sequence for a single-purpose prototype skill that needs no validation checkpoints, slightly capped by step 1's reference to a DESIGN.md that is not provided.	4 / 5
Progressive Disclosure	Sections are well-organized (Workflow, Output contract) for a short skill, but the workflow's opening 'Read DESIGN.md' references a file that does not exist in any bundle directory, a broken one-level reference that hinders navigation and execution.	3 / 5
	Total	16 / 20 Passed

Description

83%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 description that clearly states both what it produces and when to use it, with concrete trigger phrases including a non-English synonym. It is mostly specific and distinct, with only minor gaps in trigger coverage and a slightly generic term ('objectives').

Dimension	Reasoning	Score
Specificity	Lists several concrete output components — 'quarter banner', 'three objectives with their key results as progress bars, owner avatars, status pills, ... sidebar' — giving specific building blocks of the artifact, though framed as output features rather than distinct actions.	4 / 5
Completeness	Explicitly answers both 'what' (an OKR tracker page with enumerated components) and 'when' ('Use when the brief mentions OKRs, key results, objectives, or 目标') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Triggers 'OKRs', 'key results', 'objectives', and '目标' are natural user phrases with a non-English synonym included, but common variations like 'goals' or 'KRs' are missing.	4 / 5
Distinctiveness Conflict Risk	The OKR/key-results niche is clearly distinct with specific triggers, but 'objectives' alone is generic enough to create minor overlap risk with general goal- or planning-oriented skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/team-okrs/SKILL.md
Commit: 1a7a23d

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