Scrapingbee CLI
ScrapingBee/scrapingbee-cli
Fetch and read any web page, search the web, crawl a site, or pull structured data out of pages.
Review or write CLI documentation. An agent skill from CelestoAI/celesto.
Install CLI Docs Guidelines
$ npx skills add CelestoAI/celesto --skill cli-docs-guidelines -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CelestoAI/celesto cli-docs-guidelines --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/CelestoAI/celesto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/cli-docs-guidelines .claude/skills/cli-docs-guidelines && 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 "cli-docs-guidelines" agent skill from https://github.com/CelestoAI/celesto/tree/main/.agents/skills/cli-docs-guidelines into .claude/skills/cli-docs-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-docs-guidelines", 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/CelestoAI/celesto/tree/main/.agents/skills/cli-docs-guidelinesType 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 CelestoAI/celesto --skill cli-docs-guidelines -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CelestoAI/celesto cli-docs-guidelines --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CelestoAI/celesto.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/cli-docs-guidelines .agents/skills/cli-docs-guidelines && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cli-docs-guidelines" agent skill from https://github.com/CelestoAI/celesto/tree/main/.agents/skills/cli-docs-guidelines into .agents/skills/cli-docs-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-docs-guidelines", 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 CelestoAI/celesto --skill cli-docs-guidelines -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CelestoAI/celesto cli-docs-guidelines --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CelestoAI/celesto.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/cli-docs-guidelines .cursor/skills/cli-docs-guidelines && 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 "cli-docs-guidelines" agent skill from https://github.com/CelestoAI/celesto/tree/main/.agents/skills/cli-docs-guidelines into .cursor/skills/cli-docs-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-docs-guidelines", 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/CelestoAI/celesto.git --path .agents/skills/cli-docs-guidelines--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 CelestoAI/celesto --skill cli-docs-guidelines -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CelestoAI/celesto cli-docs-guidelines --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CelestoAI/celesto.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/cli-docs-guidelines .gemini/skills/cli-docs-guidelines && 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 "cli-docs-guidelines" agent skill from https://github.com/CelestoAI/celesto/tree/main/.agents/skills/cli-docs-guidelines into .gemini/skills/cli-docs-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-docs-guidelines", 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 CelestoAI/celesto cli-docs-guidelinesInstalls 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 CelestoAI/celesto --skill cli-docs-guidelines -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CelestoAI/celesto.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/cli-docs-guidelines .github/skills/cli-docs-guidelines && 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 "cli-docs-guidelines" agent skill from https://github.com/CelestoAI/celesto/tree/main/.agents/skills/cli-docs-guidelines into .github/skills/cli-docs-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-docs-guidelines", 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 CelestoAI/celesto --skill cli-docs-guidelines -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CelestoAI/celesto cli-docs-guidelines --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CelestoAI/celesto.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/cli-docs-guidelines .opencode/skills/cli-docs-guidelines && 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 "cli-docs-guidelines" agent skill from https://github.com/CelestoAI/celesto/tree/main/.agents/skills/cli-docs-guidelines into .opencode/skills/cli-docs-guidelines/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-docs-guidelines", 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
cli-docs-guidelines- GitHub stars
- 1k
- Token cost
- ~805 tokens
- SKILL.md length
- 342 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Review or write CLI documentation. An agent skill from CelestoAI/celesto.
- Works in 5 steps: Logical command ordering → Introduce a concept before its flags → Show expected output after commands that… → …
- Asked to write CLI docs
- SKILL.md covers Core Principles, Review Checklist and Output Format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
CLI Docs Guidelines is an agent skill from CelestoAI/celesto. Review or write CLI documentation. Enforces progressive disclosure, logical command ordering, and plain-language explanations. Use when asked to "write CLI docs", "document commands", "review CLI reference", or "update command docs".
Its SKILL.md is about 810 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 Writing & Content, covering Plain language and style rules and Browser automation. The repository describes itself as: Secure and persistent computer for AI agents. The licence is Apache-2.0.
When your agent uses it
- Asked to write CLI docs
- Document commands
- Review CLI reference
- Update command docs
Example prompts
- “write CLI docs”
- “document commands”
- “review CLI reference”
- “/cli-docs-guidelines”
Workflow steps
5 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 ca3885e. 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 (its code samples are bash).
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
CLI Docs Guidelines loads about 805 tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 342 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 CelestoAI/celesto at commit ca3885e, republished under its Apache-2.0 licence (© CelestoAI). 342 words, ~805 tokens.
Download SKILL.mdSave it as
.claude/skills/cli-docs-guidelines/SKILL.md (or your agent's skills folder).- name
- cli-docs-guidelines
- description
- Review or write CLI documentation. Enforces progressive disclosure, logical command ordering, and plain-language explanations. Use when asked to "write CLI docs", "document commands", "review CLI reference", or "update command docs".
- argument-hint
- <file-or-section>
- metadata.author
- Celesto Team
- metadata.version
- 1.0.0
CLI Documentation Guidelines
Review or write CLI docs following these principles. CLI docs serve two audiences: newcomers running their first command, and experienced users scanning for flags.
Core Principles
All README Guidelines apply here. In addition:
1. Logical command ordering
Commands must appear in the order a user would run them. A command should never reference output or state from a command that appears later in the docs.
Wrong — stop appears before the user knows how to list:
celesto sandbox stop <sandbox-name>
celesto sandbox listRight — create, inspect, then destroy:
celesto sandbox create --name my-sandbox
celesto sandbox list
celesto sandbox stop my-sandbox2. Introduce a concept before its flags
Show the base command before showing any flags or subcommands. Each flag is a new concept — don't introduce two flags in the same example unless they always go together.
Wrong — --os and --name are both new:
celesto sandbox create --os debian --name my-debian-sandboxRight — --name first, then a separate example for --os:
# Create a sandbox with a name
celesto sandbox create --name my-sandbox
# Use a different OS image
celesto sandbox create --os debian --name my-debian-sandbox3. Show expected output after commands that produce it
When a command prints a value the user needs (an ID, a URL, a status), show it. The reader should never have to run the command to find out what it returns.
celesto browser start --live
# Session: sess_a1b2c3
# Live view: http://localhost:60804. One topic per section
Don't mix sandbox lifecycle commands with browser session commands in the same section. Each distinct workflow gets its own heading.
5. Flags reference comes after prose explanation
Never lead with a flags table. Explain what the command does in plain language first, then list flags for readers who want to go deeper.
Review Checklist
- Commands appear in the order a user would run them
- Every placeholder (
<sandbox-name>,<session-id>) is introduced by a prior command or clearly labelled as "output from the previous step" - Each code block introduces at most one new flag or subcommand
- Commands that print useful output show that output as a comment
- Conceptually distinct workflows (e.g. sandbox vs. browser) are in separate sections
- Flags/options table, if present, appears after the prose description
- No jargon (SSH, TAP device, CIDR, firecracker, QEMU) without a plain-language explanation on first use
Output Format
For each violation found, output:
Line <N>: [rule violated]
Current: <quote the problematic text>
Fix: <suggested rewrite>Then provide a revised version of any section that has more than one violation.
© CelestoAI, 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
Just SKILL.md in .agents/skills/cli-docs-guidelines of CelestoAI/celesto.
Open the folder on GitHubat commit ca3885e
Compare with similar skills
CLI Docs Guidelines 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 |
|---|---|---|---|---|---|---|
| CLI Docs Guidelines this skillCelestoAI/celesto | 1k | — | ~805 | Automated safety check: Pass | Apache-2.0 | |
| Scrapingbee CLIScrapingBee/scrapingbee-cli | 108 | — | ~3.2k | Automated safety check: Notes | MIT | |
| Aqua Evaluationoracle/accelerated-data-science | 125 | — | ~1.6k | Automated safety check: Pass | UPL-1.0 | |
| Routine From Chatrome-os/rome | 725 | — | ~3.8k | Automated safety check: Pass | MIT | |
| Publish X Articlesugarforever/01coder-agent-skills | 136 | — | ~5k | Automated safety check: Pass | MIT | |
| Shopify Contentjezweb/claude-skills | 1.1k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Aqua Evaluation
oracle/accelerated-data-science
Evaluate LLM model quality using BERTScore, ROUGE, Perplexity, and Text Readability metrics on OCI AI Quick Actions (AQUA).
Routine From Chat
rome-os/rome
Turn a plain-language "do this automatically" request into a routine — either event-triggered ("text me when I get an email from my landlord") or scheduled ("remind me every Friday at 9am").
Publish X Article
sugarforever/01coder-agent-skills
Publishes a Markdown file or URL to the X Articles editor with formatting kept, turning tables, mermaid diagrams and deep headers that X cannot show into images.
Shopify Content
jezweb/claude-skills
Create and manage Shopify pages, blog posts, navigation menus, redirects, and SEO metadata via the Admin API or browser automation.
Workflow Automator
LeoYeAI/openclaw-master-skills
Automate repeatable workflows with WhatsApp/Telegram notifications, Excel/CSV processing, browser automation, and flexible scheduling.
More from CelestoAI/celesto
Readme Guidelines
CelestoAI/celesto
Review or write README content for open-source projects. An agent skill from CelestoAI/celesto.
Related
Questions about CLI Docs Guidelines
What does CLI Docs Guidelines do?
Review or write CLI documentation. An agent skill from CelestoAI/celesto. CLI Docs Guidelines is an agent skill from CelestoAI/celesto. Review or write CLI documentation.
When should I use CLI Docs Guidelines?
CLI Docs Guidelines fits situations like: asked to write CLI docs; document commands; review CLI reference; update command docs.
How do I install CLI Docs Guidelines in Claude Code?
Run `npx skills add CelestoAI/celesto --skill cli-docs-guidelines -a claude-code`. Or copy the skill folder (.agents/skills/cli-docs-guidelines in CelestoAI/celesto) into .claude/skills/cli-docs-guidelines in your project. Claude Code loads it when a task matches its description.
How do I install CLI Docs Guidelines in Codex?
Run `npx skills add CelestoAI/celesto --skill cli-docs-guidelines -a codex`. Or copy the skill folder (.agents/skills/cli-docs-guidelines in CelestoAI/celesto) into .agents/skills/cli-docs-guidelines in your project. Codex loads it when a task matches its description.
Can I use CLI Docs Guidelines 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 CelestoAI/celesto --skill cli-docs-guidelines -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cli-docs-guidelines, .gemini/skills/cli-docs-guidelines, .github/skills/cli-docs-guidelines and .opencode/skills/cli-docs-guidelines in your project.
What does CLI Docs Guidelines need to run?
SKILL.md names no scripts, command-line tools or credentials: CLI Docs Guidelines is instructions for the agent only.
Does CLI Docs Guidelines 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 CLI Docs Guidelines 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 CLI Docs Guidelines use?
CLI Docs Guidelines 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 CLI Docs Guidelines use?
About 805 tokens (SKILL.md is roughly 3.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 CLI Docs Guidelines?
Skills that share tags, products or a category with CLI Docs Guidelines: Scrapingbee CLI (ScrapingBee/scrapingbee-cli, 108 stars), Aqua Evaluation (oracle/accelerated-data-science, 125 stars), Routine From Chat (rome-os/rome, 725 stars) and Publish X Article (sugarforever/01coder-agent-skills, 136 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CLI Docs Guidelines?
CelestoAI (a GitHub organization) maintains it in CelestoAI/celesto, which has 1,016 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 7, 2026.
Source: CelestoAI/celesto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.