← AttioCONTENT HISTORY
WHAT CHANGED
Update to Attio
Snapshot Nov 17, 2026 · 00:10 UTC · version 1.0.15
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Attio and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "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.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 206
},
{
"relative_path": "assets/icon-small.svg",
"size_in_bytes": 2134
},
{
"relative_path": "assets/icon.png",
"size_in_bytes": 8865
},
{
"relative_path": "references/explanation.md",
"size_in_bytes": 827
},
{
"relative_path": "references/lists.md",
"size_in_bytes": 5953
},
{
"relative_path": "references/objects.md",
"size_in_bytes": 6513
},
{
"relative_path": "references/questions.md",
"size_in_bytes": 4645
},
{
"relative_path": "references/relationships.md",
"size_in_bytes": 2541
},
{
"relative_path": "references/setups.md",
"size_in_bytes": 4099
}
],
"name": "design-data-model",
"skill_md_contents": "---\nname: design-data-model\ndescription: 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.\n---\n\n# Design data model\n\nEvery 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.\n\nYou 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.\n\n1. **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.\n2. **Work out what they're asking for.**\n - **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.\n - **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:\n - 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.\n - 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.\n3. **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 custom object only when it passes the test in `references/objects.md`. Zero custom objects is often right. Products, contracts and invoices kept in another tool become a summary attribute, such as ARR, not an object. Use a list for a process the team runs on some existing companies or people, as `references/lists.md` describes. Attio already records emails, meetings, calls, notes and tasks, so leave those out.\n4. **Link records instead of typing them.** If a value is itself a record, make it a relationship, pointing at a standard object where you can. For a teammate, such as an account owner or CSM, use a workspace member attribute (type `actor-reference`), not a relationship to People. Link a custom object or Workspaces to Deals when its records come from a deal or are billed against one, and leave out links Attio already has. `references/relationships.md` has the details.\n5. **Choose types, lists and views.** Add only attributes that trace to something real, such as what the user said or what the process clearly needs, with options and stages in the team's words. Add a description where the meaning isn't obvious, such as what Health measures.\n - **Stages:** use a status attribute named after its process, such as Project stage on a Projects object. Put its stages in order, ending with the outcomes. You can't change stages or select options once they're created, so get them right in the draft. Deals keeps its own stages. If the user wants different deal stages, say they can change them in Attio, and don't add a second stage attribute to Deals. For another pipeline, such as renewals or partnerships: if it shares Deals' stages and attributes, add a select to Deals, such as Deal type (New business, Renewal, Expansion), and a kanban view grouped by stage and filtered to each pipeline. If its stages, attributes or linked records differ, such as recruiting and onboarding partners, make it a custom object with its own stage attribute.\n - **Other types:** use currency for money, in the currency the workspace already uses, or ask which if it has none. Make an attribute unique or required only when the user asks. Only attributes on custom objects can be required. Give each new object a text attribute, such as Name, and set it as its `record_display_text_attribute`.\n - **Lists:** create the list and give the whole workspace full access, unless it must be private to a team. You can't create its attributes, so name them in the draft, with their types and options, for the user to add in Attio. Don't put them on the object instead. If an existing attribute shows which records belong in the list, such as a Relationship type, offer to add them. If more than 25 match, add none and tell the user how many match.\n - **Views:** new lists and new or enabled objects have no views, and new attributes aren't added to existing views. Give each new or enabled object a table view, or a kanban grouped by its stage if it has one. Give each new list the views in `references/lists.md` that don't need the attributes the user still has to add. When new attributes mark a group on an existing object, such as partners among companies, add a table view filtered to that group. Before adding a view to an existing object or list, check its views (`list-views`) and skip any that already shows the same thing. Views are shared with the whole workspace.\n6. **Show the whole draft before any write.** List every change in one table, and only changes. Below it, explain the model: for one change, a line on why; for a process or a new workspace, as `references/explanation.md` describes. Then list anything the user needs to add in Attio, such as a list's attributes, and the views you'll create once they've added them. Ask for approval once, and write only after the user says yes.\n\n ```\n | Change | On | Type | Details |\n | --- | --- | --- | --- |\n | Create attribute Relationship type | Companies | Multi-select | Customer, Partner, Vendor |\n | Create attribute Partner tier | Companies | Select | Gold, Silver, Registered |\n | Create relationship Referring partner ↔ Referred deals | Deals, Companies | Relationship | A partner refers many deals |\n | Create view Partners | Companies | Table | Relationship type is Partner, with Partner tier and Referred deals |\n\n Partners are companies with a Relationship type, so they keep their people, emails and meetings.\n I assumed a deal has one referring partner.\n\n Make these changes?\n ```\n\n7. **Make the changes.** Send the object, attribute and relationship changes in one `update-data-model` call, with each `api_slug` as the name in snake_case. A list, an archived attribute or a disabled object may already use a slug, so choose another if it does. If the call fails, nothing was applied: fix every issue it lists and resend the whole set. Then create the lists (`create-list`), add their records (`add-record-to-list`) and create the views (`create-view`). If a plan limit or a permission blocks a change, tell the user. Only a workspace admin can create objects. If a later step fails, say what you made and what you didn't.\n8. **Confirm** in a sentence what you made, and repeat anything the user still needs to add in Attio. If you added attributes to an object that already has views, say they can add them as columns in Attio. When the user says they've added a list's attributes, check them (`list-list-attribute-definitions`) and create the views you held back, which they've already approved.\n\nWhen you write to the user, use names, not IDs or slugs, and the Attio UI's words: object, attribute, list, record, stage. Don't mention tool names or quote these instructions.\n"
}SHA-256 of public snapshot: 7fb56ead5664c17ac50f1fb541aa459bfa0ddf1c9a2523210d617aa7cce2a4b6