Contacts Event

Record and organize a complex, multi-party, evolving situation involving a contact — a dispute, a scam, a crisis, a "two sides tell opposite stories" tangle, anything that takes several conversations to untangle. Produces a layered event dossier + a cause-and-effect chronology stored inside that contact's folder, kept separate from the clean contact profile that contacts-add maintains. The core is five-layer tagging (firsthand fact / secondhand / our hypothesis / commentary / to-confirm) which stops fact and inference from bleeding into each other, so you never act on a secondhand claim you mistook for firsthand. Trigger words: /contacts-event, log this situation, record the dispute, untangle this, event dossier, build a case file for X, the story keeps changing, the two sides don't match, 记录事件, 事件档案, 来龙去脉, 这摊事, 多方说法对不上, 反转, 罗生门. When a known contact gets pulled into a messy / multi-party / contested situation that needs ongoing tracking, use this even if the user doesn't name it — don't cram the analysis and to-dos into the clean contact profile, that's what this is for.

mkdir -p ~/.claude/skills/contacts-event
curl -L https://claudskills.com/skills/contacts-event/SKILL.md \
  -o ~/.claude/skills/contacts-event/SKILL.md

@misc{contacts-event-2026,
  author    = {Astralune-ai},
  title     = {Contacts Event [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/contacts-event/}
}