A test runner for Portwood that combines browser checks, Apex tests, formatting checks, and code analysis into one quality check.

Use it after a change, before opening a pull request, or when identifying whether a failing suite comes from the code or the test setup.

It gives contributors one repeatable way to find failures before a pull request, including a fast offline mode when no Salesforce organisation is available.

How Portwood-Global-Solutions/Portwood configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Portwood-Global-Solutions/Portwood. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Portwood-Global-Solutions/Portwood/main/.claude/skills/run-tests/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Portwood-Global-Solutions/Portwood

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/portwood-global-solutions/portwood/run-tests/github.svg)](https://agentmods.dev/skills/portwood-global-solutions/portwood/run-tests)

Your own site

<a href="https://agentmods.dev/skills/portwood-global-solutions/portwood/run-tests"><img src="https://agentmods.dev/badge/skills/portwood-global-solutions/portwood/run-tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/portwood-global-solutions/portwood/run-tests"><img src="https://agentmods.dev/badge/skills/portwood-global-solutions/portwood/run-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,697 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.01697
Opus 5.5	$0.00026	$0.00679
Sonnet 5.5	$0.00013	$0.00339
Haiku 4.5	$0.00006	$0.00170

Measured 2mo ago against content hash b0f8275bede6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/run-tests/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Running Portwood's tests

The one command

npm run qa

Runs every suite against the docgen-verify org and writes one report. Exit code is 0 only when every evaluated check passed, so it drops straight into CI.

npm run qa -- --org myorg           # a different org
npm run qa -- --offline             # only suites needing no org — CI-safe, fast
npm run qa -- --fast                # skip the slow suites
npm run qa -- --suite merge-tags,metadata-audit
npm run qa -- --headed              # watch the browser suites run
npm run qa -- --list                # what suites exist

Output lands in scripts/qa/report/:

qa-report.md — headline numbers, coverage by area, and an ordered what to fix list
qa-report.json — the same data, for tracking over time

Start with npm run qa -- --offline. It needs no org at all, so it's the fastest way to know whether you broke something, and it's what a contributor without a configured org can still run.

Suites

apex-e2e, apex-unit, flow-actions, merge-tags, metadata-audit, output-formats, pdf-content, record-pages, template-integrity, ui-admin, ui-designer, ui-runner.

A suite that cannot run returns "skipped" rather than throwing — the report says so out loud instead of quietly reporting 100%. A skipped suite is not a passing suite; check the report rather than just the exit code when you care about coverage.

Adding a suite

Drop a file in scripts/qa/suites/ exporting run({ org, headed, base }) that returns suiteResult(...) from lib/report.mjs, then register it in SUITES in scripts/qa/run-all.mjs. Suites must never throw.

The pure-Node checks

scripts/qa/canvas-*.mjs and friends run serializer and layout logic with no browser and no org — that's why the serializer is written to survive typeof document === 'undefined'. They're the fastest feedback loop in the repo:

node scripts/qa/canvas-serializer-check.mjs
node scripts/qa/canvas-anchor-check.mjs
node scripts/qa/canvas-export-roundtrip-check.mjs
node scripts/qa/canvas-import-fidelity.mjs
node scripts/qa/canvas-inline-sanitize-check.mjs

Read the full file on GitHub · 159 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 159 lines · 64 tokens per session scan A b0f8275bede6

Subscribe to this mod's changes

run-tests is a skill published in the GitHub repository Portwood-Global-Solutions/Portwood (132 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 1,697 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

E2E testing Testing Unit testing apex barcode bulk-generation document-generation docx flow-actions

run-tests next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
run-testsPortwood-Global-Solutions/Portwood	Skill	132	yesterday	Apache-2.0	A	64	Claude Code
test-masterJeffallan/claude-skills	Skill	12k	7d ago	MIT	A	104	Claude Code
axiom-testingCharlesWiltgen/Axiom	Skill	1.3k	yesterday	MIT	A	38	Claude Code
test-generatorrshankras/claude-code-apple-skills	Skill	864	2d ago	MIT	A	33	Claude Code
testing-blocksadobe/skills	Skill	319	yesterday	Apache-2.0	A	61	Claude Code
designing-testsCloudAI-X/claude-workflow-v2	Skill	1.4k	1mo ago	MIT	A	48	Claude Code
test-automation-expertcuriositech/some_claude_skills	Skill	263	yesterday	MIT	A	133	Claude Code

Portwood: Skill for Claude Code