agentleFS
Sign inStart free
latour-ailatour-ai/skills/inbox-triage/SKILL.md

inbox-triage

Skill69 starsChanged 26 days agoNo licenceView on GitHub

Pre-market inbox triage for hedge fund executives. Scans Gmail and surfaces only the emails that matter before the trading day starts. Use this skill whenever the user asks to triage their inbox for trading day prep, says "pre-market inbox", "morning email scan", "what's urgent before the open", "check my email", "inbox triage", "morning briefing", "email priorities", "what needs my attention", "any urgent emails", "what did I miss overnight", "catch me up on email", "what's waiting for me", "pre-market check", "morning triage", or any variation of wanting to see what emails need attention before markets open. Also trigger when the user says "trading day prep", "what came in overnight", "anything from investors", "LP emails", "compliance emails", "risk alerts", or mentions needing to scan email before the bell. This skill is purpose-built for hedge fund and investment management executives who receive hundreds of emails daily and need a ruthlessly filtered view of what actually matters.

52 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 45 edited versions we read keep these.

  • 10

    Distinctive

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

Check your setup, free