agentleFS
Sign inStart free
DeevsDeevsDeevsDeevs/agent-system/alpha-squad/SKILL.md

alpha-squad

Skill40 starsChanged 8 months agoApache-2.0View on GitHub

Run multi-lens hypothesis generation across accounting, flows, networks, microstructure, and causal checks. Use when you need market hypotheses with mechanism, counterparty, and decay. Triggers: alpha squad, fundamentalist, vulture, network-architect, book-physicist, causal-detective, hypothesis generation, mechanism first.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants market hypotheses generated from complementary lenses.

    line 8
  2. Distinctive:

    Read README.md and enforce mechanism-first reasoning.

    line 20
  3. Very specific:

    If the user specified one role, spawn exactly that role with agent_type and task context.

    line 21
  4. Distinctive:

    If no role was specified, spawn all five roles in parallel and ask each for 1-3 high-conviction hypotheses.

    line 22
  5. Very specific:

    Use wait to gather results, then synthesize a single hypothesis slate.

    line 23
  6. Distinctive:

    Ensure every proposed hypothesis includes counterparty, constraint, decay horizon, and mechanism sketch.

    line 24
  7. Very specific:

    If confidence is weak or confounding is likely, run a follow-up pass with causal-detective before presenting final output.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Alpha Squad

Use this skill when the user wants market hypotheses generated from complementary lenses.

Role Map

  • fundamentalist -> agents/fundamentalist.md
  • vulture -> agents/vulture.md
  • network-architect -> agents/network-architect.md
  • book-physicist -> agents/book-physicist.md
  • causal-detective -> agents/causal-detective.md

Workflow

  1. Read README.md and enforce mechanism-first reasoning.
  2. If the user specified one role, spawn exactly that role with agent_type and task context.
  3. If no role was specified, spawn all five roles in parallel and ask each for 1-3 high-conviction hypotheses.
  4. Use wait to gather results, then synthesize a single hypothesis slate.
  5. Ensure every proposed hypothesis includes counterparty, constraint, decay horizon, and mechanism sketch.
  6. If confidence is weak or confounding is likely, run a follow-up pass with causal-detective before presenting final output.

Download now (ZIP)

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