Splunk Lookup File Editing Setup

SkillFiles & storage

"Use when the user asks to install, configure, operate, or validate Lookup File Editing. Render and

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Splunk Lookup File Editing Setup skill

What this skill tells your AI

The instructions your AI receives, as published by chambear2809/splunk-cisco-skills in skills/splunk-lookup-file-editing-setup/SKILL.md and read by ahel’s review.

Prerequisites

Tool or accessPurposeVerify
Bash and Python 3Run bundled setup and validation helpersbash --version && python3 --version
Required product/platform accessInspect or configure the selected targetComplete the documented preflight
Credential files for live modesKeep secrets out of chatVerify paths only

Workflow Overview

┌───────────┐   ┌───────────────┐   ┌───────────────┐   ┌─────────────────┐
│ Preflight │ → │ Render/review │ → │ Apply/handoff │ → │ Validate evidence │
└───────────┘   └───────────────┘   └───────────────┘   └─────────────────┘

When to Activate

  • Install, configure, operate, or validate Lookup File Editing.
  • Preview and review the splunk lookup file editing 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/splunk-lookup-file-editing-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/splunk-lookup-file-editing-setup/scripts/validate.sh --help

Expected output: offline, live, and completion options are displayed when the skill supports them; help exits without mutation.

Troubleshooting

IssueCauseResolution
Preflight failsA required tool or access path is missingResolve it before rendering or applying
Rendered assets are incompleteRequired non-secret inputs are absentComplete intake and render again
Apply is blockedReview, credentials, or explicit acceptance is missingUse the documented handoff
Validation is incompleteLive evidence is unavailableRecord the gap and keep completion open

Shared add-on completion gate

Whenever this workflow installs, configures, or hands off the Lookup File Editing app or a dependency, follow the shared completion gate. Package delivery alone is not success; validate applicable lookup operations and shipped views, or record explicit evidence that no dashboards ship.

Render-first workflow for the Splunk App for Lookup File Editing. It emits install readiness, CSV/KV Store lookup inventory SPL, SHC backup-replication notes, app health checks, and handoffs to knowledge-object and KV Store skills. It does not edit lookup files or app configuration.

Workflow

bash skills/splunk-lookup-file-editing-setup/scripts/setup.sh --render \
  --platform auto --lookup-scope both --shc-mode true

Execute

Preview package install and validation:

bash skills/splunk-lookup-file-editing-setup/scripts/setup.sh --all \
  --dry-run --json

Install and validate:

bash skills/splunk-lookup-file-editing-setup/scripts/setup.sh --all --live

Lookup contents, ACL updates, SHC app config, and KV Store operations remain delegated to knowledge-object and KV Store workflows.

bash skills/splunk-lookup-file-editing-setup/scripts/validate.sh \
  --rendered-dir splunk-lookup-file-editing-rendered --live

See reference.md for SHC and lookup-governance guardrails.

Signals

GitHub stars
37
Forks
8
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
splunk-lookup-file-editing-setup
Source
github.com/chambear2809/splunk-cisco-skills