@hailer/mcp 1.1.11 → 1.1.13

package/.claude/skills/hailer-permissions-system/SKILL.md

@@ -1,121 +0,0 @@
----
-name: hailer-permissions-system
-description: Hailer app permissions - users, teams, and access control
-version: 1.1.0
-triggers: Grant access, permissions, app access, user permissions, team access
----
-
-# Hailer Permissions System
-
-Managing access to Hailer **apps** for users and teams.
-
-<scope-notice>
-**This skill covers APP permissions only.**
-
-For other permission types, see:
-- **Workflow permissions** (who can access a workflow) → SDK-ws-config-skill, main.ts `members[]`
-- **Phase permissions** (field visibility, transitions) → SDK-ws-config-skill, phases.ts
-- **Team management** (create/edit teams) → SDK-ws-config-skill, teams.ts
-
-App permissions = who can see/use an app in Hailer UI.
-Workflow permissions = who can see/edit activities in a workflow.
-</scope-notice>
-
-## Overview
-
-Hailer apps can have restricted access. Users must be explicitly granted access to see/use an app.
-
-**Access can be granted to:**
-- Individual users (by email/ID)
-- Teams (groups of users)
-
----
-
-## MCP Tools
-
-| Tool | Purpose |
-|------|---------|
-| `mcp__hailer__list_apps` | List all apps in workspace |
-| `mcp__hailer__search_workspace_users` | Find user by email/name |
-| `mcp__hailer__add_app_member` | Grant access |
-| `mcp__hailer__remove_app_member` | Revoke access |
-
----
-
-## Common Workflows
-
-### Grant User Access
-
-1. **Search for user:**
-```
-mcp__hailer__search_workspace_users({ query: "john@example.com" })
-```
-
-2. **Get app ID (if not known):**
-```
-mcp__hailer__list_apps({})
-```
-
-3. **Add user as member:**
-```
-mcp__hailer__add_app_member({
-  appId: "64a1b2c3d4e5f6a7b8c9d0e1",
-  memberId: "user_64a1b2c3d4e5f6a7b8c9d0e2",
-  memberType: "user"
-})
-```
-
-### Grant Team Access
-
-1. **Get team ID from workspace config:**
-```typescript
-// Read from workspace/teams.ts or workspace/enums.ts
-import { TeamIds } from './workspace/enums';
-```
-
-2. **Add team as member:**
-```
-mcp__hailer__add_app_member({
-  appId: "64a1b2c3d4e5f6a7b8c9d0e1",
-  memberId: TeamIds.sales_team,
-  memberType: "team"
-})
-```
-
-### Revoke Access
-
-```
-mcp__hailer__remove_app_member({
-  appId: "64a1b2c3d4e5f6a7b8c9d0e1",
-  memberId: "user_64a1b2c3d4e5f6a7b8c9d0e2",
-  memberType: "user"
-})
-```
-
----
-
-## Public vs Authenticated Apps
-
-| Type | Access | Use Case |
-|------|--------|----------|
-| Public | Anyone with URL | Customer-facing portals using public insights |
-| Authenticated | Only granted users/teams | Internal tools, admin dashboards |
-
-**Public apps:**
-- Use public insights for data
-- No Hailer login required
-- Read-only typically
-
-**Authenticated apps:**
-- Use Hailer user management
-- Can read/write based on user permissions
-- Full Hailer SDK capabilities
-
----
-
-## Best Practices
-
-1. **Verify before granting** - Search for user first to confirm they exist
-2. **Use teams for groups** - Easier to manage than individual users
-3. **Audit periodically** - Review who has access to sensitive apps
-4. **Confirm revocations** - Double-check before removing access

package/.claude/skills/hailer-project-protocol/SKILL.md

