ClawHub

Jules CLI

v1.0.2

Interact with the Jules CLI to manage asynchronous coding sessions. Use this skill sparingly for complex, isolated tasks that benefit from a remote VM.

⭐ 1· 2.1k·0 current·0 all-time
byAndrew Stafford@ajstafford
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name/description match the SKILL.md: it instructs how to run the `jules` CLI and uses `python3` for lightweight parsing. It does not request unrelated binaries, credentials, or config paths.
ℹ
Instruction Scope
The runtime instructions stay on-topic (creating/listing/pulling remote sessions) and include explicit safety rules (input validation, quoting, using env vars, asking user approval before sensitive commands). Note: these safety controls rely on the agent obeying them — the SKILL.md mandates asking user approval before `jules remote new`, `jules remote pull --apply`, and `jules teleport`.
✓
Install Mechanism
No install spec or code files are present (instruction-only). Nothing is downloaded or written to disk by the skill itself.
✓
Credentials
No required environment variables or credentials are declared. The instructions reference HOME and use a transient env var (JULES_SESSION_ID) for safe shell interaction, which is proportionate to the task.
ℹ
Persistence & Privilege
The skill is not forced always-on and does not persist credentials. Model-invocation is allowed (platform default). Because the SKILL.md requires explicit user approval for session-creating/modifying commands, confirm the agent will actually prompt before executing those commands if you want that protection enforced.
Assessment
This skill is an instruction-only guide for using a separate Jules CLI tool; it does not install software or ask for secrets. Before installing/using it: (1) ensure you have a trusted `jules` binary on your system (the skill assumes the CLI is already present), (2) confirm your agent will prompt you for approval before creating or applying remote sessions (the SKILL.md requires this), and (3) avoid sending sensitive data in session descriptions or commands — treat sessions as potentially visible to the remote VM/service. If the publisher later adds an install step (downloading a binary) or starts requesting API keys/credentials, re-evaluate — that would change this assessment.

Like a lobster shell, security has layers — review code before you run it.

latestvk97brrd8vraf2a2p9np9tj4yqs810t4w

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments