Is Sf Testing safe and trustworthy?

tashan scores Sf Testing on public evidence — it is currently active. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Sf Testing?

Drop the skill folder into ~/.claude/skills/ (user scope) or .claude/skills/ (project scope).

Who maintains Sf Testing?

7 GitHub contributors, source: Brite-Nites/brite-claude-plugins.

‹ The Index

Sf Testing

skill

Author’s activation text, quoted as published

Apex test execution and coverage discipline (Brite edition) with 120-point scoring. TRIGGER when user runs Apex tests, checks coverage, fixes failing tests, touches Test.cls / Test.cls files, works in brite-salesforce, asks about 100% class coverage targets, @TestSetup static-state trap, Queueables inside Test.stopTest() re-entering handlers, @TestVisible + Test.isRunningTest() escape-hatch gating, BypassValidationRules honoring in tests, LWC Jest pre-commit, or scratch-org-per-PR validation. 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).

Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format

Install (Claude Code):

cp -r sf-testing ~/.claude/skills/

Adoption: 1 repos
Upkeep: 95.0
Freshness: 90.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
Contributors: 7

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

Its own instructions

Its SKILL.md says when to use it and covers setup.

Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Pro adds the history to tashan doctor, so a run over your own config says which of yours gained an advisory, started running an install script, or lost its last maintainer — and what to move to.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

source ↗ · skill:Brite-Nites/sf-testing

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-12 · scorer s5 · how · something wrong here?