@@ -1,488 +0,0 @@
----
-name: hailer-project-protocol
-description: Complete Hailer project management workflow schemas, field definitions, and protocols for SDK projects
-version: 1.0.1
----
-
-# Hailer Project Management Protocol
-
-This skill contains the complete Hailer project management workflow schemas, field definitions, and protocols for working with Hailer SDK projects.
-
----
-
-<critical-rules>
-## Overview
-
-Every Hailer workspace uses project management workflows. Claude installs and maintains these automatically using MCP or SDK.
-
-**CRITICAL: Real-Time Updates**
-- Update Hailer items IN REAL-TIME as work progresses
-- Do NOT batch updates - update immediately when status changes
-- When completing a task, update Hailer BEFORE moving to next task
-
-**Context File Hierarchy**
-1. **SESSION-HANDOFF.md** - Previous session state (read first when resuming)
-2. **DEVELOPMENT.md** - Local backup/snapshot of Hailer state
-3. **Hailer Workflows** - Source of truth for project data
-</critical-rules>
-
----
-
-## Workflow 1: Project Planning
-
-**Workflow name:** `Project Planning`
-
-### Phases (in order)
-1. `Planning`
-2. `In Progress`
-3. `On Hold`
-4. `Completed`
-
-### Fields
-
-| Field Name | Field Type | Configuration |
-|------------|------------|---------------|
-| Title | Text | - |
-| Description | Long text | - |
-| Type | Predefined options (single) | Options: `Project`, `Feature`, `Session Handoff`, `PRD` |
-| Project | Activity link | Links to: `Project Planning` workflow |
-| Child Features | Linked from | Linked from: `Project Planning` → `Project` field |
-| Dev Tasks | Linked from | Linked from: `Dev Tasks` → `Feature` field |
-| Goal | Long text | - |
-| Documentation | Long text | - |
-| Technical Notes | Long text | - |
-| Blockers | Long text | - |
-| User Stories | Long text | PRD: As a [user], I want [X] so that [Y] |
-| Acceptance Criteria | Long text | PRD: Checklist of "done" conditions |
-| Technical Constraints | Long text | PRD: Performance, security, compatibility |
-| Out of Scope | Long text | PRD: What this feature does NOT include |
-
-### Field Explanations
-- **Project**: Features use this to link UP to their parent Project
-- **Child Features**: Automatically shows Features that link to this Project
-- **Dev Tasks**: Automatically shows Tasks/Bugs that link to this Feature
-- **Documentation**: How it works, usage instructions, user-facing docs
-- **Technical Notes**: Architecture decisions, implementation details
-- **User Stories/Acceptance Criteria/Technical Constraints/Out of Scope**: PRD fields for requirements
-
----
-
-## Workflow 2: Dev Tasks
-
-**Workflow name:** `Dev Tasks`
-
-### Phases (in order)
-1. `Backlog`
-2. `Todo`
-3. `In Progress`
-4. `Review`
-5. `Done`
-
-### Fields
-
-| Field Name | Field Type | Configuration |
-|------------|------------|---------------|
-| Title | Text | - |
-| Description | Long text | - |
-| Type | Predefined options (single) | Options: `Task`, `Bug`, `Tech Debt` |
-| Priority | Predefined options (single) | Options: `HIGH`, `MEDIUM`, `LOW` |
-| Feature | Activity link | Links to: `Project Planning` workflow |
-| Blocked By | Activity link | Links to: `Dev Tasks` workflow |
-| Blocks | Linked from | Linked from: `Dev Tasks` → `Blocked By` field |
-| Related Items | Activity link | Links to: `Dev Tasks` workflow |
-| Related From | Linked from | Linked from: `Dev Tasks` → `Related Items` field |
-| Files Modified | Text | - |
-| Commits | Text | - |
-
-### Field Explanations
-- **Feature**: Links UP to parent Feature in Project Planning
-- **Blocked By**: Links to other Dev Tasks that block this one
-- **Blocks**: Automatically shows Dev Tasks that this task blocks
-- **Related Items**: Links to related Tasks/Bugs (e.g., Bug → Task that caused it)
-- **Related From**: Automatically shows items that link to this one
-
----
-
-## Link Relationship Summary
-
-```
-Project Planning                          Dev Tasks
-┌─────────────────────┐                  ┌─────────────────────┐
-│ Project             │                  │ Task/Bug/Tech Debt  │
-│                     │                  │                     │
-│ Child Features ◄────┼── Project ───────┼── (not used)        │
-│ (linked from)       │                  │                     │
-└─────────────────────┘                  │                     │
-         ▲                               │                     │
-         │                               │                     │
-┌────────┴────────────┐                  │                     │
-│ Feature / PRD       │                  │                     │
-│                     │                  │                     │
-│ Project ────────────┼─► Project        │                     │
-│ (activity link)     │                  │                     │
-│                     │                  │                     │
-│ Dev Tasks ◄─────────┼──────────────────┼── Feature           │
-│ (linked from)       │                  │   (activity link)   │
-└─────────────────────┘                  │                     │
-                                         │ Blocked By ─────────┼─► Dev Tasks
-                                         │ (activity link)     │
-                                         │                     │
-                                         │ Blocks ◄────────────┼── Blocked By
-                                         │ (linked from)       │   (from other)
-                                         └─────────────────────┘
-```
-
----
-
-## Protocol: Starting in a Workspace
-
-### Step 1: Check for Existing Workflows
-
-**AUTOMATIC CREATION: If workflows don't exist, CREATE THEM.**
-
-Look for workflows named exactly:
-- `Project Planning`
-- `Dev Tasks`
-
-### Step 2: Create Workflows if Missing
-
-**This is NOT optional - create them automatically.**
-
-Notify user: "Setting up project management workflows for this workspace..."
-
-#### Create Project Planning Workflow
-
-```typescript
-// Using Hailer MCP or SDK
-{
-  name: "Project Planning",
-  phases: ["Planning", "In Progress", "On Hold", "Completed"],
-  fields: [
-    { name: "Title", type: "text" },
-    { name: "Description", type: "longtext" },
-    { name: "Type", type: "predefined_single", options: ["Project", "Feature", "Session Handoff", "PRD"] },
-    { name: "Project", type: "activity_link", linkedWorkflow: "Project Planning" },
-    { name: "Goal", type: "longtext" },
-    { name: "Documentation", type: "longtext" },
-    { name: "Technical Notes", type: "longtext" },
-    { name: "Blockers", type: "longtext" },
-    // PRD fields
-    { name: "User Stories", type: "longtext" },
-    { name: "Acceptance Criteria", type: "longtext" },
-    { name: "Technical Constraints", type: "longtext" },
-    { name: "Out of Scope", type: "longtext" }
-  ]
-}
-```
-
-#### Create Dev Tasks Workflow
-
-```typescript
-{
-  name: "Dev Tasks",
-  phases: ["Backlog", "Todo", "In Progress", "Review", "Done"],
-  fields: [
-    { name: "Title", type: "text" },
-    { name: "Description", type: "longtext" },
-    { name: "Type", type: "predefined_single", options: ["Task", "Bug", "Tech Debt"] },
-    { name: "Priority", type: "predefined_single", options: ["HIGH", "MEDIUM", "LOW"] },
-    { name: "Feature", type: "activity_link", linkedWorkflow: "Project Planning" },
-    { name: "Blocked By", type: "activity_link", linkedWorkflow: "Dev Tasks" },
-    { name: "Related Items", type: "activity_link", linkedWorkflow: "Dev Tasks" },
-    { name: "Files Modified", type: "text" },
-    { name: "Commits", type: "text" }
-  ]
-}
-```
-
-### Step 3: Verify PRD Fields Exist
-
-If `Project Planning` workflow exists but is missing PRD fields, ADD THEM:
-- User Stories
-- Acceptance Criteria
-- Technical Constraints
-- Out of Scope
-
-### Step 4: Read Current State
-
-Before starting work:
-1. Check for SESSION-HANDOFF.md - read if exists (previous session context)
-2. Check for active Project (Type = `Project`, Phase = `In Progress`)
-3. If no Project exists, ask user for project name and create one
-4. Fetch In Progress Features and Tasks
-5. Check for recent Session Handoff (Type = `Session Handoff`)
-6. Summarize state to user
-
----
-
-## Protocol: During Development (Real-Time Updates)
-
-### Starting New Work
-1. Ensure a Feature exists (Type = `Feature`)
-   - Set `Project` field to link to parent Project
-2. Create Task in Dev Tasks (Type = `Task`)
-   - Set `Feature` field to link to parent Feature
-3. **IMMEDIATELY** move Task to `In Progress`
-4. Keep only ONE task `In Progress` at a time
-
-### Completing Work
-1. **IMMEDIATELY** update Task:
-   - `Files Modified`: List changed files
-   - `Commits`: Add commit hashes
-2. **IMMEDIATELY** move to `Done`
-3. If new work discovered → create new Tasks in `Backlog`
-
-### Finding Bugs
-1. **IMMEDIATELY** create item in Dev Tasks (Type = `Bug`)
-2. Set `Feature` to link to relevant Feature
-3. Set `Priority` based on severity
-4. Optionally set `Related Items` to link to Task that caused it
-
-### Blocked Tasks
-1. Set `Blocked By` to link to blocking Task(s)
-2. Update Description with blocker details
-3. When blocker resolved, clear `Blocked By` and continue
-
-### Technical Decisions
-Update the Feature's `Technical Notes` field with:
-- Architecture decisions and rationale
-- Important discoveries
-- Trade-offs considered
-
-### Documentation
-When feature is complete or stable, update `Documentation` field with:
-- How it works
-- Usage instructions
-- Configuration options
-
----
-
-## Protocol: Session Handoff
-
-### When to Create
-- Context reaches 70-80%
-- Before ending a long session
-- User requests it
-
-### Create Session Handoff Item
-In Project Planning workflow:
-
-| Field | Value |
-|-------|-------|
-| Title | `Session Handoff - YYYY-MM-DD HH:MM` |
-| Type | `Session Handoff` |
-| Project | Link to active Project |
-| Phase | `Completed` |
-| Description | See template below |
-| Technical Notes | Key discoveries and decisions |
-| Blockers | Unresolved issues, next steps |
-
-**Description template:**
-```
-## Completed This Session
-- [List completed tasks]
-
-## In Progress
-- [Current work state]
-
-## Next Steps
-- [What to do when resuming]
-```
-
-### Local SESSION-HANDOFF.md
-Also create/update `SESSION-HANDOFF.md` in project root:
-
-```markdown
-## Session Handoff - YYYY-MM-DD HH:MM
-
-### Completed This Session
-- [What was accomplished]
-
-### Current State
-- [Work in progress, any partial implementations]
-
-### Blockers / Issues Found
-- [Problems encountered, unresolved errors]
-
-### Next Steps
-- [Immediate actions for next session]
-
-### Key Decisions Made
-- [Important context that shouldn't be lost]
-
-### Files Modified
-- [List of changed files with brief description]
-```
-
----
-
-## Protocol: Creating Items
-
-### New Project
-| Field | Value |
-|-------|-------|
-| Title | Project name (ask user) |
-| Type | `Project` |
-| Phase | `In Progress` |
-| Description | Project overview |
-| Goal | What success looks like |
-
-### New Feature
-| Field | Value |
-|-------|-------|
-| Title | Feature name (use prefixes: `Sales Orders → Automations`) |
-| Type | `Feature` |
-| Project | Link to parent Project |
-| Phase | `Planning` or `In Progress` |
-| Description | Scope and requirements |
-| Goal | Acceptance criteria |
-| Documentation | How it works (fill when complete) |
-| Technical Notes | Architecture decisions |
-
-### New PRD (Product Requirements Document)
-| Field | Value |
-|-------|-------|
-| Title | `PRD: [Feature Name]` |
-| Type | `PRD` |
-| Project | Link to parent Project |
-| Phase | `Planning` |
-| Description | Executive summary |
-| Goal | Success metrics |
-| User Stories | As a [user], I want [X] so that [Y] |
-| Acceptance Criteria | - [ ] Criterion 1<br>- [ ] Criterion 2 |
-| Technical Constraints | Performance, security, compatibility needs |
-| Out of Scope | What this does NOT include |
-
-### New Task
-| Field | Value |
-|-------|-------|
-| Title | Specific, actionable description |
-| Type | `Task` |
-| Feature | Link to parent Feature |
-| Priority | `MEDIUM` (default) |
-| Phase | `Backlog` or `Todo` |
-| Description | Implementation details |
-
-### New Bug
-| Field | Value |
-|-------|-------|
-| Title | Clear bug description with context |
-| Type | `Bug` |
-| Feature | Link to affected Feature |
-| Priority | Based on severity |
-| Phase | `Backlog` or `Todo` |
-| Description | Steps to reproduce, expected vs actual |
-| Related Items | Link to Task that caused it (if known) |
-
----
-
-## Protocol: DEVELOPMENT.md Sync
-
-When user requests sync (`/project-status`):
-
-1. Fetch all data from Hailer workflows:
-   - Active Project
-   - All Features with their phases
-   - All Dev Tasks (grouped by phase)
-   - Recent Session Handoffs
-
-2. Generate DEVELOPMENT.md:
-```markdown
-# [Project Title] Development Status
-
-**Last Updated:** YYYY-MM-DD
-**Hailer Sync:** YYYY-MM-DD HH:MM
-
----
-
-## Active Feature
-**Name:** [Feature Title]
-**Goal:** [Feature Goal]
-**Status:** [Phase]
-
----
-
-## Current Sprint
-
-### In Progress
-- [ ] [Task Title] (Feature: [Feature Name])
-
-### Completed This Session
-- [x] [Task Title] (YYYY-MM-DD)
-
-### Blocked
-- [ ] [Task Title] - **Blocker:** [reason]
-
----
-
-## Backlog
-- [ ] [Task Title] (Feature: [Feature Name], Priority: [Priority])
-
----
-
-## Known Issues
-| Priority | Issue | Status |
-|----------|-------|--------|
-| HIGH | [Bug Title] | [Phase] |
-
----
-
-## Technical Notes
-[Aggregated from Features' Technical Notes fields]
-
----
-
-## Session Notes
-[Local notes not synced to Hailer]
-```
-
----
-
-## Naming Conventions
-
-### Features
-Use arrow prefix for related features:
-- `Sales Orders` (main workflow)
-- `Sales Orders → Automations`
-- `Sales Orders → ERP Integration`
-
-### Tasks
-Specific and actionable:
-- `Add customer reference field to orders`
-- `Work on orders`
-
-### Bugs
-Include context:
-- `Order total wrong when discount applied`
-- `Calculation bug`
-
-### PRDs
-Always prefix with "PRD:":
-- `PRD: User Authentication`
-- `PRD: Sales Order Automations`
-
----
-
-## Hailer Project Structure
-
-```
-workspace/              # Local config (check FIRST)
-apps/                   # Frontend apps (if monorepo)
-integrations/           # Backend services (if monorepo)
-.claude/
-  agents/               # Agent definitions
-  hooks/                # Safety hooks
-  skills/               # On-demand documentation
-  commands/             # Slash commands
-  settings.json         # Permissions
-CLAUDE.md               # Project instructions
-DEVELOPMENT.md          # Project state (synced with Hailer)
-SESSION-HANDOFF.md      # Previous session context
-```
-
-### Key Principles
-- **Local-first**: Check `workspace/` before making API calls
-- **Skills before actions**: Load relevant skill before SDK/MCP commands
-- **Hooks protect you**: Push commands require confirmation via hooks
-- **Check scripts**: Run `npm run` to see available commands
-- **Session continuity**: Read SESSION-HANDOFF.md when resuming work

