Box
asgeirtj/system_prompts_leaks
Search, read, upload, download, move, rename, delete, restore, and share Box content; manage comments and metadata.
Render an answer inline as compact ASCII or box-drawing art with semantic status icons.
MITAuto-check passed
Install Ork Glyph
$ npx skills add yonatangross/orchestkit --skill ork-glyph -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install yonatangross/orchestkit ork-glyph --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/yonatangross/orchestkit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ork-codex/skills/ork-glyph .claude/skills/ork-glyph && 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 "ork-glyph" agent skill from https://github.com/yonatangross/orchestkit/tree/main/plugins/ork-codex/skills/ork-glyph into .claude/skills/ork-glyph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ork-glyph", 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/yonatangross/orchestkit/tree/main/plugins/ork-codex/skills/ork-glyphType 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 yonatangross/orchestkit --skill ork-glyph -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install yonatangross/orchestkit ork-glyph --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ork-codex/skills/ork-glyph .agents/skills/ork-glyph && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ork-glyph" agent skill from https://github.com/yonatangross/orchestkit/tree/main/plugins/ork-codex/skills/ork-glyph into .agents/skills/ork-glyph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ork-glyph", 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 yonatangross/orchestkit --skill ork-glyph -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install yonatangross/orchestkit ork-glyph --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ork-codex/skills/ork-glyph .cursor/skills/ork-glyph && 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 "ork-glyph" agent skill from https://github.com/yonatangross/orchestkit/tree/main/plugins/ork-codex/skills/ork-glyph into .cursor/skills/ork-glyph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ork-glyph", 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/yonatangross/orchestkit.git --path plugins/ork-codex/skills/ork-glyph--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 yonatangross/orchestkit --skill ork-glyph -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install yonatangross/orchestkit ork-glyph --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ork-codex/skills/ork-glyph .gemini/skills/ork-glyph && 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 "ork-glyph" agent skill from https://github.com/yonatangross/orchestkit/tree/main/plugins/ork-codex/skills/ork-glyph into .gemini/skills/ork-glyph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ork-glyph", 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 yonatangross/orchestkit ork-glyphInstalls 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 yonatangross/orchestkit --skill ork-glyph -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ork-codex/skills/ork-glyph .github/skills/ork-glyph && 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 "ork-glyph" agent skill from https://github.com/yonatangross/orchestkit/tree/main/plugins/ork-codex/skills/ork-glyph into .github/skills/ork-glyph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ork-glyph", 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 yonatangross/orchestkit --skill ork-glyph -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install yonatangross/orchestkit ork-glyph --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/yonatangross/orchestkit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ork-codex/skills/ork-glyph .opencode/skills/ork-glyph && 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 "ork-glyph" agent skill from https://github.com/yonatangross/orchestkit/tree/main/plugins/ork-codex/skills/ork-glyph into .opencode/skills/ork-glyph/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ork-glyph", 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
ork-glyph- GitHub stars
- 292
- Token cost
- ~860 tokens
- SKILL.md length
- 410 words
- Files
- 2
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Render an answer inline as compact ASCII or box-drawing art with semantic status icons.
- Requests to show something visually
- SKILL.md covers Choose the form and Rendering contract
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Conceptual explanations
What it does
Ork Glyph is an agent skill from yonatangross/orchestkit. Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets, comparisons, rankings, pipelines, or requests to show something visually. Do not use for definitions, conceptual explanations, one-sentence answers, or requests for a saved page or file.
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
The repository describes itself as: The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install ork for stable (v9.x), or ork-alpha for the v10 line, which ships daily. The licence is MIT.
When your agent uses it
- Requests to show something visually
- Conceptual explanations
- One-sentence answers
- Requests for a saved page
Example prompts
- “/ork-glyph”
Requirements
- Docker
What it can do on your machine
Read from SKILL.md and the folder at commit e4ff8d9. 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
Ork Glyph loads about 860 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 410 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 yonatangross/orchestkit at commit e4ff8d9, republished under its MIT licence (© yonatangross). 410 words, ~860 tokens.
Download SKILL.mdSave it as
.claude/skills/ork-glyph/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- ork-glyph
- description
- Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Use for status, inventories, budgets, comparisons, rankings, pipelines, or requests to show something visually. Do not use for definitions, conceptual explanations, one-sentence answers, or requests for a saved page or file.
Ork Glyph
Render immediately from the user's topic. With no topic, use the current conversation. Choose the form yourself without setup questions, task creation, or subagents. The inline rendering itself needs no external tools.
Encode information in structure. State the verdict in one prose line, then draw one render in a monospace code block. Follow it with two or three short observations when the diagram reveals something worth explaining.
Choose the form
| Data shape | Render |
|---|---|
| Inventory, audit, budget | Header meter, sections, rows, totals, caveats |
| Status, progress, health | Status box and bar meters |
| Options, trade-offs | Comparison table |
| Steps, pipeline, handoffs | Flow with arrows |
| Containment, layers | Nested boxes or tree |
| Ranking, scores, counts | Table and bars |
| Change over time | Sparkline or milestone track |
Rendering contract
- One render per reply, at most about 50 lines. In a terminal, keep each line within 76 display cells. In chat, web transcripts, and other non-TTY surfaces, use at most 72 cells and one narrow table or a vertical list, never side-by-side boards. Default to the non-TTY layout when the surface is uncertain.
- Use one box style per render:
┌─┐│└─┘normally,╭─╮│╰─╯for soft status cards, or+-|for ASCII-only surfaces. Keep nesting to three levels. Use arrows→,↓, or->and meters▓▓▓░░with the numeric value beside them. - Pair every status icon with a word: ✅ done, ❌ failed, ⚠️ warning, 🔄 in progress, ⏸ waiting, 💡 idea, 🚨 hard block, 🎯 goal, 🔥 top priority, 📜 doc, 🤖 agent, ⚡ hook, ℹ️ caveat. Risk uses 🟢 low, 🟡 medium, 🔴 high; ranking uses 🥇 1st, 🥈 2nd, 🥉 3rd.
- For domain rows, use at most one leading icon: 🐳 docker, 🌐 browser, 📦 package, 🐍 python, 🧠 model, 📱 device, 💾 volume, 🗑️ trash, 🗂️ files, 📥 downloads, 🔑 secret, 🧪 test, 🖥️ host, ☁️ cloud, 📧 mail, 💬 chat. Keep icons out of prose sentences and avoid emoji chains.
- Align labels and numbers by display width, accounting for wide characters. Avoid full-width decorative rules, em or en dashes, and Mermaid in this inline mode.
- Use only supplied or verified data. Print
?for unknown values. Show units, denominators, and arithmetic for totals; call out overlaps or estimates. - An inventory proceeds from subject and headline meter to labeled sections, then rows containing label, bar, value, and action when relevant. Finish with section totals, the overall arithmetic, and caveats. Omit unsupported fields.
Show full SKILL.md (54 more words)Show less
Example with supplied counts:
Checks 3 / 4 passed
┌──────────┬─────────────┐
│ Unit │ ✅ done │
│ Security │ ✅ done │
│ Build │ ✅ done │
│ Browser │ ⏸ waiting │
└──────────┴─────────────┘Keep output inline unless the user requested a file. If the full data exceeds the budget, render a labeled summary and state what was omitted. For an explicit file or page request, use the host's available artifact workflow and link the resulting artifact; do not assume another plugin's commands exist.
© yonatangross, 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 1 other file in plugins/ork-codex/skills/ork-glyph of yonatangross/orchestkit.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit e4ff8d9
Compare with similar skills
Ork Glyph 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 |
|---|---|---|---|---|---|---|
| Ork Glyph this skillyonatangross/orchestkit | 292 | — | ~860 | Automated safety check: Pass | MIT | |
| Boxasgeirtj/system_prompts_leaks | 69k | — | ~1.1k | Automated safety check: Pass | CC0-1.0 | |
| Strategic Compactaffaan-m/ECC | 277k | 1 repos | ~2.1k | Automated safety check: Pass | MIT | |
| Render Blockingthedaviddias/Front-End-Checklist | 74k | — | ~430 | Automated safety check: Pass | MIT | |
| RenderLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Javascript Inlinethedaviddias/Front-End-Checklist | 74k | — | ~461 | Automated safety check: Pass | MIT |
Similar skills
Strategic Compact
affaan-m/ECC
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction.
Render Blocking
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Eliminate render-blocking resources.
Render
LeoYeAI/openclaw-master-skills
Deploy and operate apps on Render (Blueprint + one-click Dashboard deeplink, same flow as Codex render-deploy).
Javascript Inline
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing scripts, client components, bundles, or runtime behavior related to Avoid inline JavaScript.
SVG Inline
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing image assets, markup, and CDN or build transforms related to Manage inline SVG size and complexity.
More from yonatangross/orchestkit
All 107 skills in this repoAPI Design
yonatangross/orchestkit
API contract design for REST and GraphQL, covering resource shape, URL and header versioning with deprecation windows, RFC 9457 Problem Details error handling, and OpenAPI specs.
Architecture Decision Record
yonatangross/orchestkit
ADR templates in the Nygard format with context, decision, consequences, and alternatives.
Audit Full
yonatangross/orchestkit
Single-pass codebase analysis leveraging a 1M-token context window for comprehensive security scanning, architecture review, and dependency auditing.
Code Review Playbook
yonatangross/orchestkit
Structured review processes, conventional comments, language-specific checklists, and feedback templates.
Create PR
yonatangross/orchestkit
Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation.
Explore
yonatangross/orchestkit
Multi-angle codebase exploration spawning 3-5 parallel agents for code structure, data flow, architecture patterns, and health assessment.
Questions about Ork Glyph
What does Ork Glyph do?
Render an answer inline as compact ASCII or box-drawing art with semantic status icons. Ork Glyph is an agent skill from yonatangross/orchestkit. Render an answer inline as compact ASCII or box-drawing art with semantic status icons.
When should I use Ork Glyph?
Ork Glyph fits situations like: requests to show something visually; conceptual explanations; one-sentence answers; requests for a saved page.
How do I install Ork Glyph in Claude Code?
Run `npx skills add yonatangross/orchestkit --skill ork-glyph -a claude-code`. Or copy the skill folder (plugins/ork-codex/skills/ork-glyph in yonatangross/orchestkit) into .claude/skills/ork-glyph in your project. Claude Code loads it when a task matches its description.
How do I install Ork Glyph in Codex?
Run `npx skills add yonatangross/orchestkit --skill ork-glyph -a codex`. Or copy the skill folder (plugins/ork-codex/skills/ork-glyph in yonatangross/orchestkit) into .agents/skills/ork-glyph in your project. Codex loads it when a task matches its description.
Can I use Ork Glyph 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 yonatangross/orchestkit --skill ork-glyph -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ork-glyph, .gemini/skills/ork-glyph, .github/skills/ork-glyph and .opencode/skills/ork-glyph in your project.
What does Ork Glyph need to run?
SKILL.md names no scripts, command-line tools or credentials: Ork Glyph is instructions for the agent only. Our summary lists: Docker.
Does Ork Glyph 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 Ork Glyph 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 Ork Glyph use?
Ork Glyph 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 Ork Glyph use?
About 860 tokens (SKILL.md is roughly 3.4k 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 Ork Glyph?
Skills that share tags, products or a category with Ork Glyph: Box (asgeirtj/system_prompts_leaks, 69k stars), Strategic Compact (affaan-m/ECC, 277k stars), Render Blocking (thedaviddias/Front-End-Checklist, 74k stars) and Render (LeoYeAI/openclaw-master-skills, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ork Glyph?
yonatangross (a GitHub user) maintains it in yonatangross/orchestkit, which has 292 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 10, 2026.
Source: yonatangross/orchestkit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.