Skip to main content

Acquaintance

Run a short opt-in get-to-know-you ritual.

Skill metadata​

SourceBundled (installed by default)
Pathskills/memory/acquaintance
Version1.0.0
AuthorVibeOS
LicenseMIT
Platformslinux, macos, windows
Tagsmemory, user, onboarding, profile
Related skillsepisodic-diary, archival-recall

Reference: full SKILL.md​

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Acquaintance Skill

Help the user build a compact User profile (USER.md) so later sessions feel personal — without reading email, calendar, or the whole home directory.

When to Use​

  • User says «познакомимся», «remember me», «update my profile», or /acquaintance.
  • New profile with empty USER.md.
  • User wants to redo preferences after a month.

Do not use this skill to scan disk or connected accounts. Machine Portrait is a separate opt-in product.

Prerequisites​

  • Built-in memory enabled (memory.user_profile_enabled / memory tool).
  • Optional CLI: vibeos memory acquaint.

How to Run​

Preferred (deterministic): guide the user through CLI or Desktop button:

vibeos memory acquaint --schema          # question list
vibeos memory acquaint # interactive
vibeos memory acquaint --answers-json answers.json --json

In chat: ask at most 5–8 light questions (skip allowed). After each durable answer, save with memory tool target="user" — compact lines only (Name: …, Tone / style: …). Decline / stop anytime.

Quick Reference​

FieldExample USER line
NameName: Alex
LanguageLanguage: Russian
ToneTone / style: short bullets
FocusFocus: coding and deploy ops
ProjectsActive projects: VibeOS desktop
RulesStanding preferences: never force-push main

Procedure​

  1. Offer — do not assume. Explain they can skip or stop.
  2. Ask the questionnaire (see CLI --schema); one question at a time is fine.
  3. Persist with memory(target="user") — no silent account lookups.
  4. If they say «always/never/from now on», treat as preference (may also land in proposed_core via correction detect).
  5. Summarize what was saved; point to Settings → Memory browser to edit.

Pitfalls​

  • Do not write secrets into USER.
  • Do not dump long bios — USER budget is small; details go to Archival.
  • Profiles are islands — no cross-profile merge.
  • Mid-session writes use hot facts; frozen prompt updates next session.

Verification​

  • Clean profile → ≥5 USER entries after ritual (UF3).
  • User can edit/delete in Memory browser.
  • Declining mid-flow leaves USER unchanged for unanswered questions.