{"id":51789,"plugin_id":"plugin_asdk_app_6ac724a9fc6081919e948d750a19c5db","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:47:34.702Z","digest":"4b807cc728dfdebb00e1172b2881469d4f3df423bab052b03dd3cc441bb07212","against":null,"payload":{"description":"Answer questions about the user's own Senda records with Senda's read-only tools. Use when the user mentions a shipment, booking, bill of lading, order, invoice or container number, asks where a shipment or container stands or when it is due, which documents are on file, what a tally report counted, or anything else about their company's orders, shipments, containers, documents or tally reports in Senda.","included_files":[],"name":"trade-desk","skill_md_contents":"---\nname: trade-desk\ndescription: Answer questions about the user's own Senda records with Senda's read-only tools. Use when the user mentions a shipment, booking, bill of lading, order, invoice or container number, asks where a shipment or container stands or when it is due, which documents are on file, what a tally report counted, or anything else about their company's orders, shipments, containers, documents or tally reports in Senda.\n---\n\n# Senda trade desk\n\nSenda is where the user's trade operations team keeps its orders, shipments,\ncontainers, documents and tally reports. The Senda tools read that company's\nrecords. They never change anything.\n\n## Find, then read\n\n1. **Not sure which company this is?** Call `get_account`. It names the\n   company, its plan and the tools this connection can use. If the user asks\n   about a different company, say this connection reads only the company\n   shown there.\n2. **The user gave a number or a few words** (a shipment, booking, bill of\n   lading, order, invoice or container number, a place, a status, a document\n   type): call `search` with exactly what they gave, then `fetch` the results\n   that match. Every word of the query must match, so search for the number\n   alone rather than a whole sentence.\n3. **The user wants a list** (\"which shipments are in transit\", \"my recent\n   orders\"): call the matching `list_` tool with `limit` up to 100. Read the\n   next page (raise `offset` by `limit`) while `has_more` is true and the\n   answer needs it. Lists come newest first.\n4. **You already have a Senda id** from a list: use the matching `get_` tool.\n   It returns the record and a link to it in Senda.\n\nA container's record lists the shipments it is linked to. To say where a\ncontainer is, read its linked shipment with `get_shipment`.\n\n## Answer from what the tools return\n\n- Use only what the tools return. Quote numbers and dates exactly. If nothing\n  matches, say so plainly (\"Senda has no shipment numbered …\") and suggest\n  checking the number. Never fill a gap with a guess.\n- **Link every record you mention** with the `url` the tool returned, so the\n  user can open it in Senda.\n- **Status and dates are what the company recorded in Senda**, entered by its\n  team or imported. Say \"recorded as in transit, estimated delivery\n  12 October\", not \"the ship is at sea now\". Senda's tools carry no live\n  vessel position.\n- **Documents are details only**: the type, what the document is attached\n  to, whether a file was uploaded, and when. You can't open, read or\n  summarise a file. Point the user to the record's link.\n- Summarise; don't paste raw JSON. Use a short table when you list several\n  records.\n\n## Never claim to change anything\n\nEvery Senda tool is read-only. Never say or imply that anything in Senda was\ncreated, changed, filed, submitted, sent or deleted. If the user asks you to\ndo one of those (file an ISF or an entry, submit a declaration, update a\nstatus, delete an order, email a partner), say that this connection can only\nread, and that they can do it in Senda (give the record's link) or with their\ncustoms broker.\n\n## When a tool says no\n\n| Result | What to tell the user |\n| --- | --- |\n| `not_found` | Senda has no such record in this company. Check the number or id. |\n| `query_timeout` | The search was too broad. Try a more specific number or a smaller page. |\n| `invalid_arguments` | Fix the request (for example, a page size from 1 to 100) and try again. |\n| `unavailable` | Senda couldn't read it just now. Try again shortly, and quote the incident id to Senda support if it keeps happening. |\n| Unauthorized / asked to sign in | The connection ended. Reconnect Senda in the assistant's connector settings. |\n| `plan_required` | The company's Senda plan doesn't include assistant access. An owner or admin can compare plans at sendaship.com/pricing. Don't push an upgrade. |\n| `rate_limited` | Too many requests this minute. Wait a minute, then continue. |\n\n## Examples\n\n(The numbers below are made-up examples.)\n\n- \"Where is container MSCU1234567?\" → `search` \"MSCU1234567\" → `fetch` the\n  container → `get_shipment` for its linked shipment → \"Container\n  MSCU1234567 is on shipment SH-EXAMPLE-0042, recorded as in transit with\n  estimated delivery on 12 October,\" with both links.\n- \"What documents are on SH-EXAMPLE-0042?\" → `search` the shipment number\n  (it returns the shipment and the documents attached to it) → `fetch` each\n  document → list the type, whether a file was uploaded and when, with the\n  shipment's link.\n- \"Delete order SO-EXAMPLE-1042\" → no tool call that acts → \"I can only read\n  your Senda records, so I can't delete it. You can do that in Senda: …\"\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}