Run any Skill in Manus with one click

jules-config

Stars0

Forks0

UpdatedJuly 1, 2026 at 12:09

Automatically configure any repository for Google Jules cloud VM execution, wrapping 1Password CLI dependencies safely, generating automated environment bootstrap scripts for databases (Postgres/MySQL) and runtimes, and writing the required documentation to AGENTS.md.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

delorenj

delorenj/00_ceiling

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

2 files

SKILL.md

readonly

name	jules-config
description	Automatically configure any repository for Google Jules cloud VM execution, wrapping 1Password CLI dependencies safely, generating automated environment bootstrap scripts for databases (Postgres/MySQL) and runtimes, and writing the required documentation to AGENTS.md.

Google Jules Project Configuration

Optimize any repository to run successfully and securely inside Google Jules's isolated cloud VM.

Operating Principles

Graceful Fallbacks: Cloud VM sandboxes lack access to host-specific tools (like 1Password CLI op authentication). Always wrap credential-pulling tasks with fallback options (like using .env.example or local defaults).
Service Port Invariance: Local Postgres in a VM runs on standard port 5432 instead of host-mapped Docker ports (like 5439). Ensure database URLs are adjusted for native services.
Self-Documenting: Maintain a ## Jules Setup section in AGENTS.md (or README.md) detailing the setup script and VM snapshot configuration.

Quick Navigation

Action	Command / File
Configure repository for Jules	`python3 /home/delorenj/.gemini/config/skills/jules-config/scripts/jules-init.py`
View/Edit Jules VM setup script	`scripts/jules-setup.sh`
Documented VM setup process	`AGENTS.md` or `README.md`

How to Run

To optimally configure the current repository, execute the following command from the root:

python3 /home/delorenj/.gemini/config/skills/jules-config/scripts/jules-init.py

This utility automatically:

Detects language runtime (Bun, Node, Python).
Detects database dependencies (PostgreSQL, MySQL).
Patches standard mise.toml hooks so op (1Password) doesn't hang.
Generates an executable scripts/jules-setup.sh that boots local services, provisions users/DBs, installs packages, runs migrations/seeds, and executes unit tests.
Documents the setup in AGENTS.md so the Jules agent inherits these VM bootstrap instructions.

Out of Scope

This skill does NOT cover:

Deploying to production hosting: Use docker compose, Traefik, or cloud hosting deployment scripts.
Tiller sheet synchronization credentials: Jules does not run Google service account credentials; it runs against the mock database seeded by seed.ts.
Hindsight bank configuration: Hindsight memory banks are configured via the Hindsight CLI separately.

More from this repository

same repository

civilwar-letterifier

delorenj/00_ceiling

Rewrite any text as a solemn, slightly absurd 19th-century Civil War field dispatch (Ken Burns documentary voice), then optionally turn it into a multimodal video — period narration via ElevenLabs, the letter in fancy script on aged parchment, a mournful music bed, and a slow Ken Burns pan/zoom of the letter being read. Use when the user types /civilwar, asks to "civil-war-ify" or "Ken Burns" some text, or asks for a documentary-style letter video.

2026-07-070

33god-ecosystem

delorenj/00_ceiling

Router / skill-set hub for the 33GOD / DeLoNET project platform. Routes user intent to the right member skill: project bootstrap (33god-projects), pjangler implementation (pjangler-dev), agent hook/skill fan-out (agent-config-fanout), Hermes fleet operations (hermes-fleet-operations), Plane ticket operations (managing-tickets-and-tasks-in-plane), Bloodbank events (bloodbank-integration), host conventions (delonet-conventions), versioning (mise-versioning), task authoring (mise-tasks), and memory (hindsight). Use when the request spans multiple 33GOD components or when you are unsure which member skill owns a 33GOD task. Triggers: 33god, 33GOD, DeLoNET, project platform, pjangler, CommonProject, Hermes, Plane, Bloodbank, agent hooks, skill fan-out, fleet, project bootstrap. Does NOT implement procedures; it loads the member skill that does.

2026-07-070

33god-projects

delorenj/00_ceiling

Create, wire, and maintain 33god/DeLoNET projects. Covers pjangler/CommonProject bootstrap, repo-local `.project.json`, Hermes PM and scrum-master/Ticket Sentinel provisioning requests, mise/.env.op, BMAD, Hindsight/Bloodbank hook wiring, and project-scoped hook + skill fan-out adoption. Use when running `pjangler init`, `pjangler hermes-agent`, or `mise run init-project`; adding PM/sentinel agents; wiring mise/op inject; installing BMAD; configuring hooks; or adopting `.agents/local.json`, `defer_to_global`, and `hooks.master.json`. Do NOT use for developing pjangler (pjangler-dev), generic fan-out mechanics (agent-config-fanout), fleet updates/backfills (hermes-fleet-operations), live Plane issues, Bloodbank schemas, or host conventions.

