Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
A skill your agent uses when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for…
Install Spa Create Config
$ npx skills add splunk/splunk-platform-automator --skill spa-create-config -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install splunk/splunk-platform-automator spa-create-config --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/splunk/splunk-platform-automator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/spa/spa-create-config .claude/skills/spa-create-config && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "spa-create-config" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-create-config into .claude/skills/spa-create-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-create-config", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-create-configType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add splunk/splunk-platform-automator --skill spa-create-config -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install splunk/splunk-platform-automator spa-create-config --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/splunk-platform-automator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/spa/spa-create-config .agents/skills/spa-create-config && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "spa-create-config" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-create-config into .agents/skills/spa-create-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-create-config", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add splunk/splunk-platform-automator --skill spa-create-config -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install splunk/splunk-platform-automator spa-create-config --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/splunk-platform-automator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/spa/spa-create-config .cursor/skills/spa-create-config && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "spa-create-config" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-create-config into .cursor/skills/spa-create-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-create-config", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/splunk/splunk-platform-automator.git --path skills/spa/spa-create-config--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add splunk/splunk-platform-automator --skill spa-create-config -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install splunk/splunk-platform-automator spa-create-config --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/splunk-platform-automator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/spa/spa-create-config .gemini/skills/spa-create-config && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "spa-create-config" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-create-config into .gemini/skills/spa-create-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-create-config", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install splunk/splunk-platform-automator spa-create-configInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add splunk/splunk-platform-automator --skill spa-create-config -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/splunk/splunk-platform-automator.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/spa/spa-create-config .github/skills/spa-create-config && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "spa-create-config" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-create-config into .github/skills/spa-create-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-create-config", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add splunk/splunk-platform-automator --skill spa-create-config -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install splunk/splunk-platform-automator spa-create-config --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/splunk/splunk-platform-automator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/spa/spa-create-config .opencode/skills/spa-create-config && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "spa-create-config" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-create-config into .opencode/skills/spa-create-config/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-create-config", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
spa-create-config- GitHub stars
- 137
- Token cost
- ~3.5k tokens
- SKILL.md length
- 1,367 words
- Files
- 17 (incl. scripts, references, assets)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Proprietary
At a glance
A skill your agent uses when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for…
- Works in 10 steps: Environment setup → Topology path → Sizing tier → …
- Updating splunkconfig.yml
- SKILL.md covers When to Use, When NOT to Use, Secrets — never display… and Reference files (load on demand), plus 17 more sections
- Calls python3 and aws; needs SPLUNKBASE_PASSWORD and AWS_ACCESS_KEY_ID
What it does
Spa Create Config is an agent skill from splunk/splunk-platform-automator. Use when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for SPA. Guides interactive design on AWS Linux: deployment intent, SVA topology, role placement, OS/SSH, splunkconfigaws.py discovery, licenses, apps, validation. In Cursor invoke with /spa-create-config.
Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including scripts, reference files and assets (for example `assets/architecture-plan-template.md`, `assets/config-header-template.md` and `references/apps-questionnaire.md`). Compatibility notes: Requires SPA repo root (ansible.cfg, bin/). Optional boto3 for AWS discovery.
It sits in DevOps & Cloud, covering Infrastructure as code and Deployment. It works with Splunk, Amazon Web Services, Linux and Terraform. The repository describes itself as: Ansible framework providing a fast and simple way to spin up complex Splunk environments.
When your agent uses it
- Updating splunkconfig.yml
- Designing Splunk Enterprise lab topology
- Architecture plan before config
- AWS Terraform block for SPA
Example prompts
- “/spa-create-config”
Requirements
- Python 3
- A credential in AWS_SECRET_ACCESS_KEY
- A credential in AWS_SESSION_TOKEN
- Compatibility (from SKILL.md): Requires SPA repo root (ansible.cfg, bin/). Optional boto3 for AWS discovery.
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Environment setup
- Topology path
- Sizing tier
- Linux OS
- AWS settings
- Topology counts
- Apps (optional)
- Write config
- Validate (quality gate)
- Handoff
What it can do on your machine
Read from SKILL.md and the folder at commit 6071df2. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
python3aws
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use aws, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
SPLUNKBASE_PASSWORDAWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_SESSION_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires SPA repo root (ansible.cfg, bin/). Optional boto3 for AWS discovery.
From compatibility in the SKILL.md frontmatter.
Context cost
Spa Create Config loads about 3.5k tokens when it runs, and up to ~16k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 1,367 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Proprietary) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,367 words (~3,528 tokens).
“Interactive workflow for config/splunk_config.yml on AWS. Linux only.”
- name
- spa-create-config
- compatibility
- Requires SPA repo root (ansible.cfg, bin/). Optional boto3 for AWS discovery.
- license
- Proprietary
- metadata.product
- splunk-platform-automator
- metadata.version
- 1.0.0
- paths
- config/splunk_config.yml, examples/**/*.yml, examples/configuration_description.yml
Files
SKILL.md and 16 other files (scripts, references, assets) in skills/spa/spa-create-config of splunk/splunk-platform-automator.
- SKILL.md
- assets/architecture-plan-template.md
- assets/config-header-template.md
- references/apps-questionnaire.md
- references/architecture-requirements.md
- references/aws-baseline.md
- references/aws-os-matrix.md
- references/aws-without-credentials.md
- references/licenses.md
- references/reference-links.md
- references/rf-sf-sizing.md
- references/role-placement.md
- references/secrets-handling.md
- references/sva-questionnaire.md
- references/sva-topology-map.md
- references/validation.md
- scripts/README.md
Open the folder on GitHubat commit 6071df2
Compare with similar skills
Spa Create Config next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Spa Create Config this skillsplunk/splunk-platform-automator | 137 | — | ~3.5k | Automated safety check: Pass | Proprietary | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 259 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Devops Deploysickn33/agentic-awesome-skills | 47k | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Configuring AWS Verified Access For Ztnamukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Cloud Infrastructureaiskillstore/marketplace | 430 | 1 repos | ~1.3k | Automated safety check: Pass | None | |
| Discover Infrarand/cc-polymath | 181 | — | ~783 | Automated safety check: Pass | MIT |
Similar skills
Devops Deploy
sickn33/agentic-awesome-skills
DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.
Configuring AWS Verified Access For Ztna
mukul975/Anthropic-Cybersecurity-Skills
Configure AWS Verified Access to provide VPN-less zero trust network access to internal apps, combining identity trust providers (IAM Identity Center, Okta/OIDC), device posture providers…
Cloud Infrastructure
aiskillstore/marketplace
Cloud infrastructure design and deployment patterns for AWS, Azure, and GCP.
Discover Infra
rand/cc-polymath
Automatically discover cloud, infrastructure, deployment, and container skills when working with AWS, GCP, Azure, Docker, Kubernetes, Terraform, Netlify, Heroku, serverless, or IaC
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
More from splunk/splunk-platform-automator
Spa Add Test Scenario
splunk/splunk-platform-automator
A skill your agent uses when adding app scope/routing test coverage (deployer, CM, DS, direct).
Related
Categories
Questions about Spa Create Config
What does Spa Create Config do?
A skill your agent uses when creating or updating splunkconfig.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for…. Spa Create Config is an agent skill from splunk/splunk-platform-automator.yml, designing Splunk Enterprise lab topology, multisite IDXC, SHC layout, architecture plan before config, or AWS Terraform block for SPA.
When should I use Spa Create Config?
Spa Create Config fits situations like: updating splunkconfig.yml; designing Splunk Enterprise lab topology; architecture plan before config; AWS Terraform block for SPA.
How do I install Spa Create Config in Claude Code?
Run `npx skills add splunk/splunk-platform-automator --skill spa-create-config -a claude-code`. Or copy the skill folder (skills/spa/spa-create-config in splunk/splunk-platform-automator) into .claude/skills/spa-create-config in your project. Claude Code loads it when a task matches its description.
How do I install Spa Create Config in Codex?
Run `npx skills add splunk/splunk-platform-automator --skill spa-create-config -a codex`. Or copy the skill folder (skills/spa/spa-create-config in splunk/splunk-platform-automator) into .agents/skills/spa-create-config in your project. Codex loads it when a task matches its description.
Can I use Spa Create Config in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add splunk/splunk-platform-automator --skill spa-create-config -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/spa-create-config, .gemini/skills/spa-create-config, .github/skills/spa-create-config and .opencode/skills/spa-create-config in your project.
What does Spa Create Config need to run?
Going by SKILL.md and its folder, Spa Create Config needs the command-line tools its instructions call (python3 and aws) and credentials named SPLUNKBASE_PASSWORD, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN. Our summary lists: Python 3; A credential in AWS_SECRET_ACCESS_KEY; A credential in AWS_SESSION_TOKEN. Compatibility (from SKILL.md): Requires SPA repo root (ansible.cfg, bin/). Optional boto3 for AWS discovery..
Does Spa Create Config access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Spa Create Config safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Spa Create Config use?
Spa Create Config carries a proprietary licence (declared in SKILL.md). It is published on GitHub, but it is not open source: read the licence file before using or sharing it.
How many tokens does Spa Create Config use?
About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.
What are the alternatives to Spa Create Config?
Skills that share tags, products or a category with Spa Create Config: Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 259 stars), Devops Deploy (sickn33/agentic-awesome-skills, 47k stars), Configuring AWS Verified Access For Ztna (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Cloud Infrastructure (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Spa Create Config?
splunk (a GitHub organization) maintains it in splunk/splunk-platform-automator, which has 137 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: splunk/splunk-platform-automator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.