@hailer/mcp 0.0.1

package/.claude/skills/remove-workflow-skill/SKILL.md

@@ -0,0 +1,920 @@
+---
+name: Removing Hailer Workflows
+description: Complete guide for safely removing Hailer workflows - use when deleting workflows or cleaning up workspace
+---
+
+# Removing Hailer Workflows - Complete Guide
+
+Complete reference for safely removing Hailer workflows using the `remove_workflow` MCP tool.
+
+## Table of Contents
+1. [Quick Reference](#quick-reference)
+2. [Overview](#overview)
+3. [What Gets Deleted](#what-gets-deleted)
+4. [Prerequisites](#prerequisites)
+5. [Basic Usage](#basic-usage)
+6. [Safety Checklist](#safety-checklist)
+7. [Common Scenarios](#common-scenarios)
+8. [Before Removing](#before-removing)
+9. [After Removing](#after-removing)
+10. [Troubleshooting](#troubleshooting)
+11. [Best Practices](#best-practices)
+
+## Quick Reference
+
+**⚠️ DANGER: This operation is PERMANENT and CANNOT be undone!**
+
+**Basic Removal:**
+
+```javascript
+remove_workflow({
+  workflowId: "68446dc05b30685f67c6fcd4"
+})
+```
+
+**With Workspace Specification:**
+
+```javascript
+remove_workflow({
+  workflowId: "68446dc05b30685f67c6fcd4",
+  workspaceId: "6901c67b4e80fecb6fd7b38a"  // Optional
+})
+```
+
+**Key Requirements:**
+- User must be workspace administrator
+- Workflow ID must be valid and exist
+- Cannot be undone - all data permanently deleted
+- Affects: workflow, activities, discussions, relationships
+
+## Overview
+
+The `remove_workflow` tool permanently deletes a workflow (also called a "process") from your Hailer workspace. This is a **destructive operation** that removes not just the workflow structure, but all associated data.
+
+**Think of it as:**
+- Dropping a database table AND all its rows
+- Deleting the schema AND all records
+- Removing structure AND content permanently
+
+**When to use:**
+- Cleaning up test/development workflows
+- Removing unused or obsolete workflows
+- Workspace reorganization
+- Decommissioning old processes
+
+**When NOT to use:**
+- If you might need the data later (export first)
+- If other workflows reference it via ActivityLinks
+- If you're unsure about dependencies
+- For temporary workflow deactivation (use phases instead)
+
+## What Gets Deleted
+
+### 1. The Workflow Structure
+- Workflow definition (name, description)
+- All field definitions
+- All phase definitions
+- Workflow configuration settings
+- View settings (timeline, kanban, etc.)
+
+### 2. All Activities (Records)
+Every activity in the workflow is permanently deleted:
+- Activity names and content
+- All field values
+- Activity metadata (created date, updated date, creator)
+- Activity phase assignments
+- Team/user assignments
+
+### 3. All Discussions
+Every discussion thread linked to activities in the workflow:
+- Discussion messages
+- Message history
+- Attachments in discussions
+- Discussion participants
+- Read receipts and notifications
+
+### 4. Relationship Data
+- ActivityLink references FROM this workflow TO other workflows
+- May break ActivityLink references FROM other workflows TO this workflow (see warnings)
+
+### What Does NOT Get Deleted
+- Files attached to activities (files remain in file storage but lose association)
+- Users who participated in discussions
+- Insights that query this workflow (will break and show errors)
+- Other workflows that reference this workflow (links will break)
+
+## Prerequisites
+
+### Required Permissions
+**User must be workspace administrator**
+
+Check your permissions:
+```javascript
+get_current_workspace()
+// Look for your user role - must be admin
+```
+
+If you don't have admin permissions:
+- You'll get "Permission Denied" error
+- Contact workspace administrator
+- Cannot be bypassed
+
+### Required Information
+
+**1. Workflow ID**
+
+Get workflow ID from `list_workflows`:
+```javascript
+list_workflows()
+// Returns list with _id field for each workflow
+```
+
+**2. Workflow Dependencies**
+
+Check if other workflows reference this workflow:
+```javascript
+list_workflows()
+// Look for ActivityLink fields with data: ["target-workflow-id"]
+```
+
+## Basic Usage
+
+### Example 1: Remove Simple Workflow
+
+```javascript
+// 1. Find the workflow
+list_workflows()
+// Output shows: { _id: "68446dc05b30685f67c6fcd4", name: "Test Tasks" }
+
+// 2. Remove it
+remove_workflow({
+  workflowId: "68446dc05b30685f67c6fcd4"
+})
+
+// Output:
+// ✅ Workflow Removed Successfully
+// Workflow: Test Tasks
+// Workflow ID: 68446dc05b30685f67c6fcd4
+// ⚠️ All activities and discussions permanently deleted
+```
+
+### Example 2: Remove in Specific Workspace
+
+```javascript
+// Useful when managing multiple workspaces
+remove_workflow({
+  workflowId: "68446dc05b30685f67c6fcd4",
+  workspaceId: "6901c67b4e80fecb6fd7b38a"
+})
+```
+
+### Example 3: Remove with Verification
+
+```javascript
+// 1. List workflows to verify
+const workflows = list_workflows();
+console.log(workflows);
+
+// 2. Get workflow details
+const schema = get_workflow_schema({
+  workflowId: "68446dc05b30685f67c6fcd4"
+});
+console.log("Removing workflow:", schema.name);
+
+// 3. Check for activities
+const activities = list_activities({
+  workflowId: "68446dc05b30685f67c6fcd4",
+  limit: 1
+});
+console.log("Activity count:", activities.total);
+
+// 4. Confirm and remove
+remove_workflow({
+  workflowId: "68446dc05b30685f67c6fcd4"
+})
+```
+
+## ⚠️ MANDATORY: Comprehensive Confirmation Protocol
+
+**BEFORE calling `remove_workflow`, you MUST gather complete context and show it to the user:**
+
+### Required Context to Gather
+
+1. **Workspace Information:**
+   - Workspace ID: Get from `list_workflows` response
+   - Workspace name: Get from API init or workflow data
+
+2. **Workflow Information:**
+   - Workflow ID (provided by user)
+   - Workflow name: Get from `list_workflows`
+   - Activity count: Get from `list_workflows` (createdActivities field)
+
+3. **Impact Analysis:**
+   - Other workflows linking TO this workflow: Check `list_workflows` for ActivityLink fields with `data` containing this workflow ID
+   - List affected workflows by name
+
+### Required Confirmation Message Format
+
+**You MUST display this information to the user BEFORE calling the tool:**
+
+```
+⚠️ WARNING: This action is irreversible!
+
+You are about to permanently delete the following:
+
+**Workspace**:
+- Workspace ID: `<workspace-id>`
+- Workspace name: <workspace-name>
+
+**Workflow to Delete**:
+- Name: <workflow-name>
+- ID: `<workflow-id>`
+
+**What Will Be Lost**:
+- ❌ The workflow structure and all fields
+- ❌ **<activity-count> activities** will be permanently deleted
+- ❌ All associated discussions will be deleted
+- ❌ All workflow configuration will be lost
+
+**⚠️ Impact on Other Workflows**:
+- The **<Workflow A>** workflow has activity links pointing to this workflow
+- The **<Workflow B>** workflow has activity links pointing to this workflow
+- These links will be broken after deletion
+
+**This operation cannot be undone. All data will be permanently lost.**
+
+Do you want to proceed with permanently deleting this workflow?
+```
+
+### Example: Complete Safe Removal Flow
+
+```javascript
+// Step 1: Gather complete context
+const workflows = list_workflows()
+const targetWorkflow = workflows.find(w => w._id === "target-id")
+
+// Step 2: Identify affected workflows
+const affectedWorkflows = workflows.filter(w => {
+  const hasLink = Object.values(w.fields || {}).some(field =>
+    field.type === 'activitylink' &&
+    (field.data || []).includes(targetWorkflow._id)
+  )
+  return hasLink
+})
+
+// Step 3: Show comprehensive confirmation message to user
+console.log(`
+⚠️ WARNING: This action is irreversible!
+
+**Workspace**:
+- Workspace ID: \`${targetWorkflow.workspaceId}\`
+- Workspace name: ${workspaceName}
+
+**Workflow to Delete**:
+- Name: ${targetWorkflow.name}
+- ID: \`${targetWorkflow._id}\`
+
+**What Will Be Lost**:
+- ❌ The workflow structure and all fields
+- ❌ **${targetWorkflow.activityCount} activities** will be permanently deleted
+- ❌ All associated discussions will be deleted
+
+**⚠️ Impact on Other Workflows**:
+${affectedWorkflows.map(w => `- The **${w.name}** workflow has activity links pointing to this workflow`).join('\n')}
+
+This operation cannot be undone.
+`)
+
+// Step 4: Wait for explicit user confirmation
+
+// Step 5: Only after confirmation, call the tool
+remove_workflow({ workflowId: targetWorkflow._id })
+```
+
+### **FAILURE TO GATHER AND SHOW THIS CONTEXT IS AN ERROR**
+
+If you call `remove_workflow` without first gathering and displaying all this information to the user, you are violating safety protocols.
+
+## Safety Checklist
+
+**Before removing ANY workflow, complete this checklist:**
+
+### Step 1: Identify the Workflow
+- [ ] Confirmed workflow name with `list_workflows`
+- [ ] Verified workflow ID is correct
+- [ ] Checked workflow contains expected data
+
+### Step 2: Check Dependencies
+- [ ] Searched for workflows with ActivityLinks to this workflow
+- [ ] Identified any insights that query this workflow
+- [ ] Reviewed apps that might reference this workflow
+- [ ] Checked if data is referenced in documentation/reports
+
+### Step 3: Export Data (If Needed)
+- [ ] Exported activities with `list_activities` if backup needed
+- [ ] Saved workflow schema with `get_workflow_schema`
+- [ ] Documented field definitions and relationships
+- [ ] Archived any important discussions
+
+### Step 4: Notify Stakeholders
+- [ ] Informed users who work with this workflow
+- [ ] Updated documentation that references workflow
+- [ ] Communicated removal timeline
+- [ ] Provided alternative workflows if applicable
+
+### Step 5: Verify Permissions
+- [ ] Confirmed you have workspace admin rights
+- [ ] Checked with other admins if unsure
+- [ ] Verified no organizational policies prevent removal
+
+### Step 6: Final Confirmation
+- [ ] Double-checked workflow ID one more time
+- [ ] Confirmed this is the intended workflow to remove
+- [ ] Accepted that this cannot be undone
+- [ ] Ready to proceed with deletion
+
+## Common Scenarios
+
+### Scenario 1: Clean Up Test Workflows
+
+**Situation:** Created test workflows during development/training.
+
+**Steps:**
+```javascript
+// 1. List all workflows
+list_workflows()
+
+// 2. Identify test workflows (look for "test", "demo", "sandbox" in names)
+// Example IDs: "test-workflow-id-1", "test-workflow-id-2"
+
+// 3. Remove each test workflow
+remove_workflow({ workflowId: "test-workflow-id-1" })
+remove_workflow({ workflowId: "test-workflow-id-2" })
+
+// 4. Verify removal
+list_workflows()
+```
+
+### Scenario 2: Replace Workflow with Improved Version
+
+**Situation:** Created new workflow to replace old one.
+
+**Steps:**
+```javascript
+// 1. Install new workflow
+install_workflow({
+  workflowTemplates: [{ _id: '_0001', name: 'Tasks v2', ... }]
+})
+// Returns new workflow ID
+
+// 2. Migrate data (manually or with script)
+// - Export old activities with list_activities
+// - Create new activities in new workflow
+
+// 3. Update ActivityLinks in other workflows
+update_workflow_field({
+  workflowId: "other-workflow-id",
+  fieldId: "link-field-id",
+  fieldData: {
+    data: ["new-workflow-id"]  // Point to new workflow
+  }
+})
+
+// 4. Remove old workflow
+remove_workflow({
+  workflowId: "old-workflow-id"
+})
+```
+
+### Scenario 3: Remove Unused Workflow
+
+**Situation:** Workflow exists but no longer used.
+
+**Steps:**
+```javascript
+// 1. Verify no recent activity
+list_activities({
+  workflowId: "workflow-id",
+  limit: 10
+})
+// Check if any activities or all old
+
+// 2. Check for dependencies
+list_workflows()
+// Search for ActivityLinks referencing this workflow
+
+// 3. Export for archive (if needed)
+const activities = list_activities({
+  workflowId: "workflow-id",
+  limit: 1000
+})
+// Save to file for records
+
+// 4. Remove workflow
+remove_workflow({
+  workflowId: "workflow-id"
+})
+```
+
+### Scenario 4: Cascade Deletion (Related Workflows)
+
+**Situation:** Need to remove related workflows (parent and children).
+
+**Steps:**
+```javascript
+// Example: Projects → Tasks hierarchy
+
+// 1. Remove child workflows FIRST
+remove_workflow({ workflowId: "tasks-workflow-id" })
+
+// 2. Then remove parent workflow
+remove_workflow({ workflowId: "projects-workflow-id" })
+
+// Note: Removing parent first would break ActivityLinks in children
+```
+
+### Scenario 5: Partial Cleanup
+
+**Situation:** Want to remove workflow but preserve some data.
+
+**Steps:**
+```javascript
+// 1. Export important activities
+const activities = list_activities({
+  workflowId: "old-workflow-id",
+  filters: [{ field: "status", operator: "eq", value: "Important" }]
+})
+// Save to external storage
+
+// 2. Create new workflow for preserved data
+install_workflow({ ... })
+
+// 3. Manually recreate important activities
+activities.forEach(activity => {
+  create_activity({
+    workflowId: "new-workflow-id",
+    name: activity.name,
+    fields: { ... }
+  })
+})
+
+// 4. Remove old workflow
+remove_workflow({ workflowId: "old-workflow-id" })
+```
+
+## Before Removing
+
+### Check for ActivityLink References
+
+**Other workflows might link TO this workflow:**
+
+```javascript
+// 1. List all workflows
+const workflows = list_workflows()
+
+// 2. Check each workflow's schema
+workflows.forEach(workflow => {
+  const schema = get_workflow_schema({ workflowId: workflow._id })
+
+  // 3. Look for ActivityLink fields
+  const activityLinks = schema.fields.filter(field =>
+    field.type === 'activitylink' &&
+    field.data.includes("target-workflow-id")
+  )
+
+  if (activityLinks.length > 0) {
+    console.log(`⚠️ Workflow "${workflow.name}" has links to target workflow`)
+  }
+})
+```
+
+**What happens to broken links:**
+- Activities with links to removed workflow will keep field values
+- But linked activities won't be accessible (broken reference)
+- UI will show "Activity not found" or similar error
+
+### Check for Insights
+
+**Insights query workflows:**
+
+```javascript
+// 1. List insights
+list_insights()
+
+// 2. Check each insight's sources
+insights.forEach(insight => {
+  if (insight.sources.some(s => s.workflowId === "target-workflow-id")) {
+    console.log(`⚠️ Insight "${insight.name}" queries this workflow`)
+  }
+})
+```
+
+**What happens to broken insights:**
+- Insights will show errors when executed
+- Must update or remove affected insights manually
+
+### Export Data for Backup
+
+**Export activities:**
+```javascript
+// Get all activities (paginate if needed)
+const activities = list_activities({
+  workflowId: "workflow-id",
+  limit: 1000,
+  returnFlat: true
+})
+
+// Save to JSON file or database
+console.log(JSON.stringify(activities, null, 2))
+```
+
+**Export schema:**
+```javascript
+const schema = get_workflow_schema({
+  workflowId: "workflow-id"
+})
+
+// Save schema definition
+console.log(JSON.stringify(schema, null, 2))
+```
+
+## After Removing
+
+### Verify Removal
+
+```javascript
+// 1. Check workflow list
+list_workflows()
+// Removed workflow should not appear
+
+// 2. Try to access workflow (should fail)
+get_workflow_schema({
+  workflowId: "removed-workflow-id"
+})
+// Should return error: "Workflow not found"
+```
+
+### Update Documentation
+
+- Update workspace documentation
+- Remove workflow references from guides
+- Update team training materials
+- Archive workflow specifications
+
+### Fix Broken References
+
+**Update ActivityLinks in other workflows:**
+```javascript
+update_workflow_field({
+  workflowId: "other-workflow-id",
+  fieldId: "link-field-id",
+  fieldData: {
+    data: []  // Remove reference or update to new workflow
+  }
+})
+```
+
+**Update or remove affected insights:**
+```javascript
+// Option 1: Remove insight
+remove_insight({
+  insightId: "affected-insight-id"
+})
+
+// Option 2: Update insight sources
+// (Must use update_insight tool - not in current tool set)
+```
+
+### Clean Up Related Data
+
+**Remove associated apps if any:**
+```javascript
+list_apps()
+// Check for apps that were specific to removed workflow
+
+remove_app({
+  appId: "app-id"
+})
+```
+
+## Troubleshooting
+
+### Error: "Permission Denied"
+
+**Cause:** User is not workspace administrator.
+
+**Solution:**
+- Contact workspace administrator
+- Request admin permissions
+- Have admin perform removal
+- Cannot be bypassed - security requirement
+
+**Verification:**
+```javascript
+get_current_workspace()
+// Check your role - must show admin privileges
+```
+
+### Error: "Workflow Not Found"
+
+**Cause:** Workflow ID is invalid or workflow already deleted.
+
+**Solutions:**
+
+1. **Verify workflow ID:**
+```javascript
+list_workflows()
+// Check if workflow exists in list
+```
+
+2. **Check workspace context:**
+```javascript
+get_current_workspace()
+// Ensure you're in correct workspace
+```
+
+3. **Try with explicit workspace ID:**
+```javascript
+remove_workflow({
+  workflowId: "workflow-id",
+  workspaceId: "workspace-id"
+})
+```
+
+### Error: "Workflow is referenced by other workflows"
+
+**Note:** This error may not be shown by API, but is a logical concern.
+
+**Solution:**
+
+1. **Find references:**
+```javascript
+// Check all workflows for ActivityLinks
+list_workflows().forEach(workflow => {
+  const schema = get_workflow_schema({ workflowId: workflow._id })
+  // Look for activitylink fields with data containing target workflow
+})
+```
+
+2. **Update references first:**
+```javascript
+// Remove or update ActivityLink fields pointing to this workflow
+update_workflow_field({
+  workflowId: "referencing-workflow-id",
+  fieldId: "link-field-id",
+  fieldData: { data: [] }  // Remove reference
+})
+```
+
+3. **Then remove workflow:**
+```javascript
+remove_workflow({ workflowId: "target-workflow-id" })
+```
+
+### Error: "Network Error" or Timeout
+
+**Cause:** Workflow has large number of activities/discussions.
+
+**Solution:**
+- Wait for operation to complete (may take time)
+- Retry if timeout occurs
+- Check server logs if persistent
+- Contact support for very large workflows
+
+### Workflow Removed But Still Appears
+
+**Cause:** Cache not updated.
+
+**Solution:**
+```javascript
+// Refresh workspace cache
+get_current_workspace()
+list_workflows()
+```
+
+### Accidentally Removed Wrong Workflow
+
+**Reality Check:** **Cannot be undone.**
+
+**Mitigation steps:**
+
+1. **If you have backup:**
+   - Reinstall workflow with `install_workflow`
+   - Manually recreate activities from backup
+   - Will have different IDs - references broken
+
+2. **If no backup:**
+   - Data is permanently lost
+   - Contact Hailer support (may have database backups)
+   - Implement backup procedures for future
+
+3. **Prevention:**
+   - Always verify workflow ID before removing
+   - Use descriptive workflow names
+   - Export data before removal
+   - Test in development workspace first
+
+## Best Practices
+
+### 1. Always Verify Before Removing
+
+**Bad:**
+```javascript
+// Removed without checking
+remove_workflow({ workflowId: "some-id" })
+```
+
+**Good:**
+```javascript
+// 1. Verify workflow
+const workflows = list_workflows()
+const target = workflows.find(w => w._id === "some-id")
+console.log("About to remove:", target.name)
+
+// 2. Check activity count
+const activities = list_activities({ workflowId: "some-id", limit: 1 })
+console.log("Contains activities:", activities.total)
+
+// 3. Confirm and remove
+remove_workflow({ workflowId: "some-id" })
+```
+
+### 2. Document Removal Reason
+
+Keep a record of why workflows were removed:
+```javascript
+// Log removal for audit trail
+console.log({
+  action: "remove_workflow",
+  workflowId: "workflow-id",
+  workflowName: "Old Tasks",
+  reason: "Replaced by Tasks v2",
+  date: new Date().toISOString(),
+  removedBy: "admin-user-id"
+})
+```
+
+### 3. Use Descriptive Workflow Names
+
+Makes identification easier:
+- ✅ "Tasks (Test - Can Delete)"
+- ✅ "Legacy Customers - Archive 2023"
+- ❌ "Workflow 1"
+- ❌ "Test"
+
+### 4. Export Before Removing
+
+Always export unless certain data not needed:
+```javascript
+// Export activities
+const backup = {
+  workflow: get_workflow_schema({ workflowId: "id" }),
+  activities: list_activities({ workflowId: "id", limit: 1000 }),
+  exportDate: new Date().toISOString()
+}
+
+// Save to file
+console.log(JSON.stringify(backup, null, 2))
+
+// Then remove
+remove_workflow({ workflowId: "id" })
+```
+
+### 5. Remove Test Workflows Promptly
+
+Don't let test workflows accumulate:
+- Remove after testing complete
+- Use clear naming (e.g., "TEST - Delete After Demo")
+- Regular cleanup schedule (weekly/monthly)
+
+### 6. Communicate Before Removing
+
+Notify team before removing shared workflows:
+- Send message in workspace
+- Post in relevant discussions
+- Update documentation
+- Provide migration path if replacing workflow
+
+### 7. Remove Children Before Parents
+
+When removing related workflows:
+```javascript
+// Correct order: Child → Parent
+remove_workflow({ workflowId: "tasks-id" })      // Child
+remove_workflow({ workflowId: "topics-id" })     // Parent of tasks
+remove_workflow({ workflowId: "projects-id" })   // Top parent
+```
+
+### 8. Consider Alternatives to Removal
+
+**Instead of removing, consider:**
+
+**Option 1: Rename for clarity**
+```javascript
+update_workflow({
+  workflowId: "id",
+  name: "Archived - Old Tasks (2023)"
+})
+```
+
+**Option 2: Remove from views**
+- Users can hide workflows from their view
+- Preserves data without deletion
+
+**Option 3: Move to archive workspace**
+- Create "Archive" workspace
+- Move data there (manually)
+- Keep original workspace clean
+
+## Integration with Other Tools
+
+### Used With list_workflows
+
+```javascript
+// 1. List to find ID
+const workflows = list_workflows()
+
+// 2. Remove specific workflow
+const testWorkflow = workflows.find(w => w.name.includes("Test"))
+if (testWorkflow) {
+  remove_workflow({ workflowId: testWorkflow._id })
+}
+```
+
+### Used With get_workflow_schema
+
+```javascript
+// 1. Get details before removing
+const schema = get_workflow_schema({ workflowId: "id" })
+console.log("Removing workflow:", schema.name)
+console.log("Fields:", schema.fields.length)
+
+// 2. Remove
+remove_workflow({ workflowId: "id" })
+```
+
+### Used With list_activities
+
+```javascript
+// 1. Check activity count
+const activities = list_activities({
+  workflowId: "id",
+  limit: 1
+})
+
+if (activities.total > 0) {
+  console.log(`⚠️ Warning: Removing workflow with ${activities.total} activities`)
+}
+
+// 2. Confirm and remove
+remove_workflow({ workflowId: "id" })
+```
+
+### Used With install_workflow
+
+**Replace workflow pattern:**
+```javascript
+// 1. Install new version
+const result = install_workflow({
+  workflowTemplates: [{ _id: '_0001', name: 'Tasks v2', ... }]
+})
+
+// 2. Migrate data (if needed)
+// ... migration logic ...
+
+// 3. Remove old version
+remove_workflow({ workflowId: "old-workflow-id" })
+```
+
+## Summary
+
+**Key Takeaways:**
+1. ⚠️ **Permanent deletion** - cannot be undone
+2. 🔒 **Admin only** - requires workspace administrator rights
+3. 🗑️ **Complete removal** - workflow, activities, discussions all deleted
+4. 🔗 **Breaks references** - ActivityLinks from other workflows will break
+5. 💾 **Export first** - always backup important data
+6. ✅ **Verify twice** - double-check workflow ID before removing
+7. 📢 **Communicate** - inform team before removing shared workflows
+
+**Quick Decision Tree:**
+
+```
+Need to remove workflow?
+│
+├─ Contains important data? → Export first, then remove
+├─ Referenced by other workflows? → Update references first, then remove
+├─ Used by insights? → Update/remove insights first, then remove
+├─ Test/demo workflow? → Remove immediately
+├─ Might need later? → Consider archiving instead
+└─ Sure about removal? → Verify ID and remove
+```
+
+## Additional Resources
+
+- See `install-workflow-skill` for creating workflows
+- See `update-workflow-field-skill` for modifying workflows (alternative to removal)
+- Use `list_workflows` to view all workflows
+- Use `get_workflow_schema` to inspect workflow structure before removal
+- See `hailer-api` skill for comprehensive API documentation
+- See `mcp-tools` skill for implementation patterns