createcli
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Other
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- Python
- Permissions
-
- Read-only
- Write / modify
- Shell exec
- Env read
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: createcli
description: | Use when this capability is needed. | Task | Stack | Reason | |------|-------|--------| | File…
category: other
runtime: Python
---
# createcli output preview
## PART A: Task fit
- Use case: | Use when this capability is needed. | Task | Stack | Reason | |------|-------|--------| | Files, glob, regex, JSON piping | bash | Fastest if < 50 lines | | Anything complex, types, JSON handling | TypeScript (bun) | Default | | Data-heavy operations, ML libraries | Python (uv) | Library access | runs entirely locally; runs on Python. Works with Claude ….
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Stack choice / Anatomy (TypeScript default) / Anatomy (bash)” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “| Use when this capability is needed. | Task | Stack | Reason | |------|-------|--------| | Files, glob, regex, JSON piping | bash | Fastest if < 50 lines | | Anything complex, types, JSON handling | TypeScript (bun) | Default | | Data-heavy operations, ML libraries | Python (uv) | Library access | runs entirely locally; runs on Python. Works with Claude …”.
- **02** When the source has headings, the agent prioritizes “Stack choice / Anatomy (TypeScript default) / Anatomy (bash)” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files, run shell commands, read environment variables.
Start with a small task and check whether the result follows “Stack choice / Anatomy (TypeScript default) / Anatomy (bash)”. Inspect diffs, logs, previews, or tests before expanding scope.
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: createcli
description: | Use when this capability is needed. | Task | Stack | Reason | |------|-------|--------| | File…
category: other
source: tomevault-io/skills-registry
---
# createcli
## When to use
- | Use when this capability is needed. | Task | Stack | Reason | |------|-------|--------| | Files, glob, regex, JSON p…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Stack choice / Anatomy (TypeScript default) / Anatomy (bash)” and keep inference separate from source facts.
- read files, write/modify files, run shell commands, read environment variables; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "createcli" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Stack choice / Anatomy (TypeScript default) / Anatomy (bash)
rules -> SKILL.md triggers / order / output contract
runtime -> Python | read files, write/modify files, run shell commands, read environment variables | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
} CreateCLI
Role: quick CLI authoring for ~/.claude/scripts/.
Stack choice
| Task | Stack | Reason |
|---|---|---|
| Files, glob, regex, JSON piping | bash | Fastest if < 50 lines |
| Anything complex, types, JSON handling | TypeScript (bun) | Default |
| Data-heavy operations, ML libraries | Python (uv) | Library access |
Anatomy (TypeScript default)
#!/usr/bin/env bun
/**
* [scriptname] — [short description]
*
* Usage: [scriptname] [args] [flags]
*
* Created: 2026-MM-DD via createcli skill
*/
import { parseArgs } from 'util';
const { values, positionals } = parseArgs({
args: process.argv.slice(2),
options: {
'dry-run': { type: 'boolean', default: true }, // destructive: default ON
'verbose': { type: 'boolean', short: 'v' },
'help': { type: 'boolean', short: 'h' },
},
allowPositionals: true,
});
if (values.help) {
console.log(`[scriptname] — [description]
Usage:
[scriptname] [args]
Flags:
--dry-run Show what would happen without doing it (default: ON for destructive)
--verbose More detailed output
--help This text
`);
process.exit(0);
}
// ... core logic
Anatomy (bash)
#!/usr/bin/env bash
set -euo pipefail
usage() {
cat <<EOF
[scriptname] — [description]
Usage: [scriptname] [args]
Flags:
-n, --dry-run Show what would happen
-v, --verbose More detailed output
-h, --help This text
EOF
}
DRY_RUN=true # destructive default
while [[ $# -gt 0 ]]; do
case "$1" in
-n|--dry-run) DRY_RUN=true; shift ;;
--no-dry-run) DRY_RUN=false; shift ;;
-v|--verbose) VERBOSE=true; shift ;;
-h|--help) usage; exit 0 ;;
*) ARGS+=("$1"); shift ;;
esac
done
# core logic
Rules
- Destructive = dry-run default ON. Must use explicit
--no-dry-runto execute. - Log to
~/.claude/logs/[scriptname].jsonlfor an audit trail when relevant (file-modifying, network-fetching, API calls). chmod +xafter Write — exec bit must be set.--helpis mandatory — show it even when no args.- Never hardcode credentials — read from
~/.claude/.env. - Output in markdown if the script produces a text report (not tabular).
Workflow
1. The user describes: "I need a script that [X]"
2. Choose stack (bash/TS/Python) per the table above
3. Create the anatomy template
4. Implement core logic
5. chmod +x ~/.claude/scripts/[scriptname]
6. Test: ./scripts/[scriptname] --help
7. Test: ./scripts/[scriptname] --dry-run [args]
8. Report to user: what the script does + examples
Version history
- v3.0 (2026-05-02): initial public release.
Source: carlheath/ogmios — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review