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.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryScience & researchStars0
About this skill
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.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
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.
About this listing
Category
Science & research
Reported license
MIT
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI