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.
A skill your agent uses when adding or changing what a CLI command prints - creating or editing views (views.ts), list/item/grid/table rendering, deciding what --output plain, json, or toon emit…
MITAuto-check passed
Install Render Command Output
$ npx skills add crowdin/crowdin-cli --skill render-command-output -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install crowdin/crowdin-cli render-command-output --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/crowdin/crowdin-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/render-command-output .claude/skills/render-command-output && 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 "render-command-output" agent skill from https://github.com/crowdin/crowdin-cli/tree/main/.agents/skills/render-command-output into .claude/skills/render-command-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "render-command-output", 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/crowdin/crowdin-cli/tree/main/.agents/skills/render-command-outputType 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 crowdin/crowdin-cli --skill render-command-output -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install crowdin/crowdin-cli render-command-output --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/crowdin/crowdin-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/render-command-output .agents/skills/render-command-output && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "render-command-output" agent skill from https://github.com/crowdin/crowdin-cli/tree/main/.agents/skills/render-command-output into .agents/skills/render-command-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "render-command-output", 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 crowdin/crowdin-cli --skill render-command-output -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install crowdin/crowdin-cli render-command-output --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/crowdin/crowdin-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/render-command-output .cursor/skills/render-command-output && 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 "render-command-output" agent skill from https://github.com/crowdin/crowdin-cli/tree/main/.agents/skills/render-command-output into .cursor/skills/render-command-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "render-command-output", 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/crowdin/crowdin-cli.git --path .agents/skills/render-command-output--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 crowdin/crowdin-cli --skill render-command-output -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install crowdin/crowdin-cli render-command-output --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/crowdin/crowdin-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/render-command-output .gemini/skills/render-command-output && 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 "render-command-output" agent skill from https://github.com/crowdin/crowdin-cli/tree/main/.agents/skills/render-command-output into .gemini/skills/render-command-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "render-command-output", 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 crowdin/crowdin-cli render-command-outputInstalls 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 crowdin/crowdin-cli --skill render-command-output -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/crowdin/crowdin-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/render-command-output .github/skills/render-command-output && 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 "render-command-output" agent skill from https://github.com/crowdin/crowdin-cli/tree/main/.agents/skills/render-command-output into .github/skills/render-command-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "render-command-output", 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 crowdin/crowdin-cli --skill render-command-output -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install crowdin/crowdin-cli render-command-output --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/crowdin/crowdin-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/render-command-output .opencode/skills/render-command-output && 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 "render-command-output" agent skill from https://github.com/crowdin/crowdin-cli/tree/main/.agents/skills/render-command-output into .opencode/skills/render-command-output/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "render-command-output", 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
render-command-output- GitHub stars
- 319
- Token cost
- ~1.6k tokens
- SKILL.md length
- 784 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when adding or changing what a CLI command prints - creating or editing views (views.ts), list/item/grid/table rendering, deciding what --output plain, json, or toon emit…
- Changing what a CLI command prints - creating
- SKILL.md covers The model, What each format is for, and…, --verbose adds more information and Rendering surface - Output…, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Editing views (views.ts)
What it does
Render Command Output is an agent skill from crowdin/crowdin-cli. Use when adding or changing what a CLI command prints - creating or editing views (views.ts), list/item/grid/table rendering, deciding what --output plain, json, or toon emit, --verbose behavior, empty states, warnings and errors, stdout vs stderr, or reviewing output-related changes.
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 repository describes itself as: A command-line client for the Crowdin API. The licence is MIT.
When your agent uses it
- Changing what a CLI command prints - creating
- Editing views (views.ts)
- List/item/grid/table rendering
- Deciding what --output plain
Example prompts
- “/render-command-output”
What it can do on your machine
Read from SKILL.md and the folder at commit 1522c9b. 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
Render Command Output loads about 1.6k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 784 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 crowdin/crowdin-cli at commit 1522c9b, republished under its MIT licence (© crowdin). 784 words, ~1,564 tokens.
Download SKILL.mdSave it as
.claude/skills/render-command-output/SKILL.md (or your agent's skills folder).- name
- render-command-output
- description
- Use when adding or changing what a CLI command prints - creating or editing views (views.ts), list/item/grid/table rendering, deciding what --output plain, json, or toon emit, --verbose behavior, empty states, warnings and errors, stdout vs stderr, or reviewing output-related changes.
Command output philosophy
The model
One global flag, four formats: --output = text (default) | json | toon | plain, implemented in cli/utils/output.ts + cli/utils/formatter.ts. Two axes classify them:
- Machine vs prose: json, toon, and plain are parseable contracts - the command owes the caller a result document, not narrative.
- Structured vs line-oriented: json/toon serialize a value wholesale; text and plain emit lines.
Core principle: stdout carries only the result document; diagnostics go to stderr in every format.
What each format is for, and how it should look
text - a human at a terminal. The only format with ceremony: colors, success/info symbols, spinners, intro/outro, empty-state notices, friendly sentences. Everything decorative lives here and only here. Views color their own lines (colors.yellow('#id'), green names) - colors auto-disable outside text, so views never guard them.
plain - a shell pipeline. Machine-oriented but line-oriented: the zero-dependency format for grep/xargs/awk. One bare line per entity: identifier first, then space-safe fields - a field that can contain spaces goes last or stays out, so the line splits predictably on whitespace. No symbols, no color, no prose: File #12: path is a text line, not a plain line; self-description for machines lives in json/toon. The line is the contract - its wording is frozen once shipped, and zero lines is itself a valid answer (an empty list prints nothing). A view defines plain when the pipeline line differs from the human line; when the text line already is the bare contract, plain falls back to it.
json - a parser. The complete structured result: values in raw shape (the view does no display shaping here), narrowed by the view's keys to the fields the rendered line shows, pretty-printed on stdout. Missing keys become null rather than vanishing, so lists stay uniform. Diagnostics are one compact record per line on stderr ({"level","message"[,"code"]}), emitted as they happen so a killed run keeps what it already reported.
toon - an AI agent. The same data contract as json in TOON's token-efficient tabular encoding. Never diverges from json in what is carried, only in how it's encoded (stderr records are blank-line separated).
--verbose adds more information
--verbose doesn't depend on the output format - it means "show more information", and each format renders that the way it renders everything else. Mechanically, a verbose view extends the base view (the text line and keys); shipped plain lines keep their contract.
Rendering surface - Output methods per format
| Method | text | plain | json / toon |
|---|---|---|---|
list(items, view, {empty}) | ◆ view.text per item; info line with empty when zero items | view.plain (fallback: view.text) per item; nothing when empty | items narrowed to view.keys; [] when empty |
item(value, view, {mark}) | view.text, ◆ prefix unless mark: false | view.plain ?? view.text, bare | value narrowed to view.keys |
grid / table | rendered grid | nothing - hand-roll a plain view (see Report shapes) | serialized rows |
warning / error | icon line → stderr | bare line → stderr | one record per line → stderr |
success / info / log, intro/outro, spinner progress | shown | silent | silent |
A spinner's error operation routes to error(), so spinner failures reach stderr in every format; only its progress messages are text-only.
Show full SKILL.md (288 more words)Show less
Report shapes - follow the precedent
| Shape | Plain form | Precedent |
|---|---|---|
Entity report (info-style) | bare-id headline + the same detail lines as text | commands/string/views.ts createStringView |
| Stats report | Key: value per line; no title, no footer | commands/context/views.ts contextStatusPlainView |
| 2-D grid (languages × metrics) | hand-rolled plain view; a direct options.output === 'plain' branch is allowed here | commands/status/StatusCommand.ts |
| Dry-run path listing | machine format wins over --tree; use printDryRunPaths | commands/common/dryRunPaths.ts |
Multi-line reports render via output.item(value, view, { mark: false }) - a report block, not a mutation echo.
Contract rules
- Plain wording is frozen. Scripts parse these lines. Changing an existing plain line - or a
keysname - is a breaking change. "Friendlier"/"more readable" belongs to text; plain optimizes forawk '{print $1}', not for eyes. - Behavior differences between formats are contracts, not tools. A few commands deliberately behave differently under plain (suppressed messages, an error where text warns); each is documented in a code comment where it occurs. Never invent new ones.
- Direct format branching (
options.output === 'plain',isMachineFormat,isStructuredFormat) in an action is allowed only for hand-rolled reports and the established behavior differences above. Everything else goes through oneViewand theOutputhelper.
Common mistakes
| Mistake | Reality |
|---|---|
Expecting the empty message in machine formats | It renders via info() → text only. json/toon print []; plain prints nothing - zero lines is the answer |
Emitting warnings via log()/console.log, or assuming they're dropped outside text | output.warning() → stderr in every format, structured record in json/toon |
| Decorating the plain line to make it self-describing | Plain is bare fields, identifier first; self-description lives in json/toon |
Branching on options.output for a plain list | One View + output.list covers all four formats |
Checking === 'plain' where json/toon also owe the result | Use isMachineFormat/isStructuredFormat from formatter.ts |
| Rewording an existing plain line during a refactor | Frozen contract - treat as a breaking change, don't |
© crowdin, 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 .agents/skills/render-command-output of crowdin/crowdin-cli.
Open the folder on GitHubat commit 1522c9b
Compare with similar skills
Render Command Output 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 |
|---|---|---|---|---|---|---|
| Render Command Output this skillcrowdin/crowdin-cli | 319 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Render Blockingthedaviddias/Front-End-Checklist | 74k | — | ~430 | Automated safety check: Pass | MIT | |
| Web Renderer Testremotion-dev/remotion | 62k | — | ~547 | Automated safety check: Pass | Custom licence | |
| Make Changesremix-run/remix | 33k | — | ~2.4k | Automated safety check: Pass | MIT | |
| RenderLeoYeAI/openclaw-master-skills | 2.2k | — | ~4.8k | Automated safety check: Pass | MIT | |
| Orch Change Featureaffaan-m/ECC | 274k | 1 repos | ~420 | Automated safety check: Pass | MIT |
Similar skills
- Official
Web Renderer Test
remotion-dev/remotion
Add explicitly requested web renderer tests or update existing ones for implementation changes.
Make Changes
remix-run/remix
Create or update Remix repo change files under packages//.changes.
Render
LeoYeAI/openclaw-master-skills
Deploy and operate apps on Render (Blueprint + one-click Dashboard deeplink, same flow as Codex render-deploy).
Orch Change Feature
affaan-m/ECC
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit.
CSS Print
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing stylesheets, component styles, and responsive behavior related to Include a print stylesheet.
More from crowdin/crowdin-cli
Add E2E Test Suite
crowdin/crowdin-cli
Adds a new end-to-end (e2e) test suite for the Crowdin CLI under tests/e2e/suites/, exercising real CLI commands against a freshly-created Crowdin project.
Crowdin API Client
crowdin/crowdin-cli
A skill your agent uses when implementing, refactoring, or reviewing @crowdin/crowdin-api-client usage in any JavaScript or TypeScript project, especially for endpoint selection, request/response…
Live Crowdin CLI Validation
crowdin/crowdin-cli
Validates CLI commands against live environments with safe setup and cleanup.
Questions about Render Command Output
What does Render Command Output do?
A skill your agent uses when adding or changing what a CLI command prints - creating or editing views (views.ts), list/item/grid/table rendering, deciding what --output plain, json, or toon emit…. Render Command Output is an agent skill from crowdin/crowdin-cli.ts), list/item/grid/table rendering, deciding what --output plain, json, or toon emit, --verbose behavior, empty states, warnings and errors, stdout vs stderr, or reviewing output-related changes.
When should I use Render Command Output?
Render Command Output fits situations like: changing what a CLI command prints - creating; editing views (views.ts); list/item/grid/table rendering; deciding what --output plain.
How do I install Render Command Output in Claude Code?
Run `npx skills add crowdin/crowdin-cli --skill render-command-output -a claude-code`. Or copy the skill folder (.agents/skills/render-command-output in crowdin/crowdin-cli) into .claude/skills/render-command-output in your project. Claude Code loads it when a task matches its description.
How do I install Render Command Output in Codex?
Run `npx skills add crowdin/crowdin-cli --skill render-command-output -a codex`. Or copy the skill folder (.agents/skills/render-command-output in crowdin/crowdin-cli) into .agents/skills/render-command-output in your project. Codex loads it when a task matches its description.
Can I use Render Command Output 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 crowdin/crowdin-cli --skill render-command-output -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/render-command-output, .gemini/skills/render-command-output, .github/skills/render-command-output and .opencode/skills/render-command-output in your project.
What does Render Command Output need to run?
SKILL.md names no scripts, command-line tools or credentials: Render Command Output is instructions for the agent only.
Does Render Command Output 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 Render Command Output 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 Render Command Output use?
Render Command Output 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 Render Command Output use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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 Render Command Output?
Skills that share tags, products or a category with Render Command Output: Render Blocking (thedaviddias/Front-End-Checklist, 74k stars), Web Renderer Test (remotion-dev/remotion, 62k stars), Make Changes (remix-run/remix, 33k 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 Render Command Output?
crowdin (a GitHub organization) maintains it in crowdin/crowdin-cli, which has 319 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 6, 2026.
Source: crowdin/crowdin-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.