agentleFS
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/qualified-lead-scoring/SKILL.md

qualified-lead-scoring

Skill4 starsChanged 6 months agoMITView on GitHub

Score leads based on quality signals, not just lead price. Connect ad source to booking and sales quality. Use when evaluating campaign ROI or optimizing for downstream conversions.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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:

    When evaluating the true ROI of a campaign (e.g., high CPL but high conversion rate).

    line 12
  2. Distinctive:

    When optimizing ad targeting or creative for downstream quality.

    line 13
  3. Distinctive:

    When analyzing the source-to-close journey of a lead.

    line 14
  4. Distinctive:

    When developing a lead scoring model for a new funnel.

    line 15
  5. Distinctive:

    Develop Scoring Model: Create a system to assign points based on quality signals (e.g., +10 for a booked call, +5 for a specific job title).

    line 28
  6. Distinctive:

    Always connect ad source to downstream quality (e.g., a cheap lead that never books a call is worthless).

    line 41
  7. Distinctive:

    Use evidence from CRM data to validate the scoring model.

    line 42
  8. Distinctive:

    If the CRM data is incomplete or inaccurate, flag it immediately and request a data cleanup.

    line 45
  9. Distinctive:

    If a campaign generates a high volume of unqualified leads, escalate to pause or restructure the campaign.

    line 46

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Qualified Lead Scoring Analyst

Purpose

Score leads based on quality signals, not just lead price. Connect ad source to booking and sales quality to optimize for profitable, qualified leads and customers.

When to Use This Skill

  • When evaluating the true ROI of a campaign (e.g., high CPL but high conversion rate).
  • When optimizing ad targeting or creative for downstream quality.
  • When analyzing the source-to-close journey of a lead.
  • When developing a lead scoring model for a new funnel.

Inputs Required

  • Lead data (source, campaign, ad set, ad).
  • CRM data (pipeline stages, sales qualification signals, booked calls, closed deals).
  • The definition of a "qualified lead" (e.g., budget, timeline, authority, need).
  • The current lead scoring model (if any).

Step-by-Step Workflow

  1. Define Quality Signals: Identify the key attributes of a qualified lead (e.g., job title, company size, engagement level).
  2. Map the Journey: Trace the lead from the initial ad click to the final conversion event (e.g., booked call, closed deal).
  3. Analyze Source Quality: Compare the quality of leads generated by different campaigns, ad sets, and creatives.
  4. Develop Scoring Model: Create a system to assign points based on quality signals (e.g., +10 for a booked call, +5 for a specific job title).
  5. Evaluate ROI: Calculate the true cost per qualified lead (CPQL) and return on ad spend (ROAS) for each source.

Output Format

Provide a structured lead scoring report containing:

  • Quality Signals Identified: The key attributes used to score leads.
  • Source Analysis: A breakdown of lead quality by campaign, ad set, and creative.
  • Scoring Model: The proposed point system for evaluating leads.
  • ROI Evaluation: The calculated CPQL and ROAS for each source.
  • Recommendations: Actionable steps to optimize for higher-quality leads.

Decision Rules

  • Never optimize for low CPL at the expense of poor lead quality.
  • Always connect ad source to downstream quality (e.g., a cheap lead that never books a call is worthless).
  • Use evidence from CRM data to validate the scoring model.

Escalation Rules

  • If the CRM data is incomplete or inaccurate, flag it immediately and request a data cleanup.
  • If a campaign generates a high volume of unqualified leads, escalate to pause or restructure the campaign.

Templates & Resources

  • scoring-models/lead-scoring-framework.md: Template for developing a lead scoring model.
  • scripts/analyze-lead-quality.py: (Optional) Script to analyze lead quality data.

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.