neo-identity-update
Skill11 starsChanged yesterdayMITView on GitHub
Protocol for coherent Neo identity updates across all surfaces; use when changing taglines/positioning/descriptions/keywords/pillars/CTAs, asked to update identity/README/branding, framing is outgrown, or facts drift.
In this repository39 other files it gives its agents.
- architecture-pre-flightSkill
- blocked-task-stateSkill
- blog-postSkill
- context-recoverySkill
- create-skillSkill
- design-sweepSkill
- epic-createSkill
- epic-resolutionSkill
- epic-reviewSkill
- goal-scopingSkill
- guide-authoringSkill
- hostile-content-quarantineSkill
- ideation-sandboxSkill
- identity-firewallSkill
- industry-friction-radarSkill
- lane-intentSkill
- lead-roleSkill
- memory-miningSkill
- neo-app-authoringSkill
- neural-linkSkill
- overviewSkill
- peer-namingSkill
- peer-roleSkill
- post-review-pickupSkill
- pr-reviewSkill
- pull-requestSkill
- release-notesSkill
- self-repairSkill
- session-sunsetSkill
- structural-pre-flightSkill
- tech-debt-radarSkill
- ticket-createSkill
- ticket-intakeSkill
- ticket-triageSkill
- turn-memory-pre-flightSkill
- unit-testSkill
- update-roadmapSkill
- video-createSkill
- whitebox-e2eSkill
The file
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

