Agent skill

Divine Context

by divinevideo in divinevideo/divine-mobile

A skill your agent uses when starting work in any divine- repo (divine-web, divine-mobile, divine-funnelcake, keycast, divine-blossom, divine-router, etc.) or when you've learned a cross-repo fact…

MPL-2.0Auto-check passed

Install Divine Context

skills CLI

$ npx skills add divinevideo/divine-mobile --skill divine-context -a claude-code

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

GitHub CLI

$ gh skill install divinevideo/divine-mobile divine-context --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/divinevideo/divine-mobile.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/divine-context .claude/skills/divine-context && 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/

Paste into Claude Code

Install the "divine-context" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/divine-context into .claude/skills/divine-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "divine-context", 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

$skill-installer install https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/divine-context

Type 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.

skills CLI

$ npx skills add divinevideo/divine-mobile --skill divine-context -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install divinevideo/divine-mobile divine-context --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/divine-context .agents/skills/divine-context && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "divine-context" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/divine-context into .agents/skills/divine-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "divine-context", 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.

skills CLI

$ npx skills add divinevideo/divine-mobile --skill divine-context -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install divinevideo/divine-mobile divine-context --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/divine-context .cursor/skills/divine-context && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "divine-context" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/divine-context into .cursor/skills/divine-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "divine-context", 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

$ gemini skills install https://github.com/divinevideo/divine-mobile.git --path .agents/skills/divine-context

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add divinevideo/divine-mobile --skill divine-context -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install divinevideo/divine-mobile divine-context --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/divine-context .gemini/skills/divine-context && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "divine-context" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/divine-context into .gemini/skills/divine-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "divine-context", 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.

GitHub CLI

$ gh skill install divinevideo/divine-mobile divine-context

Installs 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).

skills CLI

$ npx skills add divinevideo/divine-mobile --skill divine-context -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/divine-context .github/skills/divine-context && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "divine-context" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/divine-context into .github/skills/divine-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "divine-context", 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.

skills CLI

$ npx skills add divinevideo/divine-mobile --skill divine-context -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install divinevideo/divine-mobile divine-context --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/divinevideo/divine-mobile.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/divine-context .opencode/skills/divine-context && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "divine-context" agent skill from https://github.com/divinevideo/divine-mobile/tree/main/.agents/skills/divine-context into .opencode/skills/divine-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "divine-context", 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: divine-context
GitHub stars: 266
Token cost: ~1.6k tokens
SKILL.md length: 702 words
Files: 1
Skills in repo: 103
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MPL-2.0

At a glance

A skill your agent uses when starting work in any divine- repo (divine-web, divine-mobile, divine-funnelcake, keycast, divine-blossom, divine-router, etc.) or when you've learned a cross-repo fact…

