Sync Upstream
nyaruka/phonenumbers
Sync this Go port with a new upstream google/libphonenumber release — regenerate the embedded metadata and reconcile the ported Java logic.
Drive a Grain engineering goal through one composed Allium and Event Model loop.
Install Grain
$ npx skills add ObneyAI/grain --skill grain -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ObneyAI/grain grain --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/ObneyAI/grain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/grain .claude/skills/grain && 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 "grain" agent skill from https://github.com/ObneyAI/grain/tree/main/skills/grain into .claude/skills/grain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grain", 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/ObneyAI/grain/tree/main/skills/grainType 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 ObneyAI/grain --skill grain -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ObneyAI/grain grain --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ObneyAI/grain.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/grain .agents/skills/grain && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "grain" agent skill from https://github.com/ObneyAI/grain/tree/main/skills/grain into .agents/skills/grain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grain", 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 ObneyAI/grain --skill grain -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ObneyAI/grain grain --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ObneyAI/grain.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/grain .cursor/skills/grain && 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 "grain" agent skill from https://github.com/ObneyAI/grain/tree/main/skills/grain into .cursor/skills/grain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grain", 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/ObneyAI/grain.git --path skills/grain--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 ObneyAI/grain --skill grain -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ObneyAI/grain grain --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ObneyAI/grain.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/grain .gemini/skills/grain && 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 "grain" agent skill from https://github.com/ObneyAI/grain/tree/main/skills/grain into .gemini/skills/grain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grain", 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 ObneyAI/grain grainInstalls 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 ObneyAI/grain --skill grain -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ObneyAI/grain.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/grain .github/skills/grain && 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 "grain" agent skill from https://github.com/ObneyAI/grain/tree/main/skills/grain into .github/skills/grain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grain", 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 ObneyAI/grain --skill grain -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ObneyAI/grain grain --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ObneyAI/grain.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/grain .opencode/skills/grain && 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 "grain" agent skill from https://github.com/ObneyAI/grain/tree/main/skills/grain into .opencode/skills/grain/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "grain", 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
grain- GitHub stars
- 123
- Token cost
- ~482 tokens
- SKILL.md length
- 204 words
- Files
- 1
- Skills in repo
- 8
- Repo updated
- First seen
- Licence
- MIT
At a glance
Drive a Grain engineering goal through one composed Allium and Event Model loop.
- Works in 5 steps: Gather durable context with Allium… → Use Allium propagate for behavioural… → Implement and run tests. Confirm new… → …
- Specification work
- SKILL.md covers Preflight and Composed loop
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Grain is an agent skill from ObneyAI/grain. Drive a Grain engineering goal through one composed Allium and Event Model loop. Use for Grain features, specification work, implementation, reconciliation, or when the user invokes Grain as the entry point. Delegate observable behaviour to installed Allium skills and add Grain service-topology work; continue until specs, tests, code, runtime validation, and trace links agree.
Its SKILL.md is about 480 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 Business, Finance & HR, covering Accounting and bookkeeping. The repository describes itself as: Build Reasonable Applications with Clojure in the World of Natural Language Programming. The licence is MIT.
When your agent uses it
- Specification work
- The user invokes Grain as the entry point
Example prompts
- “/grain”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Gather durable context with Allium elicit or distill, then run the matching
- Use Allium propagate for behavioural tests. Use event-model-propagate for
- Implement and run tests. Confirm new behavioural tests were red before the
- Verify with Allium weed, allium check, and allium analyse; then run
- If behaviour was wrong, revise with Allium tend; if topology was wrong, use
What it can do on your machine
Read from SKILL.md and the folder at commit dbf5b52. 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
Links to these hosts (documentation or services it may open):
github.com
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
Grain loads about 482 tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 204 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from ObneyAI/grain at commit dbf5b52, republished under its MIT licence (© ObneyAI). 204 words, ~482 tokens.
Download SKILL.mdSave it as
.claude/skills/grain/SKILL.md (or your agent's skills folder).- name
- grain
- description
- Drive a Grain engineering goal through one composed Allium and Event Model loop. Use for Grain features, specification work, implementation, reconciliation, or when the user invokes Grain as the entry point. Delegate observable behaviour to installed Allium skills and add Grain service-topology work; continue until specs, tests, code, runtime validation, and trace links agree.
Grain
Use Allium as the behavioural host and Event Model as its Grain topology extension. Never copy behavioural rules or Given/When/Then into Event Model.
Preflight
Confirm the Allium entry and verb skills are installed. If not, pause and give the installation command appropriate to the active editor from https://github.com/juxt/allium. Do not vendor or silently replace Allium.
Inspect .allium files, defeventmodel forms, the live Grain catalog when
available, and current tests. Decide whether the goal changes behaviour,
topology, or both.
Composed loop
- Gather durable context with Allium
elicitordistill, then run the matchingevent-model-elicitorevent-model-distillphase for topology. - Use Allium
propagatefor behavioural tests. Useevent-model-propagatefor topology, boot-mandate, and composition contract tests. - Implement and run tests. Confirm new behavioural tests were red before the implementation when doing spec-first work.
- Verify with Allium
weed,allium check, andallium analyse; then runevent-model-weed, strict runtime validation, and composition validation. - If behaviour was wrong, revise with Allium
tend; if topology was wrong, useevent-model-tend. Re-propagate and repeat.
Finish only when behavioural specs, topology, generated tests, implementation, runtime registries, and Allium trace links agree and no open question remains.
Read the event-model skill for the Grain schema and exact REPL APIs.
© ObneyAI, 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 skills/grain of ObneyAI/grain.
Open the folder on GitHubat commit dbf5b52
Compare with similar skills
Grain 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 |
|---|---|---|---|---|---|---|
| Grain this skillObneyAI/grain | 123 | — | ~482 | Automated safety check: Pass | MIT | |
| Sync Upstreamnyaruka/phonenumbers | 1.6k | — | ~2.8k | Automated safety check: Pass | MIT | |
| Longbridge Value Investinghelsome/folio | 269 | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Radiology Tablehuang-sir1/radiology-skills | 1.9k | — | ~1.3k | Automated safety check: Pass | Custom licence | |
| Odoo Agency Fleet Reviewerpipe-org/mcp-odoo | 420 | — | ~699 | Automated safety check: Pass | MIT | |
| Beancount Closebex-co/beancount-io | 295 | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Longbridge Value Investing
helsome/folio
Value investing analysis using Graham (NCAV/net-net/defensive-investor) and Buffett (economic moat/ROE/FCF) methodologies.
Radiology Table
huang-sir1/radiology-skills
Create/audit editable publication tables with source reconciliation; not figures or statistical inference.
Odoo Agency Fleet Review
erpipe-org/mcp-odoo
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50…
Beancount Close
bex-co/beancount-io
Close an accounting period in a Beancount ledger by reconciling each active account through beancount-reconcile, checking assertions and recurring gaps, reviewing flags, then proposing a commit with…
ERPClaw ERP Controller
avansaber/erpclaw
Operates the ERPClaw self-hosted ERP in plain language: accounting, invoicing, inventory, purchasing, tax, HR, payroll and reports, treating the ERP as the single source of truth.
More from ObneyAI/grain
All 8 skills in this repoEvent Model
ObneyAI/grain
Read, write, and validate Grain's service-area-first Event Model topology.
Grain Genome
ObneyAI/grain
Build or update Grain's interactive component genome. An agent skill from ObneyAI/grain.
Event Model Distill
ObneyAI/grain
Distill Grain Event Model topology from an existing system as the topology companion to Allium distill.
Event Model Propagate
ObneyAI/grain
Generate Grain topology and composition contract tests after Allium propagates behavioural tests.
Event Model Weed
ObneyAI/grain
Reconcile Grain Event Model topology with the live runtime and its linked Allium declarations as the topology phase after Allium weed.
Event Model Elicit
ObneyAI/grain
Add Grain Event Model topology to an Allium intent-first elicitation.
Related
Categories
Questions about Grain
What does Grain do?
Drive a Grain engineering goal through one composed Allium and Event Model loop. Grain is an agent skill from ObneyAI/grain. Drive a Grain engineering goal through one composed Allium and Event Model loop.
When should I use Grain?
Grain fits situations like: specification work; the user invokes Grain as the entry point.
How do I install Grain in Claude Code?
Run `npx skills add ObneyAI/grain --skill grain -a claude-code`. Or copy the skill folder (skills/grain in ObneyAI/grain) into .claude/skills/grain in your project. Claude Code loads it when a task matches its description.
How do I install Grain in Codex?
Run `npx skills add ObneyAI/grain --skill grain -a codex`. Or copy the skill folder (skills/grain in ObneyAI/grain) into .agents/skills/grain in your project. Codex loads it when a task matches its description.
Can I use Grain 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 ObneyAI/grain --skill grain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/grain, .gemini/skills/grain, .github/skills/grain and .opencode/skills/grain in your project.
What does Grain need to run?
SKILL.md names no scripts, command-line tools or credentials: Grain is instructions for the agent only.
Does Grain access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Grain 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 Grain use?
Grain 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 Grain use?
About 482 tokens (SKILL.md is roughly 1.9k 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 Grain?
Skills that share tags, products or a category with Grain: Sync Upstream (nyaruka/phonenumbers, 1.6k stars), Longbridge Value Investing (helsome/folio, 269 stars), Radiology Table (huang-sir1/radiology-skills, 1.9k stars) and Odoo Agency Fleet Review (erpipe-org/mcp-odoo, 420 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Grain?
ObneyAI (a GitHub organization) maintains it in ObneyAI/grain, which has 123 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on September 24, 2026.
Source: ObneyAI/grain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.