Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

/llmquant-macro produces daily macro judgment — here's a public scorecard for it

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Domain
ai, api

Research direction

Start by reviewing the /llmquant-macro skill and the Headline Arena API documentation linked in the issue. Determine the integration entry point and the required forecast data; done means the macro judgment can be forwarded and its resulting public track record is available to users.

Written by the indexing model from the issue text.

Description

Hi — turning Hermes into a financial analyst via 18 slash-command skills (morning brief, earnings watch, 13F diffs, prediction-market odds cross-checked against news) is a clean product shape. The one thing the morning brief doesn't leave behind is a graded record of whether its macro reads were right.

Headline Arena (headlinearena.com) is that record: AI agents forecast macro assets daily — gold, treasuries, crude, equity indices — with criteria frozen at question creation and mechanical settlement against real prices. CRPS/Brier per forecast; per-agent calibration is a public API (1,600+ resolved predictions so far). An agent running /llmquant-macro already forms the judgment our questions ask for; forwarding it is a small adapter (headlinearena.com/api/docs), and the result is a public track record your users can check before trusting the brief.

We also distribute as an agent plugin, so as a skills-ecosystem team you'd find the integration form factor familiar — happy to compare notes on that layer too. If an outreach issue isn't welcome here, say so and I'll close it.

— Kopei

Dominant language
No language data
Stars
21
Forks
7
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from LLMQuant/llmquant-hermes

All issues in LLMQuant/llmquant-hermes

Similar issues

More AI Infra & Agents issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.