2026-07-070

agent-config-fanout

delorenj/00_ceiling

Keep one hand-edited master config and generate per-agent CLI configs from it. Covers SSOT fan-out for agent hooks and skills: master-to-dialect propagation, ambiguity lock files, drift checks, and the Bloodbank services/agent-hooks reference implementation. Use for hooks.master.json, hooks.mappings.lock.json, generated-config drift, fan-out, SSOT, agent hooks, defer_to_global, .agents/local.json, sync.py, project-scoped hooks, skill fan-out, and new agent CLI dialects. Do NOT use for using pjangler to create projects or adoption checklists (33god-projects), event schemas or Bloodbank topology (bloodbank-integration), versioning (mise-versioning), or single-target config.

2026-07-070

bloodbank-integration

delorenj/00_ceiling

Integrate services or agent harnesses with the 33GOD Bloodbank event bus. Covers schemas in Bloodbank schemas/ and docs/event-naming.md, producing events (NATS preferred; Dapr, HTTP /publish, hookd_bridge alternatives), consuming events (NATS, Dapr, FastStream, event-toaster), and agent hook wiring. Use for event publish/consume, authoring schemas, integrating harnesses (Claude Code, Copilot CLI, OpenCode, Cursor, Aider, Codex CLI), or debugging missing envelopes. Triggers: bloodbank, event bus, publish, subscribe, NATS subject, holyfields legacy, CloudEvents, hookd, event-toaster, ntfy.delo.sh/bloodbank, agent.session.started, agent.tool.invoked, command.{agent}.{action}. Skip for generic brokers, n8n, hindsight memory, or non-event-bus 33GOD.

2026-07-070

hermes-fleet-operations

delorenj/00_ceiling

Operate and maintain the Hermes agent fleet: shared install, ~/.hermes/fleet.env, ~/.hermes/config.yaml, ~/.hermes/agents-registry.yaml, hermes-agent-template, role profiles and inherited config, runtime repo provisioning, systemd user units, fleet self-checks, template defaults, and PM/template backfills. Use when updating Hermes core, changing fleet defaults, provisioning agents, debugging fleet-wide MCP failures, running a Hermes fleet self-check, or propagating template changes to existing PM agents. Triggers: Hermes fleet, hermes-agent-template, ~/.hermes/fleet.env, ~/.hermes/config.yaml, ~/.hermes/agents-registry.yaml, inherited profile, fleet self-check, systemd hermes-*, template backfill, runtime repo provisioning. Do NOT use for: project bootstrap decisions or repo-local agent requests (→ 33god-projects); Plane ticket operations (→ managing-tickets-and-tasks-in-plane); Bloodbank event contracts (→ bloodbank-integration); generic SSOT config fan-out mechanics (→ agent-config-fanout).

2026-07-070

name	jules-config
description	Automatically configure any repository for Google Jules cloud VM execution, wrapping 1Password CLI dependencies safely, generating automated environment bootstrap scripts for databases (Postgres/MySQL) and runtimes, and writing the required documentation to AGENTS.md.

Google Jules Project Configuration

Optimize any repository to run successfully and securely inside Google Jules's isolated cloud VM.

Operating Principles

Graceful Fallbacks: Cloud VM sandboxes lack access to host-specific tools (like 1Password CLI op authentication). Always wrap credential-pulling tasks with fallback options (like using .env.example or local defaults).
Service Port Invariance: Local Postgres in a VM runs on standard port 5432 instead of host-mapped Docker ports (like 5439). Ensure database URLs are adjusted for native services.
Self-Documenting: Maintain a ## Jules Setup section in AGENTS.md (or README.md) detailing the setup script and VM snapshot configuration.

Quick Navigation

Action	Command / File
Configure repository for Jules	`python3 /home/delorenj/.gemini/config/skills/jules-config/scripts/jules-init.py`
View/Edit Jules VM setup script	`scripts/jules-setup.sh`
Documented VM setup process	`AGENTS.md` or `README.md`

How to Run

To optimally configure the current repository, execute the following command from the root:

python3 /home/delorenj/.gemini/config/skills/jules-config/scripts/jules-init.py

This utility automatically:

Detects language runtime (Bun, Node, Python).
Detects database dependencies (PostgreSQL, MySQL).
Patches standard mise.toml hooks so op (1Password) doesn't hang.
Generates an executable scripts/jules-setup.sh that boots local services, provisions users/DBs, installs packages, runs migrations/seeds, and executes unit tests.
Documents the setup in AGENTS.md so the Jules agent inherits these VM bootstrap instructions.

Out of Scope

This skill does NOT cover:

Deploying to production hosting: Use docker compose, Traefik, or cloud hosting deployment scripts.
Tiller sheet synchronization credentials: Jules does not run Google service account credentials; it runs against the mock database seeded by seed.ts.
Hindsight bank configuration: Hindsight memory banks are configured via the Hindsight CLI separately.