AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Pw Framework Tooling

skill-mallikarjun-roddannavar-playwright-pom-agent-skills-pw-framework-tooling · by Mallikarjun-Roddannavar

Maintain framework-wide quality tooling, runtime configuration, waits, logging, reporting, and Playwright config for the `playwright-pom-agent-skills` Playwright framework. Use when tasks touch playwright.config.ts, package.json scripts, eslint/prettier/typecheck setup, waits, logger, custom reporter, or README sections about framework behavior.

↗ Repository
— No reviews yet
0 installs
26 views
0.0% view→install

Install

$ agentstack add skill-mallikarjun-roddannavar-playwright-pom-agent-skills-pw-framework-tooling

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mallikarjun-roddannavar-playwright-pom-agent-skills-pw-framework-tooling)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Pw Framework Tooling? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

PW Framework Tooling

Maintain the framework infrastructure that supports test execution quality and developer workflow.

Use This Skill When

  • Changing playwright.config.ts, package.json, linting, formatting, typechecking, waits, logging, or reporting.
  • Adding or updating validation scripts.
  • Updating framework documentation about tooling or execution behavior.

Covered Areas

  • playwright.config.ts
  • package.json
  • eslint.config.mjs
  • tsconfig.json
  • utils/common/Logger.ts
  • utils/common/Waits.ts
  • utils/common/CustomReporter.ts
  • scripts/checkNamingConventions.mjs
  • framework README quality/tooling sections

Follow These Rules

  • Keep config/test-config.json as the single config source for base URLs, role credentials, and shared waits.
  • Keep framework timeout derivation in utils/common/Waits.ts.
  • Keep scoped logging via logger.withScope(...).
  • Keep the custom reporter at utils/common/CustomReporter.ts.
  • Keep ESLint, Prettier, and tsc --noEmit working together.
  • Keep @typescript-eslint/no-floating-promises enabled.
  • Keep npm run check:naming passing for framework naming rules.

Inspect First

  1. Identify the smallest set of tooling files that own the behavior.
  2. Check whether the change is configuration, validation, runtime helper, or documentation.
  3. Reuse an existing script or helper before adding a new one.
  4. Keep claims in docs limited to what the framework actually implements.

Preferred Change Order

  1. Change configuration or shared helper logic first.
  2. Change scripts next if deterministic enforcement is needed.
  3. Update documentation last so it reflects the final behavior.
  4. Avoid spreading the same rule across multiple files unless each layer truly needs it.

Validation Workflow

Prefer direct local binaries if npm run is unreliable in the AI shell:

  • node ./scripts/checkNamingConventions.mjs
  • ./node_modules/.bin/eslint.cmd .
  • ./node_modules/.bin/tsc.cmd --noEmit
  • ./node_modules/.bin/prettier.cmd . --check
  • ./node_modules/.bin/playwright.cmd test --list

Run the smallest set that proves the change.

Finish Checklist

  • The change is centralized in the narrowest responsible tooling layer.
  • Validation scripts and config still agree with each other.
  • Documentation claims only what is currently implemented.
  • The minimal relevant validation commands were run or explicitly skipped.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in AI & ML