Skip to content
SkillScript-led633 tokens in use

Edge Hint Extractor

Converts daily market summaries, anomaly lists and news reactions into structured edge hints in hints.yaml, with optional LLM-written ideas merged in.

7,426 stars on the repository MIT Licensetradermonty/claude-trading-skills · skills/edge-hint-extractor

Skill label

measured from its files

What installing Edge Hint Extractor costs

37tokens idle
633tokens in use
1,095tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/build_hints.py.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter8/15
  • Structure23/25
  • Examples12/15
  • Output7/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 51
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    scripts/build_hints.py, line 525

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community68
  • Maturity36
  • Momentum40

Edge Hint Extractor is the first stage of the split edge research workflow: observe, abstract, design, pipeline. It reads market_summary.json, anomalies.json and optional news reaction files from a detector run, and a Python script generates deterministic rule-based hints.

You can add ideas written by a language model, either from a pre-written YAML file or from an external command. The result is hints.yaml with metadata and rule and LLM hint counts. It structures research input and gives no investment advice.

What You Get

  • A hints.yaml file with a list of structured hints
  • Generation metadata and counts of rule-based and LLM-generated hints
  • Constrained ideas, because model hints are tied to the day’s anomalies and news context
  • A clean input file for the concept synthesizer or the candidate detector

Common Use Cases

  • Turning a day’s anomalies and news reactions into reusable hint objects
  • Letting the model propose ideas that stay close to the observed data
  • Preparing the input for concept synthesis in a daily research routine

What Makes It Unique

It supports two ways to add model ideas, an external command and a hints file, so it works with a separate LLM tool and with Claude writing hints inside the session. Rule-based hints are always generated first, which keeps the base output repeatable.

Under The Hood

The agent runs a local Python script that reads JSON and CSV observation files and writes hints.yaml. With the command option the script starts the command you supply as a subprocess and reads its output, so that command runs on your machine with whatever access it has. The file option reads a local YAML file. It needs Python and PyYAML, and a hints schema reference loads when needed.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers