Galileo Agent Control Setup
SkillAI & models"Use when the user asks to govern runtime agent behavior with Agent Control and wire control events to
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Galileo Agent Control Setup skill
What this skill tells your AI
The instructions your AI receives, as published by chambear2809/splunk-cisco-skills in skills/galileo-agent-control-setup/SKILL.md and read by ahel’s review.
Prerequisites
| Tool or access | Purpose | Verify |
|---|---|---|
| Bash and Python 3 | Run bundled setup and validation helpers | bash --version && python3 --version |
| Required product/platform access | Inspect or configure the selected target | Complete the documented preflight |
| Credential files for live modes | Keep secrets out of chat | Verify paths only |
Workflow Overview
┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘ └───────────────┘ └───────────────┘ └─────────────────┘
When to Activate
- Govern runtime agent behavior with Agent Control and wire control events to Splunk Platform or Splunk Observability Cloud.
- Preview and review the galileo agent control setup workflow before any live apply phase.
- Diagnose failed prerequisites, generated assets, configuration, or validation evidence.
Scope
Follow the documented read-only or render-first path whenever it is available. This skill does not imply permission to mutate live systems. Require explicit apply flags, protected credentials, and operator review for state changes.
Examples
Inspect the supported setup modes before selecting one:
bash skills/galileo-agent-control-setup/scripts/setup.sh --help
Expected output: usage, supported modes, and required arguments are displayed without changing the target environment.
Inspect validation modes before running completion checks:
bash skills/galileo-agent-control-setup/scripts/validate.sh --help
Expected output: offline, live, and completion options are displayed when the skill supports them; help exits without mutation.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Preflight fails | A required tool or access path is missing | Resolve it before rendering or applying |
| Rendered assets are incomplete | Required non-secret inputs are absent | Complete intake and render again |
| Apply is blocked | Review, credentials, or explicit acceptance is missing | Use the documented handoff |
| Validation is incomplete | Live evidence is unavailable | Record the gap and keep completion open |
This skill renders Agent Control runtime assets without exposing secret values.
It owns external/open-source runtime and sink examples, and delegates Splunk-side
HEC, OTel Collector, dashboard, and detector work to the existing Splunk skills.
Use galileo-on-prem-agent-control-setup for Galileo's packaged Kubernetes
chart, database migrations, service, feature flag, routing, or UI integration.
Required Intake
Before rendering, validating, doctoring, probing, or applying this skill, ask
the user for the Galileo instance console URL and record the exact value they
provide, for example https://console.demo-v2.galileocloud.io/. Do not assume
the default Galileo Cloud URL unless the user explicitly confirms it.
Pass the URL as --galileo-console-url "$GALILEO_CONSOLE_URL" or set
galileo.console_url in the spec. This URL is separate from
--server-url, which points to the standalone Agent Control server.
Use galileo-platform-setup instead when the user is asking about the Galileo
Agent Observability Controls console tab, Log stream control attachment, or
exported control-span evidence. This skill is for external/open-source Agent
Control runtime and server assets.
The July 7, 2026 AI Assistant beta, global dashboards, generic alert webhooks,
experiment groups, and large-dataset batching are Galileo Platform features;
route those requests to galileo-platform-setup. They do not change this
standalone Agent Control server contract.
Supported Paths
- Server readiness: render Docker/external server readiness notes, health endpoint checks, and auth expectations.
- Auth templates: render file-backed Agent Control API and admin key env templates.
- Controls: render starter policy templates for observe-first and deny controls.
- Runtime snippets: render Python
@control()and TypeScript skeleton snippets for protected agents. - Event sinks: render the built-in OTel sink env and a custom Splunk HEC event sink.
- Splunk handoffs:
- HEC token/service:
splunk-hec-service-setup - Splunk OTel Collector:
splunk-observability-otel-collector-setup - Dashboards:
splunk-observability-dashboard-builder - Detectors/native ops:
splunk-observability-native-ops
- HEC token/service:
Safe First Command
bash skills/galileo-agent-control-setup/scripts/setup.sh --help
Primary Workflow
Render default artifacts first:
bash skills/galileo-agent-control-setup/scripts/setup.sh \
--render \
--galileo-console-url "$GALILEO_CONSOLE_URL" \
--output-dir galileo-agent-control-rendered
Render from the intake template:
bash skills/galileo-agent-control-setup/scripts/setup.sh \
--render \
--validate \
--galileo-console-url "$GALILEO_CONSOLE_URL" \
--spec skills/galileo-agent-control-setup/template.example \
--output-dir galileo-agent-control-rendered
Apply only explicit sections:
bash skills/galileo-agent-control-setup/scripts/setup.sh \
--apply splunk-hec,otel-collector,dashboards,detectors \
--galileo-console-url "$GALILEO_CONSOLE_URL" \
--realm "$SPLUNK_O11Y_REALM" \
--splunk-hec-url "$SPLUNK_HEC_URL" \
--splunk-hec-token-file /tmp/splunk_hec_token \
--o11y-token-file /tmp/splunk_o11y_token
CLI Contract
setup.sh supports --render, --validate, --doctor, --apply SECTIONS,
--dry-run, and --json.
Apply sections:
serverauthcontrolspython-runtimetypescript-runtimeotel-sinksplunk-sinksplunk-hecotel-collectordashboardsdetectors
Secret Handling
Use file-based flags only:
--agent-control-api-key-file--agent-control-admin-key-file--splunk-hec-token-file--o11y-token-file
Never pass token values on the command line or in chat. Direct token/password
flags such as --agent-control-api-key, --agent-control-admin-key,
--splunk-hec-token, --o11y-token, --token, --api-key, --password, and
--authorization are rejected.
Because Agent Control and HEC requests carry credentials, their URLs must not
embed user information. --server-url accepts only an HTTP(S) origin (no path,
query, or fragment), and --splunk-hec-url accepts an origin or the exact
/services/collector[/event] path. Both require HTTPS outside loopback; the
renderer normalizes the HEC destination to /services/collector/event.
Validation
bash skills/galileo-agent-control-setup/scripts/validate.sh \
--output-dir galileo-agent-control-rendered
For code validation:
python3 -m py_compile \
skills/galileo-agent-control-setup/scripts/render_assets.py
See reference.md for server, control, sink, and Splunk handoff notes.
Signals
- GitHub stars
- 37
- Forks
- 8
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
galileo-agent-control-setup- Source
- github.com/chambear2809/splunk-cisco-skills