Skip to content
Back to search

automation-skills

MarketplaceWorks with Claude CodeGitHub

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.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/awesomer9561--automation-skills/badge.svg)](/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
  1. {
  2. "name": "automation-skills",
  3. "owner": { "name": "Parvez Ali" },
  4. "plugins": [
  5. {
  6. "name": "steps-to-spec",
  7. "source": "./",
  8. "description": "Turn plain-text test steps into Playwright specs: probe pages, write steps, generate, run.",
  9. "version": "0.2.2"
  10. }
  11. ]
  12. }
README.md · README · 49 lines
  1. # Automation.Skills
  2. Shared tooling for the Playwright automation repos: Claude Code skills, the generator they drive, and the rules each
  3. project family (and, rarely, each repo) adds on top.
  4. ```
  5. skills/steps-to-spec/SKILL.md generic workflow: probe pages -> write steps -> generate -> run
  6. steps-core/ the generator, published as the npm package `steps-to-specs` (also ships the skill)
  7. projects/
  8. _projects/<project>/rules.md rules shared by a project family (repos whose .crossrepo.json says "project": "<project>")
  9. _projects/<project>/*.js optional packs: steps shared by the family (probuy: pack.js, the login for all
  10. portals), listed in each repo's steps.config.js packs
  11. <repo-folder>/rules.md rare per-repo overrides; win over the family file
  12. ```
  13. Generic behaviour goes in the skill or `steps-core`; anything true only for one product goes under `projects/`.
  14. ## Install
  15. No clone needed. Either way you get the `steps-to-spec` skill; the generator is the npm package `steps-to-specs`.
  16. ```bash
  17. # A) npm: the package plus a one-line skill installer (macOS, Linux, Windows; copies, no symlinks)
  18. npm i -D steps-to-specs # in each automation repo
  19. npx steps-to-specs # installs the skill to ~/.claude/skills (add --project for ./.claude/skills)
  20. # B) Claude Code plugin marketplace (skill only; still `npm i -D steps-to-specs` in each repo)
  21. /plugin marketplace add Awesomer9561/Automation.Skills
  22. /plugin install steps-to-spec@automation-skills
  23. ```
  24. Contributing / using the team's ProBuy rules and pack: clone this repo next to the automation repos
  25. (`../Automation.Skills`) and link instead:
  26. macOS / Linux / Git Bash:
  27. ```bash
  28. ln -s "$PWD/skills/steps-to-spec" ~/.claude/skills/steps-to-spec
  29. ```
  30. Windows (PowerShell; a junction needs no admin rights, unlike `ln -s`/symlinks):
  31. ```powershell
  32. New-Item -ItemType Junction -Path "$HOME\.claude\skills\steps-to-spec" -Target "$PWD\skills\steps-to-spec"
  33. ```
  34. Needs Node 18+ and Git on both systems. Everything the tools run is Node, so the same `npm run` scripts work in
  35. PowerShell, cmd, Git Bash and zsh. A `.gitattributes` keeps files LF, and `gen:check` ignores CRLF, so specs generated on
  36. one OS verify on the other.
  37. 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 in

Free to use. If it’s helped, pass it on.