Update to Attio
Snapshot Nov 17, 2026 · 00:10 UTC · version 1.0.15
Collection source: downloaded plugin package.
Instructions updated for draft-follow-up-email
Skill instructions — Now says: the meeting's participants (`search-meetings`), or else from their person records (`search-records`). 2. Check whether the user already followed up, unless...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 11, 2026 · 12:08 UTC
their person records (`search-records`). 2. Check whether the user already followed up. Call `search-emails-by-metadata` with the recipients' addresses since the call, and `get-email-content` for anything the user sent. If they already s...
Nov 17, 2026 · 00:10 UTC
the meeting's participants (`search-meetings`), or else from their person records (`search-records`). 2. Check whether the user already followed up, unless you already checked in this conversation. Call `search-emails-by-metadata` with t...
Supporting files
Nov 11, 2026 · 12:08 UTC
[{"relative_path":"references/ai-tells.md","size_in_bytes":3065}]
Nov 17, 2026 · 00:10 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":224},{"relative_path":"assets/icon-small.svg","size_in_bytes":2134},{"relative_path":"assets/icon.png","size_in_bytes":8865}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -5,9 +5,9 @@ # Draft follow-up email -1. Find the conversation and the people. Use the call the user names, or the notes they paste. To read a recording, use the `analyze-call-recording` skill, or `get-call-recording` if you can't. If it's unclear which call, ask. The recipients are the external people on the call: not workspace members (`list-workspace-members`), and not on the user's email domain. Get their email addresses from their person records (`search-records`). -2. Check whether the user already followed up. Call `search-emails-by-metadata` with the recipients' addresses since the call, and `get-email-content` for anything the user sent. If they already sent a follow-up, say so and stop, unless they want another. If the prospect wrote since, reply to that email instead. -3. Learn the user's voice from 3 to 5 emails they sent to external people. Use `search-emails-by-metadata` with `exclude_automated_participants`, then `get-email-content`, and check the user is the sender. Note their greeting, sign-off, usual length, formality, and habits such as lowercase, exclamation marks or dashes. If you find none, write plainly and say so. +1. Find the conversation and the people. Use the call the user names, or the notes they paste. To read a recording, use the `analyze-call-recording` skill, or `get-call-recording` if you can't. If it's unclear which call, ask. The recipients are the external people on the call: not workspace members (`list-workspace-members`), and not on the user's email domain. Get their email addresses from the meeting's participants (`search-meetings`), or else from their person records (`search-records`). +2. Check whether the user already followed up, unless you already checked in this conversation. Call `search-emails-by-metadata` with the recipients' addresses since the call, and `get-email-content` for anything the user sent. If they already sent a follow-up, say so and stop, unless they want another. If the prospect wrote since, reply to that email instead. If an email's content can't be retrieved, judge from its subject and snippet. If you still can't tell, say which email it was and ask before you draft. If you find nothing, say no follow-up was found in Attio, not that none was sent: searches only cover mailboxes connected to Attio. +3. Learn the user's voice from 3 to 5 emails they sent to external people, unless you already learned it in this conversation. Use `search-emails-by-metadata` with `exclude_automated_participants`, then `get-email-content`, and check the user is the sender. Note their greeting, sign-off, usual length, formality, and habits such as lowercase, exclamation marks or dashes. If you find none, or can't retrieve their content, write plainly and say you couldn't learn their style. Don't learn it from snippets: they're too short. 4. Write the email: - Open with every recipient's first name ("Hi Martin, James,"), then one sentence that thanks them and names something specific from the call. - Then short paragraphs, leaving out any the call didn't cover: their situation in their own words, answers to their questions, what the user will do and by when, what you need from them, and the next step with a date and who should attend. @@ -17,5 +17,5 @@ - Don't invent prices, discounts, dates, features, certifications, links or attachments. If something the user must supply is missing, put a short `[gap]` where it goes and list the gaps after the draft. - Leave out internal details: stage names, deal values, forecasts, notes and other customers. - Write in the prospect's language. Use a short subject that names the topic, or reply in their thread. -5. Reread the draft as the prospect, then edit it. Cut every sentence that carries no fact, answer or action, and any sentence that repeats the one before. Then remove the AI tells listed in [references/ai-tells.md](references/ai-tells.md), keeping anything the user writes in their own emails from step 3. +5. Load the `humanize-text` skill and follow it to edit the draft, with what you learned in step 3 as the writer's voice. Only if it isn't installed: cut every sentence that carries no fact, answer or action, then remove stock phrases, inflated words and any formatting the user doesn't use in their own emails. 6. Show the draft: To, Cc, Subject and body, then any gaps and open questions. Say it's ready to send from their own mail client. There is no tool to send email, so never claim it was sent. When another skill is building a preview, give it the draft and let that skill ask.
Full technical diff · 2 changed fields
changed /included_files
[
{
"relative_path": "references/ai-tells.md",
"size_in_bytes": 3065
}
][
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 224
},
{
"relative_path": "assets/icon-small.svg",
"size_in_bytes": 2134
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 8865
}
]changed /skill_md_contents
"---\nname: draft-follow-up-email\ndescription: Draft a follow-up email after a call or meeting, in the user's own voice, from what was actually said. Checks the user hasn't already followed up, learns their greeting, sign-off and tone from emails they've sent, and uses only facts from the call and Attio. Drafts only, never sends. Use when the user asks for a follow-up, recap or next-steps email to a prospect or customer (\"write a follow-up to Leif from today's call\"), or when another skill needs one. Not for cold outreach, sequences, bulk email or internal updates.\n---\n\n# Draft follow-up email\n\n1. Find the conversation and the people. Use the call the user names, or the notes they paste. To read a recording, use the `analyze-call-recording` skill, or `get-call-recording` if you can't. If it's unclear which call, ask. The recipients are the external people on the call: not workspace members (`list-workspace-members`), and not on the user's email domain. Get their email addresses from their person records (`search-records`).\n2. Check whether the user already followed up. Call `search-emails-by-metadata` with the recipients' addresses since the call, and `get-email-content` for anything the user sent. If they already sent a follow-up, say so and stop, unless they want another. If the prospect wrote since, reply to that email instead.\n3. Learn the user's voice from 3 to 5 emails they sent to external people. Use `search-emails-by-metadata` with `exclude_automated_participants`, then `get-email-content`, and check the user is the sender. Note their greeting, sign-off, usual length, formality, and habits such as lowercase, exclamation marks or dashes. If you find none, write plainly and say so.\n4. Write the email:\n - Open with every recipient's first name (\"Hi Martin, James,\"), then one sentence that thanks them and names something specific from the call.\n - Then short paragraphs, leaving out any the call didn't cover: their situation in their own words, answers to their questions, what the user will do and by when, what you need from them, and the next step with a date and who should attend.\n - Keep it to their usual length, and never over 300 words. Use bullets only to recap three or more separate topics.\n - Use no headings, bold text or template labels.\n - Commit the user only to what they offered on the call. No \"I'll look into…\" or \"I'll put together…\" they didn't say. If the answer to a question is in the call, Attio or what the user told you, put it in. If not, list the question for the user after the draft instead of promising an answer.\n - Don't invent prices, discounts, dates, features, certifications, links or attachments. If something the user must supply is missing, put a short `[gap]` where it goes and list the gaps after the draft.\n - Leave out internal details: stage names, deal values, forecasts, notes and other customers.\n - Write in the prospect's language. Use a short subject that names the topic, or reply in their thread.\n5. Reread the draft as the prospect, then edit it. Cut every sentence that carries no fact, answer or action, and any sentence that repeats the one before. Then remove the AI tells listed in [references/ai-tells.md](references/ai-tells.md), keeping anything the user writes in their own emails from step 3.\n6. Show the draft: To, Cc, Subject and body, then any gaps and open questions. Say it's ready to send from their own mail client. There is no tool to send email, so never claim it was sent. When another skill is building a preview, give it the draft and let that skill ask.\n"
"---\nname: draft-follow-up-email\ndescription: Draft a follow-up email after a call or meeting, in the user's own voice, from what was actually said. Checks the user hasn't already followed up, learns their greeting, sign-off and tone from emails they've sent, and uses only facts from the call and Attio. Drafts only, never sends. Use when the user asks for a follow-up, recap or next-steps email to a prospect or customer (\"write a follow-up to Leif from today's call\"), or when another skill needs one. Not for cold outreach, sequences, bulk email or internal updates.\n---\n\n# Draft follow-up email\n\n1. Find the conversation and the people. Use the call the user names, or the notes they paste. To read a recording, use the `analyze-call-recording` skill, or `get-call-recording` if you can't. If it's unclear which call, ask. The recipients are the external people on the call: not workspace members (`list-workspace-members`), and not on the user's email domain. Get their email addresses from the meeting's participants (`search-meetings`), or else from their person records (`search-records`).\n2. Check whether the user already followed up, unless you already checked in this conversation. Call `search-emails-by-metadata` with the recipients' addresses since the call, and `get-email-content` for anything the user sent. If they already sent a follow-up, say so and stop, unless they want another. If the prospect wrote since, reply to that email instead. If an email's content can't be retrieved, judge from its subject and snippet. If you still can't tell, say which email it was and ask before you draft. If you find nothing, say no follow-up was found in Attio, not that none was sent: searches only cover mailboxes connected to Attio.\n3. Learn the user's voice from 3 to 5 emails they sent to external people, unless you already learned it in this conversation. Use `search-emails-by-metadata` with `exclude_automated_participants`, then `get-email-content`, and check the user is the sender. Note their greeting, sign-off, usual length, formality, and habits such as lowercase, exclamation marks or dashes. If you find none, or can't retrieve their content, write plainly and say you couldn't learn their style. Don't learn it from snippets: they're too short.\n4. Write the email:\n - Open with every recipient's first name (\"Hi Martin, James,\"), then one sentence that thanks them and names something specific from the call.\n - Then short paragraphs, leaving out any the call didn't cover: their situation in their own words, answers to their questions, what the user will do and by when, what you need from them, and the next step with a date and who should attend.\n - Keep it to their usual length, and never over 300 words. Use bullets only to recap three or more separate topics.\n - Use no headings, bold text or template labels.\n - Commit the user only to what they offered on the call. No \"I'll look into…\" or \"I'll put together…\" they didn't say. If the answer to a question is in the call, Attio or what the user told you, put it in. If not, list the question for the user after the draft instead of promising an answer.\n - Don't invent prices, discounts, dates, features, certifications, links or attachments. If something the user must supply is missing, put a short `[gap]` where it goes and list the gaps after the draft.\n - Leave out internal details: stage names, deal values, forecasts, notes and other customers.\n - Write in the prospect's language. Use a short subject that names the topic, or reply in their thread.\n5. Load the `humanize-text` skill and follow it to edit the draft, with what you learned in step 3 as the writer's voice. Only if it isn't installed: cut every sentence that carries no fact, answer or action, then remove stock phrases, inflated words and any formatting the user doesn't use in their own emails.\n6. Show the draft: To, Cc, Subject and body, then any gaps and open questions. Say it's ready to send from their own mail client. There is no tool to send email, so never claim it was sent. When another skill is building a preview, give it the draft and let that skill ask.\n"
Full snapshot data
{
"description": "Draft a follow-up email after a call or meeting, in the user's own voice, from what was actually said. Checks the user hasn't already followed up, learns their greeting, sign-off and tone from emails they've sent, and uses only facts from the call and Attio. Drafts only, never sends. Use when the user asks for a follow-up, recap or next-steps email to a prospect or customer (\"write a follow-up to Leif from today's call\"), or when another skill needs one. Not for cold outreach, sequences, bulk email or internal updates.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 224
},
{
"relative_path": "assets/icon-small.svg",
"size_in_bytes": 2134
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 8865
}
],
"name": "draft-follow-up-email",
"skill_md_contents": "---\nname: draft-follow-up-email\ndescription: Draft a follow-up email after a call or meeting, in the user's own voice, from what was actually said. Checks the user hasn't already followed up, learns their greeting, sign-off and tone from emails they've sent, and uses only facts from the call and Attio. Drafts only, never sends. Use when the user asks for a follow-up, recap or next-steps email to a prospect or customer (\"write a follow-up to Leif from today's call\"), or when another skill needs one. Not for cold outreach, sequences, bulk email or internal updates.\n---\n\n# Draft follow-up email\n\n1. Find the conversation and the people. Use the call the user names, or the notes they paste. To read a recording, use the `analyze-call-recording` skill, or `get-call-recording` if you can't. If it's unclear which call, ask. The recipients are the external people on the call: not workspace members (`list-workspace-members`), and not on the user's email domain. Get their email addresses from the meeting's participants (`search-meetings`), or else from their person records (`search-records`).\n2. Check whether the user already followed up, unless you already checked in this conversation. Call `search-emails-by-metadata` with the recipients' addresses since the call, and `get-email-content` for anything the user sent. If they already sent a follow-up, say so and stop, unless they want another. If the prospect wrote since, reply to that email instead. If an email's content can't be retrieved, judge from its subject and snippet. If you still can't tell, say which email it was and ask before you draft. If you find nothing, say no follow-up was found in Attio, not that none was sent: searches only cover mailboxes connected to Attio.\n3. Learn the user's voice from 3 to 5 emails they sent to external people, unless you already learned it in this conversation. Use `search-emails-by-metadata` with `exclude_automated_participants`, then `get-email-content`, and check the user is the sender. Note their greeting, sign-off, usual length, formality, and habits such as lowercase, exclamation marks or dashes. If you find none, or can't retrieve their content, write plainly and say you couldn't learn their style. Don't learn it from snippets: they're too short.\n4. Write the email:\n - Open with every recipient's first name (\"Hi Martin, James,\"), then one sentence that thanks them and names something specific from the call.\n - Then short paragraphs, leaving out any the call didn't cover: their situation in their own words, answers to their questions, what the user will do and by when, what you need from them, and the next step with a date and who should attend.\n - Keep it to their usual length, and never over 300 words. Use bullets only to recap three or more separate topics.\n - Use no headings, bold text or template labels.\n - Commit the user only to what they offered on the call. No \"I'll look into…\" or \"I'll put together…\" they didn't say. If the answer to a question is in the call, Attio or what the user told you, put it in. If not, list the question for the user after the draft instead of promising an answer.\n - Don't invent prices, discounts, dates, features, certifications, links or attachments. If something the user must supply is missing, put a short `[gap]` where it goes and list the gaps after the draft.\n - Leave out internal details: stage names, deal values, forecasts, notes and other customers.\n - Write in the prospect's language. Use a short subject that names the topic, or reply in their thread.\n5. Load the `humanize-text` skill and follow it to edit the draft, with what you learned in step 3 as the writer's voice. Only if it isn't installed: cut every sentence that carries no fact, answer or action, then remove stock phrases, inflated words and any formatting the user doesn't use in their own emails.\n6. Show the draft: To, Cc, Subject and body, then any gaps and open questions. Say it's ready to send from their own mail client. There is no tool to send email, so never claim it was sent. When another skill is building a preview, give it the draft and let that skill ask.\n"
}SHA-256 of public snapshot: 97c9f7c5c20a437c593af7cc53fb093691460d0d2c7447f1b71e3135d35b3bb6