Implement
sickn33/agentic-awesome-skills
Implement a piece of work based on a PRD or set of issues. An agent skill from sickn33/agentic-awesome-skills.
Adding or modifying Golem CLI StructuredOutput implementations, command-output.schema.json, or DTO-backed output schema generators.
Custom licenceAuto-check passed
Install Modifying CLI Output Schema
$ npx skills add golemcloud/golem --skill modifying-cli-output-schema -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install golemcloud/golem modifying-cli-output-schema --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/golemcloud/golem.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/modifying-cli-output-schema .claude/skills/modifying-cli-output-schema && 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 "modifying-cli-output-schema" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/modifying-cli-output-schema into .claude/skills/modifying-cli-output-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modifying-cli-output-schema", 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/golemcloud/golem/tree/main/.agents/skills/modifying-cli-output-schemaType 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 golemcloud/golem --skill modifying-cli-output-schema -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install golemcloud/golem modifying-cli-output-schema --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/modifying-cli-output-schema .agents/skills/modifying-cli-output-schema && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "modifying-cli-output-schema" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/modifying-cli-output-schema into .agents/skills/modifying-cli-output-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modifying-cli-output-schema", 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 golemcloud/golem --skill modifying-cli-output-schema -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install golemcloud/golem modifying-cli-output-schema --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/modifying-cli-output-schema .cursor/skills/modifying-cli-output-schema && 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 "modifying-cli-output-schema" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/modifying-cli-output-schema into .cursor/skills/modifying-cli-output-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modifying-cli-output-schema", 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/golemcloud/golem.git --path .agents/skills/modifying-cli-output-schema--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 golemcloud/golem --skill modifying-cli-output-schema -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install golemcloud/golem modifying-cli-output-schema --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/modifying-cli-output-schema .gemini/skills/modifying-cli-output-schema && 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 "modifying-cli-output-schema" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/modifying-cli-output-schema into .gemini/skills/modifying-cli-output-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modifying-cli-output-schema", 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 golemcloud/golem modifying-cli-output-schemaInstalls 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 golemcloud/golem --skill modifying-cli-output-schema -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/modifying-cli-output-schema .github/skills/modifying-cli-output-schema && 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 "modifying-cli-output-schema" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/modifying-cli-output-schema into .github/skills/modifying-cli-output-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modifying-cli-output-schema", 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 golemcloud/golem --skill modifying-cli-output-schema -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install golemcloud/golem modifying-cli-output-schema --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/golemcloud/golem.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/modifying-cli-output-schema .opencode/skills/modifying-cli-output-schema && 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 "modifying-cli-output-schema" agent skill from https://github.com/golemcloud/golem/tree/main/.agents/skills/modifying-cli-output-schema into .opencode/skills/modifying-cli-output-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "modifying-cli-output-schema", 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
modifying-cli-output-schema- GitHub stars
- 1.5k
- Token cost
- ~2.7k tokens
- SKILL.md length
- 1,231 words
- Files
- 1
- Skills in repo
- 289
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Adding or modifying Golem CLI StructuredOutput implementations, command-output.schema.json, or DTO-backed output schema generators.
- Works in 7 steps: Keep the public $type discriminator… → $type values are semantic output… → Keep machine-readable structured output… → …
- SKILL.md covers Core Rules, Important Files, Generator Rules and Accepted Generic JSON Leaves, plus 7 more sections
- Calls cargo and npm
What it does
Modifying CLI Output Schema is an agent skill from golemcloud/golem. Adding or modifying Golem CLI StructuredOutput implementations, command-output.schema.json, or DTO-backed output schema generators.
Its SKILL.md is about 2.7k 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: Golem Cloud is the agent-native platform for building AI agents and distributed applications that never lose state, never duplicate work, and never require you to build…
Example prompts
- “/modifying-cli-output-schema”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Keep the public $type discriminator model. Every structured output document
- $type values are semantic output identifiers. Prefer command-like
- Keep machine-readable structured output on stdout and human logs, prompts,
- Prefer typed schema definitions over JsonValue. Use generic JSON only when
- Match serde's actual serialized shape, not the Rust type shape you expect.
- For exact object schemas, set additionalProperties: false and keep
- Every top-level output definition listed in x-golem-cli-output-types must
What it can do on your machine
Read from SKILL.md and the folder at commit c6a3029. 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:
cargonpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
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
Modifying CLI Output Schema loads about 2.7k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 1,231 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,231 words (~2,724 tokens).
“Use this skill when changing structured output from golem-cli, including:”
- name
- modifying-cli-output-schema
Files
Just SKILL.md in .agents/skills/modifying-cli-output-schema of golemcloud/golem.
Open the folder on GitHubat commit c6a3029
Compare with similar skills
Modifying CLI Output Schema 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 |
|---|---|---|---|---|---|---|
| Modifying CLI Output Schema this skillgolemcloud/golem | 1.5k | — | ~2.7k | Automated safety check: Pass | Custom licence | |
| Implementsickn33/agentic-awesome-skills | 47k | 5 repos | ~306 | Automated safety check: Pass | MIT | |
| Implementcodewhale-hq/Codewhale | 41k | — | ~190 | Automated safety check: Pass | MIT | |
| Golem Create GolemThinkR-open/golem | 946 | — | ~473 | Automated safety check: Pass | Custom licence | |
| Incremental Implementationaddyosmani/agent-skills | 103k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Implementbestofjs/bestofjs | 3.1k | 18 repos | ~109 | Automated safety check: Pass | MIT |
Similar skills
Implement
codewhale-hq/Codewhale
Carry an authorized, defined request or approved plan through scoped edits and proportionate verification.
Golem Create Golem
ThinkR-open/golem
Create a new golem Shiny application. An agent skill from ThinkR-open/golem.
Incremental Implementation
addyosmani/agent-skills
Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.
Implement
bestofjs/bestofjs
Implement a piece of work based on a spec or set of tickets.
Implement
Automattic/simplenote-android
End-to-end implementation workflow: plan, implement, verify, commit, and open a draft PR.
More from golemcloud/golem
All 289 skills in this repoMoonbit C Binding
golemcloud/golem
Guide for writing MoonBit bindings to C libraries using native FFI.
Adding Dependencies
golemcloud/golem
Adding or updating crate dependencies in the Golem workspace.
Analysing CI Failures
golemcloud/golem
Analysing GitHub Actions CI failures from a run URL. An agent skill from golemcloud/golem.
Creating New Builtin Plugins
golemcloud/golem
Adds a built-in WASM plugin that is externally released and provisioned by the registry service.
DB Migration Scripts
golemcloud/golem
Writing database migration SQL scripts. An agent skill from golemcloud/golem.
Debugging Hanging Tests
golemcloud/golem
Diagnosing and fixing hanging worker executor or integration tests.
Questions about Modifying CLI Output Schema
What does Modifying CLI Output Schema do?
Adding or modifying Golem CLI StructuredOutput implementations, command-output.schema.json, or DTO-backed output schema generators. Modifying CLI Output Schema is an agent skill from golemcloud/golem.json, or DTO-backed output schema generators.
How do I install Modifying CLI Output Schema in Claude Code?
Run `npx skills add golemcloud/golem --skill modifying-cli-output-schema -a claude-code`. Or copy the skill folder (.agents/skills/modifying-cli-output-schema in golemcloud/golem) into .claude/skills/modifying-cli-output-schema in your project. Claude Code loads it when a task matches its description.
How do I install Modifying CLI Output Schema in Codex?
Run `npx skills add golemcloud/golem --skill modifying-cli-output-schema -a codex`. Or copy the skill folder (.agents/skills/modifying-cli-output-schema in golemcloud/golem) into .agents/skills/modifying-cli-output-schema in your project. Codex loads it when a task matches its description.
Can I use Modifying CLI Output Schema 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 golemcloud/golem --skill modifying-cli-output-schema -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/modifying-cli-output-schema, .gemini/skills/modifying-cli-output-schema, .github/skills/modifying-cli-output-schema and .opencode/skills/modifying-cli-output-schema in your project.
What does Modifying CLI Output Schema need to run?
Going by SKILL.md and its folder, Modifying CLI Output Schema needs the command-line tools its instructions call (cargo and npm).
Does Modifying CLI Output Schema access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Modifying CLI Output Schema 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 Modifying CLI Output Schema use?
Modifying CLI Output Schema has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Modifying CLI Output Schema use?
About 2.7k tokens (SKILL.md is roughly 11k 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 Modifying CLI Output Schema?
Skills that share tags, products or a category with Modifying CLI Output Schema: Implement (sickn33/agentic-awesome-skills, 47k stars), Implement (codewhale-hq/Codewhale, 41k stars), Golem Create Golem (ThinkR-open/golem, 946 stars) and Incremental Implementation (addyosmani/agent-skills, 103k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Modifying CLI Output Schema?
golemcloud (a GitHub organization) maintains it in golemcloud/golem, which has 1,507 GitHub stars. The repository holds 289 skills in this directory. The repository was last updated on October 8, 2026.
Source: golemcloud/golem on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.