agentleFS
SalesforceLabsSalesforceLabs/afls-for-claude/skills/lsc-health-check/SKILL.md

lsc-health-check

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

For health check guidance, call search_lsc_knowledge({ query: "health check configuration" }) to get sourced documentation. This skill activates when users ask about org health, configuration status, or want a general assessment of their LSC setup. After a health check, common next steps include: - /lsc:audit for detailed validation rule checks - toggle_trigger_handler to enable missing handlers - assign_permission_set to fix user access - /lsc:generate-metadata-cache to refresh mobile cache

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run the health_check tool to get a comprehensive assessment

    line 16
  2. Distinctive:

    Territory Model: No active territory model means territory features are broken

    line 28
  3. Distinctive:

    After a health check, common next steps include:

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

For health check guidance, call search_lsc_knowledge({ query: "health check configuration" }) to get sourced documentation.

Life Sciences Cloud (LSC) Health Check

This skill activates when users ask about org health, configuration status, or want a general assessment of their LSC setup.

When to Activate

  • User asks "Is my org set up correctly?" or "Check my org health"
  • User asks about missing configuration or setup issues
  • User wants to verify their LSC deployment is complete
  • User is preparing for a go-live or deployment

Steps

  1. Run the health_check tool to get a comprehensive assessment
  2. Present findings organized by severity (errors first, then warnings, then info)
  3. For each issue, explain:
    • What it means in business terms
    • The impact if not fixed
    • How to resolve it (with specific tool/command references)
  4. Offer to fix issues using the appropriate tools

Key Areas Checked

  • Trigger Handlers: Inactive handlers that may prevent LSC features from working
  • Permission Sets: Missing LSC permission set licenses that prevent user access
  • Territory Model: No active territory model means territory features are broken
  • DB Schema: Missing records mean mobile app won't sync data
  • Mobile Cache: Stale cache means recent config changes aren't reflected on mobile

Follow-up Actions

After a health check, common next steps include:

  • /lsc:audit for detailed validation rule checks
  • toggle_trigger_handler to enable missing handlers
  • assign_permission_set to fix user access
  • /lsc:generate-metadata-cache to refresh mobile cache

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.