jules

jules-skills

A Claude Code plugin that wraps the Jules API (v1alpha) as five focused slash commands. Lets you drive Jules — Google's autonomous coding agent — without leaving your terminal.

/jules:setup        # one-time API-key setup
/jules:sources      # list connected GitHub repos
/jules:start        # create a new Jules session (prompt + repo + branch)
/jules:sessions     # list / get / sendMessage / approvePlan
/jules:activities   # plan, diffs, bash output, failure reasons

Why a plugin

Toggle the whole jules:* namespace on or off as one unit via /plugin enable|disable. Disabling reclaims the description tokens of all five commands at once.

Install

In a Claude Code session:

/plugin marketplace add dr-data/jules-skills
/plugin install jules@jules-skills

That's it. The five /jules:* commands are now available.

To verify they loaded, type / and look for jules:setup, jules:sources, jules:start, jules:sessions, jules:activities.

API-key handling

The plugin never stores the key, never reads it into Claude's context.

1. Generate a key at https://jules.google.com/settings#api (max 3 per Google account).
2. Run /jules:setup and paste it when asked, or set it up yourself:

   mkdir -p ~/.config/jules && chmod 700 ~/.config/jules
   printf %s 'YOUR_KEY' > ~/.config/jules/api_key
   chmod 600 ~/.config/jules/api_key
   

3. Alternatively export JULES_API_KEY=... in your shell — the plugin checks the file first, falls back to the env var.

Each command's curl invocation pulls the key at runtime with:

H="X-Goog-Api-Key: $(cat ~/.config/jules/api_key 2>/dev/null || printf %s "$JULES_API_KEY")"

So the key lives on disk only, never inside the loaded skill markdown.

Typical workflow

/jules:sources                                     # find your repo's source id
/jules:start                                       # describe the task; pick source + branch
   # → returns a session id and a jules.google.com URL
/jules:activities <SID>                            # watch progress; see the plan
/jules:sessions approve <SID>                      # if requirePlanApproval=true
/jules:activities <SID>                            # read generated diff / bash output
/jules:sessions send <SID> "also update the README" # follow-up

For sessions started with automationMode: AUTO_CREATE_PR, Jules opens the PR itself; the URL appears in outputs[].pullRequest.url on the session resource.

Toggle on / off

/plugin disable jules@jules-skills
/plugin enable  jules@jules-skills

Or use the /plugin UI.

Uninstall

/plugin uninstall jules@jules-skills
/plugin marketplace remove jules-skills

The on-disk key at ~/.config/jules/api_key is not touched by uninstall — remove it manually with rm ~/.config/jules/api_key if you want it gone.

Repo layout

jules-skills/
├── .claude-plugin/
│   ├── marketplace.json   # marketplace name: jules-skills
│   └── plugin.json        # plugin name: jules
├── commands/
│   ├── setup.md           → /jules:setup
│   ├── sources.md         → /jules:sources
│   ├── start.md           → /jules:start
│   ├── sessions.md        → /jules:sessions
│   └── activities.md      → /jules:activities
└── README.md

Each commands/*.md is a Claude Code slash-command spec: YAML frontmatter (name, description) plus the procedural body Claude reads when the command fires.

API coverage

Command	Endpoint
/jules:sources	GET /v1alpha/sources, GET /v1alpha/sources/{id}
/jules:start	POST /v1alpha/sessions
/jules:sessions (list/get)	GET /v1alpha/sessions, GET /v1alpha/sessions/{id}
/jules:sessions send	POST /v1alpha/sessions/{id}:sendMessage
/jules:sessions approve	POST /v1alpha/sessions/{id}:approvePlan
/jules:activities	GET /v1alpha/sessions/{id}/activities[/{aid}]

Schemas (Session, SourceContext, Activity, Plan, GitPatch, etc.) are summarised inline in each command file — sourced from the official REST reference.

The Jules API is in alpha; field names may shift. If a request fails after the API moves, re-fetch the reference page and update the relevant commands/*.md.

License

MIT. See plugin.json.

Contributing

PRs welcome. Keep skill bodies focused: only what Claude can't already infer. No real API keys, no PII, no absolute home-directory paths in committed files.