Skip to content
Agentmart
Submit a tool

named-account-trigger-radar

Identify named accounts with timely buying or expansion signals and recommend next actions.

Skill by zapierOfficial

IndexedMIT★ 351
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/zapier-named-account-trigger-radar

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Identify named accounts with timely buying or expansion signals and recommend next actions.

Use cases: sales

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/named-account-trigger-radar

What's inside

Skill name
named-account-trigger-radar
Description
Identify named accounts with timely buying or expansion signals and recommend next actions.
License
MIT
Instructions
25 lines in SKILL.md · view on GitHub

Files (6)

  • ONBOARDING-PROMPT.md
  • README.md
  • SCHEMA-MAP.md
  • SETUP.md
  • SKILL.md
  • metadata.yaml

SKILL.md (first lines)

# Named Account Trigger Radar

Use this skill to decide which named accounts sales or marketing should work now, why they are timely, and what action should happen next.

## Workflow

1. Define the account pool and separate new-logo, recovery, and expansion motions.
2. Gather company-approved evidence first, then add public triggers when useful.
3. Score accounts based on actionability, recency, fit, and next-step clarity.
4. Return a short ranked list, not a generic market summary.
5. Label weak or stale evidence rather than forcing a recommendation.

## Zapier MCP And SDK Role

- Use Zapier MCP to read CRM, account lists, approved account signals, public research, and collaboration context.
- Use Zapier SDK for scheduled account watchlists, account-priority logging, and approved owner notifications.
- Keep CRM updates and outbound recommendations human-reviewed.

## Guardrails

- Do not recommend accounts solely because they are large.
- Do not fabricate ownership, intent, or titles.
- Use absolute dates for trigger recency.

From zapier/gtm-cheat-codes, MIT.

More from zapier/gtm-cheat-codes

Signals

Stars
351
Forks
21
Open issues
0
Last commit (this folder)
May 19, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from zapier

Cite this page

named-account-trigger-radar skill. Agent Mart. https://agentmart.dev/skills/zapier-named-account-trigger-radar (last updated 2026-10-24)