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.
70
86%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Neo Identity Update Skill
Neo's identity is distributed across ~30+ surfaces; editing one (e.g. README) leaves machine-facing JSON, build-generated SEO files, external platform settings, and CTA targets drifting silently. Before changing ANY identity surface (tagline, description, keywords, pillar story, CTA / next-step door, or a drifted fact like version / MCP-server-count / Node-req), you MUST read .agents/skills/neo-identity-update/references/update-protocol.md and follow it — it routes to the surface inventory, facts ledger, framing-governance payload, and CTA-governance payload.
Non-negotiables: FACTS converge to one source (derive/coherence-check the rest); FRAMING stays audience-segmented against the README apex (escalate contradictions, never find-replace); ACTIONS / CTAs keep pitches from dead-ending and surface proof without inventing business-owned offer content; never edit build-generated output (edit the generator buildScripts/docs/seo/generate.mjs); every identity-surface PR needs a cross-family review; never name a client/partner/customer. Foundation: ADR 0018.
- Repository
- neomjs/neo
- Commit
c1ce853
- Last updated
- First committed
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.