Agent skill

Sf Testing

Apex test execution, coverage analysis, and test-fix loops with 120-point scoring.

MITAuto-check passedTesting & QA

Install Sf Testing

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sf-testing .claude/skills/sf-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "sf-testing" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-testing into .claude/skills/sf-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sf-testing .agents/skills/sf-testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "sf-testing" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-testing into .agents/skills/sf-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sf-testing .cursor/skills/sf-testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "sf-testing" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-testing into .cursor/skills/sf-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Jaganpro/sf-skills.git --path skills/sf-testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sf-testing .gemini/skills/sf-testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "sf-testing" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-testing into .gemini/skills/sf-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sf-testing .github/skills/sf-testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "sf-testing" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-testing into .github/skills/sf-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Jaganpro/sf-skills --skill sf-testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Jaganpro/sf-skills sf-testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Jaganpro/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sf-testing .opencode/skills/sf-testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "sf-testing" agent skill from https://github.com/Jaganpro/sf-skills/tree/main/skills/sf-testing into .opencode/skills/sf-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sf-testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: sf-testing
GitHub stars: 424
Token cost: ~1.1k tokens
SKILL.md length: 411 words
Files: 16 (incl. references, assets)
Skills in repo: 36
Repo updated: Apr 27, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Apex test execution, coverage analysis, and test-fix loops with 120-point scoring.

Works in 5 steps: Discover test scope → Run the smallest useful test set first → Analyze results → …
: user runs Apex tests
SKILL.md covers When This Skill Owns the Task, Required Context to Gather First, Recommended Workflow and High-Signal Rules, plus 4 more sections
Runs Python scripts from its folder; calls sf

What it does

Sf Testing is an agent skill from Jaganpro/sf-skills. Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. TRIGGER when: 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 sf-apex), Agentforce agent testing (use sf-ai-agentforce-testing), or Jest/LWC tests (use sf-lwc).

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 19 other files, including reference files and assets (for example `CREDITS.md`, `README.md` and `hooks/scripts/parse-test-results.py`).

It sits in Testing & QA, covering Unit testing, Test coverage and Failing and flaky tests. It works with Jest. The repository describes itself as: [ARCHIVED — migrated to forcedotcom/afv-library] Salesforce Skills for Agentic Coding Tools — Apex, Flow, LWC, SOQL, Agentforce, Data Cloud, OmniStudio. Read-only archive; active… The licence is MIT.

When your agent uses it

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

Example prompts

“/sf-testing”

Requirements

Python 3

Workflow steps

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

Discover test scope
Run the smallest useful test set first
Analyze results
Run a disciplined fix loop
Improve coverage intentionally

What it can do on your machine

