agentleFS
latour-ailatour-ai/skills/performance-attribution-narrator/SKILL.md

performance-attribution-narrator

Skill69 starsChanged 24 days agoNo licenceView on GitHub

Turn raw attribution output into the performance narrative a PM, CIO, or investor actually needs — return decomposed into alpha versus factor beta, the largest contributors and detractors assessed against the thesis that justified each position, "right for the wrong reasons" winners flagged, and a drafted performance commentary section for the investor letter in the firm's voice. For portfolio managers, CIOs, risk and quant teams, and IR professionals at hedge funds, long-only managers, and multi-strategy firms. Trigger on phrases like "write up the attribution," "explain the month," "why were we up," "what drove performance," "draft the performance commentary," "turn this attribution into a narrative," "month-end write-up," "was this alpha or beta," or when a user uploads attribution output, a P&L by position or sector, or a risk model decomposition. Do NOT use for drafting a full quarterly LP letter — use the lp-update-generator skill. Do NOT use for synthesizing other managers' letters — use the quarterly-letter-synthesizer skill. Performance commentary drafted here requires compliance review before it goes to investors.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    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 350,495 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.