"Use when the user asks to install, configure, operate, or validate Lookup File Editing. Render and
Scanned 9/9/2026
Install to Claude Code
npx -y skills add chambear2809/splunk-cisco-skills --skill splunk-lookup-file-editing-setup --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Splunk Lookup File Editing Setup?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/chambear2809-splunk-lookup-file-editing-setup)More formats (shields.io, HTML) on the badges page.
---
name: splunk-lookup-file-editing-setup
description: "Use when the user asks to install, configure, operate, or validate Lookup File Editing. Render and
validate Splunk App for Lookup File Editing readiness, including install planning, CSV and KV Store
lookup inventory checks, SHC allowRestReplay backup-replication runbook, app health checks, lookup
ownership guidance, and handoffs to knowledge-object and KV Store skills."
compatibility: "Splunk Cloud Platform 10.5.2605: conditional. Follow documented package, entitlement, topology, and customer-managed runtime guardrails; self-managed paths remain on the public 10.4 baseline."
metadata:
splunk_cloud_10_5: "conditional"
compatibility_verified: "2026-08-20"
---
# Splunk Lookup File Editing Setup
## 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
```text
┌───────────┐ ┌───────────────┐ ┌───────────────┐ ┌─────────────────┐
│ 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
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
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
| 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 |
## 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](../shared/ta_completion_gate.md). 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
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
bash skills/splunk-lookup-file-editing-setup/scripts/setup.sh --all \
--dry-run --json
```
Install and validate:
```bash
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
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.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!