Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    lead qualification workflow designer

    1

    Stop guessing why leads aren't reaching sales or why the handoff process is messy.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    lead qualification workflow designer

    lead qualification workflow designer

    Example session with this skill installed

    Define a 3-stage workflow: Discovery, Intent, and SQL. Discovery needs self-reported industry. Intent needs verified budget. SQL needs an executive meeting. Handoff to AE with 24h SLA.

    • Read your context and instructions
    • Compiled the lead qualification workflow

    I have designed the lead qualification workflow based on your requirements. I have registered the workflow document as E1.

    Lead Qualification Workflow — Acme Corp, 2024-05-24

    1. Scope, sources and assumptions

    • Sources: E1 (User Requirements)
    • As-of date: 2024-05-24
    • Access scope: Sales Team A
    • Minimum group size: 5
    • Assumption: "Executive meeting" is defined as an observed event with a source reference (E1).

    2. Stages, evidence and handoff rules

    OrderStageRequired evidenceNew at this stage
    1Discoveryindustry_refindustry_ref
    2Intentindustry_ref, budget_vbudget_v
    3SQLindustry_ref, budget_v, exec_meet_oexec_meet_o
    EvidenceKindMax age (days)Source required
    industry_refself_reported365No
    budget_vverified180Yes
    exec_meet_oobserved90Yes

    Handoff Rule:

    • From Stage: SQL (3)
    • To Role: AE
    • SLA: 24 hours
    • Consent Required: Processing & Contact
    • Cumulative Evidence: industry_ref, budget_v, exec_meet_o

    3. Design findings

    • No design findings.

    4. Lead evaluation

    No leads supplied.

    5. Proposed actions (drafts requiring approval)

    No actions proposed. No leads were provided for evaluation.

    6. Warnings and information gaps

    Information gap — organizational validation required: Maximum age for evidence was set to defaults; verify if 180 days for budget is appropriate for your cycle.

    7. Items for human review

    • Review the requirement for "verified" budget; ensure the verification process is documented.
    • Management decision required: Approval of the 24h SLA for AE handoffs.
    • Management decision required: Final sign-off on the SQL stage criteria.

    This analysis supports, and does not replace, professional judgment and management's decision.

    Next steps

    1. Provide a CSV of pseudonymous leads to test this workflow.
    2. Confirm the specific source channels that will be used for "verified" budget data.
    3. Review the 24-hour SLA with the AE team lead.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Stop guessing why leads aren't reaching sales or why the handoff process is messy. This skill forces structure onto lead qualification by defining explicit stages, evidence requirements, and expiration rules. It eliminates the ambiguity of "warm" leads by requiring specific, verifiable proof for every progression step.

    What it does

    • Design workflows by defining ordered qualification stages with mandatory evidence types.
    • Set evidence rules specifying maximum age in days, provenance requirements, and evidence kinds.
    • Establish exit criteria including disqualifiers and specific handoff rules for sales roles with SLA hours.
    • Validate designs to identify gaps like stages that add no new evidence or evidence that never expires.
    • Test leads by running authorized lead data through a deterministic script to see who qualifies for handoff.

    How it works

    1. Define the model by providing the workflow stages, evidence catalog, and handoff rules.
    2. Execute validation using the scripts/run.py tool to check for design conflicts or gaps.
    3. Simulate lead flow by supplying authorized, pseudonymous lead data to the evaluation engine.
    4. Review drafts of proposed handoff actions that require human approval before any CRM changes.

    Frameworks & tools

    This skill uses a Python-based execution engine (scripts/run.py) and JSON schemas for strict data validation. It operates on pseudonymous data to maintain privacy.

    Why this beats prompting it yourself

    Generic prompts often hallucinate conversion rates or ignore evidence expiration. This skill uses a deterministic script to ensure leads only progress when every specific evidence requirement is met, preventing the agent from "guessing" a lead's status.

    Use cases

    • Auditing a CRM workflow to find stages that lack verified evidence requirements.
    • Testing a new sales handoff SLA against a batch of historical lead data.
    • Formalizing evidence provenance rules to ensure only sourced data triggers a handoff.
    • Creating a disqualified lead report based on specific exclusionary criteria.

    Known limitations

    Does not support points-based or weighted scoring. It cannot contact leads, assign owners, or modify CRM records directly. All handoff proposals are drafts requiring human approval.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Sales & Lead Gen.

    No support for weighted scoring. Cannot edit CRM records or contact leads directly. Handoffs are drafts only. Requires human approval for all actions.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 days ago

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Environment Variables
    Listed2 days ago

    What's inside

    Frequently Asked Questions

    This skill replaces subjective lead scoring with a deterministic Python-based engine that requires verifiable evidence for every stage, ensuring sales only receives leads that meet 100% of your defined criteria.

    You will receive the Python execution engine (scripts/run.py), the JSON schemas for workflow definition, documentation on evidence rules, and example templates for stages and handoff rules.

    No, this skill operates as a standalone logic engine that processes pseudonymous lead data; it provides draft handoff proposals for human approval rather than making direct CRM edits.

    It is designed for any AI agent capable of executing Python scripts and managing JSON files, making it ideal for developer-focused environments or agents with local file system access.

    The validation tool identifies 'logic gaps,' such as stages that don't require new evidence, rules that allow for expired data, or workflows that lack a clear path to a sales handoff.

    This skill is built for strict, binary qualification (Pass/Fail) based on evidence; it does not currently support weighted points-based scoring or probabilistic lead heatmaps.

    New in Sales & Lead Gen