agentsclimarketplace
Sign in

Event preread

Skill Jinchengawu/stock-monitoring-kit/skills/event-preread

Build scenario-based prereads for earnings, CPI, payrolls, central-bank decisions, elections, Treasury events, and other scheduled market catalysts. Use when the user wants an event calendar preview, consensus comparison, prediction-market interpretation, likely transmission paths, or advance risk monitoring.From its SKILL.md

Install
npx -y skills add Jinchengawu/stock-monitoring-kit --skill event-preread

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.7 KB, 269 tokens by cl100k_base, as published. Nobody here has run it

Event Preread

Turn a scheduled catalyst into testable scenarios. Keep market-implied probability separate from factual likelihood and analyst consensus.

Workflow

  1. Verify event name, release time, timezone, source, affected markets, and relevant symbols.
  2. Collect prior reading, current consensus, range of estimates, revisions, and any official guidance.
  3. When prediction-market data is available, record question wording, timestamp, probability, liquidity, resolution rules, and source URL. Treat thin or ambiguous markets as low-confidence evidence.
  4. Create upside/base/downside scenarios. For each, specify:
    • Numeric or qualitative trigger
    • First-order impact
    • Second-order transmission across rates, currencies, commodities, sectors, and symbols
    • What would invalidate the scenario
  5. Identify positioning or technical context only when supported by supplied data.
  6. After release, preserve the preread so it can be compared with the observed result.

Output

  • Verified calendar entry
  • Consensus and uncertainty range
  • Prediction-market snapshot with caveats
  • Scenario table with optional probabilities that sum to approximately 1
  • Transmission map and exposed watchlist items
  • Release-time verification checklist
  • Sources, timestamps, missing data, and disclaimer

Never present a prediction-market price as certainty or fabricate consensus data.

What ships with it: 1 file

484 B alongside SKILL.md

agents/

Keep looking

Skills are one crate of 326,782. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.