CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 exemplary in token efficiency and gives a specific, actionable layout and output contract, but it is undermined by a dangling reference: the workflow's first step instructs reading DESIGN.md, which is absent from the bundle. Fixing or inlining that dependency would lift the workflow, actionability, and disclosure scores.

Suggestions

Ship DESIGN.md in the bundle (or inline the needed palette/typography tokens) so the workflow's first step 'Read DESIGN.md' resolves to a real file.

Add a lightweight checkpoint after layout, e.g. 'verify all three objectives have exactly 3 key results with metric, current→target, and progress bar' before emitting the artifact.

If the file exists elsewhere, reference it with an explicit relative path and link, e.g. 'Read [DESIGN.md](references/DESIGN.md)', so the dependency is clearly signaled.

DimensionReasoningScore

Conciseness

The ~20-line body is lean and efficient with zero concept explanations or padding — every line is either a layout instruction or the output contract — matching anchor 5 ('every token earns its place') rather than the minor-trimming case of anchor 4.

5 / 5

Actionability

The layout spec is concrete ('Q4 FY25, dates, overall progress chip', '3 key results, each a row with metric / current → target / progress bar') and the output contract gives an exact artifact snippet, fitting anchor 4. Not anchor 5: step 1 ('Read DESIGN.md') points to a file that does not exist in the bundle, leaving the design-token source unresolved.

4 / 5

Workflow Clarity

A three-step sequence is present but step 1 is unresolvable — DESIGN.md is not in the bundle (no references/, scripts/, or assets/ exist) — and there are no validation checkpoints, fitting anchor 3 ('sequence present but checkpoints missing or implicit') more than anchor 4's mostly-complete sequence.

3 / 5

Progressive Disclosure

The body is short and well-sectioned, but the only external reference ('Read DESIGN.md') is a dangling path with no matching bundle file and no link signaling. Under the guideline to score against the actual bundle structure, this fits anchor 3 (references present but broken/unresolvable) rather than the clean split of anchors 4-5.

3 / 5

Total

15

/

20

Passed

Description

87%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.

Strong description: concrete component inventory, an explicit 'use when' clause with natural trigger terms including a Chinese synonym, and a distinct niche. Minor room to broaden trigger coverage (e.g., 'goals', 'KPI') for a perfect score.

DimensionReasoningScore

Specificity

The description lists several concrete components — 'quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar' — which goes beyond 1-2 generic actions (anchor 3) but stops short of the comprehensive coverage of anchor 5, omitting any behavioral or output-format detail.

4 / 5

Completeness

It explicitly answers both what (a single-screen OKR tracker page with enumerated components) and when ('Use when the brief mentions...') with concrete trigger phrases, matching the anchor-5 pattern exactly rather than the weaker 'when' of anchor 4.

5 / 5

Trigger Term Quality

'Use when the brief mentions "OKRs", "key results", "objectives", or "目标"' gives good natural-term coverage including a Chinese synonym, matching anchor 4. Not anchor 5: common variations such as 'goals', 'KPI', or 'progress tracking' are missing.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche (OKR tracker page) with distinct, unambiguous triggers ('OKRs', 'key results', '目标') and minimal overlap with other skills, fitting anchor 5; it is far more specific than the broad anchor-3/4 examples.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

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.