agentleFS
link7373link7373/agentic-sales-marketing/.claude/skills/measure/SKILL.md

measure

Skill1 starsChanged 3 months agoMITView on GitHub

Produce the honest numbers — weekly scorecard, campaign performance, funnel conversion, spend efficiency — translated into three plain lines and next actions. Run weekly, and on demand for "is it working?

5 other projects use 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. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No strategy exists yet → don't fake a scorecard.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

/measure — Honest Numbers, Plain Words

Inputs: knowledge/strategy.md (targets), active briefs in knowledge/campaigns/, knowledge/pipeline.md, connected tool dashboards via knowledge/tool-registry.md, knowledge/results-history.md. Agents: growth-analyst leads; tools-operator pulls data. Method: knowledge/methods/funnel-and-measurement.md.

Steps

  1. Pull the week. From each connected source: funnel-stage numbers (visits/reach → clicks/opens → leads/conversations → sales), spend, per-campaign performance. Note retrieval dates; missing data is reported missing, never interpolated.
  2. Fill the scorecard. templates/weekly-scorecard.md — this week, last week, target. Absolute counts beside rates (small-sample honesty).
  3. Judge against the plan. Each active campaign vs its brief's success metric and kill threshold. Anything past its threshold gets flagged with the pre-committed action — kill, adjust, or extend with reason.
  4. Attribute what's knowable. UTM data, marketplace stats, and the "how did you hear about us?" answers. State confidence; "can't tell yet" is a valid finding.
  5. Reconcile the money. Update knowledge/budget.md: approved vs actually spent per channel this week, and return where attributable (revenue, or pipeline value at honest stage-weighted odds). Flag any channel spending ahead of its approval or pacing past its monthly cap. Cost-per-sale per channel is the number the operator most needs and least often sees.
  6. Track the keep-rate. Where the model supports it: repeat purchase rate (B2C), churn/renewal and expansion (B2B recurring), refund rate. A leaky bucket makes every acquisition number a lie.
  7. Write the three lines. What worked / what didn't / what changes next week — in words the operator needs no glossary for.
  8. Bank the learnings. Each finding that changes how we operate becomes one dated line in the relevant method file's "What we've learned here" section (cite the scorecard week). No essays — one line, one source.
  9. Queue next week. Approval batch needed (spend, outbound, publishing), experiments ready to call (route to /experiment), and recommended actions ranked by expected impact.

Before you start

  1. Required inputs: knowledge/strategy.md approved (targets to judge against); knowledge/results-history.md and knowledge/budget.md as they exist. This skill runs on the weekly schedule — verify the scheduled task fired it or run manually.
  2. Scan knowledge/decision-log.md for tags budget, channel — pre-committed kill thresholds are decisions, not suggestions.
  3. Gate check: none to execute — but this skill queues next week's approval batch.

If things go wrong

  • A data source is unreachable this week → report the number as missing (never interpolate), note the source and retry path; if it recurs, route to /connect-tools.
  • Numbers contradict each other across sources → report both with the discrepancy flagged; pick the more conservative for decisions.
  • No strategy exists yet → don't fake a scorecard; report activity honestly and recommend /plan-strategy.

Outputs

The weekly scorecard appended to knowledge/results-history.md; updated knowledge/budget.md; the three-line summary; a ranked action list. Close with the report per templates/skill-report.md.

Writeback

knowledge/results-history.md; knowledge/budget.md; kill/adjust decisions (tags: budget, channel) to knowledge/decision-log.md; campaign briefs' results sections; learning lines to the relevant knowledge/methods/*.md.

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.