TW

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.zip

Installs 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-up
73 charsno explicit “when” trigger
Intermediate

Key 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

You give it
Meeting transcript or summary
You get back
Created tasks in project management tools and sent follow-up emails

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

ErrorCauseSolution
No action items foundTranscript too vagueVerify meeting had clear action items
Task creation failedInvalid project/team IDCheck integration credentials
Email send failedInvalid recipientsVerify email addresses
Assignee not foundName mismatchMap 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

ServiceTasksDue DatesAssigneesPriority
AsanaYesYesYesNo
LinearYesYesYesYes
JiraYesYesYesYes
NotionYesYesYesNo

Resources

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

Completed twinmind-core-workflow-aValid transcript or summaryIntegration tokens for external services

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.

SkillInstallsUpdatedSafetyDifficulty
twinmind-core-workflow-b (this skill)124dReviewIntermediate
flow-next-work12moReviewAdvanced
linear-core-workflow-a024dReviewIntermediate
cm-start03moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

More by jeremylongshore

View all by jeremylongshore

analyzing-logs

jeremylongshore

Analyze application logs to detect performance issues, identify error patterns, and improve stability by extracting key insights.

14123

ollama-setup

jeremylongshore

Configure auto-configure Ollama when user needs local LLM deployment, free AI alternatives, or wants to eliminate hosted API costs. Trigger phrases: "install ollama", "local AI", "free LLM", "self-hosted AI", "replace OpenAI", "no API costs". Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

1167

backtesting-trading-strategies

jeremylongshore

Backtest crypto and traditional trading strategies against historical data. Calculates performance metrics (Sharpe, Sortino, max drawdown), generates equity curves, and optimizes strategy parameters. Use when user wants to test a trading strategy, validate signals, or compare approaches. Trigger with phrases like "backtest strategy", "test trading strategy", "historical performance", "simulate trades", "optimize parameters", or "validate signals".

1071

generating-database-seed-data

jeremylongshore

Process this skill enables AI assistant to generate realistic test data and database seed scripts for development and testing environments. it uses faker libraries to create realistic data, maintains relational integrity, and allows configurable data volumes. u... Use when working with databases or data models. Trigger with phrases like 'database', 'query', or 'schema'.

1033

cursor-codebase-indexing

jeremylongshore

Execute set up and optimize Cursor codebase indexing. Triggers on "cursor index setup", "codebase indexing", "index codebase", "cursor semantic search". Use when working with cursor codebase indexing functionality. Trigger with phrases like "cursor codebase indexing", "cursor indexing", "cursor".

885

testing-mobile-apps

jeremylongshore

Execute mobile app testing on iOS and Android devices/simulators. Use when performing specialized testing. Trigger with phrases like "test mobile app", "run iOS tests", or "validate Android functionality".

810

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).

13

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".

00

cm-start

tody-agent

Start the CM Workflow to execute your objective from idea to production code.

00

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.

00

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.

00

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

00

Search skills

Search the agent skills registry