twinmind-core-workflow-b
Automates meeting follow-ups by extracting action items from transcripts and syncing them with project management tools.
Install
mkdir -p .claude/skills/twinmind-core-workflow-b && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7441" && unzip -o skill.zip -d .claude/skills/twinmind-core-workflow-b && rm skill.zipInstalls to .claude/skills/twinmind-core-workflow-b
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Execute TwinMind secondary workflow: Action item extraction and follow-upKey capabilities
- →Extract action items from meeting transcripts
- →Infer priority and assignee for extracted tasks
- →Automate follow-up email generation and scheduling
- →Sync tasks to Asana, Linear, Jira, and Notion
- →Orchestrate complete follow-up workflows
How it works
Uses an ActionItemExtractor to parse transcripts for tasks and orchestrates integrations to push these items into external project management systems.
Inputs & outputs
When to use twinmind-core-workflow-b
- →Extracting tasks from meeting transcripts
- →Automating meeting follow-up emails
- →Syncing tasks to project management tools
About this skill
TwinMind Core Workflow B: Action Items & Follow-ups
Contents
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
- Linear API
Next Steps
For troubleshooting issues, see twinmind-common-errors.
When not to use it
- →When no transcript or summary is available
- →When the meeting lacks clear action items
Prerequisites
Limitations
- →Requires mapping speakers to user accounts for correct assignment
- →Task creation depends on valid project or team IDs
How it compares
Automates the entire lifecycle of meeting follow-ups from extraction to task creation, unlike manual copy-pasting.
Compared to similar skills
twinmind-core-workflow-b side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| twinmind-core-workflow-b (this skill) | 1 | 24d | Review | Intermediate |
| flow-next-work | 1 | 2mo | Review | Advanced |
| linear-core-workflow-a | 0 | 24d | Review | Intermediate |
| cm-start | 0 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
flow-next-work
gmickel
Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).
linear-core-workflow-a
jeremylongshore
Issue lifecycle management with Linear: create, update, and transition issues. Use when implementing issue CRUD operations, state transitions, or building issue management features. Trigger with phrases like "linear issue workflow", "linear issue lifecycle", "create linear issues", "update linear issue", "linear state transition".
cm-start
tody-agent
Start the CM Workflow to execute your objective from idea to production code.
lisa-setup-atlassian
CodySwannGT
Set up Atlassian (cloudId + acli profile) for this project. Writes the `atlassian` section of `.lisa.config.json` and enables the Atlassian MCP and/or installs acli as needed. Prerequisite for /lisa:setup:jira and /lisa:setup:confluence.
skill-team-implement
benbrastmckie
Orchestrate multi-agent implementation with parallel phase execution. Spawns teammates for independent phases and coordinates dependent phases. Includes debugger teammate for error recovery.
bad
stephenleo
BMad Autonomous Development — orchestrates parallel story implementation pipelines. Builds a dependency graph, updates PR status from GitHub, picks stories from the backlog, and runs each through create → dev → review → PR in parallel — each story isolated in its own git worktree — using dedicated s