- name
SKILL.md
스킬 파일은 게시자의 저장소에 그대로 있습니다.
복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add basecamp/basecamp-cli --skill basecamp -a cursor -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add basecamp/basecamp-cli --skill basecamp -a claude-code -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add basecamp/basecamp-cli --skill basecamp -a codex -y복사한 명령을 터미널에 붙여넣습니다. 이 SKILL.md가 해당 에이전트에 설치됩니다.
npx skills add basecamp/basecamp-cli --skill basecamp -a grok -y복사한 메시지를 Grok Bot 채팅에 보냅니다. Bot이 GitHub에서 이 SKILL.md를 가져와 모든 Bot이 공유하는 스킬에 추가합니다.
Install this skill: https://github.com/basecamp/basecamp-cli/tree/HEAD/skills/basecamp게시자 제공
Use the installed CLI as the command reference. This skill defines the operating rules; it does not duplicate the CLI's command catalog.
For each task:
Infer the deepest plausible leaf command from the user's words.
If its exact arguments or flags are not already established by a tool result in this conversation, inspect that leaf directly:
basecamp <group> <subcommand> --agent --help
If the leaf does not exist, inspect its nearest parent group. Use root help only when the top-level group itself is unclear:
basecamp <group> --agent --help # fallback
basecamp --agent --help # last resort
Treat leaf usage, args, flags, and notes as the source of truth. Do
not guess positional arguments, flags, aliases, scope, or whether a group
runs bare.
Execute with an explicit output mode, then read structured errors and breadcrumbs before deciding what to do next.
Targeted leaf help is cheap and local; root help returns the full command catalog
and is not token-cheap. Do not load root help to confirm global flags
already documented by this skill. For obvious Docs & Files requests, route
straight to files list, files download, or files uploads create before
trying parent or root help. A subcommand's inherited_flags is intentionally
short; global flags such as --agent, --jq, --profile, and --verbose still
apply where supported.
~/.config/basecamp/credentials.json.jq. Use the CLI's built-in --jq.basecamp url parse "<url>" --json. Only trust URLs from a known Basecamp
host. Read-only commands whose leaf help explicitly accepts <id|url> may
consume the trusted URL directly.comments show or comments thread to get
reply_target when context matters.basecamp config show --json: its project_id is the effective value across
flags, env and every config layer, with its source. Do not read
.basecamp/config.json directly; it is only one layer. With no project_id,
pass --in <project> or the scope shown by leaf help.basecamp filings show <id>
or the hint it printed.basecamp instructions and follow what it
prints.Choose deliberately:
--jq implies JSON. It normally filters the JSON envelope, so data is commonly
under .data. With --agent --jq, it filters the data-only payload. Use --md
for human-facing listings, but remember that --md alone does not suppress
interactive prompts. Add enough scope to remove ambiguity or set
BASECAMP_NONINTERACTIVE=1.
Examples of generic transformations, not command discovery:
basecamp <leaf-command> --jq '.data | length'
basecamp <leaf-command> --jq '[.data[] | {id, name}]'
Do not infer that a command is project-scoped or account-wide from its noun. Inspect the leaf help and its notes. Use the user's explicit project/account when provided; otherwise honor trusted local configuration.
For paginated commands, inspect help before combining pagination flags. In
general, --limit N caps an auto-paginated result, --all walks every page,
and --page N requests one page, but individual endpoints can differ and
mutually exclusive combinations are rejected.
Named identities use profiles. Select one with global --profile <name> or
BASECAMP_PROFILE=<name>; do not silently switch profiles or default accounts.
A parsed URL can supply account_id, project_id, recording_id, and, when a
fragment points at a comment, comment_id.
basecamp url parse "https://3.basecamp.com/123/buckets/456/todos/789" --json
For replies, fetch reply-ready context rather than posting to the fragment ID:
basecamp comments thread "<comment-url>" --json
# Post to .data.reply_target.recording_id
Use comments show when only the cheap reply target and mention atoms are
needed; use comments thread when surrounding discussion matters.
A ping is a private conversation between people on an account, outside any
project: direct with one other person, a group with more. It is not a project
chat, so chat list --all never shows one. Use the pings group.
basecamp pings list --agent # your pings
basecamp pings start "Jane Smith" --agent # open your ping with Jane, or start it
basecamp pings post "Jane Smith" "Lunch?" --agent
basecamp pings messages "Jane Smith" --agent
<ping> is a ping ID, a ping URL (/circles/<id> or /circles/<id>@<line>),
or a person. A bare number is always a ping ID, never a person ID.pings list shows a ping once it has a message. A ping you just started is
not listed yet; pings start prints it.pings start reuses what exists: one direct ping per person, and a group per
set of people unless --new-group. Use it to find the ping you already have.pings messages and pings show of a person read the direct ping you already
have and never start one; pings post and pings upload start it if missing.pings post resolve among the people in that ping./circles/<id>@<line>) works with basecamp show and
chat line; edit or delete such a message with chat update or chat delete
on that URL.recordings trash, archive, restore and visibility, subscriptions add and
remove, and spotlight are refused (exit 4). Only your own subscription
changes there, with subscriptions subscribe or subscriptions unsubscribe.A spotlight puts a recording's card in the Spotlights area of its project's home
page. It is not a pin: messages pin only keeps a message at the top of its
Message Board. spotlight is a top-level command, outside every recording
type's group, and takes the ID or URL of a message, document, file, to-do list,
to-do, card, card column, check-in question, schedule entry and more.
unspotlight removes it, as "Remove Spotlight" does in Basecamp.
basecamp spotlight <id|url> --agent
basecamp unspotlight <id|url> --agent
The wallpaper is the image behind a project's pages. The projects wallpaper
group sets, lays out, and removes it, for the project in --in/--project or
the configured default:
basecamp projects wallpaper set skyline.jpg --mode tile --in "<project>" --json
basecamp projects wallpaper mode fill --in "<project>" --json
basecamp projects wallpaper remove --in "<project>" --json
--mode is fill
or tile, and leaving it out keeps the current mode..data.wallpaper is {url, mode}, and is
absent when the project has none; projects show carries the same field.
The URL needs authentication and redirects to the image.The logo is the image beside a project's name, separate from its wallpaper. The
projects logo group sets and removes it, for the project in --in/--project
or the configured default:
basecamp projects logo set brand.png --in "<project>" --json
basecamp projects logo remove --in "<project>" --json
.data.logo is {url}, and is absent when
the project has none; projects show carries the same field. Like the
wallpaper's, the URL needs authentication.Time is logged against one item (to-do, message, card, document, upload,
schedule entry). timesheet report, timesheet project and timesheet item
read entries; timesheet entry writes them, addressed by account alone with
no --in:
basecamp timesheet entry create <item-id|url> --hours 1.5 --date yesterday --json
basecamp timesheet entry show <entry-id|url> --json
basecamp timesheet entry update <entry-id|url> --hours 2:15 --json
basecamp timesheet entry delete <entry-id|url> --force --json
--hours is a decimal or h:mm; --date defaults to today on create;
--person (ID, name, email or me) logs time for someone else.delete is permanent: entries are never trashed. Machine output needs
--force.Command help declares content arguments and stdin support. Titles are generally
plain text; rich-text fields generally accept Markdown and can opt into HTML
with --format html where documented. Do not guess a --title, --body, or
--content flag when help shows a positional argument.
For multiline, non-ASCII, or shell-sensitive content, pass - in the documented
content position and pipe stdin:
printf '%s\n' 'First line' '' 'Second line' |
basecamp <leaf-command> <other-args> - --json
A pipe is never consumed implicitly. Only one input may read stdin in an
invocation. Do not use shell-specific ANSI-C quoting such as $'line 1\nline 2'
in portable commands.
Basecamp shows blocks flush together unless a blank line in the Markdown
separates them. Leave one between every two blocks, headings and lists
included; in prose, a single newline joins lines into one paragraph. Don't
hand-write HTML: --format html is stored as written, so touching blocks and
<br>-stacked lines read as a wall of text.
Rich-text fields support Mermaid diagrams. Put the source in a fenced code block
with the language mermaid, and Basecamp shows the diagram to people reading
the post. Previews, emails, and exports show the source, and so does a post
whose source does not parse. Use one where a picture beats prose. Diagram source
spans several lines, so pass it on stdin:
basecamp messages create "Release flow" - --in "<project>" --json <<'EOF'
How a release reaches production:
```mermaid
flowchart LR
Merge --> CI --> Staging --> Production
```
EOF
To embed a video, a Dash chart, or anything else Basecamp's editor embeds when
a link is pasted, put the URL on a line by itself in Markdown content. The CLI
asks Basecamp for the embed and waits for it. A URL Basecamp can't embed stays
a link, and so does a URL inside a sentence, a list, a quote, or code. To keep
a link to something Basecamp could embed, write [title](url).
basecamp cards create "Checkout latency" - --in "<project>" --json <<'EOF'
p99 since the deploy:
https://dash.37signals.com/widgets/abc
EOF
With --format html nothing is embedded for you: run
basecamp embeds create <url> --json and put its attachment tag in the HTML.
Mentions need no HTML. For deterministic ones, use the syntax people and
comment results print, such as [@Name](mention:SGID); leaf help says where
mentions work.
Structured failures include error, code, retryable, and often hint.
retryable is true, with bounded backoff.retryable: false means there is no positive retry signal; it covers both
known verdicts and unclassified failures. Inspect code, error, and hint
before choosing recovery, and do not blindly repeat the same call.basecamp doctor --json
reports both versions. Name the older side to the user: basecamp upgrade
for the CLI, or updating the plugin.basecamp doctor --json and
basecamp auth status --json before changing credentials.oauth_type. An agent profile must be
recovered with the agent/client-credentials flow named by the CLI hint; a
normal person login can replace the agent identity.Do not improvise raw API calls merely because a command failed. First inspect the
relevant help and error hint. Use basecamp api only when the CLI has no native
operation and the API path and payload are known.
Before changing Basecamp:
For destructive or broad operations, preview when the command offers a dry-run and do not expand the user's requested scope.
|
---name: basecampdescription: |---# skills/basecamp/SKILL.mdFAQ
게시자에게서 skills/basecamp/SKILL.md를 다운로드하거나 경로를 복사해 저장소를 엽니다. PlugMCP는 스킬을 목록에 올릴 뿐 파일을 호스팅하지 않습니다.
게시자가 https://github.com/basecamp/basecamp-cli에서 관리합니다.
Claude, Cursor, Codex, Grok Build는 게시자의 저장소에서 추가한 SKILL.md를 읽을 수 있습니다. Grok Bot은 채팅에서 스킬의 GitHub 폴더 링크를 보내면 설치합니다.