agentleFS
latour-ailatour-ai/skills/executive-briefing/SKILL.md

executive-briefing

Skill69 starsChanged 24 days agoNo licenceView on GitHub

Turn messy source material into a concise executive briefing (500 words or fewer). For executives, founders, investors, consultants, and operators who need to quickly understand a topic, meeting, company, market, project, or decision context. Use whenever the user says "brief me," "executive summary," "executive briefing," "decision brief," "what do I need to know," "catch me up," "prepare me for," "summarize this for a meeting," "key takeaways," "background context," "what's important here," "TL;DR," "bottom line," "prep me," "distill this," "boil this down," or "what matters here." Also trigger when the user provides articles, meeting notes, PDFs, memos, or pasted text and wants a summary for a busy reader or decision-maker — even without the word "briefing." If the user is preparing for a meeting, board session, or investor call and wants to understand background material quickly, this skill applies. Source-agnostic.

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

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 5

    Distinctive

    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 measured: kept by at least 6 in 10 of the 8 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.

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.