automation-skills
Shared tooling for the Playwright automation repos: Claude Code skills, the generator they drive, and the rules each project family (and, rarely, each repo) adds on top.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/awesomer9561--automation-skills)HTML
<a href="/listings/awesomer9561--automation-skills"><img src="/api/listings/awesomer9561--automation-skills/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
No clone needed. Either way you get the `steps-to-spec` skill; the generator is the npm package `steps-to-specs`.
# A) npm: the package plus a one-line skill installer (macOS, Linux, Windows; copies, no symlinks) npm i -D steps-to-specs # in each automation repo npx steps-to-specs # installs the skill to ~/.claude/skills (add --project for ./.claude/skills) # B) Claude Code plugin marketplace (skill only; still `npm i -D steps-to-specs` in each repo) /plugin marketplace add Awesomer9561/Automation.Skills /plugin install steps-to-spec@automation-skills
Contributing / using the team's ProBuy rules and pack: clone this repo next to the automation repos (`../Automation.Skills`) and link instead:
macOS / Linux / Git Bash:
ln -s "$PWD/skills/steps-to-spec" ~/.claude/skills/steps-to-spec
Windows (PowerShell; a junction needs no admin rights, unlike `ln -s`/symlinks):
New-Item -ItemType Junction -Path "$HOME\.claude\skills\steps-to-spec" -Target "$PWD\skills\steps-to-spec"
Needs Node 18+ and Git on both systems. Everything the tools run is Node, so the same `npm run` scripts work in PowerShell, cmd, Git Bash and zsh. A `.gitattributes` keeps files LF, and `gen:check` ignores CRLF, so specs generated on one OS verify on the other.
Then set up each repo as in `steps-core/README.md` (devDependency + scripts + `steps.config.js`, then `npm install`).
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 12 lines
- {
- "name": "automation-skills",
- "owner": { "name": "Parvez Ali" },
- "plugins": [
- {
- "name": "steps-to-spec",
- "source": "./",
- "description": "Turn plain-text test steps into Playwright specs: probe pages, write steps, generate, run.",
- "version": "0.2.2"
- }
- ]
- }
README.md · README · 49 lines
- # Automation.Skills
- Shared tooling for the Playwright automation repos: Claude Code skills, the generator they drive, and the rules each
- project family (and, rarely, each repo) adds on top.
- ```
- skills/steps-to-spec/SKILL.md generic workflow: probe pages -> write steps -> generate -> run
- steps-core/ the generator, published as the npm package `steps-to-specs` (also ships the skill)
- projects/
- _projects/<project>/rules.md rules shared by a project family (repos whose .crossrepo.json says "project": "<project>")
- _projects/<project>/*.js optional packs: steps shared by the family (probuy: pack.js, the login for all
- portals), listed in each repo's steps.config.js packs
- <repo-folder>/rules.md rare per-repo overrides; win over the family file
- ```
- Generic behaviour goes in the skill or `steps-core`; anything true only for one product goes under `projects/`.
- ## Install
- No clone needed. Either way you get the `steps-to-spec` skill; the generator is the npm package `steps-to-specs`.
- ```bash
- # A) npm: the package plus a one-line skill installer (macOS, Linux, Windows; copies, no symlinks)
- npm i -D steps-to-specs # in each automation repo
- npx steps-to-specs # installs the skill to ~/.claude/skills (add --project for ./.claude/skills)
- # B) Claude Code plugin marketplace (skill only; still `npm i -D steps-to-specs` in each repo)
- /plugin marketplace add Awesomer9561/Automation.Skills
- /plugin install steps-to-spec@automation-skills
- ```
- Contributing / using the team's ProBuy rules and pack: clone this repo next to the automation repos
- (`../Automation.Skills`) and link instead:
- macOS / Linux / Git Bash:
- ```bash
- ln -s "$PWD/skills/steps-to-spec" ~/.claude/skills/steps-to-spec
- ```
- Windows (PowerShell; a junction needs no admin rights, unlike `ln -s`/symlinks):
- ```powershell
- New-Item -ItemType Junction -Path "$HOME\.claude\skills\steps-to-spec" -Target "$PWD\skills\steps-to-spec"
- ```
- Needs Node 18+ and Git on both systems. Everything the tools run is Node, so the same `npm run` scripts work in
- PowerShell, cmd, Git Bash and zsh. A `.gitattributes` keeps files LF, and `gen:check` ignores CRLF, so specs generated on
- one OS verify on the other.
- Then set up each repo as in `steps-core/README.md` (devDependency + scripts + `steps.config.js`, then `npm install`).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.