Neo Identity Update

Name: Neo Identity Update
Author: neomjs

ASecurity

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 / ...

11 stars
0 votes
0 copies
1 view
Added September 19, 2026

ai-agentsgonodegit

Works with

Security analysis

A100/100

Pro scans all 6 files and shows the line behind each finding

Scanned September 19, 2026

npx -y skills add neomjs/neo-agent-skills --skill neo-identity-update --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Neo Identity Update?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Neo Identity Update

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/neomjs-neo-identity-update/badge)](https://www.skillsdirectory.com/skills/neomjs-neo-identity-update)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: neo-identity-update
description: "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."
---

# 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](https://github.com/neomjs/neo/blob/dev/learn/agentos/decisions/0018-neo-identity-source-of-truth-model.md).