Add knowledge about the Salesforce org to the shared knowledge base. Use when the user wants to document custom objects, fields, naming conventions, known issues, or SOQL patterns.
From salesforce-skillnpx claudepluginhub alephventures/alephventures-claude-skills --plugin salesforce-skillThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.
You help users add knowledge about their Salesforce org to the shared knowledge base. This knowledge is stored in markdown files under the knowledge/ directory and shared with the whole team via git.
This skill is invoked with /sf-teach followed by what the user wants to document.
Examples:
/sf-teach the Opportunity object has a custom field Deal_Score__c that rates deals 1-5/sf-teach our naming convention for custom objects is [Team]_[Entity]__c/sf-teach there's a known issue where Lead conversion fails if Custom_Status__c is blank/sf-teach the Project__c object has a lookup to Account and a master-detail to Program__cParse the user's input to determine:
Map the knowledge to one of these files:
| Category | File | When to use |
|---|---|---|
| Custom objects, relationships | knowledge/org-structure/objects.md | Object definitions, lookups, master-detail, junction objects |
| Custom fields, picklists | knowledge/org-structure/fields.md | Field definitions, formulas, validation rules |
| Record types, processes | knowledge/org-structure/record-types.md | Record types, page layouts, business processes |
| SOQL patterns | knowledge/best-practices/soql-patterns.md | Queries that work well, query optimizations |
| Data model conventions | knowledge/best-practices/data-model.md | How data is structured, conventions |
| Naming conventions | knowledge/best-practices/naming-conventions.md | API name patterns, label conventions |
| External integrations | knowledge/integrations/api-notes.md | Connected apps, API endpoints, sync notes |
| Known issues, workarounds | knowledge/troubleshooting/common-issues.md | Bugs, gotchas, workarounds |
If the knowledge doesn't fit any category, ask the user which is the closest fit or suggest creating a new file.
Read the target file to understand its current structure and content. Avoid duplicating information that's already documented.
Add the new knowledge in this consistent format:
### [Brief Title]
[Description of the knowledge, pattern, or insight]
[If applicable, include code examples, SOQL queries, or field API names]
> Added by [username] on [date]
Use the Edit tool to append the entry at the end of the appropriate section in the file. Maintain the existing heading hierarchy.
After adding the entry:
Don't forget to commit and push so your team gets this knowledge:
git add knowledge/
git commit -m "knowledge: [brief description]"
git push
Custom_Object__c) alongside labels