agentleFS
andrerodriguesopsandrerodriguesops/gtm-engine/.claude/skills/weekly-exec-update/SKILL.md

weekly-exec-update

Skill0 starsChanged 9 days agoMITView on GitHub

The weekly executive sales update: a cross-deal digest of every active deal with status, latest call score, next step and the real blocker named by its MEDDPICC letter. Use for "weekly exec update", "Friday update", "brief leadership on the pipeline". For one deal, use call-debrief.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Check the calendar and inbox for the week.

    line 16
  2. Distinctive:

    Every figure comes from the CRM or the log.

    line 46

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

Weekly exec update

Workflow

  1. Pull every deal in the active stages of the pipeline (crm-records).
  2. From each description log, read the newest entries since last Friday and the latest Call score: line.
  3. Check the calendar and inbox for the week. The CRM lags: a meeting the client booked from their side, or a reply in Gmail, never reaches the record on its own. With no calendar or Gmail connector, skip this and say so at the top of the digest.
  4. Name each deal's real blocker by its MEDDPICC letter (sales-call-scorer/RUBRIC.md §B): the deal's blockers field and the latest scorecard's "MEDDPICC open" line say which letters are still unknown for its stage.
  5. Classify each deal: ADVANCED / HELD / SLIPPED / NEW / CLOSED.
  6. Roll up.

Output

Status: [N] active deals, [n] advanced, [n] slipped, [n] new. Weighted pipeline [figure from CRM].

MOVED THIS WEEK
- [Deal]: [stage change], [why, one line]

NEEDS A DECISION
- [Deal]: [decision], [who decides], [by when]

AT RISK
- [Deal]: [MEDDPICC letter] [blocker], [move]

ALL DEALS
| Deal | Stage | Last call | Score | Next step | Blocker (MEDDPICC) |

Hard rules

  • Open with plain status facts. No narrative arc, no triumphal framing.
  • Every figure comes from the CRM or the log. Nothing estimated.

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.