ClaudeSuperPower
SubmitLog in

mutual-action-plan

Skill

Build a mutual action plan (MAP) from what was actually discussed on recent calls — the shared, dated set of steps each side owns to reach the goal. Reviews recent engagements and goes deep with conversation_intelligence scoped to individual calls to pull open items, agreed next steps, owners, and t

0Learning

Install

git clone https://github.com/Zoominfo/zoominfo-mcp-plugin.git ~/.claude/skills/mutual-action-plan

What is mutual-action-plan?

Build a mutual action plan (MAP) from what was actually discussed on recent calls — the shared, dated set of steps each side owns to reach the goal. Reviews recent engagements and goes deep with conversation_intelligence scoped to individual calls to pull open items, agreed next steps, owners, and the timelines discussed. Identify the account by ZoomInfo company ID (preferred) or name/domain (triggers a lookup). Use when someone says "build a mutual action plan for Acme", "turn our last calls into a MAP", "what are the next steps and dates on both sides", or needs a close or onboarding plan. Evidence-based: it plans only what was discussed and asks for the target date if one was not stated.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~175 tokens of context used while enabled, before you invoke anything

Documentation

README · ~2 min read

Mutual Action Plan

Turn the commitments and timelines from recent calls into a single shared plan: who does what, by when, on both sides, toward an agreed goal.

Prerequisites

browse_engagements (to find the calls) is free but requires an active calendar/meeting integration; conversation_intelligence (to read them) requires at least one connected meeting or email source and consumes AI credits (minimum ~9 per call), and this skill calls it once per key engagement, so the spend scales with how many calls you deep-read. account_research (optional deal context) consumes AI credits. If no conversation data exists, say so rather than inventing a plan.

Input

Provided via $ARGUMENTS:

  • Account (required) — ZoomInfo company ID (preferred), or a name/domain to resolve via search_companies.
  • Goal & target date (ask if it matters and was not given) — the close date, go-live, or objective the plan drives toward. Do not assume it; if the plan needs a date that was never discussed, ask the user.

Workflow

  1. Resolve the account. If no account was supplied, ask the user which one before proceeding. Use the ZoomInfo ID directly, or resolve a name/domain via search_companies (browse_engagements filters by company ID + date, not by name).

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.