Read from SKILL.md and the folder at commit 53c9956. 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 script files (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

Sf Testing loads about 1.1k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 411 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~92
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k
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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from Jaganpro/sf-skills at commit 53c9956, republished under its MIT licence (© Jaganpro). 411 words, ~1,125 tokens.

Download SKILL.mdSave it as .claude/skills/sf-testing/SKILL.md (or your agent's skills folder). This skill also uses 15 other files; get the full folder from GitHub.

name: sf-testing
description: Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. TRIGGER when: 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 sf-apex), Agentforce agent testing (use sf-ai-agentforce-testing), or Jest/LWC tests (use sf-lwc).
license: MIT
metadata.version: 1.1.0
metadata.author: Jag Valaiyapathy
metadata.scoring: 120 points across 6 categories

sf-testing: Salesforce Test Execution & Coverage Analysis

Use this skill when the user needs Apex test execution and failure analysis: running tests, checking coverage, interpreting failures, improving coverage, and managing a disciplined test-fix loop for Salesforce code.

When This Skill Owns the Task

Use sf-testing when the work involves:

sf apex run test workflows
Apex unit-test failures
code coverage analysis
identifying uncovered lines and missing test scenarios
structured test-fix loops for Apex code

Delegate elsewhere when the user is:

writing or refactoring production Apex → sf-apex
testing Agentforce agents → sf-ai-agentforce-testing
testing LWC with Jest → sf-lwc

Required Context to Gather First

Ask for or infer:

target org alias
desired test scope: single class, specific methods, suite, or local tests
coverage threshold expectation
whether the user wants diagnosis only or a test-fix loop
whether related test data factories already exist

Recommended Workflow

1. Discover test scope

Identify:

existing test classes
target production classes
test data factories / setup helpers

2. Run the smallest useful test set first

Start narrow when debugging a failure; widen only after the fix is stable.

3. Analyze results

Focus on:

failing methods
exception types and stack traces
uncovered lines / weak coverage areas
whether failures indicate bad test data, brittle assertions, or broken production logic

4. Run a disciplined fix loop

When the issue is code or test quality:

delegate code fixes to sf-apex when needed
add or improve tests
rerun focused tests before broader regression

5. Improve coverage intentionally

Cover:

positive path
negative / exception path
bulk path (251+ records where appropriate)
callout or async path when relevant

Show full SKILL.md (154 more words)Show less

High-Signal Rules

default to SeeAllData=false
every test should assert meaningful outcomes
test bulk behavior, not just single-record happy paths
use factories / @TestSetup when they improve clarity and speed
pair Test.startTest() with Test.stopTest() when async behavior matters
do not hide flaky org dependencies inside tests

Output Format

When finishing, report in this order:

What tests were run
Pass/fail summary
Coverage result
Root-cause findings
Fix or next-run recommendation

Suggested shape:

text

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>

Cross-Skill Integration

Need	Delegate to	Reason
fix production code or author tests	sf-apex	code generation and repair
create bulk / edge-case data	sf-data	realistic test datasets
deploy updated tests	sf-deploy	rollout
inspect detailed runtime logs	sf-debug	deeper failure analysis

Reference Map

Start here

Specialized guidance

Score Guide

Score	Meaning
108+	strong production-grade test confidence
96–107	good test suite with minor gaps
84–95	acceptable but strengthen coverage / assertions
< 84	below standard; revise before relying on it

Files

SKILL.md and 15 other files (references, assets) in skills/sf-testing of Jaganpro/sf-skills.

SKILL.md
CREDITS.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
hooks/scripts/parse-test-results.py
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

Open the folder on GitHubat commit 53c9956

Compare with similar skills

Sf Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sf Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Sf Testing this skillJaganpro/sf-skills	424	—	~1.1k	Automated safety check: Pass	MIT	5 mo ago
Platform Apex Test Runforcedotcom/sf-skills	1.1k	—	~1.9k	Automated safety check: Pass	Apache-2.0	4 days ago
Test Guidelinesgetsentry/sentry-react-native	1.8k	—	~1.3k	Automated safety check: Pass	MIT	today
Designing TestsCloudAI-X/claude-workflow-v2	1.4k	1 repos	~1.5k	Automated safety check: Pass	MIT	yesterday
Caliber Testingcaliber-ai-org/ai-setup	1.3k	—	~3.2k	Automated safety check: Pass	MIT	13 days ago
Write Testsgrafana/synthetic-monitoring-app	171	—	~1.2k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Platform Apex Test Run
forcedotcom/sf-skills
Apex test execution, coverage analysis, and test-fix loops with 120-point scoring.
1.1k GitHub stars~1.9k tokensUpdated 4 days ago
Testing & QAAuto-check passed
Test Guidelines
getsentry/sentry-react-native
Official
Enforce Sentry React Native SDK test conventions for naming, structure, mocking, and fixtures with Jest.
1.8k GitHub stars~1.3k tokensUpdated today
Testing & QAAuto-check passed
Designing Tests
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
1.4k GitHub starsUsed in 1 repo~1.5k tokens
Testing & QAAuto-check passed
Caliber Testing
caliber-ai-org/ai-setup
Writes Vitest tests following project patterns: tests/ directories, vi.mock() for module mocking with vi.hoisted() for test-time factories, global LLM mock from src/test/setup.ts, environment…
1.3k GitHub stars~3.2k tokensUpdated 13 days ago
Testing & QAAuto-check passed
Write Tests
grafana/synthetic-monitoring-app
Official
Write Jest integration and unit tests for the Grafana Synthetic Monitoring app using React Testing Library, MSW, and src/test helpers.
171 GitHub stars~1.2k tokensUpdated today
Testing & QAAuto-check passed
Playwright Testing
chongdashu/vibejam-starter-pack
Plan, implement, and debug frontend tests: unit/integration/E2E/visual/a11y.
149 GitHub stars~2.1k tokensUpdated 5 mo ago
Testing & QAAuto-check passed

Questions about Sf Testing

What does Sf Testing do?

Apex test execution, coverage analysis, and test-fix loops with 120-point scoring. Sf Testing is an agent skill from Jaganpro/sf-skills. Apex test execution, coverage analysis, and test-fix loops with 120-point scoring.

When should I use Sf Testing?

Sf Testing fits situations like: : user runs Apex tests; checks code coverage; fixes failing tests; touches Test.cls / Test.cls files.

How do I install Sf Testing in Claude Code?

Run `npx skills add Jaganpro/sf-skills --skill sf-testing -a claude-code`. Or copy the skill folder (skills/sf-testing in Jaganpro/sf-skills) into .claude/skills/sf-testing in your project. Claude Code loads it when a task matches its description.

How do I install Sf Testing in Codex?

Run `npx skills add Jaganpro/sf-skills --skill sf-testing -a codex`. Or copy the skill folder (skills/sf-testing in Jaganpro/sf-skills) into .agents/skills/sf-testing in your project. Codex loads it when a task matches its description.

Can I use Sf Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Jaganpro/sf-skills --skill sf-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sf-testing, .gemini/skills/sf-testing, .github/skills/sf-testing and .opencode/skills/sf-testing in your project.

What does Sf Testing need to run?

Going by SKILL.md and its folder, Sf Testing needs Python for the scripts in its folder and the command-line tools its instructions call (sf). Our summary lists: Python 3.

Does Sf Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Sf Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sf Testing use?

Sf Testing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sf Testing use?

About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 12k tokens, read only when the agent opens those files.

What are the alternatives to Sf Testing?

Skills that share tags, products or a category with Sf Testing: Platform Apex Test Run (forcedotcom/sf-skills, 1.1k stars), Test Guidelines (getsentry/sentry-react-native, 1.8k stars), Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars) and Caliber Testing (caliber-ai-org/ai-setup, 1.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sf Testing?

Jaganpro (a GitHub user) maintains it in Jaganpro/sf-skills, which has 424 GitHub stars. The repository holds 36 skills in this directory. The repository was last updated on April 27, 2026.

Source: Jaganpro/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Sf Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

sf-testing: Salesforce Test Execution & Coverage Analysis

When This Skill Owns the Task

Required Context to Gather First

Recommended Workflow

1. Discover test scope

2. Run the smallest useful test set first

3. Analyze results

4. Run a disciplined fix loop

5. Improve coverage intentionally

High-Signal Rules

Output Format

Cross-Skill Integration

Reference Map

Start here

Specialized guidance

Score Guide

Files

Compare with similar skills

Similar skills

More from Jaganpro/sf-skills

Related

Questions about Sf Testing