agentleFS
SalesforceLabsSalesforceLabs/afls-for-claude/skills/lsc-key-account-management/SKILL.md

lsc-key-account-management

Skill10 starsChanged 29 days agoApache-2.0View on GitHub

Guides Life Sciences Cloud (LSC) Key Account Management (KAM) configuration for web and mobile apps. Use when user asks about account plans, KAM account plan templates, goal definitions, action plan templates, assessment tasks, account plan stakeholders, account plan participants, SWOT analysis, territory business plans, or AccountPlan/GoalDefinition/ActionPlanTemplate/AccountPlanObjective/AccountPlanStakeholder objects.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 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.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always call MCP tools to get sourced documentation: Do not answer from general knowledge alone.

    line 8
  2. Distinctive:

    Always include the citation line from the tool response in your answer.

    line 22
  3. Distinctive:

    When the user asks about configuring or enabling a KAM feature, ask them which mode they prefer:

    line 28
  4. Distinctive:

    Default to guided setup when connected to an org, or documentation mode if no org is connected.

    line 33
  5. Very specific:

    DO NOT: use run_soql for Admin Console settings — use list_admin_settings

    line 78
  6. Very specific:

    DO NOT: use run_soql for mobile cache — use check_mobile_cache_status()

    line 79
  7. Very specific:

    Must be linked to a GoalDefinition via ActionPlanTemplateAssignment

    line 92

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

How to Answer KAM Questions

Always call MCP tools to get sourced documentation. Do not answer from general knowledge alone.

User asks about...Call this tool
KAM concepts, setup, best practicesget_lsc_module_docs({ module: "key-account-management" })
Specific KAM topic (templates, stakeholders, etc.)search_lsc_knowledge({ query: "<topic>" })
Admin Console KAM settingslist_admin_settings({ category: "KAM" })
Trigger handler statuslist_trigger_handlers()
Object fields and relationshipsdescribe_sobject({ sobject: "AccountPlan" })
KAM data in the orgrun_soql({ query: "SELECT ... FROM AccountPlan ..." })
Goal definition templatesrun_soql({ query: "SELECT ... FROM GoalDefinition WHERE Category = 'Library' AND Status = 'Active' AND Type = 'Affiliate'" })
Action plan templatesrun_soql({ query: "SELECT ... FROM ActionPlanTemplate WHERE Type = 'Key Account Management'" })
Mobile cache statuscheck_mobile_cache_status()

Always include the citation line from the tool response in your answer.


Configuration Mode

When the user asks about configuring or enabling a KAM feature, ask them which mode they prefer:

  1. Show me the documentation — call get_lsc_module_docs({ module: "key-account-management" }) and present the relevant sections
  2. Walk me through it — configure it directly in their org step-by-step (guided setup below)

Default to guided setup when connected to an org, or documentation mode if no org is connected.

Guided Setup Workflow

Step 1: Check Current State

list_trigger_handlers()
list_admin_settings({ category: "KAM" })

Step 2: Report Findings

Present a summary table of what's configured vs what's missing/disabled.

Step 3: Propose Changes

For each issue found, propose the fix and wait for user confirmation.

Step 4: Apply Changes (with user confirmation)

toggle_trigger_handler({ handlerName: "KAMTriggerHandler", active: true })
update_admin_setting({ recordId: "...", fields: { ... } })

Step 5: Verify

Re-run checks from Step 1 to confirm everything is configured correctly.


Tool Usage Rules

Correct Object Names

CorrectWrong (NEVER use)
AccountPlanKamAccountPlan, AccountPlan__c, KAMPlan__c, KeyAccountPlan__c
AccountPlanObjectiveKamAccountPlanObjective, AccountObjective__c, PlanObjective__c, KAMObjective__c
GoalDefinitionGoalTemplate__c, ObjectiveTemplate__c, GoalDefinition__c
ActionPlanTemplateTacticTemplate__c, ActionTemplate__c, ActionPlanTemplate__c
AssessmentTaskTask__c, AssessmentTask__c, Todo__c
AccountPlanStakeholderKamAccountPlanStakeholder, KAMStakeholder__c, AccountPlanStakeholder__c
AccountPlanParticipantKamAccountPlanParticipant, PlanParticipant__c, TeamMember__c
AccountPlanProductKamAccountPlanProduct, KAMProduct__c
AccountPlanRelationshipKamRelatedAccountPlan
AccountPlanRelaObjAnalysisKamAccountPlanObjectAnalysis
ActionPlanTemplateAssignment—

Tool Restrictions

  • DO NOT use run_soql for Admin Console settings — use list_admin_settings
  • DO NOT use run_soql for mobile cache — use check_mobile_cache_status()
  • DO NOT suggest OmniStudio/FlexCard/OmniScript for mobile — NOT available on LSC Mobile iPad app

GoalDefinition Template Requirements

For a GoalDefinition to appear as an importable template, ALL three fields must be set:

  • Type = Affiliate (required for downstream template usage)
  • Status = Active
  • Category = Library

ActionPlanTemplate Requirements

For an ActionPlanTemplate to appear in account plan import:

  • Type = Key Account Management
  • Target Objective = Account Plan Objective (NOT Territory Business Plan Objective)
  • Must be linked to a GoalDefinition via ActionPlanTemplateAssignment

Troubleshooting

  • Related Account Plans (or any KAM related list) renders blank on mobile — On the iPad app a related-list tab shows no card header, no New button, and no rows once the parent has ≥1 child, and often reproduces on one record but not another. This is a page-layout issue, not a data or cache issue: force:relatedListSingleContainer with relatedListComponentOverride = NONE inherits its columns from the parent's RecordType page layout, and a record type whose layout omits that related list blanks the whole container. See the "Mobile Related List Renders Blank (force:relatedListSingleContainer)" section in the lsc-troubleshoot skill for the full diagnose steps and both fixes.

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.