Clipify
louisedesadeleer/clipify
Find compelling moments in a video — funny dialogue OR repeated impact actions like axe chops, hits, throws, drumbeats — cut them as standalone clips, optionally reformat 16:9 ↔ 9:16, time-warp pans…
Forge a title + subtitle (or reframe) for a BOOK, article, talk, or any technical piece, then hand off to a cover so it has LIFE and honesty — not clinical/dated.
Install Oracle Title Forge
$ npx skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Soul-Brews-Studio/arra-oracle-skills-cli oracle-title-forge --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/Soul-Brews-Studio/arra-oracle-skills-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/skills/oracle-title-forge .claude/skills/oracle-title-forge && 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 "oracle-title-forge" agent skill from https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/alpha/src/skills/oracle-title-forge into .claude/skills/oracle-title-forge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oracle-title-forge", 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/Soul-Brews-Studio/arra-oracle-skills-cli/tree/alpha/src/skills/oracle-title-forgeType 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 Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Soul-Brews-Studio/arra-oracle-skills-cli oracle-title-forge --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/skills/oracle-title-forge .agents/skills/oracle-title-forge && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oracle-title-forge" agent skill from https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/alpha/src/skills/oracle-title-forge into .agents/skills/oracle-title-forge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oracle-title-forge", 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 Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Soul-Brews-Studio/arra-oracle-skills-cli oracle-title-forge --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/skills/oracle-title-forge .cursor/skills/oracle-title-forge && 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 "oracle-title-forge" agent skill from https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/alpha/src/skills/oracle-title-forge into .cursor/skills/oracle-title-forge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oracle-title-forge", 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/Soul-Brews-Studio/arra-oracle-skills-cli.git --path src/skills/oracle-title-forge--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 Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Soul-Brews-Studio/arra-oracle-skills-cli oracle-title-forge --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/skills/oracle-title-forge .gemini/skills/oracle-title-forge && 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 "oracle-title-forge" agent skill from https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/alpha/src/skills/oracle-title-forge into .gemini/skills/oracle-title-forge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oracle-title-forge", 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 Soul-Brews-Studio/arra-oracle-skills-cli oracle-title-forgeInstalls 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 Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/skills/oracle-title-forge .github/skills/oracle-title-forge && 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 "oracle-title-forge" agent skill from https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/alpha/src/skills/oracle-title-forge into .github/skills/oracle-title-forge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oracle-title-forge", 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 Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Soul-Brews-Studio/arra-oracle-skills-cli oracle-title-forge --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/skills/oracle-title-forge .opencode/skills/oracle-title-forge && 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 "oracle-title-forge" agent skill from https://github.com/Soul-Brews-Studio/arra-oracle-skills-cli/tree/alpha/src/skills/oracle-title-forge into .opencode/skills/oracle-title-forge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oracle-title-forge", 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
oracle-title-forge- GitHub stars
- 123
- Token cost
- ~2k tokens
- SKILL.md length
- 1,009 words
- Files
- 1
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
Forge a title + subtitle (or reframe) for a BOOK, article, talk, or any technical piece, then hand off to a cover so it has LIFE and honesty — not clinical/dated.
- Works in 7 steps: Describe before you name → Find the real tension — and check it's… → Prism the candidates — 3-5 lenses → …
- : a title feels เชย/dead/generic
- SKILL.md covers Why the method works (read…, The method — 7 moves, Output shape and Proven example, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Oracle Title Forge is an agent skill from Soul-Brews-Studio/arra-oracle-skills-cli. Forge a title + subtitle (or reframe) for a BOOK, article, talk, or any technical piece, then hand off to a cover so it has LIFE and honesty — not clinical/dated. The method that produced 'Claude Code Channel ปะทะ Hermes Gateway'. Describe-before-you-name, find the real tension, prism the candidates, calibrate register (eloquent but dev-natural, not poetic), name the real technical axes in the subtitle, refuse a fake winner. Use when: a title feels เชย/dead/generic, when naming a book or post, when reframing a…
Its SKILL.md is about 2k 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 Media & Creative, covering Transcription and Accessibility. It works with Discord. The repository describes itself as: Install Oracle skills to Claude Code, OpenCode, Cursor, and 12+ AI coding agents. The licence is MIT.
When your agent uses it
- : a title feels เชย/dead/generic
- Reframing a comparison as a genuine contest
- The user says ตั้งชื่อ
- : writing the body content itself (use kien-thai / the book skills)
Example prompts
- “Claude Code Channel ปะทะ Hermes Gateway”
- “reframe”
- “Then: the cover”
- “/oracle-title-forge”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 9feea09. 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
Oracle Title Forge loads about 2k tokens when it runs. Until then it costs about 227 tokens; SKILL.md has 1,009 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 Soul-Brews-Studio/arra-oracle-skills-cli at commit 9feea09, republished under its MIT licence (© Soul-Brews-Studio). 1,009 words, ~2,038 tokens.
Download SKILL.mdSave it as
.claude/skills/oracle-title-forge/SKILL.md (or your agent's skills folder).- name
- oracle-title-forge
- description
- Forge a title + subtitle (or reframe) for a BOOK, article, talk, or any technical piece, then hand off to a cover so it has LIFE and honesty — not clinical/dated. The method that produced 'Claude Code Channel ปะทะ Hermes Gateway'. Describe-before-you-name, find the real tension, prism the candidates, calibrate register (eloquent but dev-natural, not poetic), name the real technical axes in the subtitle, refuse a fake winner. Use when: a title feels เชย/dead/generic, when naming a book or post, when reframing a comparison as a genuine contest, or when the user says 'ตั้งชื่อ', 'title', 'reframe', 'ชื่อมันเชย', 'คิดชื่อ'. After the title lands, offer the cover step (see 'Then: the cover'). DO NOT TRIGGER for: writing the body content itself (use kien-thai / the book skills), or for designing a cover from scratch when no title work is needed (go straight to /oracle-book-cover).
- argument-hint
- <what to title — topic, or the current dead title + what the piece is about>
- hidden
- true
- metadata.internal
- true
/oracle-title-forge — forge a title that has life, honestly
Born 2026-07-09 turning the dead "ผ่าไส้ Discord Channel ของ Claude Code" into "Claude Code Channel ปะทะ Hermes Gateway — สองสถาปัตยกรรมที่ทำให้ AI คุยบน Discord ได้…" The lesson: a great title is grown from understanding what the thing IS, not shuffled from words.
Why the method works (read this first)
A dead title fails one specific way: it has clarity without intrigue. "ผ่าไส้ X" tells you the topic and nothing else — no tension, no question, no stake. Every principle below exists to add intrigue without lying. The magic isn't wordsmithing; it's that each step forces you to understand the material more deeply, and the title falls out of that understanding.
The method — 7 moves
1. Describe before you name
Never start by brainstorming words. First write what each thing IS — once vividly, once in plain technical terms. The title grows from this. (For the Discord book, writing "the plugin is a stdio bridge tied to a session's lifecycle; Hermes is an always-on daemon" is what revealed the contest.)
2. Find the real tension — and check it's not forged
If it's a comparison/VS, run a skeptic pass: is the contest real or clickbait? Two things at different layers can't fight on features. Reframe the tension at the honest layer — philosophy, fit, tradeoff — not a fake feature-fight. A title promising a showdown the book can't deliver is a lie. (Discord book: they're transport vs runtime — so the contest is "two philosophies of presence," which is true, not "which codes better," which is false.)
3. Prism the candidates — 3-5 lenses
Look at each candidate from angles a single view misses. Useful lenses for titles:
- 🏪 Bookshelf browser — does the spine make someone pick it up?
- 💀 Honest skeptic — does the title over-promise? name only one side of a two-sided story?
- 🧑💻 Dev-ear — would a developer actually say this phrase? Kill words devs don't use ("ให้ AI พูด" → "AI คุยบน Discord"; "ต่อ AI เข้ากับ Discord" → clunky; "data เข้าทางไหน" ✓ real).
- ✍️ Thai editor — cadence, clean noun phrases, cut stray connectors (ด้วย/ต่อ...เข้ากับ).
- 🎯 Precision — does the subtitle name the real axes, not vague adjectives?
4. Apply the craft principles (from title research)
- Tension = clarity × intrigue. The reader must grasp something instantly AND be compelled to open it for the rest.
- Contrast breeds curiosity. Unexpected/opposed words hook ("The Wealthy Barber"). A "ปะทะ" / "vs" between two named things is contrast built-in.
- Formula: short curious head + longer explaining subtitle. Head = hook (1-6 words / a clash / a question). Subtitle = context + payoff.
- Question form raises the stakes above the mechanism ("ใครควรได้…").
- Cadence / list-of-three makes the subtitle linger ("data ขาเข้า, การคุมสิทธิ์, วงจรชีวิต").
5. Calibrate register with the human
Draft, then dial. Common arc: clinical → too poetic → eloquent-but-technical. The target for technical work: สละสลวยแต่ตรง, ไม่เล่นอุปมามาก — pleasant to the ear, but every phrase points at something real in the code. Show the human one sample paragraph in the proposed voice and let their taste calibrate. Their "แปลกๆ" is data — chase the specific weird word.
6. Name the real technical axes in the subtitle
Don't sell with adjectives ("powerful, elegant"). Sell with the concrete things the piece compares/covers — the axes a practitioner cares about (data path, access control, lifecycle), ending on the payoff ("ตัวไหนเหมาะกับงานแบบใด").
7. Honesty is a feature, not a weakness
Refuse the cheap winner. "Generic: it's a tie on different axes; situational: here's the matrix" reads as more authoritative than "X wins." A title/frame that promises an honest verdict earns trust the clickbait can't.
Output shape
Offer 2-3 candidates, each described by the feeling it gives + the craft reason it works (not a bare list), recommend one with why, then render the full cover block (head + subtitle) so the human sees it assembled. End by asking which — let taste decide the last 5%.
Show full SKILL.md (389 more words)Show less
Proven example
# Claude Code Channel ปะทะ Hermes Gateway
สองสถาปัตยกรรมที่ทำให้ AI คุยบน Discord ได้ — เทียบตั้งแต่ data ไหลเข้าทางไหน
คุมสิทธิ์การเข้าถึงยังไง ไปจนถึงว่าตัวไหนเหมาะกับงานแบบใดHead = two named contenders + ปะทะ (contrast). Subtitle = 3 real axes + payoff. Register = eloquent but dev-natural. Verdict promised = honest (fit, not a fake winner).
Related: [[kien-thai]] (Thai prose engine), [[oracle-prism]] (the lens method), the book skills (oracle-write-complete-book / -booklet / -combine-blogs) that consume the forged title.
Book mode
A book title carries more weight than an article's: it is the spine text, the search result, and the thing someone repeats to a friend. Two extra constraints on top of the 7 moves:
- Spine test — say it out loud as if recommending it. If it needs a subtitle to make sense spoken, the main title is doing too little.
- Shelf test — write it next to three real books in the same genre. Generic titles vanish; that is the whole signal.
- Subtitle carries the technical axes (the 7 moves already say this); the main title carries the tension. Do not let the subtitle rescue a dead title.
Then: the cover
This skill does not draw. Stated plainly because the alternative is pretending:
| capability | present here |
|---|---|
| generative image tool (Imagen / DALL-E / SD) | no — no such tool in this session |
codex CLI | yes — but codex does not generate images either |
ImageMagick (convert / magick) | yes — composition only: type on a ground, crops, gradients |
| typst | yes — vector/typographic covers rendered with the book |
So a cover here is one of two honest things: found art (licence-checked) or a typographic composition. Neither is "the AI drew it", and neither should be described that way.
Hand off to /oracle-book-cover — it already does this properly: finds real art with a
LICENCE gate, runs a 5-lens prism (Reader / Editor / Artist / Designer / Ads), renders 2-3
PNG candidates, bakes the winner into the book.typ cover block only, and exports social
crops. Do not rebuild that pipeline here.
/oracle-title-forge → title + subtitle
↓
/oracle-book-cover → art (licence-checked) or typographic cover → book.typIf /oracle-book-cover is not installed on this machine, say so and stop — do not
improvise a cover with convert and call it a design. A typographic fallback is legitimate
only when the human asks for it knowing no illustration is involved.
Delegating to codex: /codex:rescue or the codex-rescue agent can take a
cover-generation task (typst layout, ImageMagick composition, asset wrangling). It cannot
produce an illustration. If someone asks "get codex to draw it", the answer is that no
agent in this fleet has an image model — the work has to be found art, vector, or type.
© Soul-Brews-Studio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. 1 hidden character (zero-width or bidirectional) removed. Raw file
Files
Just SKILL.md in src/skills/oracle-title-forge of Soul-Brews-Studio/arra-oracle-skills-cli.
Open the folder on GitHubat commit 9feea09
Compare with similar skills
Oracle Title Forge 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 |
|---|---|---|---|---|---|---|
| Oracle Title Forge this skillSoul-Brews-Studio/arra-oracle-skills-cli | 123 | — | ~2k | Automated safety check: Pass | MIT | |
| Clipifylouisedesadeleer/clipify | 587 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Captions Media Accessibilitycalesthio/generative-media-skills | 197 | — | ~6.9k | Automated safety check: Pass | MIT | |
| Multimedia AccessibilityOwl-Listener/inclusive-design-skills | 105 | — | ~894 | Automated safety check: Pass | MIT | |
| YouTube Captions FetcherZeroPointRepo/youtube-skills | 1k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Video Accessibilitythedaviddias/Front-End-Checklist | 74k | — | ~490 | Automated safety check: Pass | MIT |
Similar skills
Captions Media Accessibility
calesthio/generative-media-skills
Provider-independent captions and media accessibility direction for AI agents producing or finishing generated videos, ads, social clips, explainers, avatar videos, documentaries, podcasts/video…
Multimedia Accessibility
Owl-Listener/inclusive-design-skills
Design accessible video, audio, and multimedia content with captions, transcripts, and audio descriptions.
YouTube Captions Fetcher
ZeroPointRepo/youtube-skills
Fetches timestamped captions or plain-text transcripts for any YouTube video through the TranscriptAPI service, for reading, quoting, translating or accessibility.
Video Accessibility
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Make videos accessible with captions.
Bio Atac Seq Motif Deviation
FreedomIntelligence/OpenClaw-Medical-Skills
Analyze transcription factor motif accessibility variability using chromVAR.
More from Soul-Brews-Studio/arra-oracle-skills-cli
All 31 skills in this repoDig
Soul-Brews-Studio/arra-oracle-skills-cli
Mine Claude Code sessions — timeline, gaps, repo attribution, session history.
Forward
Soul-Brews-Studio/arra-oracle-skills-cli
Hand off the current session to the next one. An agent skill from Soul-Brews-Studio/arra-oracle-skills-cli.
Project
Soul-Brews-Studio/arra-oracle-skills-cli
Clone and track external repos. An agent skill from Soul-Brews-Studio/arra-oracle-skills-cli.
Round Table
Soul-Brews-Studio/arra-oracle-skills-cli
Convene a Round Table (โต๊ะกลม): 3–8 souls — persona files, Oracles, or real people's DNA — debate ONE stakes-bearing decision over exactly 4 rounds (OPEN, DEEPEN, CONVERGE, VOTE), one subagent per…
Soul
Soul-Brews-Studio/arra-oracle-skills-cli
Bring an Oracle into the current repo — its soul, ALL its skills and its expertise — by link, never by copy.
Trace
Soul-Brews-Studio/arra-oracle-skills-cli
Find projects, code, and knowledge across git history, repos, docs, and Oracle.
Related
Works with
Categories
Questions about Oracle Title Forge
What does Oracle Title Forge do?
Forge a title + subtitle (or reframe) for a BOOK, article, talk, or any technical piece, then hand off to a cover so it has LIFE and honesty — not clinical/dated. Oracle Title Forge is an agent skill from Soul-Brews-Studio/arra-oracle-skills-cli. Forge a title + subtitle (or reframe) for a BOOK, article, talk, or any technical piece, then hand off to a cover so it has LIFE and honesty — not clinical/dated.
When should I use Oracle Title Forge?
Oracle Title Forge fits situations like: : a title feels เชย/dead/generic; reframing a comparison as a genuine contest; the user says ตั้งชื่อ; : writing the body content itself (use kien-thai / the book skills).
How do I install Oracle Title Forge in Claude Code?
Run `npx skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a claude-code`. Or copy the skill folder (src/skills/oracle-title-forge in Soul-Brews-Studio/arra-oracle-skills-cli) into .claude/skills/oracle-title-forge in your project. Claude Code loads it when a task matches its description.
How do I install Oracle Title Forge in Codex?
Run `npx skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a codex`. Or copy the skill folder (src/skills/oracle-title-forge in Soul-Brews-Studio/arra-oracle-skills-cli) into .agents/skills/oracle-title-forge in your project. Codex loads it when a task matches its description.
Can I use Oracle Title Forge 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 Soul-Brews-Studio/arra-oracle-skills-cli --skill oracle-title-forge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oracle-title-forge, .gemini/skills/oracle-title-forge, .github/skills/oracle-title-forge and .opencode/skills/oracle-title-forge in your project.
What does Oracle Title Forge need to run?
SKILL.md names no scripts, command-line tools or credentials: Oracle Title Forge is instructions for the agent only.
Does Oracle Title Forge 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 Oracle Title Forge 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 Oracle Title Forge use?
Oracle Title Forge 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 Oracle Title Forge use?
About 2k tokens (SKILL.md is roughly 8.2k 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 Oracle Title Forge?
Skills that share tags, products or a category with Oracle Title Forge: Clipify (louisedesadeleer/clipify, 587 stars), Captions Media Accessibility (calesthio/generative-media-skills, 197 stars), Multimedia Accessibility (Owl-Listener/inclusive-design-skills, 105 stars) and YouTube Captions Fetcher (ZeroPointRepo/youtube-skills, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oracle Title Forge?
Soul-Brews-Studio (a GitHub organization) maintains it in Soul-Brews-Studio/arra-oracle-skills-cli, which has 123 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 3, 2026.
Source: Soul-Brews-Studio/arra-oracle-skills-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.