package/.claude/skills/hailer-rest-api/SKILL.md

@@ -1,61 +0,0 @@
----
-name: hailer-rest-api
-description: Direct HTTP endpoints for Hailer platform operations
-version: 1.1.0
-triggers:
-  - REST API
-  - HTTP endpoint
-  - curl
-  - direct API call
-  - backend integration
-  - fallback when SDK lacks method
----
-
-# Hailer REST API Reference
-
-Direct HTTP endpoints for Hailer platform operations.
-
-## When to Use
-
-- **Integrations** (Igor): Backend services that don't use `@hailer/cli`
-- **Apps** (Giuseppe): Fallback when `@hailer/app-sdk` lacks a method
-- **Documentation** (Marcus): Reference when documenting API endpoints
-
-## Files
-
-| File | Domain | Key Operations |
-|------|--------|----------------|
-| `hailer-activities.md` | Activities | CRUD, kanban, timeline, linked, import |
-| `hailer-workflows.md` | Workflows | CRUD, fields, phases, permissions, templates |
-| `hailer-insights.md` | Insights | SQL views, execution, public insights |
-| `hailer-admin.md` | Admin | Auth, workspaces, users, teams, groups, apps, files |
-| `hailer-messaging.md` | Messaging | Discussions, messages, reactions, video |
-| `hailer-calendar.md` | Calendar | Calendars, events, recurring, iCal |
-| `hailer-feed.md` | Feed/Wall | Posts, comments, likes, pins |
-
-## Common Patterns
-
-**Base URLs:**
-- Production: `https://api.hailer.com/api`
-- Staging: `https://api.hailer.biz/api`
-
-**Authentication:**
-```bash
--H "hlrkey: YOUR_SESSION_KEY"
-```
-
-**Request format:** JSON-RPC style POST with array params
-```bash
-curl -X POST "https://api.hailer.com/api/v3/endpoint" \
-  -H "Content-Type: application/json" \
-  -H "hlrkey: SESSION_KEY" \
-  -d '["param1", {"option": "value"}]'
-```
-
-## Legacy Naming
-
-| Current | Legacy | Notes |
-|---------|--------|-------|
-| workflowId | processId | Used interchangeably |
-| workspaceId | networkId, cid, companyId | All refer to workspace |
-| activityId | - | Sometimes called "row" |