sf-harness-audit
Skill15 starsChanged 7 months agoMITView on GitHub
Use when auditing SCC harness for Salesforce development completeness. Check hooks, agents, skills, and rules health for Apex and LWC coverage, and score each category.
In this repository58 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asideSkill
- checkpointSkill
- configure-sccSkill
- continuous-agent-loopSkill
- mcp-server-patternsSkill
- model-routeSkill
- prompt-optimizerSkill
- refactor-cleanSkill
- resume-sessionSkill
- save-sessionSkill
- search-firstSkill
- security-scanSkill
- sessionsSkill
- sf-2gp-security-reviewSkill
- sf-agentforce-developmentSkill
- sf-agentforce-mcp-actionsSkill
- sf-apex-async-patternsSkill
- sf-apex-best-practicesSkill
- sf-apex-constraintsSkill
- sf-apex-cursorSkill
- sf-apex-enterprise-patternsSkill
- sf-apex-testingSkill
- sf-api-designSkill
- sf-approval-processesSkill
- sf-aura-developmentSkill
- sf-build-fixSkill
- sf-cli-referenceSkill
- sf-data-modelingSkill
- sf-debuggingSkill
- sf-deployment-constraintsSkill
- sf-deploymentSkill
- sf-devops-ci-cdSkill
- sf-docs-lookupSkill
- sf-e2e-testingSkill
- sf-experience-cloudSkill
- sf-flow-developmentSkill
- sf-governor-limitsSkill
- sf-helpSkill
- sf-integrationSkill
- sf-lwc-constraintsSkill
- sf-lwc-developmentSkill
- sf-lwc-testingSkill
- sf-metadata-managementSkill
- sf-platform-events-cdcSkill
- sf-quickstartSkill
- sf-security-constraintsSkill
- sf-securitySkill
- sf-soql-constraintsSkill
- sf-soql-optimizationSkill
- sf-tdd-workflowSkill
- sf-testing-constraintsSkill
- sf-trigger-constraintsSkill
- sf-trigger-frameworksSkill
- sf-visualforce-developmentSkill
- strategic-compactSkill
- update-docsSkill
- update-platform-docsSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
When you want to verify that SCC is fully and correctly installed in a project
- Distinctive: line 14
When diagnosing issues with hooks, agents, skills, or rules not activating
- Distinctive: line 15
When preparing for a quality audit or compliance review of your SCC configuration
- Distinctive: line 16
When comparing your current installation against the full SCC profile
- Distinctive: line 17
When you want actionable recommendations to improve your SCC setup
- Distinctive: line 23
Check what's installed in the current project:
- Very specific: line 32
If using SCC CLI: npx scc-universal status
- Very specific: line 47
Check: npx scc-universal status to see installed hooks and their profiles.
- Very specific: line 48
Check: echo $SCC_HOOK_PROFILE to verify profile level.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SCC Harness Audit — Configuration Health Check
Evaluate the SCC harness configuration and suggest improvements. Checks file existence, content coverage, hook status, and rule completeness.
When to Use
- When you want to verify that SCC is fully and correctly installed in a project
- When diagnosing issues with hooks, agents, skills, or rules not activating
- When preparing for a quality audit or compliance review of your SCC configuration
- When comparing your current installation against the full SCC profile
- When you want actionable recommendations to improve your SCC setup
Workflow
Step 1 — Scan Installation
Check what's installed in the current project:
# Check for SCC installation markers
ls -la .claude/hooks/scripts/ 2>/dev/null
ls -la .claude/agents/ 2>/dev/null
ls -la .claude/skills/ 2>/dev/nullIf using SCC CLI: npx scc-universal status
Step 2 — Score Each Category
Rate each category 0-10 using these rubrics:
Hook Coverage (0-10)
| Score | Criteria |
| 0-3 | No hooks or only SessionStart |
| 4-6 | Quality-gate and governor-check active, but missing pre-tool-use hooks |
| 7-8 | All standard profile hooks active |
| 9-10 | Strict profile enabled, all hooks active including Code Analyzer integration |
Check: npx scc-universal status to see installed hooks and their profiles.
Check: echo $SCC_HOOK_PROFILE to verify profile level.
Agent Coverage (0-10)
| Score | Criteria |
| 0-3 | Only platform agents (loop-operator, doc-updater) |
| 4-6 | Core domain agents (sf-architect, sf-apex-agent, sf-review-agent) |
| 7-8 | Full domain agents (+ sf-lwc-agent, sf-flow-agent, sf-integration-agent) |
| 9-10 | Complete coverage including sf-admin-agent, sf-agentforce-agent, sf-bugfix-agent |
Check: ls .claude/agents/sf-*.md 2>/dev/null | wc -l
Skill Coverage (0-10)
| Score | Criteria |
| 0-3 | Less than 10 skills |
| 4-6 | 10-20 skills, core SF patterns covered |
| 7-8 | 20-35 skills, enterprise patterns included |
| 9-10 | 35+ skills with full domain coverage |
Check: find .claude/skills/ -name "SKILL.md" | wc -l
Skill Coverage (User-Invocable) (0-10)
| Score | Criteria |
| 0-3 | Only basic skills (sf-architect agent, sf-apex-best-practices) |
| 4-6 | Core workflow skills (sf-deployment, sf-debugging, sf-security) |
| 7-8 | Testing and security skills (sf-tdd-workflow, sf-governor-limits) |
| 9-10 | Full suite including discovery (/sf-help, /sf-quickstart) |
Check: ls .claude/skills/sf-*/SKILL.md 2>/dev/null | wc -l
Security Posture (0-10)
| Score | Criteria |
| 0-3 | No security hooks or rules |
| 4-6 | Security rules present, quality-gate active |
| 7-8 | Governor-check active, sharing model detection, CRUD/FLS rules |
| 9-10 | Strict profile, Code Analyzer integration, security-reviewer agent active |
Step 3 — Generate Report
SCC Harness Audit
══════════════════════════════════════════
Profile: standard
Version: 1.0.0
Install Target: claude
Category Scores:
Hook Coverage: 7/10
Agent Coverage: 8/10
Rule Coverage: 6/10
Skill Coverage: 7/10
Skill (Invocable): 8/10
Security Posture: 7/10
────────────────────────
Overall Score: 7.2/10
Top Recommendations:
1. [+1.0] Enable strict hook profile: export SCC_HOOK_PROFILE=strict
2. [+0.5] Install all modules: npx scc-universal install allStep 4 — Actionable Recommendations
For each gap, provide a specific command to fix it:
| Gap | Fix Command |
| Missing hooks | npx scc-universal repair |
| Missing domain rules | npx scc-universal install all (or target: npx scc-universal install apex, npx scc-universal install lwc) |
| Low skill count | npx scc-universal install all |
| Wrong hook profile | export SCC_HOOK_PROFILE=strict |
| Drifted files | npx scc-universal doctor then npx scc-universal repair |
Examples
sf-harness-audit
sf-harness-audit Check if all Salesforce domains are covered by agents and skills
sf-harness-audit Report gaps in hook coverage and recommend improvements
sf-harness-audit Score the security posture of the current SCC installationRelated
- Skill:
/sf-harness-audit— This skill is the audit tool; no separate agent exists
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.