All authors

Claude Skills by PranavNagrecha
github.com/PranavNagrecha1,088 skills0 installs2,308 views
- Analytics Security ArchitectureUse this skill when designing or auditing CRM Analytics (formerly Einstein Analytics / Tableau CRM) data access controls: row-level security predicates, dataset-level visibility, app-level sharing roles, sharing inheritance configuration, and cross-dataset security embedding strategies. Trigger keywords: CRM Analytics security, row-level security predicate, Analytics dataset access, sharing inheritance, security predicate design, cross-dataset security, analytics entitlement dataset. NOT for ...Votes: 0GitHub stars: 15
- Api Led Connectivity ArchitectureUse this skill when designing API-led connectivity architecture for Salesforce integrations — covering System/Process/Experience layer separation, governance policy (catalog, versioning, deprecation, rate limits), multi-consumer strategy, and Agentforce Agent Fabric integration. Trigger keywords: API-led connectivity, MuleSoft three-tier, System API, Process API, Experience API, integration layer governance, API versioning policy, Agent Fabric. NOT for Salesforce's own place in the layered mo...Votes: 0GitHub stars: 15
- Architecture Decision RecordsAuthor and maintain Architecture Decision Records (ADRs) for Salesforce implementations: capture chosen approach, rejected alternatives, constraints, and consequences. Trigger keywords: adr, architecture decision record, design decision log, technical decision. NOT for making the design decision itself, e.g. Flow vs Apex — use architect/solution-design-patterns. NOT for a formal architecture review that produces findings — use architect/well-architected-review.Votes: 0GitHub stars: 15
- B2b Vs B2c ArchitectureUse this skill when designing or evaluating the architecture of a Salesforce Commerce implementation that involves choosing between B2B Commerce (on Core, Lightning platform) and B2C Commerce (Salesforce Commerce Cloud / SFCC). Trigger keywords: B2B vs B2C architecture, SFCC vs B2B Commerce, Commerce Cloud platform decision, B2B data model architecture, B2C storefront architecture, commerce infrastructure comparison, platform selection architecture. NOT for implementation mechanics — use admi...Votes: 0GitHub stars: 15
- Banking Lending ArchitectureArchitecture guidance for Salesforce FSC banking and Digital Lending: loan origination platform design, ResidentialLoanApplication data model, payment processing integration patterns, and account servicing workflow architecture. NOT for FSC Insurance policy, claims or underwriting architecture — use architect/insurance-cloud-architecture. NOT for the FSC data-model choice and Compliant Data Sharing design — use architect/fsc-architecture-patterns.Votes: 0GitHub stars: 15
- Case Deflection StrategyUse this skill when designing or assessing a Salesforce case deflection program — identifying high-frequency contact reasons, selecting deflection channels, and defining KPIs such as deflection rate and goal completion rate. Trigger keywords: case deflection, self-service, Einstein Conversation Mining, chatbot containment, knowledge-led deflection, contact reason analysis. NOT for the self-service portal UX, search experience and case-form design — use admin/self-service-design. NOT for end-t...Votes: 0GitHub stars: 15
- Ci Cd Pipeline ArchitectureUse when designing or reviewing the end-to-end stage sequence, promotion strategy, and quality gates for a Salesforce CI/CD pipeline. Trigger keywords: pipeline stages, promotion strategy, quality gate, deployment gate, CI validation sandbox, staging environment, pipeline design, release strategy, rollback strategy, environment topology. NOT for configuring an individual CI tool (GitHub Actions, GitLab CI, Jenkins) — use devops/github-actions-for-salesforce or devops/gitlab-ci-for-salesforce....Votes: 0GitHub stars: 15
- Cloud Specific Deployment ArchitectureDeployment architecture quirks per Salesforce cloud: Industries (OmniStudio), Marketing Cloud (MC packages), Commerce Cloud, Data Cloud, Agentforce. What ships via metadata API, what ships via cloud-specific tools, ordering, dependencies. NOT for building the OmniStudio DataPack pipeline itself — use omnistudio/omnistudio-ci-cd-patterns. NOT for the generic CI/CD pipeline, branch strategy or Copado-vs-Gearset choice — use architect/deployment-automation-architecture.Votes: 0GitHub stars: 15
- Commerce Integration PatternsUse this skill when designing or diagnosing end-to-end integration between Salesforce B2B or D2C Commerce and external systems — including ERP pricing/inventory, PIM product sync, payment gateways, shipping providers, tax engines, and order management systems (OMS). Covers CartExtension Apex namespace (PricingCartCalculator, ShippingCartCalculator, InventoryCartCalculator), RegisteredExternalService custom metadata, payment gateway architecture, and Product2 External ID patterns. NOT for Comm...Votes: 0GitHub stars: 15
- Composable Commerce ArchitectureComposable commerce on Salesforce: headless API layer, micro-frontends, BFF pattern, CDN strategy, third-party composability over B2C/B2B Commerce. NOT for the supported PWA Kit on Managed Runtime composable storefront — use architect/headless-commerce-architecture. NOT for standard B2C storefront setup — use admin/b2c-commerce-store-setup.Votes: 0GitHub stars: 15
- Conversational Ai ArchitectureUse when designing or evaluating a Salesforce conversational AI deployment that involves Agentforce agents, Einstein Bots, or a combination of both. Triggers: Agentforce topic design, Einstein Bot handoff to Agentforce, multi-agent orchestration, conversational channel routing, Atlas Reasoning Engine behavior, design an Agentforce agent alongside our Einstein Bot. NOT for Einstein Bot dialog and NLU design — use architect/einstein-bot-architecture. NOT for cutting an existing bot over to Agen...Votes: 0GitHub stars: 15
- Cpq Architecture PatternsCPQ solution architecture covering bundle design, pricing engine performance, multi-currency strategy, and integration patterns. Trigger keywords: CPQ architecture, quote scalability, bundle design, QCP performance, CPQ integration, large quote, pricing waterfall, ServiceRouter. NOT for a quote that already calculates slowly or times out — use data/cpq-performance-optimization. NOT for configuring individual Price Rules or Discount Schedules — use admin/cpq-pricing-rules.Votes: 0GitHub stars: 15
- Cpq Integration With ErpUse this skill when designing or troubleshooting an integration between Salesforce CPQ and an ERP system (SAP, Oracle, NetSuite, Microsoft Dynamics). Covers the canonical order transmission trigger, pricing data mastery strategy, amendment delta-quantity handling, and non-blocking inventory checks during quoting. NOT for syncing standard Accounts, Products or Orders with an ERP in an org without CPQ — use architect/sales-cloud-integration-patterns. NOT for moving CPQ Price Rules and quote tem...Votes: 0GitHub stars: 15
- Cpq Vs Standard Products DecisionUse when deciding whether to implement Salesforce CPQ or stay with standard Products and Pricebooks for quoting and pricing. Triggers: 'should we buy CPQ or use standard pricebooks', 'is CPQ worth the cost for our quoting process', 'product bundling without CPQ', 'guided selling vs manual product selection', 'complex pricing rules or multi-dimensional discounting'. NOT for designing bundles, the pricing waterfall or QCP once CPQ is chosen — use architect/cpq-architecture-patterns. NOT for pic...Votes: 0GitHub stars: 15
- Crm Analytics Vs Tableau DecisionUse when deciding between CRM Analytics (formerly Einstein Analytics / Tableau CRM) and Tableau Desktop, Tableau Server, or Tableau Cloud for a Salesforce-centric analytics requirement. Triggers: 'CRM Analytics vs Tableau', 'which BI tool for Salesforce', 'Tableau for Salesforce data', 'Einstein Analytics vs Tableau', 'analytics platform decision', 'licensing comparison CRM Analytics Tableau', 'Tableau Next', 'Tableau+ for Salesforce'. NOT for implementation guidance on configuring CRM Analyt...Votes: 0GitHub stars: 15
- Cross Cloud Data DeploymentCross-cloud data deployment: designing the data handoff when an implementation spans Sales Cloud, Service Cloud, Marketing Cloud, Data Cloud, Commerce Cloud. Shared keys, identity resolution, sync vs event, CDC, Data Cloud as hub. NOT for configuring the Data Cloud identity-resolution ruleset itself — use admin/data-cloud-identity-resolution. NOT for designing Data Cloud DMOs and their relationships — use data/data-cloud-data-model-objects. NOT for integration pattern selection — use the inte...Votes: 0GitHub stars: 15
- Customer Effort ScoringDesigning a customer experience measurement strategy using CSAT, NPS, and CES metrics in Salesforce Feedback Management: metric selection, survey timing, Feedback Management license requirements, Flow-triggered survey delivery, and CX KPI integration into Service Analytics dashboards. Use when choosing which CX metric to deploy, defining survey timing rules, or connecting survey response data to operational KPIs. NOT for building or configuring the technical survey objects, flows, or email te...Votes: 0GitHub stars: 15
- Data Cloud ArchitectureUse when designing or evaluating a Data Cloud implementation architecture — covering data lake strategy (DSO/DLO/DMO layers), identity resolution rule design, activation target configuration, and segmentation strategy. Trigger phrases: Data Cloud architecture design, identity resolution strategy, activation target setup, data lakehouse layers, unified profile design, Data Cloud segment activation, DMO mapping strategy, golden profile design. NOT for configuring a data stream, DLO-to-DMO mappi...Votes: 0GitHub stars: 15
- Data Cloud Vs Analytics DecisionUse when choosing or explaining how Salesforce Data Cloud (Data 360) and CRM Analytics (Tableau CRM / Einstein Analytics) fit together versus overlap — unified data platform vs analytics consumption, Direct Data on Data Model Objects (DMOs), identity and activation vs dashboards and recipes. Triggers: 'Data Cloud vs CRM Analytics', 'when to use Data Cloud versus Einstein Analytics', 'should we buy Data Cloud or CRM Analytics', 'CRM Analytics on Data Cloud DMOs', 'direct data connector Data Cl...Votes: 0GitHub stars: 15
- Deployment Automation ArchitectureDeployment automation architecture on Salesforce: pipeline orchestration, branch strategy, environment topology, quality gates, release trains. Selecting between Copado, Gearset, Flosum, and native SFDX + GitHub Actions. NOT for cloud-specific deploy mechanics (Industries, Marketing Cloud, Data Cloud) — use architect/cloud-specific-deployment-architecture. NOT for CI/CD tool tutorials.Votes: 0GitHub stars: 15
- Einstein Bot ArchitectureUse when designing conversational AI architecture on Salesforce: Einstein Bot dialog design, Agentforce Agent topic planning, intent models, NLU training strategy, bot-to-agent handoff, escalation paths, knowledge article surfacing, and bot analytics. Triggers: 'einstein bot architecture', 'agentforce dialog design', 'bot handoff to agent', 'intent model training'. NOT for multi-agent orchestration or Atlas Reasoning Engine behavior - use architect/conversational-ai-architecture. NOT for the ...Votes: 0GitHub stars: 15
- Embedded Analytics ArchitectureUse this skill to architect CRM Analytics dashboard embedding in Lightning pages, Experience Cloud, or Visualforce — covering dashboard context strategy, filter/state management, cross-dashboard context propagation, performance optimization, and LWC vs Aura component selection. Trigger keywords: embed CRM Analytics dashboard, embedded analytics Lightning page, analytics dashboard filter, wave dashboard LWC, analytics state attribute. NOT for a custom LWC inside a dashboard canvas - use archit...Votes: 0GitHub stars: 15
- Event Driven ArchitectureUse when making architectural style decisions about whether and how to adopt event-driven architecture (EDA) for a Salesforce solution — including selecting a bus pattern, deciding between choreography and orchestration, designing event schema, and evaluating event sourcing feasibility. Triggers: 'should we use event-driven architecture or request-reply for this integration', 'designing an event mesh for Salesforce enterprise integration', 'choreography vs orchestration for our multi-system w...Votes: 0GitHub stars: 15
- Experience Cloud Integration PatternsUse when designing or reviewing integrations between an Experience Cloud site and external systems — SSO identity providers, third-party widgets, external content sources, and behavioral data platforms. Triggers: 'integrate SSO with Experience Cloud site', 'embed third-party chat widget in LWR site', 'connect Data Cloud to Experience Cloud', 'inject Google Tag Manager into Experience Cloud', 'configure SAML for community login', 'allow external IdP login on portal'. NOT for internal Salesforc...Votes: 0GitHub stars: 15
- Experience Cloud Licensing ModelUse this skill to select the correct Experience Cloud external user license type for a portal or community. Trigger keywords: Customer Community vs Partner Community, login-based vs member-based license, External Apps license, external user license selection, Experience Cloud license tiers. NOT for adding members, self-registration or login pages — use admin/experience-cloud-member-management. NOT for bulk-migrating existing portal users between license types — use data/community-user-data-mi...Votes: 0GitHub stars: 15
- Experience Cloud PerformanceUse when diagnosing slow Experience Cloud site load times, planning CDN and caching strategy, optimizing page weight, or advising on component loading patterns for Aura and LWR-based sites. Trigger phrases: 'Experience Cloud site loads slowly', 'CDN cache not updating after publish', 'LWR site stale after deployment', 'too many Apex calls on Experience Cloud page', 'browser caching Experience Builder', 'CDN configuration Experience Cloud', 'how to reduce page load time community site', 'Exper...Votes: 0GitHub stars: 15
- Fhir Integration ArchitectureUse this skill when architecting how Health Cloud connects to external EHR/EMR systems via FHIR R4 — integration pattern selection, transformation layer design, MuleSoft Accelerator usage, and EMR bidirectional sync topology. NOT for writing the FHIR calls or HL7 v2 conversion in Apex — use apex/fhir-integration-patterns. NOT for mapping a FHIR resource to an object — use data/fhir-data-mapping.Votes: 0GitHub stars: 15
- Fsc Architecture PatternsUse when designing or reviewing a Financial Services Cloud (FSC) solution architecture covering data model selection, Compliant Data Sharing design, integration strategy, and compliance framework alignment. Triggers: 'should I use the managed-package FSC data model or the platform-native model', 'how do I design Compliant Data Sharing for cross-team visibility in FSC', 'FSC integration architecture with core banking', 'which data model does FSC use for households and financial accounts'. NOT ...Votes: 0GitHub stars: 15
- Fsl Integration PatternsUse this skill when designing FSL integrations: ERP parts/inventory sync, GPS/fleet management integration, IoT-triggered work order creation, and customer notification workflows. Trigger keywords: FSL ERP integration, ProductConsumed ERP sync, GPS fleet integration FSL, IoT work order trigger, customer notification FSL integration. NOT for Financial Services Cloud integration design — use architect/fsc-architecture-patterns. NOT for bulk-loading Work Order and Service Appointment history — u...Votes: 0GitHub stars: 15
- Fsl Multi Region ArchitectureUse this skill when designing FSL for multiple geographic regions or timezones: territory timezone configuration, cross-territory resource assignment, and concurrent optimization serialization. Trigger keywords: multi-region FSL, FSL timezone territories, cross-territory resource scheduling, concurrent optimization territories, international FSL deployment. NOT for choosing an optimization mode or fixing Global optimization timeouts — use architect/fsl-optimization-architecture. NOT for creat...Votes: 0GitHub stars: 15
- Fsl Offline ArchitectureUse this skill when designing FSL Mobile offline-first architecture: data priming strategy, priming limits, conflict resolution patterns, and sync failure handling. Trigger keywords: FSL offline priming, briefcase sync FSL, offline data limits, conflict resolution MERGE_ACCEPT_YOURS, ghost records FSL. NOT for offline in the standard mobile app — use lwc/lwc-mobile-offline-and-briefcase. NOT for installing, branding or extending the FSL mobile app — use admin/fsl-mobile-app-setup.Votes: 0GitHub stars: 15
- Fsl Optimization ArchitectureUse this skill when designing or evaluating the FSL scheduling engine architecture: optimization mode selection (Global/In-Day/Resource/Reshuffle), ESO adoption strategy, territory sizing for optimization, and fallback planning. Trigger keywords: FSL optimization engine, ESO enhanced scheduling, global optimization timeout, in-day optimization, OAAS architecture, territory optimization design. NOT for tuning an optimization run in Setup — use admin/fsl-scheduling-optimization-design. NOT for ...Votes: 0GitHub stars: 15
- Fundraising Integration PatternsUse this skill when connecting a Salesforce Nonprofit Cloud or NPSP org to fundraising-adjacent systems: payment gateways via Salesforce.org Elevate, wealth screening tools (iWave, DonorSearch), email marketing platforms (Marketing Cloud, Pardot), and event management platforms. Trigger keywords: payment gateway nonprofit, Elevate payment services, GiftTransaction API, wealth screening integration, iWave Salesforce, DonorSearch scores, donor email marketing sync, event registration fundraisin...Votes: 0GitHub stars: 15
- Government Cloud ComplianceUse when architecting or assessing a Salesforce Government Cloud org — covering FedRAMP High authorization, Hyperforce GovCloud on AWS GovCloud regions, GovCloud Plus feature set, data residency and US-only data processing, FISMA continuous monitoring, CMS ARC-AMPE controls, NIST 800-53 control mapping, compliance automation patterns, DoD IL2/IL4/IL5 considerations, and multi-org architecture in government deployments. Triggers: FedRAMP, Government Cloud, GovCloud Plus, Hyperforce government,...Votes: 0GitHub stars: 15
- Ha Dr ArchitectureDesigning high availability and disaster recovery strategies for Salesforce: Trust site monitoring, backup strategies, cross-region considerations, business continuity planning, RTO/RPO target definition, and failover patterns for integrations. Use when designing org resilience architecture, planning for outages, or defining recovery objectives, or when asked to write a Salesforce DR runbook. NOT for picking a backup product or restore mechanics — use data/salesforce-backup-and-restore. NOT f...Votes: 0GitHub stars: 15
- Headless Commerce ArchitectureUse this skill when designing or evaluating a headless B2C Commerce storefront architecture — covering the Composable Storefront (PWA Kit on Managed Runtime), SCAPI-first API design, frontend framework selection, latency budgets, and caching strategy. NOT for standard SFRA storefronts, Experience Cloud headless CMS delivery, B2B Commerce architecture, or SCAPI implementation-level coding (use apex/headless-commerce-api for that).Votes: 0GitHub stars: 15
- Headless Vs Standard ExperienceUse when choosing between Headless, LWR (Lightning Web Runtime), or Aura as the Experience Cloud frontend architecture: performance tradeoffs, developer cost, migration readiness, and flexibility. Trigger keywords: headless vs LWR, LWR vs Aura, Experience Cloud architecture decision, site performance architecture, community site technology choice. NOT for building the chosen site — branding, domain, Experience Builder pages — use admin/experience-cloud-site-setup. NOT for LWR themes and custo...Votes: 0GitHub stars: 15
- Health Cloud Data ResidencyUse this skill when architecting Health Cloud orgs that must satisfy geographic data residency, HIPAA, GDPR, or national health-data regulations on Hyperforce — scoping the HIPAA BAA, mapping transient processing exceptions, and the features that require separate compliance addenda. NOT for choosing a Hyperforce region or planning a Hyperforce migration outside healthcare — use architect/hyperforce-architecture. NOT for Shield encryption and HIPAA technical safeguards — use architect/hipaa-co...Votes: 0GitHub stars: 15
- Health Cloud Multi Cloud StrategyUse this skill when designing the license model, cloud topology, and org structure for a Salesforce Health Cloud implementation that involves more than one Salesforce cloud product (Experience Cloud patient portals, OmniStudio engagement flows, Marketing Cloud care campaigns, or Service Cloud case management). Trigger keywords: Health Cloud multi-cloud, patient portal licensing, Health Cloud Experience Cloud add-on, OmniStudio Health Cloud PSL, Marketing Cloud HIPAA BAA healthcare, multi-clou...Votes: 0GitHub stars: 15
- High Volume Sales Data ArchitectureUse when designing or reviewing Salesforce orgs with large Opportunity and Account volumes, including archival strategy, report performance, data skew prevention, SOQL tuning for sales queries, and index planning. Triggers: 'opportunity table is slow', 'account ownership skew', 'sales report timing out', 'archive old opportunities'. NOT for org-wide LDV design on non-sales objects - use architect/large-data-volume-architecture. NOT for tuning one query or reading a Query Plan - use data/soql-...Votes: 0GitHub stars: 15
- Hipaa Compliance ArchitectureUse this skill to design HIPAA-compliant Salesforce org architectures for healthcare organizations storing or processing Protected Health Information (PHI). Trigger keywords: HIPAA BAA, PHI storage, Shield encryption, Health Cloud compliance, HIPAA technical safeguards, covered entity Salesforce architecture. NOT for minimum-necessary access design — use admin/hipaa-workflow-design. NOT for non-healthcare org security review — use architect/security-architecture-review.Votes: 0GitHub stars: 15
- Hybrid Integration ArchitectureUse this skill when designing hybrid on-premises-to-Salesforce integration architectures: DMZ relay patterns, reverse proxy configuration, VPN connectivity, and Salesforce Private Connect (AWS PrivateLink) topology. Trigger keywords: on-premises to Salesforce integration network topology, DMZ relay Salesforce, hybrid integration VPN, Private Connect architecture, data residency Salesforce hybrid, route Salesforce callouts privately to our data center. NOT for choosing the authentication mecha...Votes: 0GitHub stars: 15
- Hyperforce ArchitectureUse when an architect must plan a Hyperforce migration, choose a Hyperforce region, validate Hyperforce-only feature dependencies, or assess data-residency and IP-allowlisting impact. Triggers: 'hyperforce migration', 'hyperforce region selection', 'first-generation infrastructure to hyperforce', 'hyperforce ip allowlisting', 'data residency on hyperforce', 'hyperforce features not on first gen'. NOT for general HA/DR strategy (use architect/ha-dr-architecture), NOT for Salesforce Functions d...Votes: 0GitHub stars: 15
- Industries Cloud SelectionUse this skill when selecting which Salesforce Industries (vertical) cloud fits a customer's industry and requirements — evaluating data model compatibility, licensing implications, and customization vs configuration tradeoffs before committing to a vertical cloud; pre-purchase selection only, not configuration or OmniStudio development. Trigger keywords: which industry cloud should I use, Communications Cloud vs Health Cloud, Industries licensing, vertical cloud selection, Salesforce Industr...Votes: 0GitHub stars: 15
- Industries Data ModelReference guide for Salesforce Industries cloud data models: Insurance Cloud (InsurancePolicy hierarchy), Communications Cloud (Account record types, BillingAccount), Energy & Utilities (ServicePoint, ServiceContract), and Health Cloud (CarePlan, FHIR-aligned patient objects). NOT for Health Cloud clinical objects in depth, HC24 vs FHIR R4 — use data/health-cloud-data-model. NOT for insurance module licensing, claims and underwriting design — use architect/insurance-cloud-architecture.Votes: 0GitHub stars: 15
- Industries Integration ArchitectureUse when designing or reviewing the integration layer between Salesforce Industries clouds (Insurance, Communications, Energy & Utilities) and vertical backend systems such as policy administration systems, BSS/OSS platforms, or Customer Information Systems (CIS). NOT for calling a named Industries API (TMF679, InsurancePolicy Connect) — use omnistudio/industries-api-extensions. NOT for FSC data model or module licensing — use architect/insurance-cloud-architecture.Votes: 0GitHub stars: 15
- Insurance Cloud ArchitectureArchitecture guidance for Salesforce Insurance Cloud on FSC: module licensing strategy, policy administration object model, claims processing workflow design, underwriting rule integration, and channel routing. NOT for enabling insurance objects, coverage types or claim config in Setup — use admin/industries-insurance-setup. NOT for FSC retail banking and lending architecture — use architect/banking-lending-architecture.Votes: 0GitHub stars: 15
- Integration Framework DesignUse when designing a reusable integration layer in Salesforce that serves multiple external APIs through a shared callout infrastructure. Triggers: 'how to design a reusable integration layer in Salesforce', 'architect an Apex callout framework for multiple APIs', 'create a centralized error handling pattern for integrations', 'service interface pattern for external APIs', 'factory pattern for dynamic API resolution', 'centralized callout dispatcher'. NOT for individual API implementation (us...Votes: 0GitHub stars: 15
- Integration Security ArchitectureArchitecture-layer guidance for securing Salesforce integrations: mTLS mutual authentication, OAuth 2.0 flow selection, API gateway placement, IP allowlisting strategy on Hyperforce, and certificate lifecycle management. Trigger keywords: mTLS, mutual TLS, Hyperforce IP allowlisting, Salesforce Private Connect, certificate limit, integration authentication architecture. NOT for wiring mTLS onto one Named Credential — use integration/mutual-tls-callouts. NOT for Named Credential and External C...Votes: 0GitHub stars: 15
- Knowledge Taxonomy DesignUse when designing or restructuring a Salesforce Knowledge taxonomy: Data Category Group structure, hierarchy depth, article type selection, article lifecycle governance (Draft/Published/Archived), Validation Status gating, and content gap analysis via KCS methodology and Search Activity Gaps. Triggers: knowledge taxonomy design, data category hierarchy, knowledge article lifecycle, knowledge governance model, KCS content gap analysis, search activity gaps, knowledge category structure. NOT f...Votes: 0GitHub stars: 15