sap-sac-test-automation — Claude Code skill for SAP Analytics Cloud tests
Designs Playwright test suites for SAP Analytics Cloud stories and dashboards: browser discovery first, a reviewed profile next, then repeatable runs gated in CI.
npx skills add secondsky/sap-skills --skill sap-sac-test-automation -a claude-codeWhat sap-sac-test-automation does
The skill works by one rule: discovery proposes, a person approves, Playwright executes, CI enforces. You and the agent map a story together, listing pages, widgets, locators, readiness markers and roles. That map becomes a dashboard profile draft plus a YAML scenario. Nothing gets written until you confirm file creation and pick a target folder, so profiles/<profile-id>/dashboard.yaml and its neighbours stay drafts until then.
For discovery you can use Microsoft Edge over CDP, Chrome DevTools MCP, the agent-browser CLI, or plain manual work. Name a browser or connection method and the skill checks that surface only. Private SAC content is not supposed to reach external services without approval.
Scenarios stay free of selectors; interaction runs through component IDs from the profile, behind reusable adapters. Start CI with the safe packs: an auth check, a read-only smoke run, navigation, critical widget readiness. Planning writeback, comments, data actions and visual baselines belong in controlled or nightly stages. A live tenant with SSO and writeback needs tenant-specific evidence before anyone calls the run validated. Adding browser tooling or MCP servers that touch SAC credentials makes a dependency risk review worthwhile.
What it helps with
- map widgets and locators on a SAC story
- draft a dashboard profile and YAML scenario for later runs
- move manual dashboard checks to deterministic Playwright tests
- separate safe read-only checks from planning writeback tests
- package a trace, screenshots and visual diff for a failed run
Example prompts for the agent
- Run read-only discovery on this SAC story and draft a dashboard profile, but do not create files yet
- Build a
read-only-smoke.yamlscenario for the story and show which locators come from the profile - Triage the failed run and attach the trace, screenshots and root-cause label
How to install sap-sac-test-automation
1Skills CLI (Vercel)
npx skills add secondsky/sap-skills --skill sap-sac-test-automation -a claude-code2Manually: put the files in place
~/.claude/skills/sap-sac-test-automation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/sap-sac-test-automation/
1Skills CLI (Vercel)
npx skills add secondsky/sap-skills --skill sap-sac-test-automation -a codex2Manually: put the files in place
.agents/skills/sap-sac-test-automation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add secondsky/sap-skills --skill sap-sac-test-automation -a cursor2Manually: put the files in place
.cursor/skills/sap-sac-test-automation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install secondsky/sap-skills sap-sac-test-automation2Manually: put the files in place
.github/skills/sap-sac-test-automation/SKILL.md1Skills CLI (Vercel)
npx skills add secondsky/sap-skills --skill sap-sac-test-automation -a gemini-cli2Platform CLI
gemini skills install https://github.com/secondsky/sap-skills --path plugins/sap-sac-test-automation/skills/sap-sac-test-automationManually: put the files in place
.devin/skills/sap-sac-test-automation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add secondsky/sap-skills --skill sap-sac-test-automation -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about sap-sac-test-automation
How do I install sap-sac-test-automation in Claude Code?
Run npx skills add secondsky/sap-skills --skill sap-sac-test-automation -a claude-code. The skill then sits at ~/.claude/skills/sap-sac-test-automation/SKILL.md.
What does sap-sac-test-automation do?
It guides the design of automated tests for SAP Analytics Cloud stories, reports and dashboards: component discovery, a dashboard profile, YAML scenarios and Playwright adapters.
Does it need access to a live SAC tenant?
Real runs need a tenant, SSO sign-in and writeback permissions if planning is under test. Those checks need tenant-specific evidence before you rely on them.
