twinmind-core-workflow-b
Execute TwinMind secondary workflow: Action item extraction and follow-up automation. Use when automating meeting follow-ups, extracting tasks, or integrating with project management tools. Trigger with phrases like "twinmind action items", "meeting follow-up automation", "extract tasks from meeting".
What this skill does
# TwinMind Core Workflow B: Action Items & Follow-ups ## Contents - [Overview](#overview) - [Prerequisites](#prerequisites) - [Instructions](#instructions) - [Output](#output) - [Error Handling](#error-handling) - [Examples](#examples) - [Resources](#resources) ## Overview Secondary workflow for extracting action items with priority/assignee inference, automating follow-up emails, and syncing tasks to project management tools (Asana, Linear, Jira). ## Prerequisites - Completed `twinmind-core-workflow-a` (transcription) - Valid transcript or summary available - Integration tokens for external services (optional) ## Instructions ### Step 1: Extract Action Items Build `ActionItemExtractor` that calls TwinMind's `/extract/action-items` endpoint with options for context inclusion, speaker-based assignment, and due date inference. Auto-classify priority (high/medium/low) from keywords and categorize items (Review, Development, Communication, Meetings, Documentation). ### Step 2: Automate Follow-up Emails Create `FollowUpAutomation` with `generateFollowUp()` (AI-generated email with summary + action items), `sendFollowUp()` (immediate send), and `scheduleFollowUp()` (delayed send). ### Step 3: Integrate with Task Management Implement a `TaskIntegration` interface with `createTask()` and `updateTask()`. Build concrete integrations for Asana (REST API) and Linear (GraphQL) with priority mapping. Use factory pattern via `getTaskIntegration()`. ### Step 4: Orchestrate Complete Follow-up Wire everything in `runFollowUpWorkflow()`: extract action items, create tasks in external system, then send or schedule follow-up email to attendees. See detailed implementation for complete ActionItemExtractor, FollowUpAutomation, task integrations, and orchestration code. ## Output - Extracted action items with assignees and due dates - Tasks created in project management tool - Follow-up email sent or scheduled - Complete audit trail ## Error Handling | Error | Cause | Solution | |-------|-------|----------| | No action items found | Transcript too vague | Verify meeting had clear action items | | Task creation failed | Invalid project/team ID | Check integration credentials | | Email send failed | Invalid recipients | Verify email addresses | | Assignee not found | Name mismatch | Map speakers to user accounts | ## Examples **Basic usage**: Apply twinmind core workflow b to a standard project setup with default configuration options. **Advanced scenario**: Customize twinmind core workflow b for production environments with multiple constraints and team-specific requirements. ## Supported Integrations | Service | Tasks | Due Dates | Assignees | Priority | |---------|-------|-----------|-----------|----------| | Asana | Yes | Yes | Yes | No | | Linear | Yes | Yes | Yes | Yes | | Jira | Yes | Yes | Yes | Yes | | Notion | Yes | Yes | Yes | No | ## Resources - TwinMind Action Items API - [Asana API](https://developers.asana.com) - [Linear API](https://developers.linear.app) ## Next Steps For troubleshooting issues, see `twinmind-common-errors`.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.