Platform Apex Test Run

What it does

When your agent uses it

• The user runs Apex tests
• Checks code coverage
• Fixes failing tests
• Touches Test.cls / Test.cls files

Example prompts

• “/platform-apex-test-run”

Requirements

• Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

1. 1Discover test scope
2. 2Run the smallest useful test set first
3. 3Analyze results
4. 4Run a disciplined fix loop
5. 5Improve coverage intentionally

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (Python), which the agent can run.

  Shell commands in SKILL.md call:

  • sf

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Platform Apex Test Run loads about 1.9k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 100 tokens; SKILL.md has 751 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~100

When it runs · the whole SKILL.md, loaded when a task matches

~1.9k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 751 words, ~1,876 tokens.

name

platform-apex-test-run

description

Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Use when the user runs Apex tests, checks code coverage, fixes failing tests, or touches *Test.cls / *_Test.cls files. DO NOT TRIGGER when writing Apex production code (use platform-apex-generate), Agentforce agent testing (use agentforce-test), or Jest/LWC tests (use experience-lwc-generate).

metadata.version

1.2

metadata.domains

Platform

metadata.relatedSkills

agentforce-test, experience-lwc-generate, platform-apex-generate, platform-apex-logs-debug, platform-data-manage, platform-metadata-deploy

Test run: <scope>
Org: <alias>
Result: <passed / partial / failed>
Coverage: <percent / key classes>
Issues: <highest-signal failures>
Next step: <fix class, add test, rerun scope, or widen regression>

© forcedotcom, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 14 other files (scripts, references, assets) in skills/platform-apex-test-run of forcedotcom/sf-skills.

• SKILL.md
• README.md
• assets/basic-test.cls
• assets/bulk-test.cls
• assets/dml-mock.cls
• assets/mock-callout-test.cls
• assets/stub-provider-example.cls
• assets/test-data-factory.cls
• references/cli-commands.md
• references/mocking-patterns.md
• references/performance-optimization.md
• references/test-fix-loop.md
• references/test-patterns.md
• references/testing-best-practices.md
• scripts/parse-test-results.py

Open the folder on GitHubat commit e5164d9