Image to Three.js Model
img2threejs/img2threejs
Rebuilds the object in a reference image as a procedural, animation-ready Three.js model written entirely in code, using staged sculpting with quality checks.
Research, draft, and review historical events and political writing for Statecraft: Israel.
Install Statecraft Historical Content
$ npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install eyalgolan/statecraft-israel statecraft-historical-content --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/eyalgolan/statecraft-israel.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/statecraft-historical-content .claude/skills/statecraft-historical-content && rm -rf skills-srcUse ~/.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/
Install the "statecraft-historical-content" agent skill from https://github.com/eyalgolan/statecraft-israel/tree/main/.github/skills/statecraft-historical-content into .claude/skills/statecraft-historical-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statecraft-historical-content", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/eyalgolan/statecraft-israel/tree/main/.github/skills/statecraft-historical-contentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install eyalgolan/statecraft-israel statecraft-historical-content --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eyalgolan/statecraft-israel.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/statecraft-historical-content .agents/skills/statecraft-historical-content && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "statecraft-historical-content" agent skill from https://github.com/eyalgolan/statecraft-israel/tree/main/.github/skills/statecraft-historical-content into .agents/skills/statecraft-historical-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statecraft-historical-content", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install eyalgolan/statecraft-israel statecraft-historical-content --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eyalgolan/statecraft-israel.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/statecraft-historical-content .cursor/skills/statecraft-historical-content && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "statecraft-historical-content" agent skill from https://github.com/eyalgolan/statecraft-israel/tree/main/.github/skills/statecraft-historical-content into .cursor/skills/statecraft-historical-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statecraft-historical-content", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/eyalgolan/statecraft-israel.git --path .github/skills/statecraft-historical-content--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install eyalgolan/statecraft-israel statecraft-historical-content --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eyalgolan/statecraft-israel.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/statecraft-historical-content .gemini/skills/statecraft-historical-content && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "statecraft-historical-content" agent skill from https://github.com/eyalgolan/statecraft-israel/tree/main/.github/skills/statecraft-historical-content into .gemini/skills/statecraft-historical-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statecraft-historical-content", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install eyalgolan/statecraft-israel statecraft-historical-contentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/eyalgolan/statecraft-israel.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/statecraft-historical-content .github/skills/statecraft-historical-content && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "statecraft-historical-content" agent skill from https://github.com/eyalgolan/statecraft-israel/tree/main/.github/skills/statecraft-historical-content into .github/skills/statecraft-historical-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statecraft-historical-content", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install eyalgolan/statecraft-israel statecraft-historical-content --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/eyalgolan/statecraft-israel.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/statecraft-historical-content .opencode/skills/statecraft-historical-content && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "statecraft-historical-content" agent skill from https://github.com/eyalgolan/statecraft-israel/tree/main/.github/skills/statecraft-historical-content into .opencode/skills/statecraft-historical-content/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "statecraft-historical-content", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
statecraft-historical-content- GitHub stars
- 159
- Token cost
- ~767 tokens
- SKILL.md length
- 321 words
- Files
- 5 (incl. scripts, references)
- Repo updated
- First seen
- Licence
- MIT
At a glance
Research, draft, and review historical events and political writing for Statecraft: Israel.
- Works in 7 steps: Identify the event, date range, or gap. → Check the existing content in… → Verify the factual claim with a source… → …
- Source-checking claims
- SKILL.md covers When to use, Core repo rules, Mandatory workflow and Historical writing standards, plus 3 more sections
- Runs Python scripts from its folder; calls dotnet
What it does
Statecraft Historical Content is an agent skill from eyalgolan/statecraft-israel. Research, draft, and review historical events and political writing for Statecraft: Israel. Use for source-checking claims, event drafting, content gaps, and 1948-1956 narrative work.
Its SKILL.md is about 770 tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `examples/event-gap-example.md`, `references/historical-writing-checklist.md` and `scripts/check_source_coverage.py`).
It sits in Game Development. The repository describes itself as: A Civilization-style strategy game about governing Israel from 15 May 1948. Real ministers, real map, every fact sourced. Unity + deterministic C sim. The licence is MIT.
When your agent uses it
- Source-checking claims
- 1948-1956 narrative work
Example prompts
- “/statecraft-historical-content”
Requirements
- Python 3
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Identify the event, date range, or gap.
- Check the existing content in content/events/ and the relevant people/offices structure.
- Verify the factual claim with a source before drafting.
- Draft only in the repo’s historical framing and event schema.
- Keep the text grounded, specific, and readable in a game UI.
- Leave status: draft on anything an AI drafted. Only a person who has checked every claim against its source sets fact-checked.
- Validate with dotnet test sim/Statecraft.sln when editing repo content.
What it can do on your machine
Read from SKILL.md and the folder at commit 3d427d0. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
dotnet
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
Statecraft Historical Content loads about 767 tokens when it runs, and up to ~976 if it reads all its reference files. Until then it costs about 53 tokens; SKILL.md has 321 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from eyalgolan/statecraft-israel at commit 3d427d0, republished under its MIT licence (© eyalgolan). 321 words, ~767 tokens.
Download SKILL.mdSave it as
.claude/skills/statecraft-historical-content/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- statecraft-historical-content
- description
- Research, draft, and review historical events and political writing for Statecraft: Israel. Use for source-checking claims, event drafting, content gaps, and 1948-1956 narrative work.
- argument-hint
- event topic / date range / source question / historical gap
- user-invocable
- true
- disable-model-invocation
- false
Statecraft Historical Content
When to use
- drafting or revising event text in
content/events/ - finding historical gaps in the 1948–1956 timeline
- checking whether a claim is source-backed and suitable for the repo
- editing player-facing writing for historical clarity and tone
Core repo rules
Before drafting, read these first:
Mandatory workflow
- Identify the event, date range, or gap.
- Check the existing content in
content/events/and the relevant people/offices structure. - Verify the factual claim with a source before drafting.
- Draft only in the repo’s historical framing and event schema.
- Keep the text grounded, specific, and readable in a game UI.
- Leave
status: drafton anything an AI drafted. Only a person who has checked every claim against its source setsfact-checked. - Validate with
dotnet test sim/Statecraft.slnwhen editing repo content.
Historical writing standards
- No invented quotes or verbatim speeches without direct source support.
- Use office placeholders such as
{prime_minister}rather than hard-coded names. - Prefer concrete government, military, or social context over generic historical mood-setting.
- Keep war and atrocity language precise and sensitive.
- Favor the political and logistical realities of state-building over dramatic filler.
Research checklist
- Is the claim connected to a real date and a real institutional decision?
- Is the wording supported by a cited source or a source packet?
- Does it fit the historical period and office holder?
- Does it avoid unsupported generalization or invented drama?
- Does it align with the project’s Israeli framing and source policy?
Skill bundle contents
This skill package is intentionally structured like a real agent skill bundle, not a single markdown note.
scripts/contains quick helper commands for checking source coverage and event completenesstemplates/contains YAML and checklist scaffolds for draftsexamples/contains small examples of useful historical gaps and workflow patternsreferences/contains the supporting checklists and repo reference docs
References
© eyalgolan, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references) in .github/skills/statecraft-historical-content of eyalgolan/statecraft-israel.
- SKILL.md
- examples/event-gap-example.md
- references/historical-writing-checklist.md
- scripts/check_source_coverage.py
- templates/event-draft.yaml
Open the folder on GitHubat commit 3d427d0
Compare with similar skills
Statecraft Historical Content 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Statecraft Historical Content this skilleyalgolan/statecraft-israel | 159 | — | ~767 | Automated safety check: Pass | MIT | |
| Image to Three.js Modelimg2threejs/img2threejs | 18k | 1 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 | |
| Web CloneJane-xiaoer/claude-skill-web-clone | 1k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| Threejs Game Directormajidmanzarpour/threejs-game-skills | 2.5k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Game Asset Generatorhtdt/godogen | 7.1k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Threejs Gameplay Systemsvalkor-ai/loom | 1.2k | 1 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Web Clone
Jane-xiaoer/claude-skill-web-clone
网站复刻 / 克隆方法论。USE WHEN 用户说 复刻网站、克隆网站、clone website、抄个站、仿站、 照着这个站做一个、reproduce site、还原某个网页效果、把这个站搬下来改成我的、 复刻某个交互/WebGL/Canvas/Three.js 效果。提供「先拿真源码 → 判路径 → 逆向拆解 → 搭工程 → 替换内容」的可移植决策树，覆盖静态站 /…
Threejs Game Director
majidmanzarpour/threejs-game-skills
Entrypoint for building, upgrading, and finishing Three.js browser games.
Game Asset Generator
htdt/godogen
Generates game art from text prompts: PNG images, GLB 3D models, rigged characters, animations and sprites, with background removal.
Threejs Gameplay Systems
valkor-ai/loom
Build and iterate playable Three.js game systems: starter scaffold, architecture, design briefs, core loops, level and encounter design, entities, input, camera, collision and physics, scoring…
Uloop Execute Dynamic Code
CyberAgentGameEntertainment/NovaShader
Execute C with Unity APIs when existing uloop tools cannot inspect or edit enough.
More from eyalgolan/statecraft-israel
Statecraft Writing Voice
eyalgolan/statecraft-israel
Improve and review Statecraft: Israel prose for tone, clarity, and historical credibility.
Related
Categories
Questions about Statecraft Historical Content
What does Statecraft Historical Content do?
Research, draft, and review historical events and political writing for Statecraft: Israel. Statecraft Historical Content is an agent skill from eyalgolan/statecraft-israel. Research, draft, and review historical events and political writing for Statecraft: Israel.
When should I use Statecraft Historical Content?
Statecraft Historical Content fits situations like: source-checking claims; 1948-1956 narrative work.
How do I install Statecraft Historical Content in Claude Code?
Run `npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a claude-code`. Or copy the skill folder (.github/skills/statecraft-historical-content in eyalgolan/statecraft-israel) into .claude/skills/statecraft-historical-content in your project. Claude Code loads it when a task matches its description.
How do I install Statecraft Historical Content in Codex?
Run `npx skills add eyalgolan/statecraft-israel --skill statecraft-historical-content -a codex`. Or copy the skill folder (.github/skills/statecraft-historical-content in eyalgolan/statecraft-israel) into .agents/skills/statecraft-historical-content in your project. Codex loads it when a task matches its description.
Can I use Statecraft Historical Content 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 eyalgolan/statecraft-israel --skill statecraft-historical-content -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/statecraft-historical-content, .gemini/skills/statecraft-historical-content, .github/skills/statecraft-historical-content and .opencode/skills/statecraft-historical-content in your project.
What does Statecraft Historical Content need to run?
Going by SKILL.md and its folder, Statecraft Historical Content needs Python for the scripts in its folder and the command-line tools its instructions call (dotnet). Our summary lists: Python 3.
Does Statecraft Historical Content 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 Statecraft Historical Content 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Statecraft Historical Content use?
Statecraft Historical Content 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 Statecraft Historical Content use?
About 767 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 209 tokens, read only when the agent opens those files.
What are the alternatives to Statecraft Historical Content?
Skills that share tags, products or a category with Statecraft Historical Content: Image to Three.js Model (img2threejs/img2threejs, 18k stars), Web Clone (Jane-xiaoer/claude-skill-web-clone, 1k stars), Threejs Game Director (majidmanzarpour/threejs-game-skills, 2.5k stars) and Game Asset Generator (htdt/godogen, 7.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Statecraft Historical Content?
eyalgolan (a GitHub user) maintains it in eyalgolan/statecraft-israel, which has 159 GitHub stars. The repository was last updated on October 11, 2026.
Source: eyalgolan/statecraft-israel on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.