basecamp
Interact with Basecamp via the Basecamp CLI. Full API coverage: projects, todos, cards, messages, files, schedule, check-ins, timeline, recordings, templates, webhooks, subscriptions, lineup, chat, pings, gauges, assignments, notifications, bookmarks, bubble-up, drafts, notes, calendars, and accounts. Use for ANY Basecamp question or action.
basecamp · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add basecamp/basecamp-cli --skill basecamp技能说明
name: basecamp description: | Interact with Basecamp via the Basecamp CLI. Full API coverage: projects, todos, cards, messages, files, schedule, check-ins, timeline, recordings, templates, webhooks, subscriptions, lineup, chat, pings, gauges, assignments, notifications, bookmarks, bubble-up, drafts, notes, calendars, and accounts. Use for ANY Basecamp question or action. triggers:
Direct invocations
- basecamp
- /basecamp
Resource actions
- basecamp todos
- basecamp project
- basecamp cards
- basecamp chat
- basecamp campfire
- basecamp messages
- basecamp file
- basecamp document
- basecamp bookmarks
- basecamp bubble-up
- basecamp drafts
- basecamp notes
- basecamp calendars
- basecamp schedule
- basecamp checkin
- basecamp check-in
- basecamp timeline
- basecamp template
- basecamp webhook
- basecamp gauge
- basecamp assignment
- basecamp notification
- basecamp account
Common actions
- link to basecamp
- track in basecamp
- post to basecamp
- comment on basecamp
- complete todo
- mark done
- create todo
- move card
- download file
Search and discovery
- search basecamp
- find in basecamp
- look up basecamp
- check basecamp
- list basecamp
- show basecamp
- get from basecamp
- fetch from basecamp
Questions
- can I basecamp
- how do I basecamp
- what's in basecamp
- what basecamp
- does basecamp
My work
- my todos
- my tasks
- my schedule
- my basecamp
- assigned to me
- my assignments
- my notifications
- overdue todos
- upcoming events
- project gauge
- project progress
URLs
- 3.basecamp.com
- basecampapi.com
- https://3.basecamp.com/ invocable: true argument-hint: "[action] [args...]"
/basecamp - Basecamp Workflow Command
Full CLI coverage: 189 tracked in-scope endpoints across todos, cards, messages, files, schedule, check-ins, timeline, recordings, templates, webhooks, subscriptions, lineup, chat, pings, gauges, assignments, notifications, and accounts.
Agent Invariants
MUST follow these rules:
-
Choose the right output mode —
--jqwhen you need to filter/extract data;--jsonfor full JSON;--mdwhen presenting results to a human (see Output Modes below). Never pipe to externaljq— use--jqinstead. -
Parse URLs first with
basecamp url parse "<url>"to extract IDs -
Comments are flat - reply to parent recording, not to comments
-
Check context via
.basecamp/config.jsonbefore assuming project -
Content fields accept Markdown and @mentions — message body and comment content accept Markdown syntax; the CLI converts to HTML automatically. Use Markdown formatting (lists, bold, links, code blocks, tables) for rich content. Four mention syntaxes are available (prefer deterministic for agents):
[@Name](mention:SGID)— zero API calls, embeds SGID directly (preferred for agents)[@Name](person:ID)— one API call, resolves person ID to SGID via pingable set@sgid:VALUE— inline SGID embed for pipeline composability@Name/@First.Last— fuzzy name resolution (may be ambiguous) For todos, documents, and cards, content is sent as-is — use plain text or HTML directly.
Table boundary: GFM tables round-trip: they render in message/comment bodies, display converts them back to pipe tables, and the TUI in-place editors open simple grids for editing. Only complex tables — merged cells (colspan/rowspan), captions, extra header rows, nested tables, attachments/images or block content inside cells, multi-paragraph or multi-line cells, or a table inside a blockquote or list — refuse to open, since a GFM pipe table can't represent those shapes (edit them on Basecamp web, or replace the whole field via
messages update/comments update/todos update --description, which take fresh content and are unaffected). Complex tables still display best-effort, flattened to a plain grid.Multiline / non-ASCII content: do not rely on bash ANSI-C quoting (
$'...\n...') — it is a bash/zsh extension. Under a POSIX/bin/sh(dash, busybox-ash, common in sandboxes) the$is passed through literally and posts a stray leading$, and\nstays a literal backslash-n. Pipe the content via stdin instead, using-as the content argument:printf '%s\n' '海报 mockup 方向稿:' '' '<bc-attachment ...>' | basecamp comments create <recording_id> - --in <project> --json-means "read from stdin" on every content input: content-kind positionals (comments create/update,messages create [body],cards create [body],todos create,docs documents create [content],chat post/update,boost create,checkins answer create/update,notes set) and content flags (--dataonapi post/put,--body,--content,--description,--commentontodos sweep,--fileonnotes set). Each command's--agenthelp lists its stdin inputs. Rules:- A pipe is never consumed implicitly — without
-it is ignored (or, where content is required and missing, the error teaches-). - Only one input can read stdin per invocation.
- A literal
-anywhere else (a title, a name, a path) errors when stdin is piped. Escape a positional after the--separator (basecamp projects create -- -); a flag value has no in-line escape — run the command without piped stdin.basecamp helpand shell completion are exempt: they write nothing to Basecamp, and completion legitimately receives-as the word being completed. -with nothing piped (interactive TTY) errors immediately instead of hanging; use a pipe, a heredoc (basecamp comments create <id> - <<'EOF'), or--editwhere offered.- Trailing newlines are trimmed from stdin content, so
printf 'x\n' | ... -postsx(this keeps `boost create