agentleFS
Nomanriaz786Nomanriaz786/claude-consulting-team/skills/funnel-diagnostic/SKILL.md

funnel-diagnostic

Skill1 starsChanged 25 days agoMITView on GitHub

Diagnoses funnel leakage when pipeline flow, conversion or cycle time prevents revenue delivery.

1 other project uses a version of this.

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:

    Use when sales lag despite apparent pipeline health or deals stall unexpectedly.

    line 9

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

Funnel Diagnostic

When to use it

Use when sales lag despite apparent pipeline health or deals stall unexpectedly.

What Claude needs

  • Background from client-context.md
  • Stage-level records from your CRM
  • Stage definitions and entry or exit rules
  • Source, segment, owner, value and date fields
  • Won, lost and inactive outcome reasons

Method

  1. Audit stage definitions, duplicate records and missing timestamps.
  2. Reconstruct cohorts by entry period rather than using one pipeline snapshot.
  3. Calculate stage conversion, time in stage and cumulative yield.
  4. Segment leakage by source, offer, customer type, owner and deal size.
  5. Distinguish quality, process, capacity and timing causes with an issue tree.
  6. Quantify priority bottlenecks and define measurable corrective experiments.

Output format

Provide a funnel table, cohort comparison, ageing view and bottleneck ranking. For each action show hypothesis, measure, owner and review date.

Quality checks

  • Stage populations use consistent cohort boundaries.
  • Open deals are not counted as completed outcomes.
  • Small samples and data-quality limits are clearly marked.

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.