Agent skill

Soft Predict Future

by davepoon in davepoon/buildwithclaude

Activate this skill for ANY future-oriented question. An agent skill from davepoon/buildwithclaude.

MITAuto-check passedProductivity & Automation

Install Soft Predict Future

skills CLI
$ npx skills add davepoon/buildwithclaude --skill soft-predict-future -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install davepoon/buildwithclaude soft-predict-future --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/davepoon/buildwithclaude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/foresight-intelligence/skills/soft-predict-future .claude/skills/soft-predict-future && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
soft-predict-future
GitHub stars
3.6k
Used in
1 other repo
Token cost
~5.4k tokens
SKILL.md length
1,302 words
Files
1
Skills in repo
245
Repo updated
First seen
Licence
MIT

At a glance

Activate this skill for ANY future-oriented question. An agent skill from davepoon/buildwithclaude.

  • Works in 9 steps: Validate Input → Collect Signals → Score Signals → …
  • Include: Will [X]?
  • SKILL.md covers Try Asking, The 9-Step Pipeline and Regional Multiplier Tables
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Soft Predict Future is an agent skill from davepoon/buildwithclaude. Activate this skill for ANY future-oriented question. Triggers include: "Will [X]?", "Who will win [X]?", "What happens to [X]?", "Can [X] succeed?", "What's the future of X?", foresight analysis, scenario planning, STEEEP analysis, futures cone, prediction requests, or any question about a future outcome. Year is NOT required — the engine infers the horizon. Also activate when the user says "predict", "forecast", "what are the odds", "scenario analysis", or asks about competitive races, technology adoption…

Its SKILL.md is about 5.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Web search. The repository describes itself as: A single hub to find Claude Skills, Agents, Commands, Hooks, Plugins, and Marketplace collections to extend Claude Code, Claude Desktop, Agent SDK and OpenClaw. The licence is MIT.

When your agent uses it

  • Include: Will [X]?
  • Who will win [X]?
  • What happens to [X]?
  • Can [X] succeed?

Example prompts

  • “Will [X]?”
  • “Who will win [X]?”
  • “What happens to [X]?”
  • “/soft-predict-future”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Validate Input
  2. Collect Signals
  3. Score Signals
  4. Extract Structural Drivers
  5. Build 6×3 STEEEP Matrix
  6. Cross-Impact Analysis
  7. Find 3 Historical Analogues
  8. Compute Probabilities + Confidence
  9. Write Scenarios + Assemble Report

What it can do on your machine

Read from SKILL.md and the folder at commit 10bfc43. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Soft Predict Future loads about 5.4k tokens when it runs. Until then it costs about 169 tokens; SKILL.md has 1,302 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~169
When it runs · the whole SKILL.md, loaded when a task matches
~5.4k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from davepoon/buildwithclaude at commit 10bfc43, republished under its MIT licence (© davepoon). 1,302 words, ~5,412 tokens.

