A skill your agent uses when adding app scope/routing test coverage (deployer, CM, DS, direct).
$ npx skills add splunk/splunk-platform-automator --skill spa-add-test-scenario -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install splunk/splunk-platform-automator spa-add-test-scenario --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-add-test-scenario .claude/skills/spa-add-test-scenario && 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-add-test-scenario" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-add-test-scenario into .claude/skills/spa-add-test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-add-test-scenario", 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-add-test-scenarioType 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-add-test-scenario -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install splunk/splunk-platform-automator spa-add-test-scenario --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-add-test-scenario .agents/skills/spa-add-test-scenario && 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-add-test-scenario" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-add-test-scenario into .agents/skills/spa-add-test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-add-test-scenario", 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-add-test-scenario -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install splunk/splunk-platform-automator spa-add-test-scenario --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-add-test-scenario .cursor/skills/spa-add-test-scenario && 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-add-test-scenario" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-add-test-scenario into .cursor/skills/spa-add-test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-add-test-scenario", 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-add-test-scenario--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-add-test-scenario -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install splunk/splunk-platform-automator spa-add-test-scenario --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-add-test-scenario .gemini/skills/spa-add-test-scenario && 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-add-test-scenario" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-add-test-scenario into .gemini/skills/spa-add-test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-add-test-scenario", 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-add-test-scenarioInstalls 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-add-test-scenario -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-add-test-scenario .github/skills/spa-add-test-scenario && 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-add-test-scenario" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-add-test-scenario into .github/skills/spa-add-test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-add-test-scenario", 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-add-test-scenario -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-add-test-scenario --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-add-test-scenario .opencode/skills/spa-add-test-scenario && 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-add-test-scenario" agent skill from https://github.com/splunk/splunk-platform-automator/tree/master/skills/spa/spa-add-test-scenario into .opencode/skills/spa-add-test-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "spa-add-test-scenario", 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.
spa-add-test-scenarioA skill your agent uses when adding app scope/routing test coverage (deployer, CM, DS, direct).
Spa Add Test Scenario is an agent skill from splunk/splunk-platform-automator. Use when adding app scope/routing test coverage (deployer, CM, DS, direct). Distills splunkconfig.yml into tests/configs/appscope/<name/ with expectedscope.json. NOT for flat deployment test configs under tests/configs/.yml. In Cursor invoke with /spa-add-test-scenario.
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires SPA repo root (ansible.cfg, tests/). No AWS or SSH required.
It sits in DevOps & Cloud, covering Test coverage, Deployment and Infrastructure as code. It works with Splunk, Amazon Web Services and Ansible. The repository describes itself as: Ansible framework providing a fast and simple way to spin up complex Splunk environments.
5 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 6071df2. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
ansible-playbookFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Requires SPA repo root (ansible.cfg, tests/). No AWS or SSH required.
From compatibility in the SKILL.md frontmatter.
Spa Add Test Scenario loads about 2.2k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 653 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.
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); files beside SKILL.md are not scanned.
Its licence (Proprietary) doesn't allow us to republish the file, so here is its outline and opening line. It has 653 words (~2,159 tokens).
“This skill covers app scope scenarios only. A large config like config/splunk_config.yml or tests/configs/2site-idxc_shc_mc_ds_sh_hf_uf_itsi_apps.yml can be distilled into an app scope scenario, but that is optional — it does not replace a deployment test config.”
Just SKILL.md in skills/spa/spa-add-test-scenario of splunk/splunk-platform-automator.
Open the folder on GitHubat commit 6071df2
Spa Add Test Scenario 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 Add Test Scenario this skillsplunk/splunk-platform-automator | 137 | — | ~2.2k | Automated safety check: Pass | Proprietary | |
| Implementing Deception Based Detection With Canarytokenmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~591 | Automated safety check: Pass | Apache-2.0 | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| Cloudformationitsmostafa/aws-agent-skills | 1.2k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Devops Deploysickn33/agentic-awesome-skills | 47k | 2 repos | ~1.9k | Automated safety check: Pass | MIT |
mukul975/Anthropic-Cybersecurity-Skills
Deploys and monitors Canary Tokens via the Thinkst Canary REST API for deception-based breach detection, programmatically creating web bug, DNS, MS Word document, and AWS API key tokens and…
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
itsmostafa/aws-agent-skills
AWS CloudFormation infrastructure as code for stack management.
sickn33/agentic-awesome-skills
DevOps e deploy de aplicacoes — Docker, CI/CD com GitHub Actions, AWS Lambda, SAM, Terraform, infraestrutura como codigo e monitoramento.
boundless-xyz/boundless
Internal — for Boundless team members only. An agent skill from boundless-xyz/boundless.
splunk/splunk-platform-automator
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 with
Categories
A skill your agent uses when adding app scope/routing test coverage (deployer, CM, DS, direct). Spa Add Test Scenario is an agent skill from splunk/splunk-platform-automator. Use when adding app scope/routing test coverage (deployer, CM, DS, direct).
Spa Add Test Scenario fits situations like: adding app scope/routing test coverage (deployer; tasks that involve Test coverage; tasks that involve Deployment.
Run `npx skills add splunk/splunk-platform-automator --skill spa-add-test-scenario -a claude-code`. Or copy the skill folder (skills/spa/spa-add-test-scenario in splunk/splunk-platform-automator) into .claude/skills/spa-add-test-scenario in your project. Claude Code loads it when a task matches its description.
Run `npx skills add splunk/splunk-platform-automator --skill spa-add-test-scenario -a codex`. Or copy the skill folder (skills/spa/spa-add-test-scenario in splunk/splunk-platform-automator) into .agents/skills/spa-add-test-scenario in your project. Codex loads it when a task matches its description.
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-add-test-scenario -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-add-test-scenario, .gemini/skills/spa-add-test-scenario, .github/skills/spa-add-test-scenario and .opencode/skills/spa-add-test-scenario in your project.
Going by SKILL.md and its folder, Spa Add Test Scenario needs the command-line tools its instructions call (ansible-playbook). Compatibility (from SKILL.md): Requires SPA repo root (ansible.cfg, tests/). No AWS or SSH required..
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.
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. Review the folder before installing.
Spa Add Test Scenario 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.
About 2.2k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Spa Add Test Scenario: Implementing Deception Based Detection With Canarytoken (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), AWS Cdk Development (zxkane/aws-skills, 367 stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and Cloudformation (itsmostafa/aws-agent-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
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.
