CtrlK
BlogDocsLog inGet started
Tessl Logo

neo-identity-update

Repeatable protocol for updating Neo's identity (what Neo IS) coherently across ALL surfaces that encode it — README, VISION, learn/benefits, package.json, GitHub repo metadata, portal app, and the build-generated SEO files. Treats FACTS (version, MCP-server count, Node req, dates) as single-source-derive, FRAMING (taglines, positioning) as audience-segmented against a canonical apex, and ACTIONS / CTAs as governed next-step surfaces. Triggers: Use when changing Neo's tagline / positioning / description / keywords / pillar story / CTAs; when a maintainer says 'update the identity / README / branding / how we describe Neo'; when a shipped capability outgrows the current framing; or when a fact (version, server count, requirement) drifts across surfaces. Foundation: ADR 0018.

74

Quality

93%

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

86%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 a tight, well-disciplined overview that routes to a real, well-structured reference bundle and states hard non-negotiables including validation/ review gates. It loses only slightly on actionability and workflow clarity because the executable sequence lives in the referenced protocol rather than inline in SKILL.md itself.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, stating only the routing rule and non-negotiables without restating known concepts; every line earns its place.

5 / 5

Actionability

Gives concrete pointers (MUST read references/update-protocol.md, edit the named generator buildScripts/docs/seo/generate.mjs) and specific non-negotiables, but the executable step-by-step guidance itself lives in the referenced file rather than inline, leaving a minor gap.

4 / 5

Workflow Clarity

The body states validation principles (cross-family review required, never edit generated output) and routes to update-protocol.md, which carries the sequenced Steps 0-5 with explicit validation gates and a merge-gate checkpoint; the body alone has most checkpoints but relies on the reference for the full sequence.

4 / 5

Progressive Disclosure

A concise overview points one level deep to references/update-protocol.md, which routes to four sibling payload files; all five reference files exist and are clearly signaled, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

100%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 strong across all dimensions: it concretely states what the skill does, names the affected surfaces, and provides explicit, natural 'Use when...' triggers in maintainer voice. It is specific, complete, and clearly distinct from generic skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions (facts single-source-derive, framing audience-segment against an apex, CTAs governed) and enumerates the concrete surfaces (README, VISION, package.json, GitHub metadata, portal app, SEO build files), giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Clearly answers 'what' (repeatable protocol for coherent identity updates across ~30+ surfaces) and explicitly answers 'when' with a labeled 'Triggers: Use when...' clause carrying multiple concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural maintainer-voice triggers like 'update the identity / README / branding / how we describe Neo' alongside concrete change types (tagline, positioning, pillar story, CTAs, drifted fact) match phrases a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Scoped to a very specific niche (Neo's identity source-of-truth across named surfaces, anchored to ADR 0018) with triggers unlikely to fire for unrelated skills, so conflict risk is minimal.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
neomjs/neo
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.