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

sellside-research-triage

Skill69 starsChanged 26 days agoNo licenceView on GitHub

Triage a batch of sell-side research — a morning's notes pasted or attached, a folder of PDFs, or a forwarded-email export — against a coverage list and the desk's current key debates: rating and estimate changes on covered names flagged first with the analyst's stated reason, notes carrying a genuinely new argument or data point summarized in two sentences with a "why you care" line, and everything else dismissed in one line as maintenance, duplicative, or off-coverage. Ends with a verdict on the two or three notes actually worth opening today, in priority order. For research analysts and PMs at any fund drowning in broker flow. Trigger on phrases like "triage this morning's research," "what's in the broker notes," "anything worth reading in this pile," "any estimate changes on our names," "sort my research inbox," "which of these notes matter," or when a user drops a stack of sell-side notes with a coverage list. Do NOT use for triaging a general email inbox for action items — use the inbox-triage skill. Do NOT use for a mixed reading pile of newsletters, memos, and alerts; this skill is built for broker research. Do NOT use for the earnings call or results themselves — use the earnings-call-extractor skill. A triage verdict is a reading decision, not a view on any security.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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.

Check your setup, free