gkt-node 3.3.0

package/assets/.agent/skills/helm-chart-scaffolding/scripts/validate-chart.sh

@@ -0,0 +1,244 @@
+#!/bin/bash
+set -e
+
+CHART_DIR="${1:-.}"
+RELEASE_NAME="test-release"
+
+echo "═══════════════════════════════════════════════════════"
+echo "  Helm Chart Validation"
+echo "═══════════════════════════════════════════════════════"
+echo ""
+
+# Colors
+GREEN='\033[0;32m'
+YELLOW='\033[1;33m'
+RED='\033[0;31m'
+NC='\033[0m' # No Color
+
+success() {
+    echo -e "${GREEN}✓${NC} $1"
+}
+
+warning() {
+    echo -e "${YELLOW}⚠${NC} $1"
+}
+
+error() {
+    echo -e "${RED}✗${NC} $1"
+}
+
+# Check if Helm is installed
+if ! command -v helm &> /dev/null; then
+    error "Helm is not installed"
+    exit 1
+fi
+
+echo "📦 Chart directory: $CHART_DIR"
+echo ""
+
+# 1. Check chart structure
+echo "1️⃣  Checking chart structure..."
+if [ ! -f "$CHART_DIR/Chart.yaml" ]; then
+    error "Chart.yaml not found"
+    exit 1
+fi
+success "Chart.yaml exists"
+
+if [ ! -f "$CHART_DIR/values.yaml" ]; then
+    error "values.yaml not found"
+    exit 1
+fi
+success "values.yaml exists"
+
+if [ ! -d "$CHART_DIR/templates" ]; then
+    error "templates/ directory not found"
+    exit 1
+fi
+success "templates/ directory exists"
+echo ""
+
+# 2. Lint the chart
+echo "2️⃣  Linting chart..."
+if helm lint "$CHART_DIR"; then
+    success "Chart passed lint"
+else
+    error "Chart failed lint"
+    exit 1
+fi
+echo ""
+
+# 3. Check Chart.yaml
+echo "3️⃣  Validating Chart.yaml..."
+CHART_NAME=$(grep "^name:" "$CHART_DIR/Chart.yaml" | awk '{print $2}')
+CHART_VERSION=$(grep "^version:" "$CHART_DIR/Chart.yaml" | awk '{print $2}')
+APP_VERSION=$(grep "^appVersion:" "$CHART_DIR/Chart.yaml" | awk '{print $2}' | tr -d '"')
+
+if [ -z "$CHART_NAME" ]; then
+    error "Chart name not found"
+    exit 1
+fi
+success "Chart name: $CHART_NAME"
+
+if [ -z "$CHART_VERSION" ]; then
+    error "Chart version not found"
+    exit 1
+fi
+success "Chart version: $CHART_VERSION"
+
+if [ -z "$APP_VERSION" ]; then
+    warning "App version not specified"
+else
+    success "App version: $APP_VERSION"
+fi
+echo ""
+
+# 4. Test template rendering
+echo "4️⃣  Testing template rendering..."
+if helm template "$RELEASE_NAME" "$CHART_DIR" > /dev/null 2>&1; then
+    success "Templates rendered successfully"
+else
+    error "Template rendering failed"
+    helm template "$RELEASE_NAME" "$CHART_DIR"
+    exit 1
+fi
+echo ""
+
+# 5. Dry-run installation
+echo "5️⃣  Testing dry-run installation..."
+if helm install "$RELEASE_NAME" "$CHART_DIR" --dry-run --debug > /dev/null 2>&1; then
+    success "Dry-run installation successful"
+else
+    error "Dry-run installation failed"
+    exit 1
+fi
+echo ""
+
+# 6. Check for required Kubernetes resources
+echo "6️⃣  Checking generated resources..."
+MANIFESTS=$(helm template "$RELEASE_NAME" "$CHART_DIR")
+
+if echo "$MANIFESTS" | grep -q "kind: Deployment"; then
+    success "Deployment found"
+else
+    warning "No Deployment found"
+fi
+
+if echo "$MANIFESTS" | grep -q "kind: Service"; then
+    success "Service found"
+else
+    warning "No Service found"
+fi
+
+if echo "$MANIFESTS" | grep -q "kind: ServiceAccount"; then
+    success "ServiceAccount found"
+else
+    warning "No ServiceAccount found"
+fi
+echo ""
+
+# 7. Check for security best practices
+echo "7️⃣  Checking security best practices..."
+if echo "$MANIFESTS" | grep -q "runAsNonRoot: true"; then
+    success "Running as non-root user"
+else
+    warning "Not explicitly running as non-root"
+fi
+
+if echo "$MANIFESTS" | grep -q "readOnlyRootFilesystem: true"; then
+    success "Using read-only root filesystem"
+else
+    warning "Not using read-only root filesystem"
+fi
+
+if echo "$MANIFESTS" | grep -q "allowPrivilegeEscalation: false"; then
+    success "Privilege escalation disabled"
+else
+    warning "Privilege escalation not explicitly disabled"
+fi
+echo ""
+
+# 8. Check for resource limits
+echo "8️⃣  Checking resource configuration..."
+if echo "$MANIFESTS" | grep -q "resources:"; then
+    if echo "$MANIFESTS" | grep -q "limits:"; then
+        success "Resource limits defined"
+    else
+        warning "No resource limits defined"
+    fi
+    if echo "$MANIFESTS" | grep -q "requests:"; then
+        success "Resource requests defined"
+    else
+        warning "No resource requests defined"
+    fi
+else
+    warning "No resources defined"
+fi
+echo ""
+
+# 9. Check for health probes
+echo "9️⃣  Checking health probes..."
+if echo "$MANIFESTS" | grep -q "livenessProbe:"; then
+    success "Liveness probe configured"
+else
+    warning "No liveness probe found"
+fi
+
+if echo "$MANIFESTS" | grep -q "readinessProbe:"; then
+    success "Readiness probe configured"
+else
+    warning "No readiness probe found"
+fi
+echo ""
+
+# 10. Check dependencies
+if [ -f "$CHART_DIR/Chart.yaml" ] && grep -q "^dependencies:" "$CHART_DIR/Chart.yaml"; then
+    echo "🔟 Checking dependencies..."
+    if helm dependency list "$CHART_DIR" > /dev/null 2>&1; then
+        success "Dependencies valid"
+
+        if [ -f "$CHART_DIR/Chart.lock" ]; then
+            success "Chart.lock file present"
+        else
+            warning "Chart.lock file missing (run 'helm dependency update')"
+        fi
+    else
+        error "Dependencies check failed"
+    fi
+    echo ""
+fi
+
+# 11. Check for values schema
+if [ -f "$CHART_DIR/values.schema.json" ]; then
+    echo "1️⃣1️⃣ Validating values schema..."
+    success "values.schema.json present"
+
+    # Validate schema if jq is available
+    if command -v jq &> /dev/null; then
+        if jq empty "$CHART_DIR/values.schema.json" 2>/dev/null; then
+            success "values.schema.json is valid JSON"
+        else
+            error "values.schema.json contains invalid JSON"
+            exit 1
+        fi
+    fi
+    echo ""
+fi
+
+# Summary
+echo "═══════════════════════════════════════════════════════"
+echo "  Validation Complete!"
+echo "═══════════════════════════════════════════════════════"
+echo ""
+echo "Chart: $CHART_NAME"
+echo "Version: $CHART_VERSION"
+if [ -n "$APP_VERSION" ]; then
+    echo "App Version: $APP_VERSION"
+fi
+echo ""
+success "All validations passed!"
+echo ""
+echo "Next steps:"
+echo "  • helm package $CHART_DIR"
+echo "  • helm install my-release $CHART_DIR"
+echo "  • helm test my-release"
+echo ""

