agentleFS
y0n1n1y0n1n1/financial-skills/parameters/SKILL.md

parameters

Skill1 starsChanged 38 days agoMITView on GitHub

Define trigger parameters for when a stock theory changes in truth. Analyzes fundamental, technical, competitive, and macro triggers with severity levels (minor/major/exit). Run after establishing a theory. Use with /parameters NVDA.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. iPlug2/iPlug2★ 2.4ksame name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If no theory card exists: tell Gabriel to run /theory TICKER first

    line 20
  2. Distinctive:

    Check if parameters are in independent clusters or correlated

    line 41
  3. Distinctive:

    If clustered: consolidate redundant triggers, add triggers from underrepresented categories

    line 43
  4. Distinctive:

    Always fetch CURRENT values via WebSearch to set realistic thresholds

    line 83
  5. Distinctive:

    Don't overwhelm — recommend a focused set of 6-10 key parameters

    line 85
  6. Distinctive:

    NEVER make up current values — if WebSearch fails, say so

    line 86

≈ “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.

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

Parameter Definition

Define specific, measurable triggers that would change a theory's truth value. These are set BEFORE entering a position, not after you're already emotional about it.

Input

Gabriel provides:

  • Ticker (required): e.g., NVDA
  • Theory card MUST exist at investing/theories/TICKER.md — run /theory first if it doesn't

Process

  1. Read the theory card from investing/theories/TICKER.md
    • If no theory card exists: tell Gabriel to run /theory TICKER first
    • The parameters MUST be specific to THIS theory, not generic
    • Read the pre-mortem section — extract "Suggested New Parameters" and "Gap" assessments. These are failure modes the pre-mortem identified that may not have corresponding parameters yet. Include them in the trigger proposal set.
    • Read the Fermi Decomposition sensitivity — the most sensitive Fermi component should have the MOST and TIGHTEST parameters watching it
  2. Run all 4 trigger analysis sub-skills — each in this skill's directory:
    • fundamental-triggers.md — earnings/financial triggers
    • technical-triggers.md — price/chart triggers
    • competitive-triggers.md — market position triggers
    • macro-triggers.md — external environment triggers
  3. Each sub-skill proposes specific triggers with:
    • The trigger condition (specific and measurable)
    • Current value of the metric
    • Threshold that would trigger reassessment
    • Severity: MINOR / MAJOR / EXIT
    • Whether it's theory-specific or generic
  4. FMEA score each trigger (fmea-scoring.md):
    • Rate Severity (1-10), Occurrence (1-10), Detection (1-10)
    • Calculate RPN = S × O × D
    • High-D triggers (hard to detect) get special attention — find leading indicators
  5. Present all proposed triggers organized by type with RPN scores
  6. Run Defense Independence Audit (defense-independence.md):
    • Check if parameters are in independent clusters or correlated
    • Grade: A (>80% independence) through D (<40%)
    • If clustered: consolidate redundant triggers, add triggers from underrepresented categories
  7. Ask Gabriel which triggers to activate
  8. Write chosen parameters to the theory card

Severity Levels

  • MINOR — re-run the relevant theory lens, probably hold. Something to watch.
    • Example: RSI hits 75, approaching overbought
  • MAJOR — re-run full theory analysis, position at risk. Something changed.
    • Example: earnings miss consensus by 15%
  • EXIT — theory is broken, sizing should go to zero. Get out.
    • Example: competitor achieves technological parity, destroying the moat thesis

Output Format

## Proposed Parameters for [TICKER]
Theory: "[theory statement]"

### Fundamental Triggers
| # | Trigger | Current | Threshold | Severity | Theory-Specific? |
|---|---------|---------|-----------|----------|-----------------|
| F1 | QoQ revenue growth | 80% | <15% | MAJOR | Yes — growth thesis |
| F2 | Gross margin | 75% | <65% | MAJOR | Yes — monopoly pricing |
| F3 | Earnings miss | - | >10% miss | MINOR | No — generic |

### Technical Triggers
[same format]

### Competitive Triggers
[same format]

### Macro Triggers
[same format]

Then: "which of these do you want active? you can pick all, or just the ones that matter most. i'd recommend at minimum [X, Y, Z]."

Rules

  • Parameters MUST be specific and measurable — "if X crosses Y" not "if things get bad"
  • Always fetch CURRENT values via WebSearch to set realistic thresholds
  • Distinguish between theory-specific and generic parameters
  • Don't overwhelm — recommend a focused set of 6-10 key parameters
  • NEVER make up current values — if WebSearch fails, say so
  • Gen z tone, rigorous analysis

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.