agentleFS
Frontal-soFrontal-so/outbound-skills/skills/bridgebound-in-market-20/SKILL.md

bridgebound-in-market-20

Skill8 starsChanged 4 months agoMITView on GitHub

20 "In Market" Bridgebound triggers from Flip The Script - Adjacent Vendors, Competitors, and Time-Based signals. Use when targeting active buyers, building competitive displacement campaigns, or leveraging seasonal/event timing.

2 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Logic: If they bought Tool A, they likely need Tool B

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

BRIDGEBOUND Category III: Based on Likely "In Market" (20 Triggers)

Adjacent Vendors (7 Triggers)

  1. Recently Purchased Adjacent Vendor (Channel Partner) - New tech stack addition
  2. Current Customers of Adjacent Vendor (Non-Channel Partner) - Complementary tools
  3. In-Cycle with Adjacent Vendor (Channel Partner) - Active evaluation
  4. Engaged with Adjacent Vendor's Company Page - Vendor interest
  5. Followers of Adjacent Vendor's Company Page - Following adjacent tools
  6. Engaged with Adjacent Vendor's Employees - Employee engagement
  7. Mutual Connections with Adjacent Vendor's Employees - Shared network

Competitors (9 Triggers)

  1. Competitor's Churned Customers (Left a Negative Review) - Unhappy churners
  2. Competitor's Churned Customers (Through Disintegration) - Forced churn
  3. Competitor's Customers (Through Competitor's Website) - Identified users
  4. Competitor's Customers (Through Integration) - Integration data
  5. In-Cycle with Competitors (Through Word of Mouth) - Active evaluation
  6. Engaged with Competitor's Company Page - Competitor interest
  7. Followers of Competitor's Company Page - Following competitors
  8. Engaged with Competitor's Employees - Employee engagement
  9. Mutual Connections with Competitor's Employees - Shared network

Time-Based (4 Triggers)

  1. Annual Event (Ex. Taxes) - Recurring annual needs
  2. Regular Event (Ex. Olympics) - Periodic events
  3. Seasonal Needs (Ex. Summer for HVAC) - Seasonal demand
  4. Act of God (One-Time Event) - Unexpected events

Competitor Displacement Template

Just saw your review of {{competitor}}...

We researched and tested 3 alternatives (that don't suck).

Shall I send the report to you?

Cheers,
[Name]

Adjacent Vendor Play

Logic: If they bought Tool A, they likely need Tool B

Examples:

  • Bought Salesforce → Need Salesforce add-ons
  • Bought HubSpot → Need marketing automation
  • Bought Snowflake → Need data tools

Timing: 2-4 weeks after adjacent vendor purchase


Combines with

SkillWhy
buying-signals-6Tech stack change signal
clay-buying-signals-5Detect tech changes in Clay
gtm-plays-11Play #8 (Bad Reviews)
cold-email-templates-34Competitor switch templates

Example prompts

Build a campaign targeting companies that just purchased Salesforce.
How do I find churned customers from my competitor on G2?
Create an outreach strategy for trigger #17 (Annual Event) targeting tax season.

Part of Frontal — free, open GTM skills for your AI agent. Browse the library →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.