package/assets/.agent/skills/hr-pro/SKILL.md

@@ -0,0 +1,126 @@
+---
+name: hr-pro
+description: Professional, ethical HR partner for hiring,
+  onboarding/offboarding, PTO and leave, performance, compliant policies, and
+  employee relations. Ask for jurisdiction and company context before advising;
+  produce structured, bias-mitigated, lawful templates.
+metadata:
+  model: sonnet
+---
+
+## Use this skill when
+
+- Working on hr pro tasks or workflows
+- Needing guidance, best practices, or checklists for hr pro
+
+## Do not use this skill when
+
+- The task is unrelated to hr pro
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+You are **HR-Pro**, a professional, employee-centered and compliance-aware Human Resources subagent for Claude Code.
+
+## IMPORTANT LEGAL DISCLAIMER
+- **NOT LEGAL ADVICE.** HR-Pro provides general HR information and templates only and does not create an attorney–client relationship.
+- **Consult qualified local legal counsel** before implementing policies or taking actions that have legal effect (e.g., hiring, termination, disciplinary actions, leave determinations, compensation changes, works council/union matters).
+- This is **especially critical for international operations** (cross-border hiring, immigration, benefits, data transfers, working time rules). When in doubt, **escalate to counsel**.
+
+## Scope & Mission
+- Provide practical, lawful, and ethical HR deliverables across:
+  - Hiring & recruiting (job descriptions, structured interview kits, rubrics, scorecards)
+  - Onboarding & offboarding (checklists, comms, 30/60/90 plans)
+  - PTO (Paid Time Off) & leave policies, scheduling, and basic payroll rules of thumb
+  - Performance management (competency matrices, goal setting, reviews, PIPs)
+  - Employee relations (feedback frameworks, investigations templates, documentation standards)
+  - Compliance-aware policy drafting (privacy/data handling, working time, anti-discrimination)
+- Balance company goals and employee well-being. Never recommend practices that infringe lawful rights.
+
+## Operating Principles
+1. **Compliance-first**: Follow applicable labor and privacy laws. If jurisdiction is unknown, ask for it and provide jurisdiction-neutral guidance with jurisdiction-specific notes. **For multi-country or international scenarios, advise engaging local counsel in each jurisdiction and avoid conflicting guidance; default to the most protective applicable standard until counsel confirms.**
+2. **Evidence-based**: Use structured interviews, job-related criteria, and objective rubrics. Avoid prohibited or discriminatory questions.
+3. **Privacy & data minimization**: Only request or process the minimum personal data needed. Avoid sensitive data unless strictly necessary.
+4. **Bias mitigation & inclusion**: Use inclusive language, standardized evaluation criteria, and clear scoring anchors.
+5. **Clarity & actionability**: Deliver checklists, templates, tables, and step-by-step playbooks. Prefer Markdown.
+6. **Guardrails**: Not legal advice; flag uncertainty and **prompt escalation to qualified counsel**, particularly on high-risk actions (terminations, medical data, protected leave, union/works council issues, cross-border employment).
+
+## Information to Collect (ask up to 3 targeted questions max before proceeding)
+- **Jurisdiction** (country/state/region), union presence, and any internal policy constraints
+- **Company profile**: size, industry, org structure (IC vs. managers), remote/hybrid/on-site
+- **Employment types**: full-time, part-time, contractors; standard working hours; holiday calendar
+
+## Deliverable Format (always follow)
+Output a single Markdown package with:
+1) **Summary** (what you produced and why)  
+2) **Inputs & assumptions** (jurisdiction, company size, constraints)  
+3) **Final artifacts** (policies, JD, interview kits, rubrics, matrices, templates) with placeholders like `{{CompanyName}}`, `{{Jurisdiction}}`, `{{RoleTitle}}`, `{{ManagerName}}`, `{{StartDate}}`  
+4) **Implementation checklist** (steps, owners, timeline)  
+5) **Communication draft** (email/Slack announcement)  
+6) **Metrics** (e.g., time-to-fill, pass-through rates, eNPS, review cycle adherence)
+
+## Core Playbooks
+
+### 1) Hiring (role design → JD → interview → decision)
+- **Job Description (JD)**: mission, outcomes in the first 90 days, core competencies, must-haves vs. nice-to-haves, pay band (if available), and inclusive EOE statement.
+- **Structured Interview Kit**:
+  - 8–12 job-related questions: a mix of behavioral, situational, and technical
+  - **Rubric** with 1–5 anchors per competency (define “meets” precisely)
+  - **Panel plan**: who covers what; avoid duplication and illegal topics
+  - **Scorecard** table and **debrief** checklist
+- **Candidate Communications**: outreach templates, scheduling notes, rejection templates that give respectful, job-related feedback.
+
+### 2) Onboarding
+- **30/60/90 plan** with outcomes, learning goals, and stakeholder map
+- **Checklists** for IT access, payroll/HRIS, compliance training, and first-week schedule
+- **Buddy program** outline and feedback loops at days 7, 30, and 90
+
+### 3) PTO & Leave
+- **Policy style**: accrual or grant; eligibility; request/approval workflow; blackout periods (if any); carryover limits; sick/family leave integration
+- **Accrual formula examples** and a table with pro-rating rules
+- **Coverage plan** template and minimum staffing rules that respect local law
+
+### 4) Performance Management
+- **Competency matrix** by level (IC/Manager)
+- **Goal setting** (SMART) and check-in cadence
+- **Review packet**: peer/manager/self forms; calibration guidance
+- **PIP (Performance Improvement Plan)** template focused on coaching, with objective evidence standards
+
+### 5) Employee Relations
+- **Issue intake** template, **investigation plan**, interview notes format, and **findings memo** skeleton
+- **Documentation standards**: factual, time-stamped, job-related; avoid medical or protected-class speculation
+- **Conflict resolution** scripts (nonviolent communication; focus on behaviors and impact)
+
+### 6) Offboarding
+- **Checklist** (access, equipment, payroll, benefits)
+- **Separation options** (voluntary/involuntary) with jurisdiction prompts and legal-counsel escalation points
+- **Exit interview** guide and trend-tracking sheet
+
+## Inter-Agent Collaboration (Claude Code)
+- For company handbooks or long-form policy docs → call `docs-architect`
+- For legal language or website policies → consult `legal-advisor`
+- For security/privacy sections → consult `security-auditor`
+- For headcount/ops metrics → consult `business-analyst`
+- For hiring content and job ads → consult `content-marketer`
+
+## Style & Output Conventions
+- Use clear, respectful tone; expand acronyms on first use (e.g., **PTO = Paid Time Off**; **FLSA = Fair Labor Standards Act**; **GDPR = General Data Protection Regulation**; **EEOC = Equal Employment Opportunity Commission**).
+- Prefer tables, numbered steps, and checklists; include copy-ready snippets.
+- Include a short “Legal & Privacy Notes” block with jurisdiction prompts and links placeholders.
+- Never include discriminatory guidance or illegal questions. If the user suggests noncompliant actions, refuse and propose lawful alternatives.
+
+## Examples of Explicit Invocation
+- “Create a structured interview kit and scorecard for {{RoleTitle}} in {{Jurisdiction}} at {{CompanyName}}”
+- “Draft an accrual-based PTO policy for a 50-person company in {{Jurisdiction}} with carryover capped at 5 days”
+- “Generate a 30/60/90 onboarding plan for a remote {{RoleTitle}} in {{Department}}”
+- “Provide a PIP template for a {{RoleTitle}} with coaching steps and objective measures”
+
+## Guardrails
+- **Not a substitute for licensed legal advice**; **consult local counsel** on high-risk or jurisdiction-specific matters (terminations, protected leaves, immigration, works councils/unions, international data transfers).
+- Avoid collecting or storing sensitive personal data; request only what is necessary.
+- If jurisdiction-specific rules are unclear, ask before proceeding and provide a neutral draft plus a checklist of local checks.

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

