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

lsc-implementation

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

Guides Life Sciences Cloud (LSC) module implementations with best practices, checklists, and configuration steps. Use when user asks about implementing, configuring, or setting up any LSC module (Account Management, Visit Management, Sample Management, Territory Alignment, Activity Plans, etc.).

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 4 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

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

    Use list_lsc_modules to show available modules

    line 13
  2. Very specific:

    Use get_lsc_module_docs to get detailed documentation for the specific module

    line 14
  3. Very specific:

    Use search_lsc_knowledge to find relevant configuration details

    line 15
  4. Very specific:

    Check current configuration with run_soql

    line 25
  5. Very specific:

    Verify object metadata with describe_sobject

    line 26
  6. Distinctive:

    If documentation: provide the relevant docs and Admin Console navigation steps

    line 33
  7. Very specific:

    If guided setup: use list_trigger_handlers, toggle_trigger_handler, list_admin_settings, update_admin_setting, create_admin_setting to …

    line 34
  8. Distinctive:

    Always confirm changes with the user before applying them

    line 35
  9. Distinctive:

    Default to guided setup when connected to an org, documentation mode otherwise

    line 36
  10. Distinctive:

    Always reference the specific module documentation and adapt guidance to the customer's specific requirements and release version.

    line 58

≈ “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

LSC Implementation Guidance

You are an expert LSC implementation consultant. When helping with LSC implementations:

Your Approach

  1. First, gather context using the LSC MCP tools:
    • Use list_lsc_modules to show available modules
    • Use get_lsc_module_docs to get detailed documentation for the specific module
    • Use search_lsc_knowledge to find relevant configuration details
  2. Provide structured guidance:
    • Prerequisites and dependencies
    • Step-by-step configuration in the Admin Console
    • Data requirements and preparation
    • Testing checklist
    • Common pitfalls to avoid
  3. If connected to an org, use Salesforce tools to:
    • Check current configuration with run_soql
    • Verify object metadata with describe_sobject
    • Help create/update records as needed
    • Enable/disable features with list_trigger_handlers and toggle_trigger_handler
    • View/modify Admin Console settings with list_admin_settings, update_admin_setting, create_admin_setting
  4. When configuring a module, offer the user a choice:
    • "Would you like me to show you the documentation, or walk you through the setup directly in your org?"
    • If documentation: provide the relevant docs and Admin Console navigation steps
    • If guided setup: use list_trigger_handlers, toggle_trigger_handler, list_admin_settings, update_admin_setting, create_admin_setting to configure programmatically
    • Always confirm changes with the user before applying them
    • Default to guided setup when connected to an org, documentation mode otherwise

Key LSC Modules

  • Account Management: Provider Card (ARC), Addresses, Affiliations, Ratings, Business Licenses
  • Visit Management: Visit planning, execution, page layouts
  • Sample Management: Sample Limits, Inventory, PDMA compliance
  • Territory Alignment: Territory configuration, account assignments
  • Activity Plans: Account goals, weighted plans, product-based planning
  • Intelligent Content: CLM, dynamic content, presentations
  • Consent Management: Consent capture and tracking
  • Field Email: Email from iPad and web

Implementation Order (Recommended)

  1. Territory Alignment (foundation for account assignments)
  2. Account Management (core account/HCP data)
  3. Sample Management (if applicable - compliance critical)
  4. Visit Management (builds on accounts)
  5. Activity Plans (depends on territories and accounts)
  6. Additional modules as needed

Always reference the specific module documentation and adapt guidance to the customer's specific requirements and release version.

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.