← AttioCONTENT HISTORY

Update to Attio

Snapshot Nov 17, 2026 · 00:10 UTC · version 1.0.15

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for get-sales-context

Skill instructions — Now says: `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...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save Attio and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 11, 2026 · 12:08 UTC

`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 hundreds of objects, so don't read them all. Read the attributes of `deals`, companie...

After

Nov 17, 2026 · 00:10 UTC

`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 o...

Supporting files

Before

Nov 11, 2026 · 12:08 UTC

[]

After

Nov 17, 2026 · 00:10 UTC

[{"relative_path":"agents/openai.yaml","size_in_bytes":207},{"relative_path":"assets/icon-small.svg","size_in_bytes":2134},{"relative_path":"assets/icon.png","size_in_bytes":8865}]

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -7,19 +7,19 @@
 
 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`, paging until there are no more.
-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 others only if that finds no sales pipeline, or the task needs one you haven't found. For each pipeline, note:
+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 or paused
+   - 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. Name owners with `list-workspace-members`. Owners who aren't listed are former members.
+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`).
+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.
    - **When the user asked how they sell:** reply with the write-up and nothing else. Use names, not slugs or IDs:
@@ -29,7 +29,7 @@
 
 Opportunities · object · 312 records, 87 open · you own 23
   Stages: Discovery → Demo → Trial → Proposal → Closed won · Closed lost
-  Value: Amount (USD) · Close date: Expected close · Likelihood: Forecast (select) · Owner: AE
+  Value: [field] · Owner: [field] · [other useful fields]
 Not sales: Hiring (list on people)
 Barely used: Deals object (2 records)
 
Full technical diff · 2 changed fields

changed /included_files

BEFORE
[]
AFTER
[
  {
    "relative_path": "agents/openai.yaml",
    "size_in_bytes": 207
  },
  {
    "relative_path": "assets/icon-small.svg",
    "size_in_bytes": 2134
  },
  {
    "relative_path": "assets/icon.png",
    "size_in_bytes": 8865
  }
]

changed /skill_md_contents

BEFORE
"---\nname: get-sales-context\ndescription: 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.\n---\n\n# Get sales context\n\nDon't assume a `deals` object, a `stage` attribute or a `value` field. Find them.\n\n1. Call `whoami` (only if you haven't already called it in this conversation). List everything with `list-objects`, `list-lists` and `list-activities`, paging until there are no more.\n2. 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 others only if that finds no sales pipeline, or the task needs one you haven't found. For each pipeline, note:\n   - what it sits on: its own object, or a list on companies, people or deals\n   - its stages in order, and which mean won, lost or paused\n   - 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\n3. 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. Name owners with `list-workspace-members`. Owners who aren't listed are former members.\n4. Decide what each pipeline is for, from its name, what it sits on, its stages and its fields:\n   - **New business:** stages such as qualification, demo, proposal and negotiation.\n   - **Account management:** renewal, expansion, health, ARR or churn.\n   - **Product-led:** trial stages, or `users` or `workspaces` objects that have records, with plan, seats or usage fields.\n   - **Not sales:** recruiting, fundraising, partnerships or support. Name these, but leave them out of the sales context.\n     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.\n5. 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`).\n6. 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.\n   - **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.\n   - **When the user asked how they sell:** reply with the write-up and nothing else. Use names, not slugs or IDs:\n\n```\nPeople sign up into Workspaces (1,240 records, with Plan and Seats). Sales works the larger accounts in Opportunities.\n\nOpportunities · object · 312 records, 87 open · you own 23\n  Stages: Discovery → Demo → Trial → Proposal → Closed won · Closed lost\n  Value: Amount (USD) · Close date: Expected close · Likelihood: Forecast (select) · Owner: AE\nNot sales: Hiring (list on people)\nBarely used: Deals object (2 records)\n\nQuestions\n  Is Trial a stage in Opportunities, or do trials happen in Workspaces?\n```\n\nNever call a tool that writes.\n"
AFTER
"---\nname: get-sales-context\ndescription: 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.\n---\n\n# Get sales context\n\nDon't assume a `deals` object, a `stage` attribute or a `value` field. Find them.\n\n1. 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.\n2. 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:\n   - what it sits on: its own object, or a list on companies, people or deals\n   - its stages in order, and which mean won, lost, churned, renewed or paused\n   - 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\n3. 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.\n4. Decide what each pipeline is for, from its name, what it sits on, its stages and its fields:\n   - **New business:** stages such as qualification, demo, proposal and negotiation.\n   - **Account management:** renewal, expansion, health, ARR or churn.\n   - **Product-led:** trial stages, or `users` or `workspaces` objects that have records, with plan, seats or usage fields.\n   - **Not sales:** recruiting, fundraising, partnerships or support. Name these, but leave them out of the sales context.\n     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.\n5. 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.\n6. 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.\n   - **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.\n   - **When the user asked how they sell:** reply with the write-up and nothing else. Use names, not slugs or IDs:\n\n```\nPeople sign up into Workspaces (1,240 records, with Plan and Seats). Sales works the larger accounts in Opportunities.\n\nOpportunities · object · 312 records, 87 open · you own 23\n  Stages: Discovery → Demo → Trial → Proposal → Closed won · Closed lost\n  Value: [field] · Owner: [field] · [other useful fields]\nNot sales: Hiring (list on people)\nBarely used: Deals object (2 records)\n\nQuestions\n  Is Trial a stage in Opportunities, or do trials happen in Workspaces?\n```\n\nNever call a tool that writes.\n"
Full snapshot data
{
  "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 207
    },
    {
      "relative_path": "assets/icon-small.svg",
      "size_in_bytes": 2134
    },
    {
      "relative_path": "assets/icon.png",
      "size_in_bytes": 8865
    }
  ],
  "name": "get-sales-context",
  "skill_md_contents": "---\nname: get-sales-context\ndescription: 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.\n---\n\n# Get sales context\n\nDon't assume a `deals` object, a `stage` attribute or a `value` field. Find them.\n\n1. 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.\n2. 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:\n   - what it sits on: its own object, or a list on companies, people or deals\n   - its stages in order, and which mean won, lost, churned, renewed or paused\n   - 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\n3. 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.\n4. Decide what each pipeline is for, from its name, what it sits on, its stages and its fields:\n   - **New business:** stages such as qualification, demo, proposal and negotiation.\n   - **Account management:** renewal, expansion, health, ARR or churn.\n   - **Product-led:** trial stages, or `users` or `workspaces` objects that have records, with plan, seats or usage fields.\n   - **Not sales:** recruiting, fundraising, partnerships or support. Name these, but leave them out of the sales context.\n     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.\n5. 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.\n6. 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.\n   - **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.\n   - **When the user asked how they sell:** reply with the write-up and nothing else. Use names, not slugs or IDs:\n\n```\nPeople sign up into Workspaces (1,240 records, with Plan and Seats). Sales works the larger accounts in Opportunities.\n\nOpportunities · object · 312 records, 87 open · you own 23\n  Stages: Discovery → Demo → Trial → Proposal → Closed won · Closed lost\n  Value: [field] · Owner: [field] · [other useful fields]\nNot sales: Hiring (list on people)\nBarely used: Deals object (2 records)\n\nQuestions\n  Is Trial a stage in Opportunities, or do trials happen in Workspaces?\n```\n\nNever call a tool that writes.\n"
}

SHA-256 of public snapshot: f34adfd43df58359f7f84e14e0a092a045addfcb6c5657d59554d28647415823