Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Interface with Google's Jules Tools CLI to manage AI coding sessions.
Interface with Google's Jules Tools CLI to manage AI coding sessions.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
This skill allows the AI agent to interface with the Jules Tools CLI to manage Google's Jules AI coding sessions. With this skill, the agent can start new coding sessions, list active sessions, and retrieve results directly from the terminal.
Before using any Jules commands, ensure the jules CLI is installed and authenticated.
Check if jules is installed by running: jules --version If the command is not found, install it using npm: npm install -g @google/jules Note: Installation might require sudo permissions depending on the system configuration. If npm install -g fails due to permissions, try sudo npm install -g @google/jules or ask the user for assistance.
The agent must be authenticated to interact with Jules. To authenticate, run: jules login This command will open a browser window for the user to sign in with their Google account. If the agent is running in a headless environment, guide the user to perform this step on their local machine or provide alternative authentication methods if available (refer to jules login --help). To verify authentication or log out, use: jules logout
The primary command for interacting with Jules is jules remote.
To see all active or past coding sessions: jules remote list --session To list connected repositories: jules remote list --repo
To start a new coding session (task) for Jules: jules remote new --repo <repo_name> --session "<task_description>" <repo_name>: The repository name (e.g., torvalds/linux) or . for the current directory's repo. <task_description>: A clear description of what Jules should do (e.g., "Fix the bug in the login handler"). Example: jules remote new --repo . --session "Add a new test case for the user profile component" You can also start multiple parallel sessions: jules remote new --repo . --session "Refactor the database schema" --parallel 2
Once a session is complete, you can pull the results (code changes): jules remote pull --session <session_id> <session_id>: The ID of the session you want to pull (obtained from jules remote list).
For more information on any command: jules --help jules remote --help
Command not found: Ensure jules is in the system PATH after installation. You may need to restart the shell or source the profile. Authentication errors: Try running jules logout and then jules login again. Network issues: Ensure the agent has internet access to reach Google's servers.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.