· 3 observations
Technical updates · 1
Package or technical metadata updated
View technical comparison →Attio v1.0.15
Build pipeline, grow accounts
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Prep me for my next call
Developer declarations; not independently tested. Listing last checked Nov 18, 2026. Package observed Nov 18, 2026.
From the marketplace listing
Connect your Attio workspace to build pipeline, advance deals and grow accounts. Search, create and update records, and prepare for meetings.
Language: English · Automatically detected from descriptions.
· 3 observations
Package or technical metadata updated
View technical comparison →· 10 observations
Full description changed from “Sets up the Attio plugin for a new user. Use when the user installs the Attio plugin or asks how to get started with Attio.” to “Get a new user started with the Attio plugin. Checks Attio is connected, reads their workspace and does something useful straight away, such as a short...
View comparison →Supporting files updated; open the comparison for details. Skill instructions changed from “`list-activities`, paging until there are no more. 2. Find the pipelines. A pipeline is usually an object with a status attribute. Some workspaces have...” to “`list-activities` in parallel, paging until there are no more. If...
View comparison →Supporting files updated; open the comparison for details. Skill instructions changed from “value, owner, close date and next step fields, whatever they're called. Note the stage order. Stages named won, lost or closed are closed. If you can't tell...” to “value and owner fields, and any other useful fields...
View comparison →Supporting files updated; open the comparison for details. Skill instructions changed from “speaker). Skip meetings where every participant is internal. If the user pastes notes, treat each set of notes as a call. If a meeting has no recording and...” to “speaker), in parallel. `search-meetings` lists each meeting's...
View comparison →Supporting files updated; open the comparison for details. Skill instructions changed from “their person records (`search-records`). 2. Check whether the user already followed up. Call `search-emails-by-metadata` with the recipients' addresses since...” to “the meeting's participants (`search-meetings`), or else...
View comparison →Full description changed from “task per record, covering everything to do next, for the right person,” to “open task per person on each record, covering everything they do next,”. Supporting files updated; open the comparison for details. Skill instructions changed from “task per record, covering everything to do...
View comparison →Supporting files updated; open the comparison for details. Skill instructions changed from “recording could match, list the candidates with title, date and participants, and ask which one. Metadata search returns no titles, so get them from...” to “call could match, list the candidates with title and date, and ask...
View comparison →Brand color added: “#1D1E20”. Capabilities updated; open the comparison for details. Default prompt added: “Prep me for my next call”. Default prompts updated; open the comparison for details. 23 more changes in the comparison.
View comparison →Package or technical metadata updated
View technical comparison →· 3 observations
Full description changed from “Attio connects ChatGPT directly to your CRM workspace, letting you manage customer relationships through natural conversation. Search and filter contacts,...” to “Build pipeline, advance deals, and grow accounts.”. Default prompt removed: “Find the latest notes and next steps in...
View comparison →Full description changed from “Attio connects ChatGPT directly to your CRM workspace, letting you manage customer relationships through natural conversation. Search and filter contacts,...” to “Build pipeline, advance deals, and grow accounts.”. Default prompt removed: “Find the latest notes and next steps in...
View comparison →Package or technical metadata updated
View technical comparison →· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →---
name: analyze-call-recording
description: Analyze a recorded call in Attio. Finds the call recording, reads the full transcript, classifies the call (discovery, demo, evaluation check-in, negotiation or other) and writes an analysis suited to that type. Use whenever the user asks to analyze, review, debrief or summarize a call or meeting recording, or wants feedback on how a call went, even if they only name the meeting, the person or the company they spoke to.
---
# Analyze call recording
## 1. Find the recording
In Attio, a meeting is a calendar event and a call recording is a transcript attached to a meeting. A meeting can have no recording, one recording or several (several is an edge case, e.g. when the call recorder leaves and rejoins). `get-call-recording` needs both `meeting_id` and `call_recording_id`.
| The user gives | Do this |
| ----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| An Attio link or both IDs | Use the two UUIDs directly |
| A meeting title | `search-call-recordings-by-metadata` with `meeting_title_query` |
| A person or company | `search-records` for its record ID, then `search-call-recordings-by-metadata` with `speaker_person_record_ids` (person) or `related_record_ids` (company, deal) |
| A topic ("the call where they raised security") | `semantic-search-call-recordings` |
| "My last call" | `whoami` (skip if you already know who the user is), then `search-call-recordings-by-metadata` with `speaker_workspace_member_ids` |
| A date | `search-meetings`, then use its `call_recording_ids` |
Add a time range whenever the user gives one. Results are newest first.
If more than one call could match, list the candidates with title and date, and ask which one. Metadata search returns no titles, so get them from `search-meetings` with the same filters and time range. Analyzing the wrong call wastes more of the user's time than one question does.
If the meeting has no recording, say so. Calls logged from a dialer are activity records, not call recordings, and this skill does not cover them.
## 2. Read the full transcript
Fetch the recording with `get-call-recording` and read all of it before you form a view. If the meeting has more than one recording, read them all as one call, and say which part each quote comes from. The call type often becomes clear late, for example when pricing comes up near the end.
- Analyze only recordings with `status: finished`. If it's `preparing` or `in-progress`, tell the user the recording isn't finished yet and to try again later. If it's `failed`, say the recording failed. Then stop.
- Work out which speakers are on the user's side (`whoami` and `list-workspace-members`, unless you already have them) and which are external. `search-meetings` lists who was invited, but only the transcript shows who spoke. Use the transcript's speakers, and the participants for anyone invited who didn't speak.
- Transcription garbles names of people, companies and products. Infer the intended word from contePreview of the first 4,000 characters. Read full instructions →
Referenced files: 8 — file references are metadata, not package contents.
---
name: create-follow-up-task
description: Create the follow-up task in Attio for one deal, company or person. One open task per person on each record, covering everything they do next, due when they next have to act, and without duplicating an open task. Writes only after the user confirms. Use when the user asks to add a task, reminder or follow-up ("remind me to send Leif the quote on Friday", "add a task to chase Basepoint"), or when another skill needs a follow-up task. A workflow that needs tasks for several records uses this once per record.
---
# Create follow-up task
Each person has at most one open follow-up task on a record, covering everything they do next on it.
1. Work out the next actions, such as sending something, calling someone or chasing a decision:
- Anything the user promised.
- Preparation for a booked call, due the day before it.
- If the prospect pushed their decision to a later date and nothing is booked, re-engaging two to three weeks before that date. If that's within the next week, it's halfway between today and their date.
If there's nothing to do, or the only next step is a booked call with nothing to prepare, say so and stop.
2. Work out the due date: the day they have to act, not the day it's mentioned. With several actions, it's the first one's. Get today's date and the user's time zone from your environment.
- "Early next week" is Monday, "end of the week" is Friday, "next week" with no day is Tuesday, and a named day is the next one.
- Chasing a decision that's still on is two working days before the decision date.
- Move a date you work out off weekends to the Friday before, and out of the end-of-year break (24 December to 1 January) to the last working day before. Keep a date the user gives.
- If you can't tell when, ask. Never leave a task undated.
3. Find the record: the deal if there is one, otherwise the company, otherwise the person. Use `search-records`, and ask if more than one matches. A deal that's a list entry can't be linked, so use the record the entry is on, such as its company. Assign the task to the user (call `whoami` only if you haven't already) unless they name a teammate. Find a teammate with `list-workspace-members`.
4. Check the record's open tasks with `list-tasks` (`linked_record_object`, `linked_record_id`, `is_completed: false`), paging with `offset`, unless you already read all of its open tasks in this conversation. Leave tasks assigned to anyone other than the assignee alone unless the user asks: don't change, replace or mark them done. Mention any that cover the same actions, and leave those actions out of the new task. If the assignee already has an open task on the record, don't add a second:
- If they have more than one open task here and together they cover the actions, say so and stop. Don't merge them.
- If it's right, say so and stop.
- If it covers the actions but the date is wrong, change it.
- Otherwise, offer to replace it with one task covering its actions that are still to do and the new ones. Task wording can't be edited, so replacing means marking it done and creating the new task. The user can keep both instead.
5. Write the task. If the message gives you the wording, use it, adding the company name at the start if it's missing. Otherwise, start with the company name, then each action as a verb and exactly what and for whom, under 15 words each and separated by semicolons. Name the thing, such as "the SSO answer and 120-seat quote".
6. Show it and ask. Include the Replaces line only when offering to replace an open task, and the Updates line only when changing one's date or assignee:
```
**Task:** [Company] — [actions]
**Due:** [day, date] · **For:** [you, or the teammate's name] · **Linked to:** [record]
**Replaces:** "[open task]" (will be marked done, or say to keep both)
**Updates:** "[open task]" (changes its [date or assignee], no new task)
Create it?
```
If this task is part of a bigger previePreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
---
name: design-data-model
description: Design and create objects, attributes, relationships, lists and views in the user's Attio workspace, building on the standard objects and writing only after the user approves the whole draft. Use when the user asks how to store, organize or set up something in Attio, or asks to add, rename, edit or remove an object, attribute, field, option, relationship, stage, list or pipeline ("add a Renewal date to Companies", "how should we track our partners?", "enable Deals"). Not for creating or updating records, changing existing views, or moving data.
---
# Design data model
Every change here affects the whole workspace, and an attribute is hard to remove once people fill it in. Model what the user's revenue team tracks, not how their product works inside. A lean model built on the standard objects beats a large one, and a short question beats a confidently wrong model.
You can enable Deals, Users and Workspaces, and create custom objects, attributes on objects (including status attributes with their stages), relationships, lists, list entries and views. You can't edit, rename or archive anything, add or change the options or stages of an existing attribute, or create attributes on a list. When the model needs one of these, say you can't do it here and that the user can do it in Attio, and draft the rest, if anything is left.
1. **Check what exists.** List the objects (`list-objects`) and lists (`list-lists`), and the attributes of each object the request is likely to touch and of its lists (`list-attribute-definitions`, `list-list-attribute-definitions`), paging until there are no more. For one change to an object the user named, that object and its lists are enough. Read attributes, not records or list entries, unless you're offering to add records to a new list. Check both the object and its lists before you say an attribute doesn't exist. If Deals, Users or Workspaces isn't in the objects list, it's disabled, and using it means enabling it. People and Companies already have email addresses, domains and interaction dates, and Deals has a name, stage, owner, value, company and people. If an attribute with the same meaning already exists, such as a Status when the user asks for a Stage, tell the user and ask whether to use it before you draft a new one.
2. **Work out what they're asking for.**
- **One change, or a few the user named**, such as "add a Renewal date to Companies": check them against steps 3 to 5, reading a reference a step names if you need it, and draft. Ask first only if the answer changes its type or which object it goes on, such as whether a Partner manager is a teammate or a contact.
- **A process or a new workspace**, such as "how should we track partners?" or "set us up": read `references/setups.md`, `references/objects.md`, `references/relationships.md` and `references/questions.md`, and `references/lists.md` if the team runs a process on its records. Work out the sales motion, what the team tracks, and the facts they need about each. In a new workspace, plan the whole model. In one already in use, build on what's there, and mention once what you'd have modeled differently. Before drafting:
- If you can search the web, first offer to read their company's website. Use the company they named, or their email domain (`whoami`) if it fits what they've told you. If neither gives you a website, ask for it.
- Once you've read it, or they've declined, ask the questions it leaves open, in one message, as `references/questions.md` describes. If you have a tool for asking questions with options, use it.
3. **Choose the objects.** Use the standard objects first: an organization is a company, a contact is a person, a product user or seat is a user, and a customer's account in the product is a workspace. If a group is only a label, mark it with a select, or a multi-select if a record can be in more than one group, such as a partner that's also a customer. Make a cusPreview of the first 4,000 characters. Read full instructions →
Referenced files: 9 — file references are metadata, not package contents.
---
name: draft-follow-up-email
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.
---
# 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 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.
- Keep it to their usual length, and never over 300 words. Use bullets only to recap three or more separate topics.
- Use no headings, bold text or template labels.
- 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.
- 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. 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 clienPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
--- name: end-of-day description: Update the user's Attio deals from a day of sales calls. Reads each call, proposes deal updates, at most one follow-up task per deal and a follow-up email draft, then writes after the user confirms. Use when the user says "end of day update", "eod", "update my deals from today's calls" or "process my calls", including for another day such as "yesterday's calls", or when they describe a call and want the deal updated. Not for logging a single call as an activity, reporting on the pipeline, or writing one email on its own. --- # End of day 1. Call `whoami` (only if you haven't already called it in this conversation). Get the current date, time and the user's time zone from your environment. If you can't, ask. Use the day the user names, or today. A participant is internal when they're a workspace member (`list-workspace-members`) or their email domain matches the user's. 2. Find that day's calls with `search-meetings` (in the user's time zone) and `search-call-recordings-by-metadata` (the user as a speaker), in parallel. `search-meetings` lists each meeting's participants and linked records, but not who spoke, so you'll check who spoke when you read each transcript in step 5. If the user pastes notes, treat each set of notes as a call. If a meeting has no recording and no notes, list it under Skipped in the preview. If there are no calls, say so and stop. 3. If there are calls, load the `create-follow-up-task`, `draft-follow-up-email` and `humanize-text` skills now. Don't follow them yet: you'll use them in step 9. 4. Use the `get-sales-context` skill to find the pipelines, their stages and their fields, unless it has already run in this conversation. Then get the user's open records in each sales pipeline with `list-records` (for an object) or `list-records-in-list` (for a list), filtered by owner, skipping closed stages. Don't show either's output. 5. For each call with only notes, use the notes. For each recording, use the `analyze-call-recording` skill with the meeting and recording IDs, to read the full transcript and analyze the call. Don't show its analysis, and don't save the note or tasks it offers. If you can't use it, read the transcript with `get-call-recording`. Find the need, next steps with dates, the decision date, money and risks, each with a quote, and who spoke on each side. Keep only these facts for each call, not the transcript or the analysis. If you can run subagents, analyze each call in its own subagent and have it return only these facts. Then: - A recording whose status isn't `finished` isn't ready. List it under Skipped in the preview. - If the transcript is under two minutes, or only internal people spoke at a meeting with a prospect or customer, it may be a no-show. Ask before treating it as a call. A meeting is with a prospect or customer if it's linked to a company or deal (its `linked_records`), or has participants who aren't the user's teammates (`list-workspace-members`). - Skip a call as internal only when only internal people spoke and the meeting isn't with a prospect or customer, such as a stand-up or pipeline review. - A call the user didn't speak on gets a read-only summary: no updates, tasks or email. The speaker search matches calls the user was invited to, not ones they spoke on, so check the transcript for their lines. - Combine calls with the same company into one update and one email. 6. Find each call's deal. If people from more than one external company were on the call, use the company it was mainly about, and name the others in your reply. Take the company and any deal from the meeting's `linked_records`. If it has none, work out the company from the meeting title and the external participants' email domains (`search-records`). Match it to the user's open deals from step 4. If none matches, check the company's records in each pipeline: its linked deals, and its entries in each list (`list-records-in-list` filtered by `parent_rec
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
---
name: get-customer-feedback
description: Gather customer feedback from Attio, either across every customer for one product feature or topic, or everything one customer has said. Searches call recordings, emails and notes, and reports who asked for what, in their own words, how strongly and how recently. Read-only. Use when the user asks how in demand a feature is, who has asked for it or whether it's worth building ("how many accounts want SSO?", "what are customers saying about reporting?"), or what feedback, feature requests or complaints one company or deal has given ("what has Acme asked us for?"). Not for analyzing a single call, catching up on where a deal stands, or logging new feedback.
---
# Get customer feedback
Feedback is what a customer or prospect says about the product: a feature they ask for, something missing or broken, a complaint, a comparison with a competitor, praise, or a reason they didn't buy or might leave. Look for it only in call recordings, emails and notes, not in other objects, lists or deal fields.
Feedback comes from the customer's side. Teammates are the people `list-workspace-members` returns, and anyone on their email domain. A teammate explaining a limitation or promising a date is not feedback, though their email often quotes a customer message that is.
1. Get the current date from your environment, and work out what the user is asking:
- **A feature or topic across customers** ("how many accounts want better permissions?"): follow steps 2 to 5.
- **One customer** ("what feedback has Acme given?"): follow steps 6 to 8.
- Both ("what has Acme said about permissions?"): follow steps 6 to 8 and keep only that topic.
- If you can't tell which feature or which customer, ask.
## A feature or topic across customers
2. Write three or four search phrasings. Search matches meaning, and customers describe their situation, not the feature, so a bare keyword like "permissions" finds little. Write each one as a customer saying what they want, such as "sales reps should only see their own deals". A complaint about the product, such as "the permissions aren't granular enough", mostly finds teammates explaining the limitation.
3. Search with each phrasing, and count each call, email thread and note once. The same email can come back from more than one mailbox.
- **Calls:** `semantic-search-call-recordings`, which returns the matching part of each transcript with its speaker.
- **Emails:** `semantic-search-emails` with `include_emails_of_others` and `exclude_automated_participants` set to true.
- **Notes:** `semantic-search-notes`.
4. Check each result and find its company. Keep it only if someone on the customer's side asks for the thing, misses it or complains about it.
- **Calls:** the matching part is usually enough to judge. Get the titles and dates of the calls you keep with `render-meetings`, which also shows the user that list. The company is the one the title names. Otherwise find the customer speaker in people (`search-records`) and use their company.
- **Emails:** the search returns Attio's summary, which is never the customer's wording. For every company you quote or rate above _mentioned_, read the customer's own email with `get-email-content`. Don't drop a thread because the result is a teammate's reply: open it, because the customer's message is quoted underneath. The company is the one that owns the customer's domain.
- **Notes:** read each one whose title looks relevant with `get-note-body`, skipping notes written to prepare for a meeting. The company is the note's parent record, or that record's company if it's a deal or a person.
- To look up many records at once, use one `query-particle-sql` query that selects only the columns you need. A whole company record is very large.
- A result whose company you can't find counts once, as "Unknown ([call title], [date])". Never name a row after a speaker.
5. Weigh what you kept. A company counts once, hPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
---
name: get-deal-context
description: Gather what's happening on one deal in Attio. Reads the deal's fields, its recent calls, emails and notes, open tasks and upcoming meetings, and works out where it stands, who's involved, what each side has promised, the risks and what's still unknown. Read-only. Use when the user asks what's going on with a deal, company or account ("catch me up on this deal", "where are we with the account?"), or when another skill needs a deal's history. Not for listing the whole pipeline, analyzing a single call, or updating deals.
---
# Get deal context
1. Find the deal. Call `whoami` (only if you haven't already called it in this conversation), and get the current date and the user's time zone from your environment. If the `get-sales-context` skill hasn't already run in this conversation, use it to find the pipelines, their stages and their fields. Skip its usage reports.
- Find the record the user names with `search-records`. If it's a deal, use it, even if it's closed. For a person, use their company.
- For a company, find its open deals in each pipeline: its linked deals, and its entries in each list (`list-records-in-list` filtered by `parent_record`). Skip closed ones, such as won, lost, churned or renewed.
- If more than one deal is open, ask which, unless the task already says. If none is, say so and gather the company's history alone.
2. Read the deal's stage, value, owner and other useful fields, as `get-sales-context` found them. Note the people linked to the deal, with their job titles, reading them together with `get-records-by-ids`.
3. Read the history from the last 90 days, keeping facts with their date and source. Run searches that don't depend on each other in parallel, then read the recordings, emails and notes they return in parallel too. Page through results until you have what each step asks for. For emails, keep going while the search says there are more, even if a page comes back short or empty.
- **Calls:** `search-call-recordings-by-metadata` twice, with the deal and then the company as `related_record_ids`. Combine the results, take the three most recent meetings, counting each meeting once, and read every finished recording of them with `get-call-recording`.
- **Emails:** `search-emails-by-metadata` with the company's domain over the last 30 days. Read up to five of the latest with `get-email-content`. If an email's content can't be retrieved, use its subject and snippet.
- **Notes:** `search-notes-by-metadata` for the deal and the company, then `get-note-body` for up to three of the latest.
- **Tasks:** `list-tasks` for all open tasks linked to the deal or the company.
- **Upcoming meetings:** `search-meetings` for the next 30 days with `related_record_object` and `related_record_ids` set to the deal, then the company if that finds nothing. Note who's invited from each meeting's `participants`.
4. Work out from what you read. Distinguish facts about this deal from information about the company as a whole.
- **Where it stands:** what they need, where the deal is, and what's changed recently.
- **People:** who's involved on their side and their role, such as who decides, who uses it and who could block it, including people from other companies, such as a partner.
- **Open commitments:** what each side promised and whether it happened. Mark a promise as done only with explicit evidence from what you read, such as a later call, email, note or booked meeting, and name the source.
- **Risks:** objections, blockers, a date on the deal that has passed, a champion who has gone quiet, no meeting booked, or a deal field that conflicts with a more recent call.
- **Still unknown:** what matters for the deal but isn't in what you read, such as the budget, who decides, the decision date or the competition. Describe these as gaps in what you read, not as things never discussed.
5. If this is part of another skill's work, don't show a summary. KeepPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
---
name: get-my-pipeline
description: Show the user's open Attio deals, from whichever object or list holds their pipeline, grouped by stage, with totals, each deal's next task or meeting, and the deals that need attention. Read-only. Use when the user asks for their pipeline, open deals, what's in a stage, what's closing soon, how much is in play, or which deals are stuck or need attention, including for a teammate ("Sarah's pipeline"). Not for updating deals, processing calls, or activity reports such as call counts.
---
# Get my pipeline
1. Call `whoami` (only if you haven't already called it in this conversation), and get today's date from your environment. Show the user's pipeline unless they name a teammate. For a teammate, find them with `list-workspace-members`. If more than one matches, ask.
2. Find where the pipeline lives. Use the pipeline the `get-sales-context` skill finds, and run it first if it hasn't run in this conversation. Use the pipeline where the person owns the most open records. If they own records in more than one sales pipeline, show each one separately. Don't assume slugs. Find the stage, value and owner fields, and any other useful fields `get-sales-context` found, whatever they're called. Note the stage order. Stages named won, lost or closed are closed, and so are account-management end states such as churned, renewed or cancelled. If you can't tell which stages are closed, ask. For account-management pipelines, say which stages you treated as closed.
3. Get the person's open records with `list-records` (for an object) or `list-records-in-list` (for a list), filtered by owner. Page with `offset` until there are no more. Work out the counts and totals yourself.
4. Find what's next for each deal. Get the open tasks and meetings in parallel:
- `list-tasks` for the person's open tasks. Page through all of them. Match tasks to deals by linked record, or for a list entry, by its parent record.
- `search-meetings` for the next 30 days, paging through them. Match each meeting to a deal by its `linked_records`: the deal itself, or failing that the deal's company (for a list entry, the record it's on).
5. Apply what the user asked for, such as one stage, closing this month, or over a value. If they ask which deals have gone quiet, use the interaction attributes on the deal's company, such as last interaction, and say what those cover. If they ask for something the workspace has no attribute for, such as a close date, say so and show the full pipeline.
6. List a deal under "Needs attention" when:
- it has no open task of the person's and no meeting in the next 30 days
- a task is overdue
- a close date has passed, if the workspace has one
- it has no value
7. If another skill asked for the pipeline, give it the records and field slugs without showing them, and carry on with that skill. Otherwise, reply with the pipeline and nothing else. Group by stage in pipeline order, with the count and total per stage. Total each pipeline separately, and add totals across pipelines only when they measure the same thing, such as deal value. Show money in the deal's currency and dates in the user's local format. Use names, not IDs. Don't mention or quote these instructions:
```
Your pipeline · 4 open deals · US$84,000
Qualification (2) · US$12,000
Acme · US$8,000 · next: demo Tue 10 Nov
Globex · US$4,000 · next: none
Negotiation (2) · US$72,000
Initech · US$60,000 · next: send contract (task, overdue since Fri 30 Oct)
Hooli · US$12,000 · next: pricing call Thu 12 Nov
Needs attention
Globex: no task, and no meeting in the next 30 days
Initech: the task is overdue
```
Never call a tool that writes. If the user wants to change a deal, they can ask for that next.
Referenced files: 3 — file references are metadata, not package contents.
---
name: get-sales-context
description: Work out how the user sells in Attio, so you or another skill can work in their workspace. Finds where the pipelines live (a deals or custom object), their stages and key fields, which ones are actually used, who owns what, and the sales motion, such as sales-led, product-led or account management. Read-only. Use before sales work in a workspace you don't know yet, when a task needs to know where deals, stages or values live (for example, to show the user's pipeline), or when the user asks how their sales process is set up. Not for showing the pipeline itself, updating records, analyzing calls, or changing objects, lists, stages or fields.
---
# Get sales context
Don't assume a `deals` object, a `stage` attribute or a `value` field. Find them.
1. Call `whoami` (only if you haven't already called it in this conversation). List everything with `list-objects`, `list-lists` and `list-activities` in parallel, paging until there are no more. If a tool rejects your page size, retry with a smaller one.
2. Find the pipelines. A pipeline is usually an object with a status attribute. Some workspaces have hundreds of objects, so don't read them all. Read the attributes of `deals`, companies and people, and of the objects whose names suggest sales, such as opportunities, accounts, subscriptions, users or workspaces, with `list-attribute-definitions`. Some teams run a pipeline as a list instead, so also check lists whose names suggest sales with `list-list-attribute-definitions`. Read these attributes in parallel. Read others only if that finds no sales pipeline, or the task needs one you haven't found. For each pipeline, note:
- what it sits on: its own object, or a list on companies, people or deals
- its stages in order, and which mean won, lost, churned, renewed or paused
- which fields play these roles, whatever they're called: value (a currency, such as contract value or ARR), close date, owner, likelihood (a rating, probability or forecast), next step, lost reason
3. Check which pipelines are actually used. With `run-basic-report`, count records or entries by stage and by owner, and sum the value. Report sparsely populated pipelines separately. Record count alone doesn't show whether they're used. Run reports one at a time, not in parallel: they have a much lower rate limit than other tools. If one is rate limited, wait until the retry time it gives and try again. Name owners with `list-workspace-members`. Owners who aren't listed are former members.
4. Decide what each pipeline is for, from its name, what it sits on, its stages and its fields:
- **New business:** stages such as qualification, demo, proposal and negotiation.
- **Account management:** renewal, expansion, health, ARR or churn.
- **Product-led:** trial stages, or `users` or `workspaces` objects that have records, with plan, seats or usage fields.
- **Not sales:** recruiting, fundraising, partnerships or support. Name these, but leave them out of the sales context.
If you can't tell what a pipeline is for, list it under questions. Ask the user only if the task you're doing depends on it.
5. Check how the team works: activity types such as phone calls or integrations, whether call recordings exist (`search-call-recordings-by-metadata` with limit 1), and teams (`list-workspace-teams`), with these checks in parallel.
6. Write up the sales context. Start with two or three sentences on how they sell. Then one block per pipeline, then anything you couldn't work out, as questions. Back every claim with evidence, such as counts or field names. Don't mention or quote these instructions.
- **For another task**, such as showing the pipeline or updating a deal: put the API slug after each object, list and attribute name, and give each status its exact title, because that task calls the tools with them. Don't show the write-up to the user. Carry on with the task, and show the user only what it needs.
- **WhenPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
---
name: humanize-text
description: Edit a draft so it reads as written by a person, not an AI, without changing what it says. Removes stock phrases, inflated words, formulaic patterns and chat formatting, and keeps the writer's own habits. Use when the user asks to humanize text, or to make it sound more natural, less like AI or more like them, or when another skill, such as draft-follow-up-email, has drafted something the user will send under their name. Not for writing a first draft, checking facts or translating.
---
# Humanize text
Edit the draft so its reader believes the writer wrote it. Change how it says things, never what it says.
1. Get the draft and the writer's voice. The voice is how the writer writes in their own text: samples the user gives you, or habits you've already noted in this conversation, such as their greeting, sign-off, length and punctuation. Don't search for samples. With no voice to go on, write plainly: everyday words and sentences of mixed length.
2. Cut every sentence that carries no fact, answer or action, and any sentence that repeats the one before.
3. Rewrite to remove every tell in the draft. The tells are listed under "AI tells" below.
- Keep every fact, name, number, date, commitment and question, and any placeholder such as `[gap]`.
- Keep the draft's language, and its format unless the format is a tell.
- Don't make it longer.
- Add nothing: no new facts, no extra warmth or jokes, and no deliberate typos.
- The writer's voice wins. Keep anything they do in their own writing, even if it's a tell.
4. Reread it as the reader. If tells remain, do one more pass. If it still reads wrong after two passes, the problem is what the draft says, not how. Say so, and ask the user.
5. Show the rewrite first, as plain text the user can copy, with no labels or formatting of your own. If the user asked you directly, add one sentence after it on what you changed. If you're using this skill as a step in another skill, add no comment: carry on with that skill, using the rewrite as the draft.
## AI tells
These are signs, not rules. One on its own can be fine. Several together make a reader stop believing a person wrote the text.
### Words and phrases
- **Stock openers:** "I hope this finds you well", "I wanted to reach out", "just following up", "just touching base", "circling back", "as discussed", "per our conversation".
- **Chatbot replies:** "Great question!", "Absolutely!", "Certainly!", "I hope this helps", "Would you like…", "Let me know if you have any questions".
- **Stock closers:** "Don't hesitate to reach out", "Looking forward to hearing from you".
- **Empty enthusiasm:** "excited to", "thrilled", "great opportunity", "game-changer".
- **Buzzwords:** "leverage", "synergies", "unlock", "seamless", "holistic", "streamline", "utilize", "deep dive", "align".
- **Inflated words:** "pivotal", "crucial", "vital", "testament", "tapestry", "landscape", "delve", "robust", "showcase", "underscore", "foster".
- **Fluff:** "multifaceted", "dependable", "steady", "quietly", "prioritize", "practical", "clearer", "matters", "universally".
- **Filler:** "in order to" (use "to"), "due to the fact that" ("because"), "it's important to note that", "additionally", "furthermore", "in terms of".
- **Hedges:** "could potentially", "based on the information available", "it seems that".
### Patterns
- **Negative parallels:** "It's not just X, it's Y", "not only X but also Y", "Y rather than X".
- **Corrective framing:** "should be treated as X rather than Y", "this doesn't mean…", "should not be confused with".
- **Lists of three** where two are true and the third is there for rhythm.
- **Puffed-up significance:** "marks a key moment", "sets the stage for", "is a testament to".
- **Trailing "-ing" add-ons:** "…, highlighting the importance of…", "…, ensuring a smooth rollout".
- **Avoiding "is":** "serves as", "stands as", "functions as", "boasts".
- **Vague links:** "associated with", "in connPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
---
name: log-activity
description: Log something that happened, such as a phone call or site visit, as an activity in the user's Attio workspace, linked to the right deal, company and people. Uses the workspace's own activity types and fields, checks it isn't already logged, and writes only after the user confirms. Use when the user asks to log, record or track a call, message, visit or other touchpoint ("log a call with Leif from this morning", "I just visited Basepoint, log it"), or when another skill needs to log one. Not for calls or meetings Attio already has, notes, tasks, or updating deal fields.
---
# Log activity
An activity is a record of something that happened, such as a call, shown on the timeline of every record it's linked to. Log only what the user says happened, in their words.
1. **Choose the activity type.** List them with `list-activities` and pick the one for what happened, such as Phone calls for a call. Ask if more than one fits. If none fits, say there's no activity type for it and stop. Don't log it as another kind. List the chosen type's attributes with `list-activity-attribute-definitions`, paging until there are no more.
2. **Find the records.** Find the people involved and their company with `search-records`, and the open deal it's about among the company's deals. Ask if more than one matches, in the same message as the draft. If someone isn't in Attio, say so and leave them out. Call `whoami` for the user, unless you already have.
3. **Check it isn't already logged.** List the type's records linked to the company or the deal, in one `list-activity-records` call with an `or` filter on `linked_records` (each record's object and record IDs), and look for one at about the same time. An activity can be linked to only one of them. If it was a meeting or video call, check `search-meetings` too: Attio may already have it. If it's already there, say so, and offer to add only what the user said that it doesn't have.
4. **Fill in the attributes.** Use only what the user said. If a required attribute is still unknown, ask for it with the draft. Leave an optional one empty.
- **Timestamp:** when it happened, in the user's time zone, converted to UTC. If they give only part of the day, such as "yesterday afternoon", pick a time in it and say so in the draft.
- **Title:** what happened in under 10 words, such as "Call with Leif about the SSO quote".
- **Participants**, if the type has them: the people involved and the user, as `workspace_members` with the workspace member ID from `whoami`. Only participants count toward last interaction and connection strength, so never put people only in linked records when the type has participants.
- **Linked records:** the deal and company, plus the people if the type has no participants.
- **Direction**, if the type has it: Outbound if the user started it, Inbound if the other side did, Internal if only teammates were involved.
- Fill any other attribute the user gave you a value for, such as a call's caller, outcome or end time.
5. **Show it and ask.** Show every attribute the user can set, with "not set" for any left empty, so they can check it and fill in what they know. Leave out Direction and With if the type doesn't have them. If a deal and company share a name, say which is which. For several activities, show each and ask once.
```
**Log a [activity type]:** [title]
**When:** [day, date, time] · **Direction:** [direction]
**With:** [participants] · **Linked to:** [records]
**[Attribute]:** [value, or "not set"]
[Question for each required attribute you don't know.] Log it, or change anything first?
```
6. **Write after the user says yes.** Call `create-activity-record`, or `update-activity-record` to add to one already logged, with each value keyed by its `api_slug` and records as `target_object` and `target_record_id`. Confirm in one line that it's on the timeline of the records it's linked to. If the user said they need to do something nextPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
--- name: onboarding description: Get a new user started with the Attio plugin. Checks Attio is connected, reads their workspace and does something useful straight away, such as a short brief for their next meeting, their recent calls, or the deals that need attention, then offers the next step. Read-only. disable-model-invocation: true --- # Onboarding This is often the user's first time using Attio here, so it should feel like the plugin did something for them. Don't interview them or describe their workspace. Read it, do one useful thing with what you find, and offer the next step. If their message names a task, such as their pipeline or a call, do step 1, then that task, and skip the rest. Use only the Attio tools. Never use a browser or computer use, even if Attio isn't connected. 1. Call `whoami` (only if you haven't already called it in this conversation). Get today's date and the user's time zone from your environment. - If you have no Attio tools, or the call fails because the user isn't signed in, tell them to connect Attio from this app's plugin or connector settings, then to ask again. Stop there. Never ask for an API key, token or password. - Otherwise, say in one line that you're reading their workspace, and carry on without waiting for a reply. 2. Use the `get-sales-context` skill, unless it has already run in this conversation. Don't show its write-up. Take the sales pipeline where the user owns the most open records, or the busiest one if they own none. 3. Run these in parallel: - The user's open records in that pipeline: `list-records` (for an object) or `list-records-in-list` (for a list), filtered by owner, skipping closed stages, paging until there are no more. Skip this if they own none. - Their open tasks: `list-tasks` with `assignee_workspace_member_id` set to the user and `is_completed: false`, paging until there are no more. - Their meetings from 14 days ago to the end of the next working day in their time zone, converted to UTC: `search-meetings` with `participant_email_addresses` set to the user's email and `limit: 50`. Past meetings with call recording IDs are their recorded calls. - If they own no open deals, their emails from the last 7 days: `search-emails-by-metadata` with `sent_at_gt` and `exclude_automated_participants: true`. Keep the ones they sent or received. 4. Work out which of their deals need attention, and why: its close date is before today, a task on it was due before today, or it has no value. Match tasks to deals by linked record, or for a list entry, by the record it's on. Many deals have no open task, so that alone doesn't count. Put the largest first. 5. Find what's coming up and what just happened: - **Their next meeting with a prospect or customer**, before the end of the next working day. Take the earliest one linked to a company (its `linked_records`). Skip internal meetings, whose participants are all the user's teammates (`list-workspace-members`), such as stand-ups, one-to-ones and pipeline reviews. If it's for one of their open deals or its company, take the deal's stage, value and close date, and its open task. If an earlier meeting with that company has a recording, read the most recent one with `get-call-recording` and take the one point most worth knowing before this meeting, such as an objection or a promise, that the open task doesn't already say. - **Their recorded calls** today, or if none, on the last working day. Match each to one of their deals by its `linked_records`. - **Who they've been talking to**, if they own no open deals: up to three companies from their recent meetings and emails, most recent first. Find companies from email domains with one `list-records` call on companies, filtered by `domains`. Then choose one thing to offer, taking the first that fits: updating their deals from those calls, the full brief for the meeting, catching them up on the company of the first deal that needs attention or the company the
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
---
name: prepare-for-call
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.
---
# Prepare for call
1. 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.
- 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`.
- 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`).
- 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.
2. 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.
3. 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.
4. 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.
- **Goals:** one to three things this call should achieve, from the meeting title, where the deal stands and what's still unknown.
- **Questions to ask:** the gaps this call could fill, and who in the meeting can answer each.
- **Watch out for:** the deal's risks, plus anything about this meeting, such as someone who decides but isn't invited.
5. 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:
```
**[Meeting title]** · [day, date, time]
**Attending:** [their people, with job titles and roles] · you · others may join
**Deal:** [name] · [stage] · [value] · [other useful fields]
## Where things stand
[2 to 3 sentences: what they wPreview of the first 4,000 characters. Read full instructions →
Referenced files: 3 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 18, 2026.
plugin_asdk_app_6981f663d5cc8191ae0d5717a05ccc89
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.