| name | relationship-os |
| description | Use when working inside Knowledge_OS/relationship_os to import people, maintain a flat personal CRM, update relationship graph links, summarize durable facts onto person pages, or maintain schemas, templates, indexes, logs, scripts, and agent entry files. |
Relationship OS Skill
This is the shared project skill for Agent Skills IO, Claude Code, Codex, Hermes, and OpenClaw.
The canonical operating protocol is PROJECT.md; read it first. If any instruction conflicts with PROJECT.md, follow PROJECT.md and repair the stale text.
Activation
Use this skill when the user asks to:
- import a person or self-introduction
- create or update a personal CRM profile
- summarize a chat, meeting, or durable relationship update onto a person page
- decide who someone should connect with
- generate a follow-up note or outreach message based on existing person pages
- update relationship links in the Obsidian graph
- edit project schema, templates, lint checks, or agent entry files
IO Contract
import-person
Input:
- Raw self-introduction or a
raw/ file path.
- Optional context: city, source, or relationship.
Output:
- One file in
people/ following assets/person.md.
- Updated
index.md and log.md.
- Passing
bash scripts/lint.sh.
update-person
Input:
- Person name.
- Durable relationship facts, meeting summary, or next action.
- Optional related people that should be linked.
Output:
- Updated
people/姓名.md.
- Related person links updated when needed.
- Appended
log.md.
- Passing
bash scripts/lint.sh.
suggest-links
Input:
- Person name.
- Concrete need or follow-up goal.
Output:
- Recommendations written back to
## 可链接给谁, ## 关系记录, or ## 下一步 on the relevant person page.
- Optional outreach message in the relevant person page.
- Updated
log.md.
- Passing
bash scripts/lint.sh.
Standardization Rules
- Use
assets/raw.md and assets/person.md.
- Use enum values from
references/schema.md.
- Keep the system flat.
- Do not add new frontmatter fields unless
PROJECT.md, references/schema.md, and scripts/lint.js are updated together.
- Never fabricate private information. If a field is unknown, leave it empty or use an empty list.
- Do not store phone numbers, WeChat IDs, emails, or private addresses unless the user explicitly provides and asks to store them.
Matching Principles
- Match concrete
needs to concrete offers, city, relationship, and the links already visible in the graph.
- Prefer high-signal recommendations over long lists.
- Write the recommendation where the user will actually use it: on the relevant person page.
- Keep outreach messages specific, low-pressure, and honest.
References
- Schema:
.project/skills/relationship-os/references/schema.md
- Quality checklist:
.project/skills/relationship-os/references/quality-checklist.md
- Templates:
.project/skills/relationship-os/assets/
- Root protocol:
PROJECT.md
