Agent skill · Code Review & Quality

jules

Delegate coding tasks to Google Jules AI agent for asynchronous execution. Use when user says: 'have Jules fix', 'delegate to Jules', 'send to Jules', 'ask Jules to', 'check Jules sessions', 'pull Jules results', 'jules add tests', 'jules add docs', 'jules review pr'. Handles: bug fixes, documentation, features, tests, refactoring, code reviews. Works with GitHub repos, creates PRs.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill jules --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Version: 1.0
Declared author: sanjay3290
Path: skills/agent/jules/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Jules Task Delegation Delegate coding tasks to Google's Jules AI agent on GitHub repositories. ## Environment Variables | Variable | Required | Description | |----------|----------|-------------| | `JULES_API_KEY` | For API auth | API key from [jules.google.com/settings](https://jules.google.com/settings) | ## Setup (Run Before First Command) Two auth paths are available. Use **Path 1** for interactive use, **Path 2** for headless/agent use. ### Path 1: CLI (Interactive) #### 1. Install CLI ```bash which jules || npm install -g @google/jules ``` #### 2. Check Auth ```bash jules remote list --repo ``` If fails → tell user to run `jules login` (or `--no-launch-browser` for headless) ### Path 2: API Key (Headless / Agent Use) #### 1. Get API Key Get key from [jules.google.com/settings](https://jules.google.com/settings) (3-key limit per account). #### 2. Set Environment Variable ```bash export JULES_API_KEY="your-api-key" ``` #### 3. Verify ```bash curl -s -H "x-goog-api-key: $JULES_API_KEY" \ "https://jules.googleapis.com/v1alpha/sessions?pageSize=1" | head -20 ``` ### Common Setup (Both Paths) #### Auto-Detect Repo ```bash git remote get-url origin 2>/dev/null | sed -E 's#.*(githu

What's inside
Steps it walks through
  1. Environment Variables
  2. Setup (Run Before First Command)
  3. Path 1: CLI (Interactive)
  4. Path 2: API Key (Headless / Agent Use)
  5. Common Setup (Both Paths)
  6. Commands (CLI)
  7. Create Tasks
  8. Monitor
  9. Retrieve Results
  10. Latest Session Shortcut
  11. Commands (API)
  12. Create a Task
  13. List Sessions
  14. Get Session Status
Ships with 1 file
  • metadata.json
Commands it runs
which jules || npm install -g @google/jules
jules remote list --repo
export JULES_API_KEY="your-api-key"
curl -s -H "x-goog-api-key: $JULES_API_KEY" \
git remote get-url origin 2>/dev/null | sed -E 's#.*(github\.com)[/:]([^/]+/[^/.]+)(\.git)?#\2#'
jules new "Fix auth bug"                                   # Auto-detected repo
jules new --repo owner/repo "Add unit tests"               # Specific repo
jules new --repo owner/repo --parallel 3 "Implement X"     # Parallel sessions
cat task.md | jules new --repo owner/repo                  # From stdin
jules remote list --session    # All sessions
More from claude-skill-registry
All skills →
About this skill
What does the jules skill do?

Delegate coding tasks to Google Jules AI agent for asynchronous execution. Use when user says: 'have Jules fix', 'delegate to Jules', 'send to Jules', 'ask Jules to', 'check Jules sessions', 'pull Jules results', 'jules add tests', 'jules add docs', 'jules review pr'. Handles: bug fixes, documentation, features, tests, refactoring, code reviews. Works with GitHub repos, creates PRs.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill jules --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going