[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EX920MWTHGGTCYKVDHKS7M":3,"skill-same:01M7EX920MWTHGGTCYKVDHKS7M":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7EX920MWTHGGTCYKVDHKS7M","basecamp-automation",null,"Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbasecamp-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: basecamp-automation\ndescription: \"Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio). Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Basecamp Automation via Rube MCP\n\nAutomate Basecamp operations including project management, to-do list creation, task management, message board posting, people management, and to-do group organization through Composio's Basecamp toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Basecamp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `basecamp`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `basecamp`\n3. If connection is not ACTIVE, follow the returned auth link to complete Basecamp OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage To-Do Lists and Tasks\n\n**When to use**: User wants to create to-do lists, add tasks, or organize work within a Basecamp project\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - List projects to find the target bucket_id [Prerequisite]\n2. `BASECAMP_GET_BUCKETS_TODOSETS` - Get the to-do set within a project [Prerequisite]\n3. `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS` - List existing to-do lists to avoid duplicates [Optional]\n4. `BASECAMP_POST_BUCKETS_TODOSETS_TODOLISTS` - Create a new to-do list in a to-do set [Required for list creation]\n5. `BASECAMP_GET_BUCKETS_TODOLISTS` - Get details of a specific to-do list [Optional]\n6. `BASECAMP_POST_BUCKETS_TODOLISTS_TODOS` - Create a to-do item in a to-do list [Required for task creation]\n7. `BASECAMP_CREATE_TODO` - Alternative tool for creating individual to-dos [Alternative]\n8. `BASECAMP_GET_BUCKETS_TODOLISTS_TODOS` - List to-dos within a to-do list [Optional]\n\n**Key parameters for creating to-do lists**:\n- `bucket_id`: Integer project\u002Fbucket ID (from GET_PROJECTS)\n- `todoset_id`: Integer to-do set ID (from GET_BUCKETS_TODOSETS)\n- `name`: Title of the to-do list (required)\n- `description`: HTML-formatted description (supports Rich text)\n\n**Key parameters for creating to-dos**:\n- `bucket_id`: Integer project\u002Fbucket ID\n- `todolist_id`: Integer to-do list ID\n- `content`: What the to-do is for (required)\n- `description`: HTML details about the to-do\n- `assignee_ids`: Array of integer person IDs\n- `due_on`: Due date in `YYYY-MM-DD` format\n- `starts_on`: Start date in `YYYY-MM-DD` format\n- `notify`: Boolean to notify assignees (defaults to false)\n- `completion_subscriber_ids`: Person IDs notified upon completion\n\n**Pitfalls**:\n- A project (bucket) can contain multiple to-do sets; selecting the wrong `todoset_id` creates lists in the wrong section\n- Always check existing to-do lists before creating to avoid near-duplicate names\n- Success payloads include user-facing URLs (`app_url`, `app_todos_url`); prefer returning these over raw IDs\n- All IDs (`bucket_id`, `todoset_id`, `todolist_id`) are integers, not strings\n- Descriptions support HTML formatting only, not Markdown\n\n### 2. Post and Manage Messages\n\n**When to use**: User wants to post messages to a project message board or update existing messages\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - Find the target project and bucket_id [Prerequisite]\n2. `BASECAMP_GET_MESSAGE_BOARD` - Get the message board ID for the project [Prerequisite]\n3. `BASECAMP_CREATE_MESSAGE` - Create a new message on the board [Required]\n4. `BASECAMP_POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` - Alternative message creation tool [Fallback]\n5. `BASECAMP_GET_MESSAGE` - Read a specific message by ID [Optional]\n6. `BASECAMP_PUT_BUCKETS_MESSAGES` - Update an existing message [Optional]\n\n**Key parameters**:\n- `bucket_id`: Integer project\u002Fbucket ID\n- `message_board_id`: Integer message board ID (from GET_MESSAGE_BOARD)\n- `subject`: Message title (required)\n- `content`: HTML body of the message\n- `status`: Set to `\"active\"` to publish immediately\n- `category_id`: Message type classification (optional)\n- `subscriptions`: Array of person IDs to notify; omit to notify all project members\n\n**Pitfalls**:\n- `status=\"draft\"` can produce HTTP 400; use `status=\"active\"` as the reliable option\n- `bucket_id` and `message_board_id` must belong to the same project; mismatches fail or misroute\n- Message content supports HTML tags only; not Markdown\n- Updates via `PUT_BUCKETS_MESSAGES` replace the entire body -- include the full corrected content, not just a diff\n- Prefer `app_url` from the response for user-facing confirmation links\n- Both `CREATE_MESSAGE` and `POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` do the same thing; use CREATE_MESSAGE first and fall back to POST if it fails\n\n### 3. Manage People and Access\n\n**When to use**: User wants to list people, manage project access, or add new users\n\n**Tool sequence**:\n1. `BASECAMP_GET_PEOPLE` - List all people visible to the current user [Required]\n2. `BASECAMP_GET_PROJECTS` - Find the target project [Prerequisite]\n3. `BASECAMP_LIST_PROJECT_PEOPLE` - List people on a specific project [Required]\n4. `BASECAMP_GET_PROJECTS_PEOPLE` - Alternative to list project members [Alternative]\n5. `BASECAMP_PUT_PROJECTS_PEOPLE_USERS` - Grant or revoke project access [Required for access changes]\n\n**Key parameters for PUT_PROJECTS_PEOPLE_USERS**:\n- `project_id`: Integer project ID\n- `grant`: Array of integer person IDs to add to the project\n- `revoke`: Array of integer person IDs to remove from the project\n- `create`: Array of objects with `name`, `email_address`, and optional `company_name`, `title` for new users\n- At least one of `grant`, `revoke`, or `create` must be provided\n\n**Pitfalls**:\n- Person IDs are integers; always resolve names to IDs via GET_PEOPLE first\n- `project_id` for people management is the same as `bucket_id` for other operations\n- `LIST_PROJECT_PEOPLE` and `GET_PROJECTS_PEOPLE` are near-identical; use either\n- Creating users via `create` also grants them project access in one step\n\n### 4. Organize To-Dos with Groups\n\n**When to use**: User wants to organize to-dos within a list into color-coded groups\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - Find the target project [Prerequisite]\n2. `BASECAMP_GET_BUCKETS_TODOLISTS` - Get the to-do list details [Prerequisite]\n3. `BASECAMP_GET_TODOLIST_GROUPS` - List existing groups in a to-do list [Optional]\n4. `BASECAMP_GET_BUCKETS_TODOLISTS_GROUPS` - Alternative group listing [Alternative]\n5. `BASECAMP_POST_BUCKETS_TODOLISTS_GROUPS` - Create a new group in a to-do list [Required]\n6. `BASECAMP_CREATE_TODOLIST_GROUP` - Alternative group creation tool [Alternative]\n\n**Key parameters**:\n- `bucket_id`: Integer project\u002Fbucket ID\n- `todolist_id`: Integer to-do list ID\n- `name`: Group title (required)\n- `color`: Visual color identifier -- one of: `white`, `red`, `orange`, `yellow`, `green`, `blue`, `aqua`, `purple`, `gray`, `pink`, `brown`\n- `status`: Filter for listing -- `\"archived\"` or `\"trashed\"` (omit for active groups)\n\n**Pitfalls**:\n- `POST_BUCKETS_TODOLISTS_GROUPS` and `CREATE_TODOLIST_GROUP` are near-identical; use either\n- Color values must be from the fixed palette; arbitrary hex\u002Frgb values are not supported\n- Groups are sub-sections within a to-do list, not standalone entities\n\n### 5. Browse and Inspect Projects\n\n**When to use**: User wants to list projects, get project details, or explore project structure\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - List all active projects [Required]\n2. `BASECAMP_GET_PROJECT` - Get comprehensive details for a specific project [Optional]\n3. `BASECAMP_GET_PROJECTS_BY_PROJECT_ID` - Alternative project detail retrieval [Alternative]\n\n**Key parameters**:\n- `status`: Filter by `\"archived\"` or `\"trashed\"`; omit for active projects\n- `project_id`: Integer project ID for detailed retrieval\n\n**Pitfalls**:\n- Projects are sorted by most recently created first\n- The response includes a `dock` array with tools (todoset, message_board, etc.) and their IDs\n- Use the dock tool IDs to find `todoset_id`, `message_board_id`, etc. for downstream operations\n\n## Common Patterns\n\n### ID Resolution\nBasecamp uses a hierarchical ID structure. Always resolve top-down:\n- **Project (bucket_id)**: `BASECAMP_GET_PROJECTS` -- find by name, capture the `id`\n- **To-do set (todoset_id)**: Found in project dock or via `BASECAMP_GET_BUCKETS_TODOSETS`\n- **Message board (message_board_id)**: Found in project dock or via `BASECAMP_GET_MESSAGE_BOARD`\n- **To-do list (todolist_id)**: `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS`\n- **People (person_id)**: `BASECAMP_GET_PEOPLE` or `BASECAMP_LIST_PROJECT_PEOPLE`\n- Note: `bucket_id` and `project_id` refer to the same entity in different contexts\n\n### Pagination\nBasecamp uses page-based pagination on list endpoints:\n- Response headers or body may indicate more pages available\n- `GET_PROJECTS`, `GET_BUCKETS_TODOSETS_TODOLISTS`, and list endpoints return paginated results\n- Continue fetching until no more results are returned\n\n### Content Formatting\n- All rich text fields use HTML, not Markdown\n- Wrap content in `\u003Cdiv>` tags; use `\u003Cstrong>`, `\u003Cem>`, `\u003Cul>`, `\u003Col>`, `\u003Cli>`, `\u003Ca>` etc.\n- Example: `\u003Cdiv>\u003Cstrong>Important:\u003C\u002Fstrong> Complete by Friday\u003C\u002Fdiv>`\n\n## Known Pitfalls\n\n### ID Formats\n- All Basecamp IDs are integers, not strings or UUIDs\n- `bucket_id` = `project_id` (same entity, different parameter names across tools)\n- To-do set IDs, to-do list IDs, and message board IDs are found in the project's `dock` array\n- Person IDs are integers; resolve names via `GET_PEOPLE` before operations\n\n### Status Field\n- `status=\"draft\"` for messages can cause HTTP 400; always use `status=\"active\"`\n- Project\u002Fto-do list status filters: `\"archived\"`, `\"trashed\"`, or omit for active\n\n### Content Format\n- HTML only, never Markdown\n- Updates replace the entire body, not a partial diff\n- Invalid HTML tags may be silently stripped\n\n### Rate Limits\n- Basecamp API has rate limits; space out rapid sequential requests\n- Large projects with many to-dos should be paginated carefully\n\n### URL Handling\n- Prefer `app_url` from API responses for user-facing links\n- Do not reconstruct Basecamp URLs manually from IDs\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | `BASECAMP_GET_PROJECTS` | `status` |\n| Get project | `BASECAMP_GET_PROJECT` | `project_id` |\n| Get project detail | `BASECAMP_GET_PROJECTS_BY_PROJECT_ID` | `project_id` |\n| Get to-do set | `BASECAMP_GET_BUCKETS_TODOSETS` | `bucket_id`, `todoset_id` |\n| List to-do lists | `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS` | `bucket_id`, `todoset_id` |\n| Get to-do list | `BASECAMP_GET_BUCKETS_TODOLISTS` | `bucket_id`, `todolist_id` |\n| Create to-do list | `BASECAMP_POST_BUCKETS_TODOSETS_TODOLISTS` | `bucket_id`, `todoset_id`, `name` |\n| Create to-do | `BASECAMP_POST_BUCKETS_TODOLISTS_TODOS` | `bucket_id`, `todolist_id`, `content` |\n| Create to-do (alt) | `BASECAMP_CREATE_TODO` | `bucket_id`, `todolist_id`, `content` |\n| List to-dos | `BASECAMP_GET_BUCKETS_TODOLISTS_TODOS` | `bucket_id`, `todolist_id` |\n| List to-do groups | `BASECAMP_GET_TODOLIST_GROUPS` | `bucket_id`, `todolist_id` |\n| Create to-do group | `BASECAMP_POST_BUCKETS_TODOLISTS_GROUPS` | `bucket_id`, `todolist_id`, `name`, `color` |\n| Create to-do group (alt) | `BASECAMP_CREATE_TODOLIST_GROUP` | `bucket_id`, `todolist_id`, `name` |\n| Get message board | `BASECAMP_GET_MESSAGE_BOARD` | `bucket_id`, `message_board_id` |\n| Create message | `BASECAMP_CREATE_MESSAGE` | `bucket_id`, `message_board_id`, `subject`, `status` |\n| Create message (alt) | `BASECAMP_POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` | `bucket_id`, `message_board_id`, `subject` |\n| Get message | `BASECAMP_GET_MESSAGE` | `bucket_id`, `message_id` |\n| Update message | `BASECAMP_PUT_BUCKETS_MESSAGES` | `bucket_id`, `message_id` |\n| List all people | `BASECAMP_GET_PEOPLE` | (none) |\n| List project people | `BASECAMP_LIST_PROJECT_PEOPLE` | `project_id` |\n| Manage access | `BASECAMP_PUT_PROJECTS_PEOPLE_USERS` | `project_id`, `grant`, `revoke`, `create` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Example\n\n**User request:**\n\n> Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio).\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Basecamp Automation via Rube MCP\n\nAutomate Basecamp operations including project management, to-do list creation, task management, message board posting, people management, and to-do group organization through Composio's Basecamp toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Basecamp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `basecamp`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `basecamp`\n3. If connection is not ACTIVE, follow the returned auth link to complete Basecamp OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage To-Do Lists and Tasks\n\n**When to use**: User wants to create to-do lists, add tasks, or organize work within a Basecamp project\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - List projects to find the target bucket_id [Prerequisite]\n2. `BASECAMP_GET_BUCKETS_TODOSETS` - Get the to-do set within a project [Prerequisite]\n3. `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS` - List existing to-do lists to avoid duplicates [Optional]\n4. `BASECAMP_POST_BUCKETS_TODOSETS_TODOLISTS` - Create a new to-do list in a to-do set [Required for list creation]\n5. `BASECAMP_GET_BUCKETS_TODOLISTS` - Get details of a specific to-do list [Optional]\n6. `BASECAMP_POST_BUCKETS_TODOLISTS_TODOS` - Create a to-do item in a to-do list [Required for task creation]\n7. `BASECAMP_CREATE_TODO` - Alternative tool for creating individual to-dos [Alternative]\n8. `BASECAMP_GET_BUCKETS_TODOLISTS_TODOS` - List to-dos within a to-do list [Optional]\n\n**Key parameters for creating to-do lists**:\n- `bucket_id`: Integer project\u002Fbucket ID (from GET_PROJECTS)\n- `todoset_id`: Integer to-do set ID (from GET_BUCKETS_TODOSETS)\n- `name`: Title of the to-do list (required)\n- `description`: HTML-formatted description (supports Rich text)\n\n**Key parameters for creating to-dos**:\n- `bucket_id`: Integer project\u002Fbucket ID\n- `todolist_id`: Integer to-do list ID\n- `content`: What the to-do is for (required)\n- `description`: HTML details about the to-do\n- `assignee_ids`: Array of integer person IDs\n- `due_on`: Due date in `YYYY-MM-DD` format\n- `starts_on`: Start date in `YYYY-MM-DD` format\n- `notify`: Boolean to notify assignees (defaults to false)\n- `completion_subscriber_ids`: Person IDs notified upon completion\n\n**Pitfalls**:\n- A project (bucket) can contain multiple to-do sets; selecting the wrong `todoset_id` creates lists in the wrong section\n- Always check existing to-do lists before creating to avoid near-duplicate names\n- Success payloads include user-facing URLs (`app_url`, `app_todos_url`); prefer returning these over raw IDs\n- All IDs (`bucket_id`, `todoset_id`, `todolist_id`) are integers, not strings\n- Descriptions support HTML formatting only, not Markdown\n\n### 2. Post and Manage Messages\n\n**When to use**: User wants to post messages to a project message board or update existing messages\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - Find the target project and bucket_id [Prerequisite]\n2. `BASECAMP_GET_MESSAGE_BOARD` - Get the message board ID for the project [Prerequisite]\n3. `BASECAMP_CREATE_MESSAGE` - Create a new message on the board [Required]\n4. `BASECAMP_POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` - Alternative message creation tool [Fallback]\n5. `BASECAMP_GET_MESSAGE` - Read a specific message by ID [Optional]\n6. `BASECAMP_PUT_BUCKETS_MESSAGES` - Update an existing message [Optional]\n\n**Key parameters**:\n- `bucket_id`: Integer project\u002Fbucket ID\n- `message_board_id`: Integer message board ID (from GET_MESSAGE_BOARD)\n- `subject`: Message title (required)\n- `content`: HTML body of the message\n- `status`: Set to `\"active\"` to publish immediately\n- `category_id`: Message type classification (optional)\n- `subscriptions`: Array of person IDs to notify; omit to notify all project members\n\n**Pitfalls**:\n- `status=\"draft\"` can produce HTTP 400; use `status=\"active\"` as the reliable option\n- `bucket_id` and `message_board_id` must belong to the same project; mismatches fail or misroute\n- Message content supports HTML tags only; not Markdown\n- Updates via `PUT_BUCKETS_MESSAGES` replace the entire body -- include the full corrected content, not just a diff\n- Prefer `app_url` from the response for user-facing confirmation links\n- Both `CREATE_MESSAGE` and `POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` do the same thing; use CREATE_MESSAGE first and fall back to POST if it fails\n\n### 3. Manage People and Access\n\n**When to use**: User wants to list people, manage project access, or add new users\n\n**Tool sequence**:\n1. `BASECAMP_GET_PEOPLE` - List all people visible to the current user [Required]\n2. `BASECAMP_GET_PROJECTS` - Find the target project [Prerequisite]\n3. `BASECAMP_LIST_PROJECT_PEOPLE` - List people on a specific project [Required]\n4. `BASECAMP_GET_PROJECTS_PEOPLE` - Alternative to list project members [Alternative]\n5. `BASECAMP_PUT_PROJECTS_PEOPLE_USERS` - Grant or revoke project access [Required for access changes]\n\n**Key parameters for PUT_PROJECTS_PEOPLE_USERS**:\n- `project_id`: Integer project ID\n- `grant`: Array of integer person IDs to add to the project\n- `revoke`: Array of integer person IDs to remove from the project\n- `create`: Array of objects with `name`, `email_address`, and optional `company_name`, `title` for new users\n- At least one of `grant`, `revoke`, or `create` must be provided\n\n**Pitfalls**:\n- Person IDs are integers; always resolve names to IDs via GET_PEOPLE first\n- `project_id` for people management is the same as `bucket_id` for other operations\n- `LIST_PROJECT_PEOPLE` and `GET_PROJECTS_PEOPLE` are near-identical; use either\n- Creating users via `create` also grants them project access in one step\n\n### 4. Organize To-Dos with Groups\n\n**When to use**: User wants to organize to-dos within a list into color-coded groups\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - Find the target project [Prerequisite]\n2. `BASECAMP_GET_BUCKETS_TODOLISTS` - Get the to-do list details [Prerequisite]\n3. `BASECAMP_GET_TODOLIST_GROUPS` - List existing groups in a to-do list [Optional]\n4. `BASECAMP_GET_BUCKETS_TODOLISTS_GROUPS` - Alternative group listing [Alternative]\n5. `BASECAMP_POST_BUCKETS_TODOLISTS_GROUPS` - Create a new group in a to-do list [Required]\n6. `BASECAMP_CREATE_TODOLIST_GROUP` - Alternative group creation tool [Alternative]\n\n**Key parameters**:\n- `bucket_id`: Integer project\u002Fbucket ID\n- `todolist_id`: Integer to-do list ID\n- `name`: Group title (required)\n- `color`: Visual color identifier -- one of: `white`, `red`, `orange`, `yellow`, `green`, `blue`, `aqua`, `purple`, `gray`, `pink`, `brown`\n- `status`: Filter for listing -- `\"archived\"` or `\"trashed\"` (omit for active groups)\n\n**Pitfalls**:\n- `POST_BUCKETS_TODOLISTS_GROUPS` and `CREATE_TODOLIST_GROUP` are near-identical; use either\n- Color values must be from the fixed palette; arbitrary hex\u002Frgb values are not supported\n- Groups are sub-sections within a to-do list, not standalone entities\n\n### 5. Browse and Inspect Projects\n\n**When to use**: User wants to list projects, get project details, or explore project structure\n\n**Tool sequence**:\n1. `BASECAMP_GET_PROJECTS` - List all active projects [Required]\n2. `BASECAMP_GET_PROJECT` - Get comprehensive details for a specific project [Optional]\n3. `BASECAMP_GET_PROJECTS_BY_PROJECT_ID` - Alternative project detail retrieval [Alternative]\n\n**Key parameters**:\n- `status`: Filter by `\"archived\"` or `\"trashed\"`; omit for active projects\n- `project_id`: Integer project ID for detailed retrieval\n\n**Pitfalls**:\n- Projects are sorted by most recently created first\n- The response includes a `dock` array with tools (todoset, message_board, etc.) and their IDs\n- Use the dock tool IDs to find `todoset_id`, `message_board_id`, etc. for downstream operations\n\n## Common Patterns\n\n### ID Resolution\nBasecamp uses a hierarchical ID structure. Always resolve top-down:\n- **Project (bucket_id)**: `BASECAMP_GET_PROJECTS` -- find by name, capture the `id`\n- **To-do set (todoset_id)**: Found in project dock or via `BASECAMP_GET_BUCKETS_TODOSETS`\n- **Message board (message_board_id)**: Found in project dock or via `BASECAMP_GET_MESSAGE_BOARD`\n- **To-do list (todolist_id)**: `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS`\n- **People (person_id)**: `BASECAMP_GET_PEOPLE` or `BASECAMP_LIST_PROJECT_PEOPLE`\n- Note: `bucket_id` and `project_id` refer to the same entity in different contexts\n\n### Pagination\nBasecamp uses page-based pagination on list endpoints:\n- Response headers or body may indicate more pages available\n- `GET_PROJECTS`, `GET_BUCKETS_TODOSETS_TODOLISTS`, and list endpoints return paginated results\n- Continue fetching until no more results are returned\n\n### Content Formatting\n- All rich text fields use HTML, not Markdown\n- Wrap content in `\u003Cdiv>` tags; use `\u003Cstrong>`, `\u003Cem>`, `\u003Cul>`, `\u003Col>`, `\u003Cli>`, `\u003Ca>` etc.\n- Example: `\u003Cdiv>\u003Cstrong>Important:\u003C\u002Fstrong> Complete by Friday\u003C\u002Fdiv>`\n\n## Known Pitfalls\n\n### ID Formats\n- All Basecamp IDs are integers, not strings or UUIDs\n- `bucket_id` = `project_id` (same entity, different parameter names across tools)\n- To-do set IDs, to-do list IDs, and message board IDs are found in the project's `dock` array\n- Person IDs are integers; resolve names via `GET_PEOPLE` before operations\n\n### Status Field\n- `status=\"draft\"` for messages can cause HTTP 400; always use `status=\"active\"`\n- Project\u002Fto-do list status filters: `\"archived\"`, `\"trashed\"`, or omit for active\n\n### Content Format\n- HTML only, never Markdown\n- Updates replace the entire body, not a partial diff\n- Invalid HTML tags may be silently stripped\n\n### Rate Limits\n- Basecamp API has rate limits; space out rapid sequential requests\n- Large projects with many to-dos should be paginated carefully\n\n### URL Handling\n- Prefer `app_url` from API responses for user-facing links\n- Do not reconstruct Basecamp URLs manually from IDs\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List projects | `BASECAMP_GET_PROJECTS` | `status` |\n| Get project | `BASECAMP_GET_PROJECT` | `project_id` |\n| Get project detail | `BASECAMP_GET_PROJECTS_BY_PROJECT_ID` | `project_id` |\n| Get to-do set | `BASECAMP_GET_BUCKETS_TODOSETS` | `bucket_id`, `todoset_id` |\n| List to-do lists | `BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS` | `bucket_id`, `todoset_id` |\n| Get to-do list | `BASECAMP_GET_BUCKETS_TODOLISTS` | `bucket_id`, `todolist_id` |\n| Create to-do list | `BASECAMP_POST_BUCKETS_TODOSETS_TODOLISTS` | `bucket_id`, `todoset_id`, `name` |\n| Create to-do | `BASECAMP_POST_BUCKETS_TODOLISTS_TODOS` | `bucket_id`, `todolist_id`, `content` |\n| Create to-do (alt) | `BASECAMP_CREATE_TODO` | `bucket_id`, `todolist_id`, `content` |\n| List to-dos | `BASECAMP_GET_BUCKETS_TODOLISTS_TODOS` | `bucket_id`, `todolist_id` |\n| List to-do groups | `BASECAMP_GET_TODOLIST_GROUPS` | `bucket_id`, `todolist_id` |\n| Create to-do group | `BASECAMP_POST_BUCKETS_TODOLISTS_GROUPS` | `bucket_id`, `todolist_id`, `name`, `color` |\n| Create to-do group (alt) | `BASECAMP_CREATE_TODOLIST_GROUP` | `bucket_id`, `todolist_id`, `name` |\n| Get message board | `BASECAMP_GET_MESSAGE_BOARD` | `bucket_id`, `message_board_id` |\n| Create message | `BASECAMP_CREATE_MESSAGE` | `bucket_id`, `message_board_id`, `subject`, `status` |\n| Create message (alt) | `BASECAMP_POST_BUCKETS_MESSAGE_BOARDS_MESSAGES` | `bucket_id`, `message_board_id`, `subject` |\n| Get message | `BASECAMP_GET_MESSAGE` | `bucket_id`, `message_id` |\n| Update message | `BASECAMP_PUT_BUCKETS_MESSAGES` | `bucket_id`, `message_id` |\n| List all people | `BASECAMP_GET_PEOPLE` | (none) |\n| List project people | `BASECAMP_LIST_PROJECT_PEOPLE` | `project_id` |\n| Manage access | `BASECAMP_PUT_PROJECTS_PEOPLE_USERS` | `project_id`, `grant`, `revoke`, `create` |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Example\n\n**User request:**\n\n> Automate Basecamp project management, to-dos, messages, people, and to-do list organization via Rube MCP (Composio).\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fbasecamp-automation",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill basecamp-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill basecamp-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill basecamp-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbasecamp-automation\u002FSKILL.md",true,[],[50,58,63,70,77,84],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":57},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":59,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":57},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":57},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":57},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":57},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":57},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]