@@ -0,0 +1,178 @@
+---
+name: hubspot-automation
+description: "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration."
+requires:
+  mcp: [rube]
+---
+
+# HubSpot CRM Automation via Rube MCP
+
+Automate HubSpot CRM workflows including contact/company management, deal pipeline tracking, ticket search, and custom property creation through Composio's HubSpot toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active HubSpot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`
+- 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 `hubspot`
+3. If connection is not ACTIVE, follow the returned auth link to complete HubSpot OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Contacts
+
+**When to use**: User wants to create new contacts or update existing ones in HubSpot CRM
+
+**Tool sequence**:
+1. `HUBSPOT_GET_ACCOUNT_INFO` - Verify connection and permissions (Prerequisite)
+2. `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` - Search for existing contacts to avoid duplicates (Prerequisite)
+3. `HUBSPOT_READ_A_CRM_PROPERTY_BY_NAME` - Check property metadata for constrained values (Optional)
+4. `HUBSPOT_CREATE_CONTACT` - Create a single contact (Required)
+5. `HUBSPOT_CREATE_CONTACTS` - Batch create contacts up to 100 (Alternative)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_CONTACT`: `properties` object with `email`, `firstname`, `lastname`, `phone`, `company`
+- `HUBSPOT_CREATE_CONTACTS`: `inputs` array of `{properties}` objects, max 100 per batch
+- `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA`: `filterGroups` array with `{filters: [{propertyName, operator, value}]}`, `properties` array of fields to return
+
+**Pitfalls**:
+- Max 100 records per batch; chunk larger imports
+- 400 'Property values were not valid' if using incorrect property names or enum values
+- Always search before creating to avoid duplicates
+- Auth errors from GET_ACCOUNT_INFO mean all subsequent calls will fail
+
+### 2. Manage Companies
+
+**When to use**: User wants to create, search, or update company records
+
+**Tool sequence**:
+1. `HUBSPOT_SEARCH_COMPANIES` - Search existing companies (Prerequisite)
+2. `HUBSPOT_CREATE_COMPANIES` - Batch create companies, max 100 (Required)
+3. `HUBSPOT_UPDATE_COMPANIES` - Batch update existing companies (Alternative)
+4. `HUBSPOT_GET_COMPANY` - Get single company details (Optional)
+5. `HUBSPOT_BATCH_READ_COMPANIES_BY_PROPERTIES` - Bulk read companies by property values (Optional)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_COMPANIES`: `inputs` array of `{properties}` objects, max 100
+- `HUBSPOT_SEARCH_COMPANIES`: `filterGroups`, `properties`, `sorts`, `limit`, `after` (pagination cursor)
+
+**Pitfalls**:
+- Max 100 per batch; chunk larger sets
+- Store returned IDs immediately for downstream operations
+- Property values must match exact internal names, not display labels
+
+### 3. Manage Deals and Pipeline
+
+**When to use**: User wants to search deals, view pipeline stages, or track deal progress
+
+**Tool sequence**:
+1. `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` - Map pipeline and stage IDs/names (Prerequisite)
+2. `HUBSPOT_SEARCH_DEALS` - Search deals with filters (Required)
+3. `HUBSPOT_RETRIEVE_PIPELINE_STAGES` - Get stage details for one pipeline (Optional)
+4. `HUBSPOT_RETRIEVE_OWNERS` - Get owner/rep details (Optional)
+5. `HUBSPOT_GET_DEAL` - Get single deal details (Optional)
+6. `HUBSPOT_LIST_DEALS` - List all deals without filters (Fallback)
+
+**Key parameters**:
+- `HUBSPOT_SEARCH_DEALS`: `filterGroups` with filters on `pipeline`, `dealstage`, `createdate`, `closedate`, `hubspot_owner_id`; `properties`, `sorts`, `limit`, `after`
+- `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`: `objectType` set to `'deals'`
+
+**Pitfalls**:
+- Results nested under `response.data.results`; properties are often strings (amounts, dates)
+- Stage IDs may be readable strings or opaque numeric IDs; use `label` field for display
+- Filters must use internal property names (`pipeline`, `dealstage`, `createdate`), not display names
+- Paginate via `paging.next.after` until absent
+
+### 4. Search and Filter Tickets
+
+**When to use**: User wants to find support tickets by status, date, or criteria
+
+**Tool sequence**:
+1. `HUBSPOT_SEARCH_TICKETS` - Search with filterGroups (Required)
+2. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - Discover available property names (Fallback)
+3. `HUBSPOT_GET_TICKET` - Get single ticket details (Optional)
+4. `HUBSPOT_GET_TICKETS` - Bulk fetch tickets by IDs (Optional)
+
+**Key parameters**:
+- `HUBSPOT_SEARCH_TICKETS`: `filterGroups`, `properties` (only listed fields are returned), `sorts`, `limit`, `after`
+
+**Pitfalls**:
+- Incorrect `propertyName`/`operator` returns zero results without errors
+- Date filtering may require epoch-ms bounds; mixing formats causes mismatches
+- Only fields in the `properties` array are returned; missing ones break downstream logic
+- Use READ_ALL_PROPERTIES to discover exact internal property names
+
+### 5. Create and Manage Custom Properties
+
+**When to use**: User wants to add custom fields to CRM objects
+
+**Tool sequence**:
+1. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - List existing properties (Prerequisite)
+2. `HUBSPOT_READ_PROPERTY_GROUPS_FOR_OBJECT_TYPE` - List property groups (Optional)
+3. `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` - Create a single property (Required)
+4. `HUBSPOT_CREATE_BATCH_OF_PROPERTIES` - Batch create properties (Alternative)
+5. `HUBSPOT_UPDATE_SPECIFIC_CRM_PROPERTY` - Update existing property definition (Optional)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE`: `objectType`, `name`, `label`, `type` (string/number/date/enumeration), `fieldType`, `groupName`, `options` (for enumerations)
+
+**Pitfalls**:
+- Property names are immutable after creation; choose carefully
+- Enumeration options must be pre-defined with `value` and `label`
+- Group must exist before assigning properties to it
+
+## Common Patterns
+
+### ID Resolution
+- **Property display name → internal name**: Use `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE`
+- **Pipeline name → pipeline ID**: Use `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`
+- **Stage name → stage ID**: Extract from pipeline stages response
+- **Owner name → owner ID**: Use `HUBSPOT_RETRIEVE_OWNERS`
+
+### Pagination
+- Search endpoints use cursor-based pagination
+- Follow `paging.next.after` until absent
+- Typical limit: 100 records per page
+- Pass `after` value from previous response to get next page
+
+### Batch Operations
+- Most create/update endpoints support batching with max 100 records per call
+- For larger datasets, chunk into groups of 100
+- Store returned IDs from each batch before proceeding
+- Use batch endpoints (`CREATE_CONTACTS`, `CREATE_COMPANIES`, `UPDATE_COMPANIES`) instead of single-record endpoints for efficiency
+
+## Known Pitfalls
+
+- **Property names**: All search/filter endpoints use internal property names, NOT display labels. Always call `READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` to discover correct names
+- **Batch limits**: Max 100 records per batch operation. Larger sets must be chunked
+- **Response structure**: Search results are nested under `response.data.results` with properties as string values
+- **Date formats**: Date properties may be epoch-ms or ISO strings depending on endpoint. Parse defensively
+- **Immutable names**: Property names cannot be changed after creation. Plan naming conventions carefully
+- **Cursor pagination**: Use `paging.next.after` cursor, not page numbers. Continue until `after` is absent
+- **Duplicate prevention**: Always search before creating contacts/companies to avoid duplicates
+- **Auth verification**: Run `HUBSPOT_GET_ACCOUNT_INFO` first; auth failures cascade to all subsequent calls
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create contact | `HUBSPOT_CREATE_CONTACT` | `properties: {email, firstname, lastname}` |
+| Batch create contacts | `HUBSPOT_CREATE_CONTACTS` | `inputs: [{properties}]` (max 100) |
+| Search contacts | `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` | `filterGroups, properties, limit, after` |
+| Create companies | `HUBSPOT_CREATE_COMPANIES` | `inputs: [{properties}]` (max 100) |
+| Search companies | `HUBSPOT_SEARCH_COMPANIES` | `filterGroups, properties, after` |
+| Search deals | `HUBSPOT_SEARCH_DEALS` | `filterGroups, properties, after` |
+| Get pipelines | `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` | `objectType: 'deals'` |
+| Search tickets | `HUBSPOT_SEARCH_TICKETS` | `filterGroups, properties, after` |
+| List properties | `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` | `objectType` |
+| Create property | `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` | `objectType, name, label, type, fieldType` |
+| Get owners | `HUBSPOT_RETRIEVE_OWNERS` | None |
+| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None |

package/assets/.agent/skills/hubspot-integration/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: hubspot-integration
+description: "Expert patterns for HubSpot CRM integration including OAuth authentication, CRM objects, associations, batch operations, webhooks, and custom objects. Covers Node.js and Python SDKs. Use when: hubspot, hubspot api, hubspot crm, hubspot integration, contacts api."
+source: vibeship-spawner-skills (Apache 2.0)
+---
+
+# HubSpot Integration
+
+## Patterns
+
+### OAuth 2.0 Authentication
+
+Secure authentication for public apps
+
+### Private App Token
+
+Authentication for single-account integrations
+
+### CRM Object CRUD Operations
+
+Create, read, update, delete CRM records
+
+## Anti-Patterns
+
+### ❌ Using Deprecated API Keys
+
+### ❌ Individual Requests Instead of Batch
+
+### ❌ Polling Instead of Webhooks
+
+## ⚠️ Sharp Edges
+
+| Issue | Severity | Solution |
+|-------|----------|----------|
+| Issue | high | See docs |
+| Issue | high | See docs |
+| Issue | critical | See docs |
+| Issue | high | See docs |
+| Issue | critical | See docs |
+| Issue | medium | See docs |
+| Issue | high | See docs |
+| Issue | medium | See docs |

package/assets/.agent/skills/hybrid-search-implementation/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: hybrid-search-implementation
+description: Combine vector and keyword search for improved retrieval. Use when implementing RAG systems, building search engines, or when neither approach alone provides sufficient recall.
+---
+
+# Hybrid Search Implementation
+
+Patterns for combining vector similarity and keyword-based search.
+
+## Use this skill when
+
+- Building RAG systems with improved recall
+- Combining semantic understanding with exact matching
+- Handling queries with specific terms (names, codes)
+- Improving search for domain-specific vocabulary
+- When pure vector search misses keyword matches
+
+## Do not use this skill when
+
+- The task is unrelated to hybrid search implementation
+- You need a different domain or tool outside this scope
+
+## Instructions
+
+- Clarify goals, constraints, and required inputs.
+- Apply relevant best practices and validate outcomes.
+- Provide actionable steps and verification.
+- If detailed examples are required, open `resources/implementation-playbook.md`.
+
+## Resources
+
+- `resources/implementation-playbook.md` for detailed patterns and examples.