Download SKILL.mdSave it as .claude/skills/soft-predict-future/SKILL.md (or your agent's skills folder).
name
soft-predict-future
description
Activate this skill for ANY future-oriented question. Triggers include: "Will [X]?", "Who will win [X]?", "What happens to [X]?", "Can [X] succeed?", "What's the future of X?", foresight analysis, scenario planning, STEEEP analysis, futures cone, prediction requests, or any question about a future outcome. Year is NOT required — the engine infers the horizon. Also activate when the user says "predict", "forecast", "what are the odds", "scenario analysis", or asks about competitive races, technology adoption, geopolitical shifts, or market dominance. REQUIRES web search to be enabled — if web search is unavailable, tell the user before proceeding.

Soft Predict Future — Foresight Engine

Activate when the user asks any future-oriented question — "Will [X]?", "Who will win [X]?", "What happens to [X]?", "Can [X] succeed?", or any question about a future outcome. Year is NOT required. Also activate on: foresight analysis, scenario analysis, STEEEP, futures cone, or any prediction request.


Try Asking

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TRY ASKING  (year optional — engine infers the horizon)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
■ Who will win — Google or Perplexity?
■ Will OpenAI or Anthropic dominate the AI race?
■ Will India become the global AI leader?
■ Will crypto replace banks?
■ Will remote work become permanent?
■ Will EVs dominate Indian cities by 2032?
■ Will UPI become Southeast Asia's default payment rail by 2028?
■ Will Europe lead the green energy transition by 2035?
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Soft Predict Future uses Claude's native reasoning + web search. Outputs are structurally correct and fast. For deterministic, auditable scoring say: "Run hard predict future: [your question]"


The 9-Step Pipeline

Execute ALL steps in order. Never skip. Never combine. Show your work at each step.


Step 1 — Validate Input

Apply exactly 5 binary rules. If ANY rule fails, stop and explain why. Do not proceed.

Rule 1 — Entity Reality: Does the entity actually exist in the real world? Fail if fictional, hypothetical, or unnamed.

Rule 2 — System Existence: Is the domain observable and researchable? Fail if purely philosophical or metaphysical.

Rule 3 — Time Horizon: Is the outcome observable within a 2–30 year window? A specific year is NOT required. If no year is given, infer the most reasonable horizon from the question's nature:

  • Competitive race / market dominance questions → 3–10 years (Strategic)
  • Technology adoption questions → 5–15 years (Strategic)
  • Geopolitical / societal shift questions → 10–20 years (Civilizational)
  • Company survival / near-term outcome → 2–5 years (Operational/Strategic)

Fail ONLY if the implied timescale is geological, post-human, or clearly beyond 30 years.

After applying Rule 3, state the inferred horizon (e.g. "2026–2033" or "2028–2038").

Rule 4 — Signal Availability: Could real-world evidence plausibly exist? Fail if classified, purely speculative, or unpublished.

Rule 5 — Minimum Specificity: Is the question specific enough to produce distinct scenario outcomes? Fail if trivially true for any answer.

Output:

VALIDATION
Rule 1 Entity Reality:      PASS / FAIL — [reason]
Rule 2 System Existence:    PASS / FAIL — [reason]
Rule 3 Time Horizon:        PASS / FAIL — [reason] | Inferred horizon: [YYYY–YYYY]
Rule 4 Signal Availability: PASS / FAIL — [reason]
Rule 5 Specificity:         PASS / FAIL — [reason]
Result: PROCEED / STOP

Step 2 — Collect Signals

Run exactly 6 web searches. Collect a minimum of 18 signals total. Do not proceed with fewer than 18.

Search 1: Current state — "[topic] current status [year]" Search 2: Growth indicators — "[topic] growth data market size [year]" Search 3: Barriers and headwinds — "[topic] challenges barriers risks" Search 4: Policy and regulation — "[topic] government policy regulation" Search 5: Technology or infrastructure enablers — "[topic] technology infrastructure investment" Search 6: Historical precedent — "[topic] historical analogue similar transition"

For each signal, classify all 6 attributes:

AttributeValues
directionsupporting / opposing / wildcard / neutral
steeep_categorySocial / Technological / Economic / Environmental / Ethical / Political
temporal_layerOperational (0–3yr) / Strategic (3–10yr) / Civilizational (10+yr)
source_typeprimary / secondary / opinion
recency_daysinteger
has_evidencetrue / false (contains a number, date, or measurable fact)

Present signals in a table with all 6 columns filled for every row.


Step 3 — Score Signals

Score every signal individually using this formula:

score = recency_weight × reliability_weight × type_weight × evidence_multiplier

Cap at 1.0. Round to 2 decimal places.

Recency weights:

  • 0–90 days: 1.00 · 91–365 days: 0.80 · 1–3 years: 0.60 · 3+ years: 0.40 · unknown: 0.50

Reliability weights:

  • Primary (government/official): 1.00
  • Established news (Reuters, Bloomberg, FT, ET): 0.90
  • Industry report (McKinsey, Gartner, NASSCOM): 0.85
  • Analyst commentary: 0.70 · Opinion/blog/social: 0.50 · Unknown: 0.40

Type weights:

  • Supporting: 1.00 · Opposing: 1.00 · Neutral: 0.60 · Wildcard: 1.30

Evidence multiplier:

  • DATA / STATISTIC: × 1.20 · EVENT / INCIDENT: × 1.00 · ANALYSIS / OPINION: × 0.70

Apply regional multiplier after base score:

final_score = min(1.0, base_score × regional_multiplier[steeep][temporal])

Show scoring table: Signal | recency_w | reliability_w | type_w | evidence_mult | base_score | regional_mult | final_score


Step 4 — Extract Structural Drivers

A driver is the deep structural force that explains WHY a cluster of signals exists. Signals are observable. Drivers are causal.

After scoring, group signals by STEEEP category. For each cluster of 3+ signals in the same category, identify the underlying driver.

Extract exactly 3 top drivers, ranked by the sum of final_scores of the signals they explain.

For each driver state:

  • Name: 3–5 word label (e.g. "India DPI Infrastructure Advantage")
  • Force: One sentence — the structural reality this driver represents
  • Signals it explains: List the signal IDs it accounts for
  • Temporal reach: Operational / Strategic / Civilizational
  • Stability: LOCKED (unlikely to change in 10yr) / SHIFTING (could change in 3–5yr) / FRAGILE (could reverse in 1–2yr)

Output:

STRUCTURAL DRIVERS
D1 [Name] — [Force]
   Explains: [signal list] | Temporal: [layer] | Stability: [tier]

D2 [Name] — [Force]
   Explains: [signal list] | Temporal: [layer] | Stability: [tier]

D3 [Name] — [Force]
   Explains: [signal list] | Temporal: [layer] | Stability: [tier]

Drivers feed directly into scenario writing in Step 8. Each scenario must be traceable to at least one driver.


Step 5 — Build 6×3 STEEEP Matrix

Populate all 18 cells. Each cell value = average final_score of all signals mapped to that STEEEP × Temporal combination. Empty cells = 0.

Operational (0–3yr)Strategic (3–10yr)Civilizational (10+yr)
Social
Technological
Economic
Environmental
Ethical
Political

Apply regional multipliers to each cell. Then identify:

  • Hot zones: cells with score > 0.50
  • Gap zones: cells with score = 0.00
  • Dominant zone: single highest-scoring cell

Show full SKILL.md (591 more words)Show less
Step 6 — Cross-Impact Analysis

Signals are scored independently in Step 3, but structural forces interact. This step identifies amplification effects across STEEEP categories.

Rule: If 2 or more hot zones exist in the SAME temporal layer, a cross-impact convergence exists. Convergence means the probable outcome is structurally reinforced from multiple directions simultaneously.

For each temporal layer (Operational / Strategic / Civilizational):

  1. Count hot zones (score > 0.50)
  2. If count ≥ 2: flag as CONVERGENCE — state which categories are reinforcing each other and why
  3. If count = 1: flag as ISOLATED — single-category signal, more fragile
  4. If count = 0: flag as BLIND LAYER — no strong evidence in this time horizon

Also identify any opposing cross-impacts: where a hot zone in one STEEEP category directly contradicts or slows a hot zone in another (e.g. Technological/Strategic hot but Political/Strategic opposing). Flag these as FRICTION POINTS.

Output:

CROSS-IMPACT
Operational:    [CONVERGENCE / ISOLATED / BLIND LAYER] — [explanation]
Strategic:      [CONVERGENCE / ISOLATED / BLIND LAYER] — [explanation]
Civilizational: [CONVERGENCE / ISOLATED / BLIND LAYER] — [explanation]

Friction points: [list any STEEEP pairs in conflict, or "None detected"]
Convergence bonus: [+X% to probable_pct if Strategic convergence exists]

Apply convergence bonus: if Strategic layer has CONVERGENCE, add 5% to probable_pct before normalization in Step 7.


Step 7 — Find 3 Historical Analogues

Identify exactly 3 real historical cases that parallel the question's trajectory.

For each:

  1. Name: Common name of the transition
  2. Similarity (%): Estimated % structural similarity (0–100)
  3. Tipping event: Single event or policy that caused acceleration
  4. Equivalent today: YES / NO / PARTIAL
  5. Which driver it validates: Match to D1, D2, or D3 from Step 4

Prefer analogues with similarity ≥ 60%. If none exceed 60%, note as a confidence penalty.


Step 8 — Compute Probabilities + Confidence
Predictions — Independent Confidence Scores

Each future type is scored independently (0–100). They do NOT sum to 100%. Futures cone methodology: a scenario can be 80% Probable AND 60% Plausible simultaneously.

R_probable  = (supporting signals with score > 0.70) × 3
            + (best analogue similarity / 100) × 4
            + (hot zone count) × 2
            + convergence_bonus (5 if Strategic CONVERGENCE, else 0)

R_plausible = (supporting signals with score 0.40–0.70) × 2
            + (second analogue similarity / 100) × 3

R_possible  = (wildcard signals) × 2
            + (opposing signals with score > 0.60) × 2
            + (gap zones / 18) × 3

Convert to independent scores (exponential curve, not normalization):

probable_score  = min(100, round((1 - e^(-R_probable  / 18)) × 100))
plausible_score = min(100, round((1 - e^(-R_plausible / 9))  × 100))
possible_score  = min(100, round((1 - e^(-R_possible  / 5))  × 100))
Confidence
signal_count_score = min(100, total_signals / 25 × 100) × 0.30
signal_diversity   = (unique STEEEP categories covered / 6 × 100) × 0.30
recency_score      = (signals with recency_days ≤ 90 / total) × 100 × 0.20
evidence_score     = (signals with has_evidence=true / total) × 100 × 0.20

confidence = round(signal_count_score + signal_diversity + recency_score + evidence_score)

Step 9 — Write Scenarios + Assemble Report
Scenario Rules

PROBABLE, PLAUSIBLE, POSSIBLE — each must:

  • Be traceable to at least one structural driver (cite D1/D2/D3)
  • Have no narrative overlap with the others
  • Include PROOF with a number or date
  • Write IF and BUT in one sentence each — no hedging ("might", "could")

PREFERABLE — IFTF Backcasting Structure

Do not write PREFERABLE as a probability-weighted outcome. Write it as a designed future, then backcast to today.

Format:

■ PREFERABLE — [Short title]
[2–3 sentences: describe the desired state as already achieved]

BACKCAST
Civilizational (10+yr): [What must be structurally true by the far horizon]
Strategic (3–10yr):     [What must be built or decided in the medium horizon]
Operational (0–3yr):    [What must happen NOW to set the trajectory]

LEVERAGE: [The single highest-leverage action available today — specific, not generic]
DRIVER:   [Which structural driver (D1/D2/D3) this path depends on most]
Decision Guidance (deterministic logic)
IF probable_score > 60:
    stance = "Align with probable scenario trajectory"
    low_regret = "Invest in capability building in the dominant hot zone"

ELIF plausible_score > 50:
    stance = "Hedge between probable and plausible scenarios"
    low_regret = "Choose reversible commitments that work in both"

ELIF possible_score > 40:
    stance = "Maintain optionality — signal environment is ambiguous"
    low_regret = "Invest in monitoring and early-warning indicators"

ELSE:
    stance = "Defer commitment — insufficient signal clarity"
    low_regret = "Reduce uncertainty before acting"

Confidence qualifier:

  • ≥ 70: prefix "High conviction —"
  • < 40: prefix "Low conviction —" and add "Expand signal collection before acting"

Risk trigger: the opposing signal with the highest final_score.

Canonical Output Template

MANDATORY: Output ALL sections below, every single run, no exceptions. Never skip a section. Never produce a partial report.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SOFT PREDICT FUTURE  ·  FORESIGHT ENGINE
[Query]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

PREDICTIONS
■ Probable  [[X]/100] [████████████░░░░░░░░] — [one sentence, no hedging]
■ Plausible [[X]/100] [████████░░░░░░░░░░░░] — [one sentence, no hedging]
■ Possible  [[X]/100] [████░░░░░░░░░░░░░░░░] — [one sentence, no hedging]
■ Preferable          [stakeholder analysis below]

Confidence: [X]/100  |  Signals: [N]  |  Horizon: [YYYY–YYYY]  |  [YYYY-MM-DD]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

SIGNAL PULSE
— How many pieces of real-world evidence support, oppose, or complicate this question
Supporting [N] [████████████░░░░░░░░]  Opposing [N] [████░░░░░░░░░░░░░░░░]  Wild [N]
Net: [SUPPORTING LEADS / OPPOSING LEADS / NEUTRAL]
Hot zone: [The single STEEEP category with strongest evidence]
Gap: [STEEEP categories with no signals, or "None — full coverage"]

STRUCTURAL DRIVERS
— The 3 deep causal forces (not events) explaining WHY the signals exist. Stability = likelihood of change.
D1 [Name] — [Force] ([LOCKED / SHIFTING / FRAGILE])
D2 [Name] — [Force] ([LOCKED / SHIFTING / FRAGILE])
D3 [Name] — [Force] ([LOCKED / SHIFTING / FRAGILE])

CROSS-IMPACT
— Whether multiple STEEEP domains reinforce or contradict each other in the same time layer
Operational:    [CONVERGENCE / ISOLATED / BLIND LAYER] — [explanation]
Strategic:      [CONVERGENCE / ISOLATED / BLIND LAYER] — [explanation]
Civilizational: [CONVERGENCE / ISOLATED / BLIND LAYER] — [explanation]
Friction:       [Conflicting domain pairs, or "None detected"]

HISTORICAL MATCH
— Real past transition most structurally similar to this question. Higher % = stronger precedent.
[Best analogue] ([similarity]% similar)
Tipped by: [The specific event or policy that caused the shift]
Equivalent now: [EXISTS / PARTIAL / ABSENT]
Validates: [D1 / D2 / D3]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

■ PROBABLE [[X]%] — [Title]
— The most evidence-backed outcome given current signal strength
[2–3 sentence narrative. No hedging.]
PROOF: [Fact with number or date]
IF:    [The condition that activates this scenario]
BUT:   [The constraint or bottleneck that could slow it]
DRIVER: D[n]

■ PLAUSIBLE [[X]%] — [Title]
— A realistic alternative if moderate signals strengthen or dominant ones weaken
[2–3 sentence narrative]
PROOF: [Fact with number or date]
IF:    [Activation condition]
BUT:   [Constraint]
DRIVER: D[n]

■ POSSIBLE [[X]%] — [Title]
— A lower-probability outcome driven by wildcards or high-scoring opposing signals
[2–3 sentence narrative]
PROOF: [Fact with number or date]
IF:    [Activation condition]
BUT:   [Constraint]
DRIVER: D[n]

■ PREFERABLE — [Title]
— Not a prediction. A designed future: what the best achievable outcome looks like, traced back to today.
[2–3 sentences: desired state as already achieved. No hedging.]
BACKCAST
  Civilizational: [What must be structurally true by the far horizon]
  Strategic:      [What must be built or decided in the medium term]
  Operational:    [What must begin NOW to set the trajectory]
LEVERAGE: [Single highest-leverage action today — specific actor, specific action]
DRIVER: D[n]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

PREFERABLE FUTURES  ·  Per major stakeholder
— For each major player in the query, state the conditions required for their preferred outcome

[Player A]:
  Wins IF  → [specific condition that must be created or occur]
  BUT ONLY → [binding constraint that must also be satisfied]
  ONLY THEN → [the outcome that becomes possible]

[Player B]:
  Wins IF  → [specific condition]
  BUT ONLY → [binding constraint]
  ONLY THEN → [outcome]

[Users/Society — always include]:
  Wins IF  → [condition for best collective outcome]
  BUT ONLY → [constraint]
  ONLY THEN → [outcome]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

THE ONE THING
— The single variable whose presence or absence determines which scenario actually unfolds
[One sentence naming the deciding variable]
INCIDENT: [Real past event showing this variable's power]
WATCH:    [Leading indicator — a milestone, metric, or policy action to monitor]
IF YES → [What accelerates]
IF NO  → [What stalls]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

DECISION GUIDANCE
Recommended stance: [From deterministic probability logic]
Low-regret move:    [Action that pays off in multiple scenarios simultaneously]
Risk trigger:       [Highest-scored opposing signal — the one that could invalidate Probable]

[REGIONAL LENS — [REGION]]
Top multipliers: [STEEEP/temporal (Xx)]  [STEEEP/temporal (Xx)]
Key local variable: [One sentence on the dominant local structural factor]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

METHODOLOGY KEY
Signal score (0–1)     Recency × source reliability × signal type × evidence strength — higher = fresher, better-sourced, stronger evidence
Confidence (0–100)     Signal density (0–40) + evidence balance (0–30) + historical grounding (0–30) − blind spot penalty (0–15)
Predictions            PROBABLE / PLAUSIBLE / POSSIBLE are independent scores (0–100 each, do NOT sum to 100)
                       Futures cone: a scenario can score high on multiple types simultaneously
STEEEP matrix          6 domains × 3 time horizons — ★ hot (>1.0) ● warm (>0.5) ✗ blind spot (0)
Historical similarity   Structural pattern match to real past transitions — 60%+ is reliable precedent; below 40% is weak grounding
Convergence bonus      +5 added to Probable score when 2+ STEEEP domains reinforce each other in the Strategic layer
Stability tiers        LOCKED = unlikely to change in 10yr | SHIFTING = could change in 3–5yr | FRAGILE = could reverse in 1–2yr
Preferable futures     Per stakeholder: Wins IF [condition] BUT ONLY [constraint] ONLY THEN [outcome]
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

---

## Visual Output (claude.ai with Artifacts)

If running on claude.ai and Artifacts are enabled, after the text report generate an HTML Artifact:

```html
<!-- Render a visual foresight report with:
  1. Predictions bar chart — horizontal bars for Probable/Plausible/Possible scores
  2. STEEEP matrix — 6×3 color-coded table (darker green = hotter cell, red = blind spot)
  3. Futures cone — SVG diagram showing 4 scenario bands expanding from present to horizon
  4. Stakeholder preferable cards — one card per player with Wins IF / BUT ONLY / ONLY THEN
  Use inline CSS only. No external dependencies. Dark background (#0f0f0f), accent color #00d4aa.
-->

Regional Multiplier Tables

Apply in Step 3 and Step 5.

India
OperationalStrategicCivilizational
Social1.101.301.20
Technological1.401.301.10
Economic1.201.251.15
Environmental0.901.001.10
Ethical0.951.001.05
Political0.850.901.00

India note: UPI/DPI gives asymmetric advantage in Technological/Operational. Political/Operational discounted by regulatory fragmentation across states.

USA
OperationalStrategicCivilizational
Social1.001.101.05
Technological1.201.401.20
Economic1.101.301.10
Environmental0.951.001.05
Ethical1.051.101.10
Political0.900.951.00

USA note: Deep capital markets amplify Technological/Strategic. Political/Operational discounted by legislative gridlock.

Europe
OperationalStrategicCivilizational
Social1.001.051.10
Technological1.001.101.05
Economic0.950.900.90
Environmental1.201.401.30
Ethical1.101.201.20
Political1.051.101.10

Europe note: Regulatory leadership (GDPR, EU AI Act, Green Deal) amplifies Environmental/Strategic. Economic/Civilizational discounted by demographic headwinds.

China
OperationalStrategicCivilizational
Social1.001.101.05
Technological1.201.501.30
Economic1.101.201.10
Environmental0.901.001.05
Ethical0.700.750.80
Political1.101.151.00

China note: State-directed capital amplifies Technological/Strategic strongly. Ethical/Operational discounted by limited transparency.

Global (default)

All multipliers = 1.0. Apply when no region is detectable.

© davepoon, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/foresight-intelligence/skills/soft-predict-future of davepoon/buildwithclaude.

Open the folder on GitHubat commit 10bfc43

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in davepoon/buildwithclaude, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Soft Predict Future next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Soft Predict Future compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Soft Predict Future this skilldavepoon/buildwithclaude3.6k1 repos~5.4kAutomated safety check: PassMIT
Brave Searchbadlogic/pi-skills2.6k6 repos~592Automated safety check: PassMIT
Enterprise AI Scenario MapMetaInFLow/Enterprise-ai-scenario-map-skill632—~1.8kAutomated safety check: PassMIT
Web Searchjjyaoao/HelloAgents3.2k1 repos~5.6kAutomated safety check: PassMIT
Ddg SearchTheSyart/claude-agent-examples4051 repos~493Automated safety check: PassNone
Local Web SearchuluckyXH/OpenMOSS1.3k—~392Automated safety check: NotesMIT

Similar skills

  • Brave Search

    badlogic/pi-skills

    Web search and content extraction via Brave Search API. An agent skill from badlogic/pi-skills.

    2.6k GitHub starsUsed in 6 repos~592 tokens
    Productivity & AutomationAuto-check passed
  • Enterprise AI Scenario Map

    MetaInFLow/Enterprise-ai-scenario-map-skill

    企业AI场景地图生成报告工具。通过 web-search 深度调研企业信息,按照V2.1标准模板生成结构化AI应用场景地图报告,包含企业画像、业务诊断、行业实践、AI场景全量表、实施路径等完整内容。

    632 GitHub stars~1.8k tokensUpdated 6 mo ago
    Productivity & AutomationAuto-check passed
  • Web Search

    jjyaoao/HelloAgents

    Implement web search capabilities using the z-ai-web-dev-sdk.

    3.2k GitHub starsUsed in 1 repo~5.6k tokens
    Productivity & AutomationAuto-check passed
  • Ddg Search

    TheSyart/claude-agent-examples

    Web search without an API key using DuckDuckGo Lite via webfetch.

    405 GitHub starsUsed in 1 repo~493 tokens
    Productivity & AutomationAuto-check passed
  • Local Web Search

    uluckyXH/OpenMOSS

    A skill your agent uses when the user asks for web search that should run via the local-160 Responses API with websearch tool (base URL like https://proxy.example.com, model gpt-5.2-codex(xhigh)).

    1.3k GitHub stars~392 tokensUpdated 3 mo ago
    Productivity & AutomationAuto-check: notes
  • Web Search

    EXboys/skilllite

    Web search and content extraction with Tavily and Exa via inference.sh CLI.

    170 GitHub starsUsed in 3 repos~1k tokens
    Productivity & AutomationAuto-check passed

More from davepoon/buildwithclaude

All 245 skills in this repo
  • Qwen Vision

    davepoon/buildwithclaude

    A skill your agent uses when the user asks to "analyze video", "watch this video", "what happens in this video", "describe this clip", "review this footage", "classify these videos", "compare…

    3.6k GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed
  • Hard Predict Future

    davepoon/buildwithclaude

    Activate this agent for any future-oriented question that requires deep quantitative analysis, historical precedents, and structured scenario planning.

    3.6k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • iOS Hig Design Guide

    davepoon/buildwithclaude

    Build, update, and apply iOS design specifications using Apple Human Interface Guidelines (HIG) source data.

    3.6k GitHub stars~735 tokensUpdated yesterday
    Auto-check passed
  • Video Downloader

    davepoon/buildwithclaude

    Download YouTube videos with customizable quality and format options.

    3.6k GitHub starsUsed in 1 repo~871 tokens
    Auto-check passed
  • Atlas Cloud Media

    davepoon/buildwithclaude

    Discover Atlas Cloud image and video models, inspect their live schemas, and submit one confirmed media generation request with bounded GET polling.

    3.6k GitHub stars~852 tokensUpdated yesterday
    Auto-check passed
  • Slack Gif Creator

    davepoon/buildwithclaude

    Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives.

    3.6k GitHub starsUsed in 12 repos~4.3k tokens
    Auto-check passed

Questions about Soft Predict Future

What does Soft Predict Future do?

Activate this skill for ANY future-oriented question. An agent skill from davepoon/buildwithclaude. Soft Predict Future is an agent skill from davepoon/buildwithclaude. Activate this skill for ANY future-oriented question.

When should I use Soft Predict Future?

Soft Predict Future fits situations like: include: Will [X]?; who will win [X]?; what happens to [X]?; can [X] succeed?.

How do I install Soft Predict Future in Claude Code?

Run `npx skills add davepoon/buildwithclaude --skill soft-predict-future -a claude-code`. Or copy the skill folder (plugins/foresight-intelligence/skills/soft-predict-future in davepoon/buildwithclaude) into .claude/skills/soft-predict-future in your project. Claude Code loads it when a task matches its description.

How do I install Soft Predict Future in Codex?

Run `npx skills add davepoon/buildwithclaude --skill soft-predict-future -a codex`. Or copy the skill folder (plugins/foresight-intelligence/skills/soft-predict-future in davepoon/buildwithclaude) into .agents/skills/soft-predict-future in your project. Codex loads it when a task matches its description.

Can I use Soft Predict Future in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add davepoon/buildwithclaude --skill soft-predict-future -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/soft-predict-future, .gemini/skills/soft-predict-future, .github/skills/soft-predict-future and .opencode/skills/soft-predict-future in your project.

What does Soft Predict Future need to run?

SKILL.md names no scripts, command-line tools or credentials: Soft Predict Future is instructions for the agent only.

Does Soft Predict Future access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Soft Predict Future safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Soft Predict Future use?

Soft Predict Future is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Soft Predict Future use?

About 5.4k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Soft Predict Future?

Skills that share tags, products or a category with Soft Predict Future: Brave Search (badlogic/pi-skills, 2.6k stars), Enterprise AI Scenario Map (MetaInFLow/Enterprise-ai-scenario-map-skill, 632 stars), Web Search (jjyaoao/HelloAgents, 3.2k stars) and Ddg Search (TheSyart/claude-agent-examples, 405 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Soft Predict Future?

davepoon (a GitHub user) maintains it in davepoon/buildwithclaude, which has 3,604 GitHub stars. The repository holds 245 skills in this directory. The repository was last updated on October 6, 2026.

Source: davepoon/buildwithclaude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.