agentleFS
Distilla-AIDistilla-AI/distilla-skills/sell-side-brief/SKILL.md

sell-side-brief

Skill9 starsChanged 41 days agoNo licenceView on GitHub

Multi-company Sell-side Brief — a one-bullet-per-ticker digest of broker research activity over a recent window (default: last 7 days): rating, target, estimate and thesis changes, new company events, theme commentary and reiterations. Covers the user''s watchlist by default, OR any universe the user names — a sector, theme, region, index or ticker list (e.g. ''HK consumer stocks'', ''my portfolio'', ''AAPL MSFT NVDA''). ALWAYS use when the user says ''sell-side brief'', ''broker brief'', ''research brief'', ''weekly/morning brief'' on broker notes, invokes ''/sell-side-brief'', or asks what brokers said, changed or published last week / over the last N days across a group of stocks — even if no watchlist is mentioned. Do NOT use for a deep single-company memo on analyst coverage, consensus, broker coverage table, or valuation methodology (use `sell-side-view`), or for a question asking which stocks were upgraded or downgraded — a rating-event screen (use `stock-screener`).

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 9 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    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.