← AttioCONTENT HISTORY
WHAT CHANGED
Update to Attio
Snapshot Nov 17, 2026 · 00:10 UTC · version 1.0.15
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Attio and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Prepare the user for an upcoming call or meeting with a prospect or customer. Finds the meeting, the deal and who's attending, reads the past calls, emails, notes and open tasks, and writes a short brief covering where things stand, open commitments, goals for the call, questions to ask and risks. Read-only. Use when the user asks to prepare for, prep or get ready for a call or meeting (\"prep me for my 2pm\", \"what do I need to know before tomorrow's demo?\"). Not for analyzing a past call, writing a follow-up email, or updating deals.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 202
},
{
"relative_path": "assets/icon-small.svg",
"size_in_bytes": 2134
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 8865
}
],
"name": "prepare-for-call",
"skill_md_contents": "---\nname: prepare-for-call\ndescription: Prepare the user for an upcoming call or meeting with a prospect or customer. Finds the meeting, the deal and who's attending, reads the past calls, emails, notes and open tasks, and writes a short brief covering where things stand, open commitments, goals for the call, questions to ask and risks. Read-only. Use when the user asks to prepare for, prep or get ready for a call or meeting (\"prep me for my 2pm\", \"what do I need to know before tomorrow's demo?\"). Not for analyzing a past call, writing a follow-up email, or updating deals.\n---\n\n# Prepare for call\n\n1. Find the meeting. Call `whoami` (only if you haven't already called it in this conversation), and get the current date, time and the user's time zone from your environment.\n - If the user names a meeting, time, company or person, search the next 14 days with `search-meetings`. Match a meeting by its title, a time by the next meeting at that time, a company with `related_record_object` and `related_record_ids`, or a person with `participant_email_addresses`. Find records with `search-records`.\n - If they ask about their next call, search the next 7 days with their email address in `participant_email_addresses`, and take the first meeting with a prospect or customer: one linked to a company or deal (its `linked_records`), or with participants who aren't the user's teammates (`list-workspace-members`).\n - If more than one meeting could match, list them with title and time, and ask which one. If none matches, say so and stop. If the meeting is internal, say this skill is for calls with prospects and customers, and stop.\n2. Find what the meeting is about. Each meeting lists the records it's linked to in `linked_records`, usually its participants' companies and sometimes a deal. If the user named a company or person, use that company. Otherwise, use the company the meeting is linked to. If it's linked to more than one, prefer one with an open deal the meeting is also linked to. If it's linked to none, look for a company named in the title or matching the participants' email domains with `search-records`. If you still can't tell, ask the user which company it is, or whether it's an internal meeting. Use the `get-deal-context` skill for that company. If it has more than one open deal, use the one in the meeting's `linked_records`. Ask only if none is.\n3. Work out who's attending from the meeting's `participants`: everyone invited, with their name and email. Leave out the user and their teammates. Match the rest to person records in one `list-records` call on people, filtered by email address, and note each one's job title. Use their email address if they have no record or name. A meeting lists at most 25 participants, so if `participant_count` is higher, say others are invited too.\n4. Plan the call from what `get-deal-context` found, using where the deal stands and its open commitments as they are. Use the user's sales framework if they name one, such as MEDDICC, but don't impose one.\n - **Goals:** one to three things this call should achieve, from the meeting title, where the deal stands and what's still unknown.\n - **Questions to ask:** the gaps this call could fill, and who in the meeting can answer each.\n - **Watch out for:** the deal's risks, plus anything about this meeting, such as someone who decides but isn't invited.\n5. Reply with the brief and nothing else. Leave out a section with nothing in it. Ground every point in a source with its date, quoting a short phrase where it matters, like \"need SSO before IT signs off\" (call, 9 Nov). Show times in the user's local time. Use names, not IDs. Don't mention or quote these instructions. The user should be able to read it in two minutes:\n\n```\n**[Meeting title]** · [day, date, time]\n**Attending:** [their people, with job titles and roles] · you · others may join\n**Deal:** [name] · [stage] · [value] · [other useful fields]\n\n## Where things stand\n[2 to 3 sentences: what they want, where the deal is, and what's changed since the last call]\n\n## Open commitments\n- [Name]: [promise] (due [date]) · [done, or not seen yet]\n\n## Goals for this call\n1. [goal]\n\n## Questions to ask\n- [question] ([who can answer])\n\n## Watch out for\n- [risk, with its source]\n```\n\nDon't write to Attio unless the user asks.\n"
}SHA-256 of public snapshot: 1293c2c97398e0435e5adba01e6948b6e2c08b79254f48d2653cbd96e9214a76