EasyFreeAny assistant

Daily tracking CRM

Every touch and reply, one tab per segment, updated every morning.

Works on its own in any assistant like Claude, on your own website and data. No MQLooP account, no extension. The MQLooP loop picks it up later if you want it to run.

The prompt, copied as is

Read this skill and run it for my company: https://mqloop.ai/gtm-resources/ai-skills/mqloop-daily-segment-sheet/SKILL.md

Then paste it into your assistant. It reads the skill and runs it on your website.

Other ways to use it

Claude reads it and can use the skill in the same conversation. In Claude Code, save the file as ~/.claude/skills/mqloop-daily-segment-sheet/SKILL.md. In Claude.ai, upload the file under skills.

What you get

  • One tab per segment
  • Every touch and reply, every morning
  • Yours as Excel or a Google Sheet, or in your own CRM

Nothing to install besides the file. It never sends anything; with MQLooP connected, every send still waits for your approval.

The skill, in full

This is exactly what your assistant reads. Inputs, method, output format and guardrails.

# MQLooP Daily Tracking CRM

Memory for everyone: one sheet, a tab per segment, every touch and reply, every morning. It
works from whatever the user already has. A CRM mirrors it when there is one; without a CRM
this sheet is the system of record.

## When to use
- "How is the wave doing?" / "Any meetings?" / "What happened with <company>?" /
  "What should we do today?"
- Every morning an outreach sequence is live.

## Inputs (any one of these is enough)
1. A spreadsheet or CSV of touches: lead or company, segment, invite date, accepted, DM date,
   email dates, reply, meeting. Column names do not matter; map them and say how you mapped.
2. A CRM export (HubSpot, Pipedrive, Salesforce, a Notion or Airtable table) with the same facts.
3. Pasted notes: "invited 40 founders Monday, 9 accepted, 2 replied, 1 meeting Thursday".
4. Optional, only if the user has it: the MQLooP connector (`mqloop` MCP server), whose tools
   return the live numbers (`get_linkedin_funnel`, `explain_lead`, `get_extension_status`) and,
   when the user names leads and the token allows writes, `approve_leads`. Nothing here needs it.

## Method
1. **Map the data.** Identify the columns or facts for: segment, lead, each touch with its date,
   accepted, replied, meeting. State the mapping in one line. Ask for the one missing column that
   changes the verdict; never ask for all of them.
2. **The funnel.** Invites, accepted and the accept rate, DMs, email touches, replies, meetings.
   Quote the numbers exactly as they appear in the data.
3. **A tab per segment.** For each segment: leads in the loop, touched, accepted, replied,
   meetings, the five most recent touches. If the data has no segment column, propose one from
   title and industry and label it "proposed".
4. **Stories.** For any lead the user names, tell the timeline in two lines: each touch and its
   date, the reply, the trigger that put them in the loop.
5. **Next.** The single highest-leverage action: replies to answer today, leads to approve or
   advance, a touch that is overdue, a segment that earns replies and deserves the next wave.
   With the MQLooP connector and the user's explicit list, `approve_leads` records the approval;
   nothing is sent by it.

## Output format
Plain text, CEO-summary style: verdict in one line, NUMBERS, READ, NEXT, then one tab block per
segment. Under 200 words unless the user asks for the full sheet; then a table per tab, ready to
paste into Excel or Google Sheets.

## Guardrails
- Facts come only from the data the user provided or the connector returned in this
  conversation. Never estimate a number that is not there; say "not reported" instead.
- No pacing recipes, daily caps or send-timing advice: pacing belongs to the sending tool and
  LinkedIn's limits, not to this sheet.
- Never invent a lead, a segment or a reply. An empty tab is a finding.
  1. 1

    Drop in a skill

    Download it, or paste its link into any assistant like Claude. No account, no extension.

  2. 2

    Approve or edit the plan

    The skill reads your website and drafts your segments and roles.

  3. 3

    Add the extension when it is time to send

    One minute in Chrome, on your own LinkedIn. Every send waits for your approval.

Claude Code

~/.claude/skills/<skill name>/SKILL.md

Download a skill, save it there, start a new session. Any other assistant: paste the file in.

Live data, the MQLooP connector

claude mcp add --transport http mqloop https://platform.mqloop.ai/api/mcp

Your token comes from the Account tab on the platform; Claude then runs your loop with MQLooP: segments, leads, approvals.

No Claude? Run it on the web: your work email is all it takes.