agentleFS
anyreachaianyreachai/claude-skills/skills/bpo-roi-internal-briefing/SKILL.md

bpo-roi-internal-briefing

Skill1 starsChanged 7 months agoNo licenceView on GitHub

Generate the internal-only Word briefing that accompanies a BPO outcomes-based ROI pitch. This is the document that goes to the BPO's internal team (sales, commercial, ops leadership) — never to the end client. It contains talking points, margin profile (honest blended cost vs. customer-paid price), red lines, intel findings, confidentiality notes, and the script for handling tough customer questions. Reuses the same config schema as bpo-roi-brief plus an optional internal_briefing section. Trigger whenever the user asks for an 'internal briefing', 'sales team briefing', 'talking points doc', 'margin profile doc', 'red lines doc', 'pre-call alignment doc', 'BPO team enablement doc', or any internal Word doc accompanying an outcomes-based ROI pitch. Always use this skill instead of writing the doc from scratch.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.