skill-library-mcp 1.0.0

package/skills/claude-scientific-skills/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: claude-scientific-skills
+description: "Scientific research and analysis skills"
+source: "https://github.com/K-Dense-AI/claude-scientific-skills"
+risk: safe
+---
+
+# Claude Scientific Skills
+
+## Overview
+
+Scientific research and analysis skills
+
+## When to Use This Skill
+
+Use this skill when you need to work with scientific research and analysis skills.
+
+## Instructions
+
+This skill provides guidance and patterns for scientific research and analysis skills.
+
+For more information, see the [source repository](https://github.com/K-Dense-AI/claude-scientific-skills).

package/skills/claude-speed-reader/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: claude-speed-reader
+description: "-Speed read Claude's responses at 600+ WPM using RSVP with Spritz-style ORP highlighting"
+source: "https://github.com/SeanZoR/claude-speed-reader"
+risk: safe
+---
+
+# Claude Speed Reader
+
+## Overview
+
+-Speed read Claude's responses at 600+ WPM using RSVP with Spritz-style ORP highlighting
+
+## When to Use This Skill
+
+Use this skill when you need to work with -speed read claude's responses at 600+ wpm using rsvp with spritz-style orp highlighting.
+
+## Instructions
+
+This skill provides guidance and patterns for -speed read claude's responses at 600+ wpm using rsvp with spritz-style orp highlighting.
+
+For more information, see the [source repository](https://github.com/SeanZoR/claude-speed-reader).

package/skills/claude-win11-speckit-update-skill/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: claude-win11-speckit-update-skill
+description: "Windows 11 system management"
+source: "https://github.com/NotMyself/claude-win11-speckit-update-skill"
+risk: safe
+---
+
+# Claude Win11 Speckit Update Skill
+
+## Overview
+
+Windows 11 system management
+
+## When to Use This Skill
+
+Use this skill when you need to work with windows 11 system management.
+
+## Instructions
+
+This skill provides guidance and patterns for windows 11 system management.
+
+For more information, see the [source repository](https://github.com/NotMyself/claude-win11-speckit-update-skill).

package/skills/clean-code/SKILL.md

@@ -0,0 +1,94 @@
+---
+name: clean-code
+description: "Applies principles from Robert C. Martin's 'Clean Code'. Use this skill when writing, reviewing, or refactoring code to ensure high quality, readability, and maintainability. Covers naming, functions, comments, error handling, and class design."
+user-invocable: true
+risk: safe
+source: "ClawForge (https://github.com/jackjin1997/ClawForge)"
+---
+
+# Clean Code Skill
+
+This skill embodies the principles of "Clean Code" by Robert C. Martin (Uncle Bob). Use it to transform "code that works" into "code that is clean."
+
+## 🧠 Core Philosophy
+> "Code is clean if it can be read, and enhanced by a developer other than its original author." — Grady Booch
+
+## When to Use
+Use this skill when:
+- **Writing new code**: To ensure high quality from the start.
+- **Reviewing Pull Requests**: To provide constructive, principle-based feedback.
+- **Refactoring legacy code**: To identify and remove code smells.
+- **Improving team standards**: To align on industry-standard best practices.
+
+## 1. Meaningful Names
+- **Use Intention-Revealing Names**: `elapsedTimeInDays` instead of `d`.
+- **Avoid Disinformation**: Don't use `accountList` if it's actually a `Map`.
+- **Make Meaningful Distinctions**: Avoid `ProductData` vs `ProductInfo`.
+- **Use Pronounceable/Searchable Names**: Avoid `genymdhms`.
+- **Class Names**: Use nouns (`Customer`, `WikiPage`). Avoid `Manager`, `Data`.
+- **Method Names**: Use verbs (`postPayment`, `deletePage`).
+
+## 2. Functions
+- **Small!**: Functions should be shorter than you think.
+- **Do One Thing**: A function should do only one thing, and do it well.
+- **One Level of Abstraction**: Don't mix high-level business logic with low-level details (like regex).
+- **Descriptive Names**: `isPasswordValid` is better than `check`.
+- **Arguments**: 0 is ideal, 1-2 is okay, 3+ requires a very strong justification.
+- **No Side Effects**: Functions shouldn't secretly change global state.
+
+## 3. Comments
+- **Don't Comment Bad Code—Rewrite It**: Most comments are a sign of failure to express ourselves in code.
+- **Explain Yourself in Code**: 
+  ```python
+  # Check if employee is eligible for full benefits
+  if employee.flags & HOURLY and employee.age > 65:
+  ```
+  vs
+  ```python
+  if employee.isEligibleForFullBenefits():
+  ```
+- **Good Comments**: Legal, Informative (regex intent), Clarification (external libraries), TODOs.
+- **Bad Comments**: Mumbling, Redundant, Misleading, Mandated, Noise, Position Markers.
+
+## 4. Formatting
+- **The Newspaper Metaphor**: High-level concepts at the top, details at the bottom.
+- **Vertical Density**: Related lines should be close to each other.
+- **Distance**: Variables should be declared near their usage.
+- **Indentation**: Essential for structural readability.
+
+## 5. Objects and Data Structures
+- **Data Abstraction**: Hide the implementation behind interfaces.
+- **The Law of Demeter**: A module should not know about the innards of the objects it manipulates. Avoid `a.getB().getC().doSomething()`.
+- **Data Transfer Objects (DTO)**: Classes with public variables and no functions.
+
+## 6. Error Handling
+- **Use Exceptions instead of Return Codes**: Keeps logic clean.
+- **Write Try-Catch-Finally First**: Defines the scope of the operation.
+- **Don't Return Null**: It forces the caller to check for null every time.
+- **Don't Pass Null**: Leads to `NullPointerException`.
+
+## 7. Unit Tests
+- **The Three Laws of TDD**:
+  1. Don't write production code until you have a failing unit test.
+  2. Don't write more of a unit test than is sufficient to fail.
+  3. Don't write more production code than is sufficient to pass the failing test.
+- **F.I.R.S.T. Principles**: Fast, Independent, Repeatable, Self-Validating, Timely.
+
+## 8. Classes
+- **Small!**: Classes should have a single responsibility (SRP).
+- **The Stepdown Rule**: We want the code to read like a top-down narrative.
+
+## 9. Smells and Heuristics
+- **Rigidity**: Hard to change.
+- **Fragility**: Breaks in many places.
+- **Immobility**: Hard to reuse.
+- **Viscosity**: Hard to do the right thing.
+- **Needless Complexity/Repetition**.
+
+## 🛠️ Implementation Checklist
+- [ ] Is this function smaller than 20 lines?
+- [ ] Does this function do exactly one thing?
+- [ ] Are all names searchable and intention-revealing?
+- [ ] Have I avoided comments by making the code clearer?
+- [ ] Am I passing too many arguments?
+- [ ] Is there a failing test for this change?

package/skills/clerk-auth/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: clerk-auth
+description: "Expert patterns for Clerk auth implementation, middleware, organizations, webhooks, and user sync Use when: adding authentication, clerk auth, user authentication, sign in, sign up."
+source: vibeship-spawner-skills (Apache 2.0)
+---
+
+# Clerk Authentication
+
+## Patterns
+
+### Next.js App Router Setup
+
+Complete Clerk setup for Next.js 14/15 App Router.
+
+Includes ClerkProvider, environment variables, and basic
+sign-in/sign-up components.
+
+Key components:
+- ClerkProvider: Wraps app for auth context
+- <SignIn />, <SignUp />: Pre-built auth forms
+- <UserButton />: User menu with session management
+
+
+### Middleware Route Protection
+
+Protect routes using clerkMiddleware and createRouteMatcher.
+
+Best practices:
+- Single middleware.ts file at project root
+- Use createRouteMatcher for route groups
+- auth.protect() for explicit protection
+- Centralize all auth logic in middleware
+
+
+### Server Component Authentication
+
+Access auth state in Server Components using auth() and currentUser().
+
+Key functions:
+- auth(): Returns userId, sessionId, orgId, claims
+- currentUser(): Returns full User object
+- Both require clerkMiddleware to be configured
+
+
+## ⚠️ Sharp Edges
+
+| Issue | Severity | Solution |
+|-------|----------|----------|
+| Issue | critical | See docs |
+| Issue | high | See docs |
+| Issue | high | See docs |
+| Issue | high | See docs |
+| Issue | medium | See docs |
+| Issue | medium | See docs |
+| Issue | medium | See docs |
+| Issue | medium | See docs |

package/skills/clickup-automation/SKILL.md

@@ -0,0 +1,234 @@
+---
+name: clickup-automation
+description: "Automate ClickUp project management including tasks, spaces, folders, lists, comments, and team operations via Rube MCP (Composio). Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# ClickUp Automation via Rube MCP
+
+Automate ClickUp project management workflows including task creation and updates, workspace hierarchy navigation, comments, and team member management through Composio's ClickUp toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active ClickUp connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `clickup`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `clickup`
+3. If connection is not ACTIVE, follow the returned auth link to complete ClickUp OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Tasks
+
+**When to use**: User wants to create tasks, subtasks, update task properties, or list tasks in a ClickUp list.
+
+**Tool sequence**:
+1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - Get workspace/team IDs [Prerequisite]
+2. `CLICKUP_GET_SPACES` - List spaces in the workspace [Prerequisite]
+3. `CLICKUP_GET_FOLDERS` - List folders in a space [Prerequisite]
+4. `CLICKUP_GET_FOLDERLESS_LISTS` - Get lists not inside folders [Optional]
+5. `CLICKUP_GET_LIST` - Validate list and check available statuses [Prerequisite]
+6. `CLICKUP_CREATE_TASK` - Create a task in the target list [Required]
+7. `CLICKUP_CREATE_TASK` (with `parent`) - Create subtask under a parent task [Optional]
+8. `CLICKUP_UPDATE_TASK` - Modify task status, assignees, dates, priority [Optional]
+9. `CLICKUP_GET_TASK` - Retrieve full task details [Optional]
+10. `CLICKUP_GET_TASKS` - List all tasks in a list with filters [Optional]
+11. `CLICKUP_DELETE_TASK` - Permanently remove a task [Optional]
+
+**Key parameters for CLICKUP_CREATE_TASK**:
+- `list_id`: Target list ID (integer, required)
+- `name`: Task name (string, required)
+- `description`: Detailed task description
+- `status`: Must exactly match (case-sensitive) a status name configured in the target list
+- `priority`: 1 (Urgent), 2 (High), 3 (Normal), 4 (Low)
+- `assignees`: Array of user IDs (integers)
+- `due_date`: Unix timestamp in milliseconds
+- `parent`: Parent task ID string for creating subtasks
+- `tags`: Array of tag name strings
+- `time_estimate`: Estimated time in milliseconds
+
+**Pitfalls**:
+- `status` is case-sensitive and must match an existing status in the list; use `CLICKUP_GET_LIST` to check available statuses
+- `due_date` and `start_date` are Unix timestamps in **milliseconds**, not seconds
+- Subtask `parent` must be a task (not another subtask) in the same list
+- `notify_all` triggers watcher notifications; set to false for bulk operations
+- Retries can create duplicates; track created task IDs to avoid re-creation
+- `custom_item_id` for milestones (ID 1) is subject to workspace plan quotas
+
+### 2. Navigate Workspace Hierarchy
+
+**When to use**: User wants to browse or manage the ClickUp workspace structure (Workspaces > Spaces > Folders > Lists).
+
+**Tool sequence**:
+1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - List all accessible workspaces [Required]
+2. `CLICKUP_GET_SPACES` - List spaces within a workspace [Required]
+3. `CLICKUP_GET_SPACE` - Get details for a specific space [Optional]
+4. `CLICKUP_GET_FOLDERS` - List folders in a space [Required]
+5. `CLICKUP_GET_FOLDER` - Get details for a specific folder [Optional]
+6. `CLICKUP_CREATE_FOLDER` - Create a new folder in a space [Optional]
+7. `CLICKUP_GET_FOLDERLESS_LISTS` - List lists not inside any folder [Required]
+8. `CLICKUP_GET_LIST` - Get list details including statuses and custom fields [Optional]
+
+**Key parameters**:
+- `team_id`: Workspace ID from GET_AUTHORIZED_TEAMS_WORKSPACES (required for spaces)
+- `space_id`: Space ID (required for folders and folderless lists)
+- `folder_id`: Folder ID (required for GET_FOLDER)
+- `list_id`: List ID (required for GET_LIST)
+- `archived`: Boolean filter for archived/active items
+
+**Pitfalls**:
+- ClickUp hierarchy is: Workspace (Team) > Space > Folder > List > Task
+- Lists can exist directly under Spaces (folderless) or inside Folders
+- Must use `CLICKUP_GET_FOLDERLESS_LISTS` to find lists not inside folders; `CLICKUP_GET_FOLDERS` only returns folders
+- `team_id` in ClickUp API refers to the Workspace ID, not a user group
+
+### 3. Add Comments to Tasks
+
+**When to use**: User wants to add comments, review existing comments, or manage comment threads on tasks.
+
+**Tool sequence**:
+1. `CLICKUP_GET_TASK` - Verify task exists and get task_id [Prerequisite]
+2. `CLICKUP_CREATE_TASK_COMMENT` - Add a new comment to the task [Required]
+3. `CLICKUP_GET_TASK_COMMENTS` - List existing comments on the task [Optional]
+4. `CLICKUP_UPDATE_COMMENT` - Edit comment text, assignee, or resolution status [Optional]
+
+**Key parameters for CLICKUP_CREATE_TASK_COMMENT**:
+- `task_id`: Task ID string (required)
+- `comment_text`: Comment content with ClickUp formatting support (required)
+- `assignee`: User ID to assign the comment to (required)
+- `notify_all`: true/false for watcher notifications (required)
+
+**Key parameters for CLICKUP_GET_TASK_COMMENTS**:
+- `task_id`: Task ID string (required)
+- `start` / `start_id`: Pagination for older comments (max 25 per page)
+
+**Pitfalls**:
+- `CLICKUP_CREATE_TASK_COMMENT` requires all four fields: `task_id`, `comment_text`, `assignee`, and `notify_all`
+- `assignee` on a comment assigns the comment (not the task) to that user
+- Comments are paginated at 25 per page; use `start` (Unix ms) and `start_id` for older pages
+- `CLICKUP_UPDATE_COMMENT` requires all four fields: `comment_id`, `comment_text`, `assignee`, `resolved`
+
+### 4. Manage Team Members and Assignments
+
+**When to use**: User wants to view workspace members, check seat utilization, or look up user details.
+
+**Tool sequence**:
+1. `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` - List workspaces and get team_id [Required]
+2. `CLICKUP_GET_WORKSPACE_SEATS` - Check seat utilization (members vs guests) [Required]
+3. `CLICKUP_GET_TEAMS` - List user groups within the workspace [Optional]
+4. `CLICKUP_GET_USER` - Get details for a specific user (Enterprise only) [Optional]
+5. `CLICKUP_GET_CUSTOM_ROLES` - List custom permission roles [Optional]
+
+**Key parameters**:
+- `team_id`: Workspace ID (required for all team operations)
+- `user_id`: Specific user ID for GET_USER
+- `group_ids`: Comma-separated group IDs to filter teams
+
+**Pitfalls**:
+- `CLICKUP_GET_WORKSPACE_SEATS` returns seat counts, not member details; distinguish members from guests
+- `CLICKUP_GET_TEAMS` returns user groups, not workspace members; empty groups does not mean no members
+- `CLICKUP_GET_USER` is only available on ClickUp Enterprise Plan
+- Must repeat workspace seat queries for each workspace in multi-workspace setups
+
+### 5. Filter and Query Tasks
+
+**When to use**: User wants to find tasks with specific filters (status, assignee, dates, tags, custom fields).
+
+**Tool sequence**:
+1. `CLICKUP_GET_TASKS` - Filter tasks in a list with multiple criteria [Required]
+2. `CLICKUP_GET_TASK` - Get full details for individual tasks [Optional]
+
+**Key parameters for CLICKUP_GET_TASKS**:
+- `list_id`: List ID (integer, required)
+- `statuses`: Array of status strings to filter by
+- `assignees`: Array of user ID strings
+- `tags`: Array of tag name strings
+- `due_date_gt` / `due_date_lt`: Unix timestamp in ms for date range
+- `include_closed`: Boolean to include closed tasks
+- `subtasks`: Boolean to include subtasks
+- `order_by`: "id", "created", "updated", or "due_date"
+- `page`: Page number starting at 0 (max 100 tasks per page)
+
+**Pitfalls**:
+- Only tasks whose home list matches `list_id` are returned; tasks in sublists are not included
+- Date filters use Unix timestamps in milliseconds
+- Status strings must match exactly; use URL encoding for spaces (e.g., "to%20do")
+- Page numbering starts at 0; each page returns up to 100 tasks
+- `custom_fields` filter accepts an array of JSON strings, not objects
+
+## Common Patterns
+
+### ID Resolution
+Always resolve names to IDs through the hierarchy:
+- **Workspace name -> team_id**: `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` and match by name
+- **Space name -> space_id**: `CLICKUP_GET_SPACES` with `team_id`
+- **Folder name -> folder_id**: `CLICKUP_GET_FOLDERS` with `space_id`
+- **List name -> list_id**: Navigate folders or use `CLICKUP_GET_FOLDERLESS_LISTS`
+- **Task name -> task_id**: `CLICKUP_GET_TASKS` with `list_id` and match by name
+
+### Pagination
+- `CLICKUP_GET_TASKS`: Page-based with `page` starting at 0, max 100 tasks per page
+- `CLICKUP_GET_TASK_COMMENTS`: Uses `start` (Unix ms) and `start_id` for cursor-based paging, max 25 per page
+- Continue fetching until response returns fewer items than the page size
+
+## Known Pitfalls
+
+### ID Formats
+- Workspace/Team IDs are large integers
+- Space, folder, and list IDs are integers
+- Task IDs are alphanumeric strings (e.g., "9hz", "abc123")
+- User IDs are integers
+- Comment IDs are integers
+
+### Rate Limits
+- ClickUp enforces rate limits; bulk task creation can trigger 429 responses
+- Honor `Retry-After` header when present
+- Set `notify_all=false` for bulk operations to reduce notification load
+
+### Parameter Quirks
+- `team_id` in the API means Workspace ID, not a user group
+- `status` on tasks is case-sensitive and list-specific
+- Dates are Unix timestamps in **milliseconds** (multiply seconds by 1000)
+- `priority` is an integer 1-4 (1=Urgent, 4=Low), not a string
+- `CLICKUP_CREATE_TASK_COMMENT` marks `assignee` and `notify_all` as required
+- To clear a task description, pass a single space `" "` to `CLICKUP_UPDATE_TASK`
+
+### Hierarchy Rules
+- Subtask parent must not itself be a subtask
+- Subtask parent must be in the same list
+- Lists can be folderless (directly in a Space) or inside a Folder
+- Subitem boards are not supported by CLICKUP_CREATE_TASK
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List workspaces | `CLICKUP_GET_AUTHORIZED_TEAMS_WORKSPACES` | (none) |
+| List spaces | `CLICKUP_GET_SPACES` | `team_id` |
+| Get space details | `CLICKUP_GET_SPACE` | `space_id` |
+| List folders | `CLICKUP_GET_FOLDERS` | `space_id` |
+| Get folder details | `CLICKUP_GET_FOLDER` | `folder_id` |
+| Create folder | `CLICKUP_CREATE_FOLDER` | `space_id`, `name` |
+| Folderless lists | `CLICKUP_GET_FOLDERLESS_LISTS` | `space_id` |
+| Get list details | `CLICKUP_GET_LIST` | `list_id` |
+| Create task | `CLICKUP_CREATE_TASK` | `list_id`, `name`, `status`, `assignees` |
+| Update task | `CLICKUP_UPDATE_TASK` | `task_id`, `status`, `priority` |
+| Get task | `CLICKUP_GET_TASK` | `task_id`, `include_subtasks` |
+| List tasks | `CLICKUP_GET_TASKS` | `list_id`, `statuses`, `page` |
+| Delete task | `CLICKUP_DELETE_TASK` | `task_id` |
+| Add comment | `CLICKUP_CREATE_TASK_COMMENT` | `task_id`, `comment_text`, `assignee` |
+| List comments | `CLICKUP_GET_TASK_COMMENTS` | `task_id`, `start`, `start_id` |
+| Update comment | `CLICKUP_UPDATE_COMMENT` | `comment_id`, `comment_text`, `resolved` |
+| Workspace seats | `CLICKUP_GET_WORKSPACE_SEATS` | `team_id` |
+| List user groups | `CLICKUP_GET_TEAMS` | `team_id` |
+| Get user details | `CLICKUP_GET_USER` | `team_id`, `user_id` |
+| Custom roles | `CLICKUP_GET_CUSTOM_ROLES` | `team_id` |

package/skills/close-automation/SKILL.md

@@ -0,0 +1,212 @@
+---
+name: close-automation
+description: "Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls/SMS, handle tasks, and track notes. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Close CRM Automation via Rube MCP
+
+Automate Close CRM operations through Composio's Close toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Close connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `close`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `close`
+3. If connection is not ACTIVE, follow the returned auth link to complete Close API authentication
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Leads
+
+**When to use**: User wants to create new leads or manage existing lead records
+
+**Tool sequence**:
+1. `CLOSE_CREATE_LEAD` - Create a new lead in Close [Required]
+
+**Key parameters**:
+- `name`: Lead/company name
+- `contacts`: Array of contact objects associated with the lead
+- `custom`: Custom field values as key-value pairs
+- `status_id`: Lead status ID
+
+**Pitfalls**:
+- Leads in Close represent companies/organizations, not individual people
+- Contacts are nested within leads; create the lead first, then contacts are included
+- Custom field keys use the custom field ID (e.g., 'custom.cf_XXX'), not display names
+- Duplicate lead detection is not automatic; check before creating
+
+### 2. Log Calls
+
+**When to use**: User wants to log a phone call activity against a lead
+
+**Tool sequence**:
+1. `CLOSE_CREATE_CALL` - Log a call activity [Required]
+
+**Key parameters**:
+- `lead_id`: ID of the associated lead
+- `contact_id`: ID of the contact called
+- `direction`: 'outbound' or 'inbound'
+- `status`: Call status ('completed', 'no-answer', 'busy', etc.)
+- `duration`: Call duration in seconds
+- `note`: Call notes
+
+**Pitfalls**:
+- lead_id is required; calls must be associated with a lead
+- Duration is in seconds, not minutes
+- Call direction affects reporting and analytics
+- contact_id is optional but recommended for tracking
+
+### 3. Send SMS Messages
+
+**When to use**: User wants to send or log SMS messages through Close
+
+**Tool sequence**:
+1. `CLOSE_CREATE_SMS` - Send or log an SMS message [Required]
+
+**Key parameters**:
+- `lead_id`: ID of the associated lead
+- `contact_id`: ID of the contact
+- `direction`: 'outbound' or 'inbound'
+- `text`: SMS message content
+- `status`: Message status
+
+**Pitfalls**:
+- SMS functionality requires Close phone/SMS integration to be configured
+- lead_id is required for all SMS activities
+- Outbound SMS may require a verified sending number
+- Message length limits may apply depending on carrier
+
+### 4. Manage Tasks
+
+**When to use**: User wants to create or manage follow-up tasks
+
+**Tool sequence**:
+1. `CLOSE_CREATE_TASK` - Create a new task [Required]
+
+**Key parameters**:
+- `lead_id`: Associated lead ID
+- `text`: Task description
+- `date`: Due date for the task
+- `assigned_to`: User ID of the assignee
+- `is_complete`: Whether the task is completed
+
+**Pitfalls**:
+- Tasks are associated with leads, not contacts
+- Date format should follow ISO 8601
+- assigned_to requires the Close user ID, not email or name
+- Tasks without a date appear in the 'no due date' section
+
+### 5. Manage Notes
+
+**When to use**: User wants to add or retrieve notes on leads
+
+**Tool sequence**:
+1. `CLOSE_GET_NOTE` - Retrieve a specific note [Required]
+
+**Key parameters**:
+- `note_id`: ID of the note to retrieve
+
+**Pitfalls**:
+- Notes are associated with leads
+- Note IDs are required for retrieval; search leads first to find note references
+- Notes support plain text and basic formatting
+
+### 6. Delete Activities
+
+**When to use**: User wants to remove call records or other activities
+
+**Tool sequence**:
+1. `CLOSE_DELETE_CALL` - Delete a call activity [Required]
+
+**Key parameters**:
+- `call_id`: ID of the call to delete
+
+**Pitfalls**:
+- Deletion is permanent and cannot be undone
+- Only the call creator or admin can delete calls
+- Deleting a call removes it from all reports and timelines
+
+## Common Patterns
+
+### Lead and Contact Relationship
+
+```
+Close data model:
+- Lead = Company/Organization
+  - Contact = Person (nested within Lead)
+  - Activity = Call, SMS, Email, Note (linked to Lead)
+  - Task = Follow-up item (linked to Lead)
+  - Opportunity = Deal (linked to Lead)
+```
+
+### ID Resolution
+
+**Lead ID**:
+```
+1. Search for leads using the Close search API
+2. Extract lead_id from results (format: 'lead_XXXXXXXXXXXXX')
+3. Use lead_id in all activity creation calls
+```
+
+**Contact ID**:
+```
+1. Retrieve lead details to get nested contacts
+2. Extract contact_id (format: 'cont_XXXXXXXXXXXXX')
+3. Use in call/SMS activities for accurate tracking
+```
+
+### Activity Logging Pattern
+
+```
+1. Identify the lead_id and optionally contact_id
+2. Create the activity (call, SMS, note) with lead_id
+3. Include relevant metadata (duration, direction, status)
+4. Create follow-up tasks if needed
+```
+
+## Known Pitfalls
+
+**ID Formats**:
+- Lead IDs: 'lead_XXXXXXXXXXXXX'
+- Contact IDs: 'cont_XXXXXXXXXXXXX'
+- Activity IDs vary by type: 'acti_XXXXXXXXXXXXX', 'call_XXXXXXXXXXXXX'
+- Custom field IDs: 'custom.cf_XXXXXXXXXXXXX'
+- Always use the full ID string
+
+**Rate Limits**:
+- Close API has rate limits based on your plan
+- Implement delays between bulk operations
+- Monitor response headers for rate limit status
+- 429 responses require backoff
+
+**Custom Fields**:
+- Custom fields are referenced by their API ID, not display name
+- Different lead statuses may have different required custom fields
+- Custom field types (text, number, date, dropdown) enforce value formats
+
+**Data Integrity**:
+- Leads are the primary entity; contacts and activities are linked to leads
+- Deleting a lead may cascade to its contacts and activities
+- Bulk operations should validate IDs before executing
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create lead | CLOSE_CREATE_LEAD | name, contacts, custom |
+| Log call | CLOSE_CREATE_CALL | lead_id, direction, status, duration |
+| Send SMS | CLOSE_CREATE_SMS | lead_id, text, direction |
+| Create task | CLOSE_CREATE_TASK | lead_id, text, date, assigned_to |
+| Get note | CLOSE_GET_NOTE | note_id |
+| Delete call | CLOSE_DELETE_CALL | call_id |