From taizen-gtm-skills
Identifies user role, team, and responsibilities from CRM, HR systems, enterprise search to set session context personalizing outputs for sales skills. Background skill runs silently without user invocation.
npx claudepluginhub taizen-ai/taizen-claude-plugins --plugin taizen-gtm-skillsThis skill uses the workspace's default tool permissions.
Automatically gather context about the current user to personalize all subsequent outputs.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Automatically gather context about the current user to personalize all subsequent outputs.
Identify the current user and gather context about their role, team, and responsibilities to personalize all subsequent interactions and outputs.
Note: This is a background skill that runs automatically when other skills need user context. It does not produce visible output and is not meant to be invoked directly by users.
The following skills automatically use session-context to personalize their outputs:
account-research - Adapts account briefs to user's rolediscovery-prep - Tailors prep materials to sales methodologysales-coaching - Personalizes coaching to rep's experience levelexecutive-briefings - Adjusts detail level based on senioritybuyer-profiles - Emphasizes relevant personas for user's dealscompetitive-intelligence - Focuses on relevant competitive scenariosemail-sequences - Adjusts tone for user's communication styleoutreach-templates - Personalizes based on user's territory/focusproduct-context - Provides product positioning and messaging that this skill uses alongside user contextfeedback-collector - Captures corrections to improve personalization accuracySetup: Connect these data sources to enable user context identification.
# SESSION CONTEXT DATA SOURCES
# Configure the sources for user identification
# Enterprise Search (searches across all internal sources)
- source: enterprise_search
connector: "{{GLEAN | MOVEWORKS | ELASTIC}}"
data:
- people_directory
- org_charts
- team_membership
# HR / Directory
- source: hr_system
connector: "{{WORKDAY | BAMBOOHR | RIPPLING}}"
data:
- employee_profiles
- job_titles
- departments
- managers
# CRM (for sales user context)
- source: crm
connector: "{{SALESFORCE | HUBSPOT}}"
data:
- user_records
- territory_assignments
- quota_data
Identify User: Search for the user's first and last name in available context (environment variables, git config, or ask if needed)
Determine Role: Based on user identification, determine:
Set Session Context: Store this context to inform all subsequent skill outputs:
user_name: Full name of the useruser_role: Job title/functionuser_team: Department or teamuser_seniority: Level (IC, Manager, Director, VP, C-level)user_focus_areas: Primary responsibilitiesThis skill is silent - it does not produce visible output to the user. Instead, it sets internal context that other skills will reference.
When context is successfully gathered, proceed with the user's original request using the established context.
If unable to determine user context, proceed with reasonable defaults for a GTM professional.