From geopol-sim
Create a new geopolitical-forecasting simulation workspace by cloning one of the registered upstream templates. Use when the user wants to "start a new geopol simulation", "set up a forecast", "scaffold a forecasting run", or asks which simulator template to use. Interactively presents the template registry with cost/depth tradeoffs, clones the chosen template into a new workspace, wires the .env file, seeds a scenario.md, and drops a .template-id sentinel.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin geopol-simThis skill is limited to using the following tools:
Creates a fresh workspace for one geopolitical-forecasting simulation, based on a chosen upstream template.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes multiple pages for keyword overlap, SEO cannibalization risks, and content duplication. Suggests differentiation, consolidation, and resolution strategies when reviewing similar content.
Share bugs, ideas, or general feedback.
Creates a fresh workspace for one geopolitical-forecasting simulation, based on a chosen upstream template.
scenario.md.templates/registry.json in the plugin. Read the registry, present each template with its name, description, and tradeoff blurb (the tradeoff field exists specifically so the user can make an informed choice). Default to asking — only auto-pick if the user has already named a template.~/repos/github/my-repos/<workspace-name>/. Confirm before creating.templates/registry.json from the plugin install dir. List the available templates.git clone <repo> into the chosen workspace path. Use the default_branch from the registry entry.env_vars list names the required keys. For each, fetch from 1Password (use the op-vault:op-get skill or op read directly). Write to .env in the workspace root. Do NOT echo the values.install_commands array in the workspace dir (e.g. pip install -e . or uv sync).id to .template-id at workspace root. This is what every other skill in this plugin uses to dispatch.scenario.md. Write a short markdown file capturing: the forecast question, the chosen template (with its tradeoff blurb), the date scaffolded, and any horizon/grounding overrides the user mentioned. This is for the user's reference, not consumed by the templates themselves.$CLAUDE_USER_DATA/geopol-sim/config.json (resolution: ${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/geopol-sim/config.json). If a runstore path is set, append the workspace path to the registered-workspaces list there. If no runstore is configured, mention it and offer to run setup-runstore./run-simulation).update-templates..template-id sentinel is the contract every other skill relies on. Don't omit it.