Update to Attio
Snapshot Nov 17, 2026 · 00:10 UTC · version 1.0.15
Collection source: downloaded plugin package.
Payment or plan references changed
Skill instructions — Now says: 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...
Observed in published text. Live prices and checkout terms have not been verified by this change.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Nov 11, 2026 · 12:08 UTC
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 which stages are closed, ask. 4. Find what's next for each deal: - `list-task...
Nov 17, 2026 · 00:10 UTC
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 ...
Supporting files
Nov 11, 2026 · 12:08 UTC
[]
Nov 17, 2026 · 00:10 UTC
[{"relative_path":"agents/openai.yaml","size_in_bytes":212},{"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 @@ -6,32 +6,32 @@ # 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, 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 which stages are closed, 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: - - `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. For a deal none of them match, check for a teammate's task: `list-tasks` with the deal, or a list entry's parent record, as `linked_record_object` and `linked_record_id`, `is_completed: false` and `limit: 1`. - - `search-meetings` for the next 30 days, paging through them. Match meetings to deals by related record, or by the deal's company. -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 or its 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. +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 and no meeting in the next 30 days + - it has no open task of the person's and no meeting in the next 30 days - a task is overdue - - its close date has passed + - 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. 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: +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 · closes Mon 30 Nov · next: demo Tue 10 Nov + Acme · US$8,000 · next: demo Tue 10 Nov Globex · US$4,000 · next: none Negotiation (2) · US$72,000 - Initech · US$60,000 · closes Thu 15 Oct · next: send contract (task, overdue since Fri 30 Oct) + 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: close date has passed, and the task is overdue + 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.
Full technical diff · 2 changed fields
changed /included_files
[]
[
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 212
},
{
"relative_path": "assets/icon-small.svg",
"size_in_bytes": 2134
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 8865
}
]changed /skill_md_contents
"---\nname: get-my-pipeline\ndescription: 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.\n---\n\n# Get my pipeline\n\n1. 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.\n2. 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, 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 which stages are closed, ask.\n3. 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.\n4. Find what's next for each deal:\n - `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. For a deal none of them match, check for a teammate's task: `list-tasks` with the deal, or a list entry's parent record, as `linked_record_object` and `linked_record_id`, `is_completed: false` and `limit: 1`.\n - `search-meetings` for the next 30 days, paging through them. Match meetings to deals by related record, or by the deal's company.\n5. 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 or its 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.\n6. List a deal under \"Needs attention\" when:\n - it has no open task and no meeting in the next 30 days\n - a task is overdue\n - its close date has passed\n - it has no value\n7. 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. 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:\n\n```\nYour pipeline · 4 open deals · US$84,000\n\nQualification (2) · US$12,000\n Acme · US$8,000 · closes Mon 30 Nov · next: demo Tue 10 Nov\n Globex · US$4,000 · next: none\nNegotiation (2) · US$72,000\n Initech · US$60,000 · closes Thu 15 Oct · next: send contract (task, overdue since Fri 30 Oct)\n Hooli · US$12,000 · next: pricing call Thu 12 Nov\n\nNeeds attention\n Globex: no task, and no meeting in the next 30 days\n Initech: close date has passed, and the task is overdue\n```\n\nNever call a tool that writes. If the user wants to change a deal, they can ask for that next.\n"
"---\nname: get-my-pipeline\ndescription: 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.\n---\n\n# Get my pipeline\n\n1. 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.\n2. 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.\n3. 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.\n4. Find what's next for each deal. Get the open tasks and meetings in parallel:\n - `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.\n - `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).\n5. 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.\n6. List a deal under \"Needs attention\" when:\n - it has no open task of the person's and no meeting in the next 30 days\n - a task is overdue\n - a close date has passed, if the workspace has one\n - it has no value\n7. 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:\n\n```\nYour pipeline · 4 open deals · US$84,000\n\nQualification (2) · US$12,000\n Acme · US$8,000 · next: demo Tue 10 Nov\n Globex · US$4,000 · next: none\nNegotiation (2) · US$72,000\n Initech · US$60,000 · next: send contract (task, overdue since Fri 30 Oct)\n Hooli · US$12,000 · next: pricing call Thu 12 Nov\n\nNeeds attention\n Globex: no task, and no meeting in the next 30 days\n Initech: the task is overdue\n```\n\nNever call a tool that writes. If the user wants to change a deal, they can ask for that next.\n"
Full snapshot data
{
"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.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 212
},
{
"relative_path": "assets/icon-small.svg",
"size_in_bytes": 2134
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 8865
}
],
"name": "get-my-pipeline",
"skill_md_contents": "---\nname: get-my-pipeline\ndescription: 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.\n---\n\n# Get my pipeline\n\n1. 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.\n2. 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.\n3. 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.\n4. Find what's next for each deal. Get the open tasks and meetings in parallel:\n - `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.\n - `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).\n5. 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.\n6. List a deal under \"Needs attention\" when:\n - it has no open task of the person's and no meeting in the next 30 days\n - a task is overdue\n - a close date has passed, if the workspace has one\n - it has no value\n7. 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:\n\n```\nYour pipeline · 4 open deals · US$84,000\n\nQualification (2) · US$12,000\n Acme · US$8,000 · next: demo Tue 10 Nov\n Globex · US$4,000 · next: none\nNegotiation (2) · US$72,000\n Initech · US$60,000 · next: send contract (task, overdue since Fri 30 Oct)\n Hooli · US$12,000 · next: pricing call Thu 12 Nov\n\nNeeds attention\n Globex: no task, and no meeting in the next 30 days\n Initech: the task is overdue\n```\n\nNever call a tool that writes. If the user wants to change a deal, they can ask for that next.\n"
}SHA-256 of public snapshot: 1e9c54db4913154d29aa4c0cef5abd68a8e825671a065e3e37b126a0d46ffab8