Oryxos Admin UI
oryx-labs/oryxos
生成或扩展 OryxOS 的 Web 管理台（web manager）前端——Vue 3 + Vite 单页应用，视觉与官网首页 （website/，VitePress）完全同源：深色底 + 橙色主色、Inter/JetBrains Mono。内置这套设计 token、 工程约定（base '/admin/'、产物落 oryxos-web static/admin、SPA…
Automate docs updates and command documentation generation. An agent skill from SAP-samples/hana-developer-cli-tool-example.
Install Docs Automation
$ npx skills add SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install SAP-samples/hana-developer-cli-tool-example docs-automation --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/SAP-samples/hana-developer-cli-tool-example.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/docs-automation .claude/skills/docs-automation && 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 "docs-automation" agent skill from https://github.com/SAP-samples/hana-developer-cli-tool-example/tree/main/.github/skills/docs-automation into .claude/skills/docs-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-automation", 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/SAP-samples/hana-developer-cli-tool-example/tree/main/.github/skills/docs-automationType 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 SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install SAP-samples/hana-developer-cli-tool-example docs-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/docs-automation .agents/skills/docs-automation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "docs-automation" agent skill from https://github.com/SAP-samples/hana-developer-cli-tool-example/tree/main/.github/skills/docs-automation into .agents/skills/docs-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-automation", 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 SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install SAP-samples/hana-developer-cli-tool-example docs-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/docs-automation .cursor/skills/docs-automation && 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 "docs-automation" agent skill from https://github.com/SAP-samples/hana-developer-cli-tool-example/tree/main/.github/skills/docs-automation into .cursor/skills/docs-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-automation", 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/SAP-samples/hana-developer-cli-tool-example.git --path .github/skills/docs-automation--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 SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install SAP-samples/hana-developer-cli-tool-example docs-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/docs-automation .gemini/skills/docs-automation && 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 "docs-automation" agent skill from https://github.com/SAP-samples/hana-developer-cli-tool-example/tree/main/.github/skills/docs-automation into .gemini/skills/docs-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-automation", 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 SAP-samples/hana-developer-cli-tool-example docs-automationInstalls 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 SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/docs-automation .github/skills/docs-automation && 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 "docs-automation" agent skill from https://github.com/SAP-samples/hana-developer-cli-tool-example/tree/main/.github/skills/docs-automation into .github/skills/docs-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-automation", 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 SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install SAP-samples/hana-developer-cli-tool-example docs-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/SAP-samples/hana-developer-cli-tool-example.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/docs-automation .opencode/skills/docs-automation && 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 "docs-automation" agent skill from https://github.com/SAP-samples/hana-developer-cli-tool-example/tree/main/.github/skills/docs-automation into .opencode/skills/docs-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-automation", 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
docs-automation- GitHub stars
- 114
- Token cost
- ~344 tokens
- SKILL.md length
- 110 words
- Files
- 2 (incl. references)
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Automate docs updates and command documentation generation. An agent skill from SAP-samples/hana-developer-cli-tool-example.
- Works in 4 steps: Identify the docs scope (all commands vs… → Run the relevant automation scripts → Spot-check updated markdown for… → …
- Generate-command-docs
- SKILL.md covers When to Use, Procedure, Notes and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Docs Automation is an agent skill from SAP-samples/hana-developer-cli-tool-example. Automate docs updates and command documentation generation. Use for generate-command-docs, enhance-command-docs, sidebar generation, and VitePress build checks.
Its SKILL.md is about 340 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/checklist.md`).
It sits in Frontend & Design, covering Static sites and blogs. It works with VitePress, SAP and Visual Studio Code. The repository describes itself as: Learn how to build a developer-centric SAP HANA command line tool, particularly designed to be used when performing SAP HANA development in non-SAP tooling (for example from VS… The licence is Apache-2.0.
When your agent uses it
- Generate-command-docs
- Enhance-command-docs
- Sidebar generation
- VitePress build checks
Example prompts
- “/docs-automation”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify the docs scope (all commands vs specific folders).
- Run the relevant automation scripts
- Spot-check updated markdown for formatting and taxonomy alignment.
- If needed, run vitepress build docs to validate the output.
What it can do on your machine
Read from SKILL.md and the folder at commit 26cbc4e. 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
Docs Automation loads about 344 tokens when it runs, and up to ~535 if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 110 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 SAP-samples/hana-developer-cli-tool-example at commit 26cbc4e, republished under its Apache-2.0 licence (© SAP-samples). 110 words, ~344 tokens.
Download SKILL.mdSave it as
.claude/skills/docs-automation/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- docs-automation
- description
- Automate docs updates and command documentation generation. Use for generate-command-docs, enhance-command-docs, sidebar generation, and VitePress build checks.
- argument-hint
- Doc scope + intent (e.g., update command docs for data-sync, regenerate sidebar)
- user-invocable
- true
Docs Automation Skill
Use this skill for documentation generation and maintenance tasks.
When to Use
- Regenerating command documentation in
docs/02-commands/ - Enhancing command docs after generation
- Updating or regenerating the VitePress sidebar
- Validating doc builds and link consistency
Procedure
- Identify the docs scope (all commands vs specific folders).
- Run the relevant automation scripts:
scripts/generate-command-docs.jsscripts/enhance-command-docs.jsscripts/populate-command-docs.jsscripts/generate-sidebar-config.jsorscripts/generate-sidebar-config-fixed.js
- Spot-check updated markdown for formatting and taxonomy alignment.
- If needed, run
vitepress build docsto validate the output.
Notes
- Follow the command documentation instructions for
docs/02-commands/. - Preserve existing category names and ordering in the sidebar.
- Use existing scripts rather than manual edits whenever possible.
References
© SAP-samples, Apache-2.0. 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 (references) in .github/skills/docs-automation of SAP-samples/hana-developer-cli-tool-example.
- SKILL.md
- references/checklist.md
Open the folder on GitHubat commit 26cbc4e
Compare with similar skills
Docs Automation 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 |
|---|---|---|---|---|---|---|
| Docs Automation this skillSAP-samples/hana-developer-cli-tool-example | 114 | — | ~344 | Automated safety check: Pass | Apache-2.0 | |
| Oryxos Admin UIoryx-labs/oryxos | 186 | — | ~913 | Automated safety check: Pass | Apache-2.0 | |
| Sync Docseslint-config/airbnb-extended | 129 | — | ~878 | Automated safety check: Pass | MIT | |
| Update Docs PRopentiny/genui-sdk | 171 | — | ~819 | Automated safety check: Pass | MIT | |
| Sake Docskattouf/Sake | 116 | — | ~778 | Automated safety check: Pass | MIT | |
| Markdown Integrationlive-codes/livecodes | 1.5k | — | ~2k | Automated safety check: Pass | MIT |
Similar skills
Sync Docs
eslint-config/airbnb-extended
Check that the VitePress docs in docs/ match the real exports, rules and CLI options in the code, then fix any drift.
Update Docs PR
opentiny/genui-sdk
After publishing a new @opentiny/genui-sdk package, update opentiny/docs (submodule, genui package versions, VitePress sidebar) and opentiny/opentiny.design (submodule commit only), then open PRs on…
Sake Docs
kattouf/Sake
A skill your agent uses when writing or updating Sake documentation — VitePress site structure, existing pages, how to add new docs, documentation conventions.
Markdown Integration
live-codes/livecodes
Integrate LiveCodes with documentation sites using remark-livecodes, markdown-it-livecodes, gatsby-remark-livecodes, or marked-livecodes for Docusaurus, Astro, VitePress, Next.js, and Storybook.
- Official
Wiki Vitepress
microsoft/skills
Packages generated wiki Markdown into a VitePress static site with dark theme, dark-mode Mermaid diagrams with click-to-zoom, and production build output.
More from SAP-samples/hana-developer-cli-tool-example
CLI Command Development
SAP-samples/hana-developer-cli-tool-example
Create or update CLI commands, routes, utilities, and tests in this repo.
MCP Server Workflows
SAP-samples/hana-developer-cli-tool-example
Create or update MCP server tools, JSON-RPC handlers, and registrations.
Related
Works with
Categories
Questions about Docs Automation
What does Docs Automation do?
Automate docs updates and command documentation generation. An agent skill from SAP-samples/hana-developer-cli-tool-example. Docs Automation is an agent skill from SAP-samples/hana-developer-cli-tool-example. Automate docs updates and command documentation generation.
When should I use Docs Automation?
Docs Automation fits situations like: generate-command-docs; enhance-command-docs; sidebar generation; vitePress build checks.
How do I install Docs Automation in Claude Code?
Run `npx skills add SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a claude-code`. Or copy the skill folder (.github/skills/docs-automation in SAP-samples/hana-developer-cli-tool-example) into .claude/skills/docs-automation in your project. Claude Code loads it when a task matches its description.
How do I install Docs Automation in Codex?
Run `npx skills add SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a codex`. Or copy the skill folder (.github/skills/docs-automation in SAP-samples/hana-developer-cli-tool-example) into .agents/skills/docs-automation in your project. Codex loads it when a task matches its description.
Can I use Docs Automation 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 SAP-samples/hana-developer-cli-tool-example --skill docs-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-automation, .gemini/skills/docs-automation, .github/skills/docs-automation and .opencode/skills/docs-automation in your project.
What does Docs Automation need to run?
SKILL.md names no scripts, command-line tools or credentials: Docs Automation is instructions for the agent only.
Does Docs Automation 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 Docs Automation 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 Docs Automation use?
Docs Automation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Docs Automation use?
About 344 tokens (SKILL.md is roughly 1.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 191 tokens, read only when the agent opens those files.
What are the alternatives to Docs Automation?
Skills that share tags, products or a category with Docs Automation: Oryxos Admin UI (oryx-labs/oryxos, 186 stars), Sync Docs (eslint-config/airbnb-extended, 129 stars), Update Docs PR (opentiny/genui-sdk, 171 stars) and Sake Docs (kattouf/Sake, 116 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Docs Automation?
SAP-samples (a GitHub organization) maintains it in SAP-samples/hana-developer-cli-tool-example, which has 114 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.
Source: SAP-samples/hana-developer-cli-tool-example on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.