agentleFS
Sign inStart free
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/ghl-funnel-inspector/SKILL.md

ghl-funnel-inspector

Skill4 starsChanged 6 months agoMITView on GitHub

Connect to GoHighLevel, inspect funnels, pages, forms, workflows, and conversion data. Map ads to pages and pages to outcomes. Use when diagnosing funnel performance or setting up tracking.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    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 diagnosing funnel performance issues (e.g., leads not entering workflows).

    line 12
  2. Distinctive:

    When setting up tracking for new campaigns.

    line 13
  3. Distinctive:

    When mapping ad performance to downstream CRM outcomes.

    line 14
  4. Distinctive:

    When reviewing automation logic and opportunity pipelines.

    line 15
  5. Distinctive:

    Analyze Pages: Check page settings, tracking codes (Meta Pixel, CAPI), and SEO metadata.

    line 27
  6. Distinctive:

    Review Forms: Ensure forms are correctly linked to workflows and capturing the necessary data.

    line 28
  7. Distinctive:

    Check Pipelines: Verify that opportunities are being created and moved correctly based on user actions.

    line 30
  8. Distinctive:

    Ensure all forms trigger the correct workflows and update the appropriate pipeline stages.

    line 43
  9. Distinctive:

    If API access is denied or credentials are invalid, request updated access.

    line 47
  10. Distinctive:

    If a critical workflow is broken (e.g., leads are not receiving follow-up emails), escalate immediately.

    line 48

≈ “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

GHL Funnel and Page Inspector

Purpose

Connect to GoHighLevel (VanX Funnels), inspect funnels, pages, forms, workflows, and conversion data. Map ads to pages and pages to outcomes to ensure seamless tracking and automation.

When to Use This Skill

  • When diagnosing funnel performance issues (e.g., leads not entering workflows).
  • When setting up tracking for new campaigns.
  • When mapping ad performance to downstream CRM outcomes.
  • When reviewing automation logic and opportunity pipelines.

Inputs Required

  • GoHighLevel API credentials or access to the VanX Funnels account.
  • Funnel or page URLs to inspect.
  • Specific workflows or forms to review.
  • The desired outcome (e.g., booked call, lead capture).

Step-by-Step Workflow

  1. Connect to GHL: Authenticate and access the relevant sub-account.
  2. Inspect Funnels: Review the structure of the funnel, including all steps and page URLs.
  3. Analyze Pages: Check page settings, tracking codes (Meta Pixel, CAPI), and SEO metadata.
  4. Review Forms: Ensure forms are correctly linked to workflows and capturing the necessary data.
  5. Examine Workflows: Trace the automation logic from form submission to the final outcome (e.g., tagging, email sequences, pipeline updates).
  6. Check Pipelines: Verify that opportunities are being created and moved correctly based on user actions.
  7. Map Data: Correlate ad clicks/leads with GHL contacts and opportunity stages.

Output Format

Provide a structured inspection report containing:

  • Funnel Overview: A summary of the funnel steps and their purpose.
  • Tracking Status: Confirmation that tracking codes are installed and firing correctly.
  • Automation Flow: A map of the workflow logic from entry to exit.
  • Issues Identified: Any broken links, missing tags, or failed automations.
  • Recommendations: Actionable steps to fix issues or improve tracking.

Decision Rules

  • Always verify tracking before making performance conclusions. If tracking is broken, flag it immediately.
  • Ensure all forms trigger the correct workflows and update the appropriate pipeline stages.
  • Recommend automations (workflows, triggers, pipelines, tagging, follow-ups) that can be systemized inside VanX Funnels.

Escalation Rules

  • If API access is denied or credentials are invalid, request updated access.
  • If a critical workflow is broken (e.g., leads are not receiving follow-up emails), escalate immediately.

Templates & Resources

  • api/ghl-endpoints.md: Reference for common GHL API endpoints.
  • scripts/pull-ghl-data.py: (Optional) Script to pull funnel data via GHL API.

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.

Check your setup, free