agentleFS
Distilla-AIDistilla-AI/distilla-skills/stock-screener/SKILL.md

stock-screener

Skill9 starsChanged 41 days agoNo licenceView on GitHub

Cross-universe / multi-company screening — filters a declared universe down to a ranked, evidence-backed shortlist. Produces a universe declaration, count contract, ranked table with per-row evidence, and caveats block. Use when the user asks "Which companies …", "Screen for …", "Rank by …", "Top N …", "Companies with X …" — any cross-sectional filter or ranking question returning a *list* of issuers **without a directional trade thesis**, including which stocks were upgraded or downgraded (rating-event screens). Do NOT use for single-company analysis (`initial-screen`, `company-brief`), market-recap summaries (`daily-brief`), historical macro pattern questions about past market behavior ("which sectors historically outperformed after X"), or actionable long/short trade recommendations carrying thesis + catalyst + invalidation + R/R — use `long-short-ideas` for that last case.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 14 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 2

    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 5 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.