agentleFS
rasulshaikhrasulshaikh/fde-desk/.claude/skills/weekly-pipeline-pulse/SKILL.md

weekly-pipeline-pulse

Skill0 starsChanged 48 days agoMITView on GitHub

Weekly snapshot of desk motion: signals in, accounts progressed, drafts shipped to human review, blockers. End of week, or /desk-close on Friday sessions. ops/<slug>/pulses/pulse-<YYYY-WW>.md

The file

Files
SKILL.md

Skill: weekly-pipeline-pulse

Weekly snapshot of desk motion: signals in, accounts progressed, drafts shipped to human review, blockers.

When to use

End of week, or /desk-close on Friday sessions.

Sections

  1. Throughput table (signals reviewed, enriched, mapped, drafted)
  2. Top movers (accounts that changed band)
  3. Slippage (stuck enrichments, missing personas)
  4. Experiments (subject lines, Clay columns, scoring tweaks)
  5. Asks for the operator next week

Output

ops/<slug>/pulses/pulse-<YYYY-WW>.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.