Systems Lab

Agent skill

evening-scan

End-of-day response check and pipeline update.

dormantNeeds a keyInstructions only640 words

Filed under Analytics and reporting.

From ekatasingh1107/b2b-gtm-skills · 99 skills · 2 · pushed 2026-04-11

What it does when it runs

End-of-day response check and pipeline update. Run at 6 PM via cron. Checks all channels for replies via Chrome DevTools MCP + Zoho MCP, updates lead statuses, pauses cadence for responded leads, sends EOD report via Telegram.

Read from the skill and the 1 file bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
  • chrome-devtools
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about evening-scan

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah
git clone --depth 1 --filter=blob:none --sparse https://github.com/ekatasingh1107/b2b-gtm-skills.git /tmp/b2b-gtm-skills
git -C /tmp/b2b-gtm-skills sparse-checkout set "skills/playbooks/evening-scan"
mkdir -p ~/.claude/skills/evening-scan
cp -R "/tmp/b2b-gtm-skills/skills/playbooks/evening-scan/." ~/.claude/skills/evening-scan/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

Before you install: this skill will not complete its job on a bare agent. It needs chrome-devtools, which you have to obtain separately.

Reproduced in full from ekatasingh1107/b2b-gtm-skills/blob/eae8dd0bb98da1c8e84abd297066a87015dd860f/skills/playbooks/evening-scan/SKILL.md, which is licensed MIT (repository). 640 words, 11 headings.

Evening Scan

Run at 6 PM daily via cron. Checks all channels for responses to outreach via Chrome DevTools MCP, updates lead statuses, and sends EOD report via Telegram.

Prerequisites

  • agency.config.json populated (tools, CRM)
  • Active leads in outreach cadence
  • Chrome Beta logged in: Zoho webmail, LinkedIn, Instagram
  • Chrome DevTools MCP available

Capabilities Used

  1. inbox-scanner -- check all channels for replies via Chrome DevTools MCP
  2. reply-analyzer -- classify response sentiment and intent (8 categories)
  3. crm-writer -- update statuses, pause cadences

Step 1.1: Check Email Replies

SKILL: inbox-scanner TOOL: Zoho MCP (being integrated) + Chrome DevTools MCP (Zoho webmail) AUTH: Already signed in via Chrome Beta

  1. mcp__chrome-devtools__navigate_page to Zoho webmail inbox
  2. Scan for new replies to outreach emails (since last scan)
  3. Extract: sender, subject, reply text, timestamp
  4. Match to CRM leads by email address

Step 1.2: Check LinkedIn Messages

SKILL: inbox-scanner TOOL: Chrome DevTools MCP → LinkedIn messaging AUTH: Already signed in via Chrome Beta

  1. mcp__chrome-devtools__navigate_page to LinkedIn messaging
  2. Scan for new/unread messages from outreach contacts
  3. Check for accepted connection requests at invitation manager
  4. Extract: sender name, company, message text, timestamp

Step 1.3: Check Instagram DMs

SKILL: inbox-scanner TOOL: Chrome DevTools MCP → Instagram DMs AUTH: Already signed in via Chrome Beta

  1. mcp__chrome-devtools__navigate_page to Instagram Direct inbox
  2. Scan for new/unread DM replies
  3. Extract: sender username, message text, timestamp

Step 2.1: Match Replies to CRM Leads

SKILL: crm-writer (READ) TOOL: Google Sheets webhook

Match each reply to CRM leads by:

  • Email address (exact match) for email replies
  • Company name (fuzzy match) for LinkedIn/Instagram
  • Contact name (fuzzy match) as fallback

Pull lead context: cadence_day, last_action, lead_status, tier, score

Step 3.1: Classify Reply Sentiment (8 Categories)

SKILL: reply-analyzer TOOL: None (LLM classification)

Categories:

CategoryAction
Positive + wants demoMark DEMO_BOOKED, send cal link, pause cadence
Positive + interestedMark REPLIED, send more info, pause cadence
Neutral + questionsMark REPLIED, answer questions, pause cadence
Negative + not interestedMark NOT_INTERESTED, send polite close, pause cadence
Negative + angry/rudeMark DO_NOT_CONTACT, no further outreach
Out of officeNote OOO, adjust cadence timing
Unsubscribe requestMark DO_NOT_CONTACT, remove from all sequences
ReferralMark REFERRED, follow up with referred contact

Step 3.2: Update CRM -- Pause Cadence, Set New Status

SKILL: crm-writer (UPDATE) TOOL: Google Sheets webhook

For each responded lead:

  1. Set response_received = "Yes"
  2. Set response_channel = channel
  3. Set response_date = today
  4. Set response_summary = summary from analyzer
  5. Update lead_status based on classification
  6. Clear next_action and next_action_date (pause cadence)
  7. If demo booked: add to calendar (if Google Calendar MCP available)

Step 3.3: EOD Report + Telegram Notification

TOOL: Telegram Bot API

Send via Telegram:

EOD SCAN -- [Date]
---
RESPONSES RECEIVED: N
- Email replies: N
- LinkedIn messages: N
- LinkedIn connections accepted: N
- Instagram DM replies: N

RESPONSE DETAILS:
1. [Company] via [Channel]: [Summary] → [Action Taken]
2. ...

DEMOS BOOKED TODAY: N
NOT INTERESTED: N
DO NOT CONTACT: N

PIPELINE UPDATE:
- Total active leads: N
- In cadence: N
- Responded (awaiting follow-up): N
- Demo booked (total): N
- Breakup sent: N

RESPONSE RATE (trailing 7 days):
- Emails sent: N → Replies: N (X%)
- LinkedIn sent: N → Replies: N (X%)
- Overall: X%

ACTION ITEMS FOR TOMORROW:
- Follow-ups due: N
- Calls scheduled: N
- New leads to process: N

Example Usage

Trigger phrases:

  • "Run the evening scan"
  • "Check for responses"
  • "It's 6 PM, any replies?"
  • "Update the pipeline with today's responses"

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what evening-scan does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.