forge-prediction
Skill2 starsChanged 6 days agoMITView on GitHub
Playbook for predictions and sports data: odds, backtests, no betting (gebruik bij voorspellingen).
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- ForgeyClap/claude-forgeedited, first seen Oct 11, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- ForgeyClap/claude-forge★ 286% same
Wrote their own version · 0
None found.
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 repository99 other files it gives its agents.
- docs/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstormingSkill
- claude-md-improverSkill
- dispatching-parallel-agentsSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- forge-a11ySkill
- forge-agent-reportSkill
- forge-agentSkill
- forge-apiSkill
- forge-authSkill
- forge-autoresearchSkill
- forge-botsSkill
- forge-brainstormSkill
- forge-cliSkill
- forge-cmsSkill
- forge-code-reviewSkill
- forge-contextSkill
- forge-councilSkill
- forge-craftSkill
- forge-databaseSkill
- forge-dataSkill
- forge-debugSkill
- forge-deeplearnSkill
- forge-devopsSkill
- forge-docdriftSkill
- forge-doctorSkill
- forge-ecc-adapterSkill
- forge-ecommerceSkill
- forge-electronSkill
- forge-extensionSkill
- forge-figmaSkill
- forge-fullstackSkill
- forge-gameSkill
- forge-graded-verifySkill
- forge-guardianSkill
- forge-heartbeatSkill
- forge-i18n-docsSkill
- forge-intakeSkill
- forge-integrationSkill
- forge-long-form-writingSkill
- forge-mcp-clientsSkill
- forge-memorySkill
- forge-migrationSkill
- forge-mindmapSkill
- forge-mlopsSkill
- forge-mobileSkill
- forge-n8nSkill
- forge-nightshiftSkill
- forge-observabilitySkill
- forge-paymentsSkill
- forge-plan-largeSkill
- forge-prdSkill
- forge-projectbrainSkill
- forge-prompt-coachSkill
- forge-qualitySkill
- forge-ragSkill
- forge-registrySkill
- forge-releaseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use for: prediction and sports-data systems, including Telegram delivery.
- Distinctive: line 13
Never claim certainty: Every output carries a confidence/risk label.
- Distinctive: line 16
Verify data-source quality.
≈ “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.
Files
Forge playbook — Prediction / sports-data
When to use
- Use for: prediction and sports-data systems, including Telegram delivery.
Hard rules
- Never claim certainty. Every output carries a confidence/risk label.
- No automatic real-money betting / no auto-stake code path.
- Backtest before trusting any model; show sample size.
- Verify data-source quality; track all assumptions.
- Telegram token in env only; one message format, tested.
Team (conditional)
Lead: mle-reviewer + planner. Specialists: mle-reviewer, python-reviewer, silent-failure-hunter (data gaps look like clean zeros), database-reviewer (data store).
Skills / commands / MCP
systematic-debugging, /test-coverage. For delivery, defer to forge-n8n or a Telegram layer (Telegram bots fold in here).
Fan-out & flow
L3. Parallel: data ingestion ∥ model/stat logic ∥ delivery formatting. Serial: ingest → backtest → value/odds calc → uncertainty labeling → delivery.
Domain gates
Data sources + quality verified; statistical logic reviewed; backtesting done; odds/value checked; confidence/risk labels on every output; assumptions documented; data freshness check.
Ship-readiness (unique)
Backtest results shown with sample size; every output labeled with confidence/risk; assumptions + data-quality notes attached; no auto-bet path; Telegram message format tested. The ship-readiness prediction + Telegram checklists are advisory; optionally run codex-reviewer (Codex) on important code — not a blocker.
Safety, approval and honesty
- Approval / safety: no automatic real-money betting / no auto-stake code path.
- Approval / safety: Telegram token in env only.
- Honest failure: never claim certainty: every output carries a confidence/risk label; backtests show sample size.
- Shared gates for every playbook (honesty, owner approval, secrets, reviews):
.claude/docs/forge-reference/playbook-template.md.
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
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.