Update to Basecamp

{
  "description": "Work with Basecamp through the Basecamp tools — find, read, create, and update projects, to-dos, cards, messages, comments, documents, schedules, and Campfire chats. Use for any Basecamp question or action, and for any basecamp.com link.",
  "included_files": [],
  "name": "basecamp",
  "skill_md_contents": "---\nname: basecamp\ndescription: Work with Basecamp through the Basecamp tools — find, read, create, and update projects, to-dos, cards, messages, comments, documents, schedules, and Campfire chats. Use for any Basecamp question or action, and for any basecamp.com link.\n---\n\n# Basecamp\n\nEvery Basecamp action is its own tool, named for what it does: `get_*` and\n`list_*` read; `create_*`, `update_*`, `complete_*`, `move_*`, `trash_*` and\nthe rest change data. Everything runs as the signed-in person and sees only\nwhat they can see.\n\nThe server keeps the reference notes on how Basecamp works:\n`get_basecamp_guide` returns the core concepts with no `topic`, or one\ntopic — `concepts` (accounts, projects, the dock, and the IDs each tool\ntakes), `finding-things`, `my-work`, `posting-and-mentions` (HTML, mentions,\nwho is notified), and `deleting-and-trash`. Read the topic before a task it\ncovers that you have not done in this conversation.\n\n## Where to start\n\n- **A Basecamp link?** Pass it to `get_by_url` as `url`. It returns the IDs\n  the link names, the record itself, and, for anything that takes comments\n  when this connection can post them, `reply_target`: the tool and IDs a\n  reply goes to. A link to a comment answers with the comment and its\n  parent as the reply target, since comments are not threaded. No\n  `reply_target` means no reply can be posted from here. Don't read IDs out\n  of the link yourself.\n- **By keyword?** `search`, then `get_by_url` with a result's `app_url` for\n  the full record.\n- **Mine?** `get_my_assignments` (priorities first), `get_my_day` (today's\n  schedule and due to-dos), `get_overdue_todos`, `get_upcoming_schedule`,\n  `get_my_notifications` (unreads first; the Hey! menu in Basecamp 4), `get_catchup`\n  (what happened while away).\n- **In a project?** `list_projects` or `search` to find it, then\n  `get_project` for its dock: each dock tool's ID is what that tool's\n  `list_*` and `create_*` calls take.\n- **Long results** come a page at a time. A result carrying `next_cursor`\n  or `next_page` has more: pass that value back as `cursor` or `page` to\n  continue.\n\n## Accounts and projects\n\nEach connection works in one Basecamp account; `get_me` names the\nsigned-in person and that account. A link into another account is out of\nreach from this connection — `get_by_url` says so; tell the person rather\nthan guess. When a request needs a project and doesn't name one, ask which\n— don't pick one for them.\n\n## Writing\n\n- **Rich text** — message bodies, comments, documents, to-do and card notes\n  — is HTML; titles, to-do names and Campfire lines are plain text. The\n  `posting-and-mentions` topic lists the tags Basecamp keeps.\n- **@-mentions.** `create_comment` takes `mentions`: person IDs from\n  `list_pingable_people` or `list_project_people`.\n- **Assigning.** `assignee_ids` replaces the whole list; include everyone\n  who stays assigned. Dates are `YYYY-MM-DD`.\n- **Notifications.** Posting can notify people, but not always: a message\n  or document created without `status: \"active\"` is an unposted draft, and\n  a to-do or event notifies only when `notify` is true. The\n  `posting-and-mentions` topic says who each post notifies; report what was\n  actually sent. Confirm with the person before posting on their behalf to\n  others, and quote what will be posted.\n\n## Removing things\n\n`trash_*` tools move an item to the Basecamp trash, where it can be\nrestored. Tools whose description says \"Permanently\" cannot be undone: run\none only when the person asked for exactly that deletion. The\n`deleting-and-trash` topic covers the difference, and archiving.\n\n## Replying well\n\nLink to what you mention: every item carries an `app_url`. Name the project\nand, when the person has several accounts, the account. Say plainly when\nsomething could not be found or read rather than filling the gap.\n\n**Say what your reads covered.** Every summary, recap, brief or triage\nstates what its reads did and didn't cover, and never claims more than was\nfetched. Reads stop short in known ways: a result marked truncated, a\ntimeline that ends at its latest 100 events, a window capped at 14 days, an\nundated list, a thread whose comments you didn't open, records that include\nother people's work. When one applies, say so in the reply (\"Done covers\nto-dos only\", \"the timeline reaches back to Tuesday\") instead of presenting\nthe section as complete.\n"
}