hmbown/foresight
generated/hermes/investigation-and-preparation/foresight/SKILL.md
Foresight produces bounded forecasts with explicit uncertainty to guide decisions. It is NOT: - Preflight checks: Verifying prerequisites before executing a known action (disk space, backups, connection strings). Those are safety gates, not forecasts. - Diagnosis/Debugging: Finding what's broken right now (null pointers, deprecated APIs). Those are root-cause analyses, not predictions. - Monitoring: Watching real-time metrics or alerting on thresholds. Those are observability tasks, not forward-looking estimates. - Reconnaissance: Gathering facts about competitors or systems. Intelligence gathering feeds foresight but isn't foresight itself. Key distinction: If the user wants to know "what will likely happen if we choose X," use Foresight. If they want to know "is it safe to run X now," "what's broken," or "what are they doing," use a different spell.
$ install --global
skillsauthnpx skillsauth add hmbown/wizards-of-the-ghosts foresightInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 4:46 PM3.8s1 file scanned
SKILL.md
- name:
- foresight
- description:
- Foresight produces bounded forecasts with explicit uncertainty to guide decisions. It is NOT:\n- Preflight checks: Verifying prerequisites before executing a known action (disk space, backups, connection strings). Those are safety gates, not forecasts.\n- Diagnosis/Debugging: Finding what's broken right now (null pointers, deprecated APIs). Those are root-cause analyses, not predictions.\n- Monitoring: Watching real-time metrics or alerting on thresholds. Those are observability tasks, not forward-looking estimates.\n- Reconnaissance: Gathering facts about competitors or systems. Intelligence gathering feeds foresight but isn't foresight itself. Key distinction: If the user wants to know \"what will likely happen if we choose X,\" use Foresight. If they want to know \"is it safe to run X now,\" \"what's broken,\" or \"what are they doing,\" use a different spell.
- version:
- 1.0.0
- author:
- Wizards of the Ghosts
- license:
- CC0-1.0
- compatibility:
- Hermes Agent skills system
Foresight
Estimate likely outcomes before committing to a plan, change, or launch.
What This Skill Does
Foresight produces bounded forecasts with explicit uncertainty to guide decisions. It is NOT:
- Preflight checks: Verifying prerequisites before executing a known action (disk space, backups, connection strings). Those are safety gates, not forecasts.
- Diagnosis/Debugging: Finding what's broken right now (null pointers, deprecated APIs). Those are root-cause analyses, not predictions.
- Monitoring: Watching real-time metrics or alerting on thresholds. Those are observability tasks, not forward-looking estimates.
- Reconnaissance: Gathering facts about competitors or systems. Intelligence gathering feeds foresight but isn't foresight itself. Key distinction: If the user wants to know "what will likely happen if we choose X," use Foresight. If they want to know "is it safe to run X now," "what's broken," or "what are they doing," use a different spell. In this grimoire, Foresight is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Foresight (spell).
When To Use
- Activate this spell when the user asks for a forward-looking, probability-weighted forecast to inform a decision. Look for:
- Explicit choice between options ("should we X or Y?", "migrate vs stay", "build vs buy")
- Time-bounded outcome requests ("over the next 12 months", "by Q3", "18-month trajectory")
- Risk/uncertainty language ("risk-weighted", "confidence level", "probability", "best case/worst case", "weal or woe")
- Decision frameworks with explicit unknowns ("what would change your recommendation?", "decisive unknowns")
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Scope the decision: Restate the choice, the time horizon, and what success/failure looks like.
- Map the paths: List the strongest upside and downside scenarios for each option.
- Estimate from evidence: Assign likelihoods based on current data, not vibes. State your assumptions explicitly.
- Return the forecast: Deliver (a) a recommendation with confidence level, (b) a short risk matrix, and (c) the decisive unknowns that would change the call.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- Recommendation: [clear choice] (Confidence: X%) Assumptions: [what you're basing this on]
- | Path | Upside | Downside | Likelihood |
- Decisive Unknowns: [1-3 things that would change this call] ```
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not use for: "Check if the backup completed before I run this" → Preflight
- Do not use for: "Find all deprecated API calls in our codebase" → Scan/Diagnosis
- Do not use for: "Alert me if error rates exceed 2% this hour" → Monitoring
- Do not use for: "What features is our competitor shipping?" → Reconnaissance
- Do not use for: "Why is this function throwing a null pointer?" → Diagnosis
- Do not use for: Activate only when the core request is forecasting outcomes to inform a choice under uncertainty.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
Example Invocation
/foresight evaluate this decision, give me the likely upside and downside, and tell me what would change your call
Related Skills
hmbown/zone-of-truth
testing
VerifiedTrustedCommunity
Enter a mode where every assertion is backed by evidence, confidence is calibrated, speculation is flagged, and hallucination is actively resisted.
55SKILL.mdUpdated Apr 5, 2026
hmbown/vicious-mockery
development
VerifiedTrustedCommunity
The bard's cantrip that deals psychic damage through insults. In practice this is adversarial review — the art of finding and articulating exactly what is wrong with something in a way that is impossible to ignore. Unlike polite feedback that gets filed and forgotten, vicious mockery lands. It is the red-team report that makes the PM cancel the launch, the code review that makes the author delete the PR, the roast that makes the founder pivot. The damage is the point.
55SKILL.mdUpdated Apr 5, 2026
hmbown/unseen-servant
tools
VerifiedTrustedCommunity
Use this spell when you need a tireless helper that organizes, tidies, triages, and maintains without requiring your constant attention.
55SKILL.mdUpdated Apr 5, 2026
hmbown/true-strike
testing
VerifiedTrustedCommunity
Use this spell for preflight certainty: dry runs, validation checks, dependency verification, and rehearsals that make the next deploy, query, or command much more likely to succeed. It trades a little time up front for fewer blind swings and fewer expensive misses.
55SKILL.mdUpdated Apr 5, 2026