Works in 6 steps: Read this repo's key files (5 min, no… → Read every divine-context file (they're… → Build a proposal list — for each item:… → …
Starting work in any divine- repo (divine-web
SKILL.md covers On disk, Reading divine-context, Updating divine-context and End-of-task report, plus 1 more section
Calls git and gh

What it does

Divine Context is an agent skill from divinevideo/divine-mobile. Use when starting work in any divine- repo (divine-web, divine-mobile, divine-funnelcake, keycast, divine-blossom, divine-router, etc.) or when you've learned a cross-repo fact worth sharing back. The shared divine-context handbook at ~/code/divine/divine-context/ is the source of truth for cross-cutting architecture, Nostr usage, terminology, and the project catalog across the ~50 divine- repos.

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

The licence is MPL-2.0.

When your agent uses it

Starting work in any divine- repo (divine-web
Divine-funnelcake
Youve learned a cross-repo fact worth sharing back

Example prompts

“/divine-context”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

Read this repo's key files (5 min, no deep dive): README.md, AGENTS.md, .claude/rules/*, docs/**, package.json / Cargo.toml / pubspec.yaml…
Read every divine-context file (they're short).
Build a proposal list — for each item: one line of what, one line of evidence (path:line in this repo).
Show the proposal list to the user before editing anything. Wait for approval.
For approved items only, branch from origin/main (not local main, which may be stale) and make the edits
One logical change per PR. Five unrelated improvements = five PRs.

What it can do on your machine

Read from SKILL.md and the folder at commit 4c622be. 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
Shell commands in SKILL.md call:
- git
- gh
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

Divine Context loads about 1.6k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 702 words of instructions outside code blocks.

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

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 divinevideo/divine-mobile at commit 4c622be, republished under its MPL-2.0 licence (© divinevideo). 702 words, ~1,631 tokens.

Download SKILL.mdSave it as .claude/skills/divine-context/SKILL.md (or your agent's skills folder).

name: divine-context
description: Use when starting work in any divine-* repo (divine-web, divine-mobile, divine-funnelcake, keycast, divine-blossom, divine-router, etc.) or when you've learned a cross-repo fact worth sharing back. The shared divine-context handbook at ~/code/divine/divine-context/ is the source of truth for cross-cutting architecture, Nostr usage, terminology, and the project catalog across the ~50 divine-* repos.

Divine Context

The divine-context repo is the cross-repo handbook for the diVine platform. Every divine-* repo's AGENTS.md should pull in @../divine-context/AGENT_CONTEXT.md, but if it doesn't, load it manually before doing real cross-repo work.

On disk

Cloned as a sibling of the current repo:

~/code/divine/
├── divine-context/          ← read this
├── divine-web/
├── divine-mobile/
├── divine-funnelcake/
└── ... (~50 divine-* repos)

If divine-context isn't cloned:

bash

(cd ~/code/divine && [ -d divine-context ] || gh repo clone divinevideo/divine-context)

Reading divine-context

For everyday work, AGENT_CONTEXT.md is enough. It links out to deeper files:

File	Read when
`AGENT_CONTEXT.md`	Always — single-page primer
`PROJECT.md`	Need product context (what diVine is, who it's for)
`ARCHITECTURE.md`	Touching cross-service flows
`PROJECTS.md`	Asking "is there already a service for X?"
`NOSTR.md`	Publishing/querying/signing Nostr events
`GLOSSARY.md`	Hit an unfamiliar term
`ANDOTHERSTUFF.md`	Need parent-org context

These files describe state at the time they were written. If a file in a divine-* repo contradicts divine-context, trust the code — and if the contradiction is durable, propose a divine-context update (see below).

Updating divine-context

When you learn a cross-repo fact while working in a divine-* repo, propose it back. Cross-repo means: would an agent in a different divine-* repo benefit from knowing this? If no, it stays in this repo's AGENTS.md or .claude/rules/.

Workflow

Read this repo's key files (5 min, no deep dive): README.md, AGENTS.md, .claude/rules/*, docs/**, package.json / Cargo.toml / pubspec.yaml / go.mod, top-level src/.
Read every divine-context file (they're short).
Build a proposal list — for each item: one line of what, one line of evidence (path:line in this repo).
Show the proposal list to the user before editing anything. Wait for approval.
For approved items only, branch from origin/main (not local main, which may be stale) and make the edits:
bash
```
cd ~/code/divine/divine-context
git fetch origin main
git worktree add .claude/worktrees/dc-<topic> -b update-from-<thisrepo>-<topic>-$(date +%Y-%m-%d) origin/main
# edit files
cd .claude/worktrees/dc-<topic>
git add <only the files you changed>          # never -A
git commit -m "<short desc>: <what changed>"
git push -u origin HEAD
gh pr create --title "..." --body "..."
```
Use a worktree inside the divine-context checkout. Other agents may be editing divine-context concurrently; isolating in a worktree avoids branch-state collisions. Put it in .claude/worktrees/ (gitignored there) — not /tmp. On macOS /tmp is swept, and a worktree there takes any uncommitted work with it; see WORKTREES.md in divine-context. Remove it with git worktree remove once the PR merges, since nothing cleans it up for you.
One logical change per PR. Five unrelated improvements = five PRs.

What goes in divine-context (and what doesn't)

Goes in divine-context	Stays in this repo
Cross-repo architecture / data flow	Repo-local file paths, hooks, components
New event kinds, NIPs, relay gotchas	Implementation details of one repo's code
Domain terms an outside agent would hit cold	Repo-specific code conventions
`<!-- TODO -->` markers you can now answer	Debugging recipes (those go in skills/)
Catalog corrections in `PROJECTS.md`	One-off solutions to one repo's bug

Show full SKILL.md (302 more words)Show less

Hard rules

Don't invent. Cite a file path (and line if practical) in this repo for every claim. If you can't verify in 2 minutes, mark the proposed change  instead of guessing.
No secrets, internal URLs, or anything sensitive. divine-context is intended to eventually be sharable with outside contributors.
No copying of repo-local rules. Flutter/BLoC specifics belong in divine-mobile, not divine-context. The "Flutter / divine-mobile specifics" subsection of AGENT_CONTEXT.md is the only exception.
Length is a budget, not a void to fill. Prefer tightening existing prose to adding new prose. AGENT_CONTEXT.md is loaded into every divine-* agent's session — additions there must earn their place.
Don't git add -A. Stage only the divine-context files you changed.
Don't amend existing commits. Create new ones.
Don't open empty PRs. If you have nothing to propose after reading, say so and stop.

End-of-task report

After running the update workflow, report:

Proposed changes to divine-context:
- <file>: <one-line description>  — evidence: <path:line in this repo>
- ...

PR opened: <url>
(or: No PR — divine-context is accurate for this repo.)

Common rationalizations to ignore

Excuse	Reality
"I'll just edit divine-context directly without showing the user first"	Some proposals may be intentional omissions. Show the list first.
"This is repo-local but feels useful, so I'll add it anyway"	Cross-repo only. Repo-local belongs in `AGENTS.md`.
"Local main looks fine, no need to fetch"	Local main may be days stale. Always branch from `origin/main`.
"I'll skip the worktree, just `git checkout` in place"	Concurrent agents may be editing. Use a `.claude/worktrees/dc-<topic>` worktree.
"I'll put the worktree in `/tmp`, it's throwaway"	`/tmp` is swept on macOS and takes uncommitted work with it. Keep it inside the divine-context checkout.
"I'll bundle five small fixes into one PR — easier to review"	One logical change per PR. Reviewers can disagree with one without blocking the others.
"I'll `git add -A` — faster"	Catches unrelated files. Stage by name.
"I can't verify this fact, but it sounds right"	Mark `<!-- TODO: verify -->` instead of inventing.

Files

Just SKILL.md in .agents/skills/divine-context of divinevideo/divine-mobile.

Open the folder on GitHubat commit 4c622be

Compare with similar skills

Divine Context 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.

Divine Context compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Divine Context this skilldivinevideo/divine-mobile	266	—	~1.6k	Automated safety check: Pass	MPL-2.0	today
StartDonchitos/Claude-Code-Game-Studios	26k	—	~6.4k	Automated safety check: Pass	MIT	9 days ago
Session Start Hookasgeirtj/system_prompts_leaks	69k	1 repos	~1.2k	Automated safety check: Pass	CC0-1.0	today
Where Do I Startmohitagw15856/pm-claude-skills	1.4k	—	~912	Automated safety check: Pass	MIT	yesterday
Cold Start Interviewanthropics/claude-for-legal	9.6k	3 repos	~11k	Automated safety check: Pass	Apache-2.0	8 days ago
Cold Start Interviewanthropics/claude-for-legal	9.6k	2 repos	~8k	Automated safety check: Pass	Apache-2.0	8 days ago

Similar skills

Start
Donchitos/Claude-Code-Game-Studios
First-time onboarding — asks where you are, then guides you to the right workflow.
26k GitHub stars~6.4k tokensUpdated 9 days ago
Game DevelopmentAuto-check passed
Session Start Hook
asgeirtj/system_prompts_leaks
Creating and developing startup hooks for Claude Code on the web.
69k GitHub starsUsed in 1 repo~1.2k tokens
DevelopmentAuto-check passed
Where Do I Start
mohitagw15856/pm-claude-skills
Turn a chaotic pile of everything-in-your-head into one clear first action — the antidote to the paralysis of too much at once.
1.4k GitHub stars~912 tokensUpdated yesterday
Productivity & AutomationAuto-check passed
Cold Start Interview
anthropics/claude-for-legal
Official
Run the cold-start interview to learn your IP practice and write your practice profile.
9.6k GitHub starsUsed in 3 repos~11k tokens
Agent WorkflowsAuto-check passed
Cold Start Interview
anthropics/claude-for-legal
Official
Cold-start setup — learns your jurisdictional footprint and escalation rules from your handbook and termination memos.
9.6k GitHub starsUsed in 2 repos~8k tokens
Agent WorkflowsAuto-check passed
Cold Start Interview
anthropics/claude-for-legal
Official
Run the cold-start interview to learn your commercial contracts practice and write your team practice profile.
9.6k GitHub starsUsed in 2 repos~12k tokens
Agent WorkflowsAuto-check passed

Questions about Divine Context

What does Divine Context do?

A skill your agent uses when starting work in any divine- repo (divine-web, divine-mobile, divine-funnelcake, keycast, divine-blossom, divine-router, etc.) or when you've learned a cross-repo fact…. Divine Context is an agent skill from divinevideo/divine-mobile.) or when you've learned a cross-repo fact worth sharing back.

When should I use Divine Context?

Divine Context fits situations like: starting work in any divine- repo (divine-web; divine-funnelcake; youve learned a cross-repo fact worth sharing back.

How do I install Divine Context in Claude Code?

Run `npx skills add divinevideo/divine-mobile --skill divine-context -a claude-code`. Or copy the skill folder (.agents/skills/divine-context in divinevideo/divine-mobile) into .claude/skills/divine-context in your project. Claude Code loads it when a task matches its description.

How do I install Divine Context in Codex?

Run `npx skills add divinevideo/divine-mobile --skill divine-context -a codex`. Or copy the skill folder (.agents/skills/divine-context in divinevideo/divine-mobile) into .agents/skills/divine-context in your project. Codex loads it when a task matches its description.

Can I use Divine Context 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 divinevideo/divine-mobile --skill divine-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/divine-context, .gemini/skills/divine-context, .github/skills/divine-context and .opencode/skills/divine-context in your project.

What does Divine Context need to run?

Going by SKILL.md and its folder, Divine Context needs the command-line tools its instructions call (git and gh).

Does Divine Context 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 Divine Context 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 Divine Context use?

Divine Context is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Divine Context use?

About 1.6k tokens (SKILL.md is roughly 6.5k 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 Divine Context?

Skills that share tags, products or a category with Divine Context: Start (Donchitos/Claude-Code-Game-Studios, 26k stars), Session Start Hook (asgeirtj/system_prompts_leaks, 69k stars), Where Do I Start (mohitagw15856/pm-claude-skills, 1.4k stars) and Cold Start Interview (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Divine Context?

divinevideo (a GitHub organization) maintains it in divinevideo/divine-mobile, which has 266 GitHub stars. The repository holds 103 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Divine Context

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Divine Context

On disk

Reading divine-context

Updating divine-context

Workflow

What goes in divine-context (and what doesn't)

Hard rules

End-of-task report

Common rationalizations to ignore

Files

Compare with similar skills

Similar skills

More from divinevideo/divine-mobile

Questions about Divine Context