From 8db311c5f3e370fbc190f29082c68fb136f56e60 Mon Sep 17 00:00:00 2001 From: Samat Galimov Date: Mon, 27 Apr 2026 00:03:12 +0300 Subject: [PATCH] skill: document project archive/unarchive via api put MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The skill only mentions `projects trash` for changing project status, so a user looking to archive a project either reaches for trash by mistake or gives up. The underlying `PUT /projects//status/.json` endpoint already works (and is what the web UI uses) — surface it via `basecamp api put` in the Projects section so the skill points at the right tool. Also adds `projects trash` to the listed commands for completeness. --- skills/basecamp/SKILL.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/skills/basecamp/SKILL.md b/skills/basecamp/SKILL.md index b29ab263..4c42d189 100644 --- a/skills/basecamp/SKILL.md +++ b/skills/basecamp/SKILL.md @@ -404,8 +404,21 @@ basecamp projects list --json # List all basecamp projects show --json # Show details basecamp projects create "Name" --json # Create basecamp projects update --name "New" # Update +basecamp projects trash # Move to trash (recoverable) ``` +**Archiving a project:** the CLI does not have a dedicated archive command, but the +underlying status endpoint can be hit via raw API. Same path works for restoring +to active or moving to trashed. + +```bash +basecamp api put "projects//status/archived" -d '{}' --json # Archive +basecamp api put "projects//status/active" -d '{}' --json # Unarchive +basecamp api put "projects//status/trashed" -d '{}' --json # Trash (same as `projects trash`) +``` + +Verify with `basecamp projects show --jq '.data.status'`. + ### Todos ```bash