skills/profile/SKILL.md
AE professional identity and context used for personalized output across all commands
npx skillsauth add chieflatif/SalesSidekick-Claude-CoWork profileInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Tier 3 — This entire file is regenerated during /setup Phase 1-2 based on the AE's identity, company, and territory context.
Contains the AE's complete professional identity: who they are, what they sell, their territory, their qualification gates, and their operating rhythm. This skill fires on nearly every session because it provides the foundational context for all other operations.
Name: {{AE_NAME}} Title: {{AE_TITLE}} Company: {{COMPANY}} ({{COMPANY_URL}}) Manager: {{MANAGER_NAME}} Team: {{TEAM_NAME}} Region: {{REGION}}
Primary Product: {{PRIMARY_PRODUCT}} Additional Products: {{SECONDARY_PRODUCTS}} Description: {{PRODUCT_DESCRIPTION}}
Territory Type: {{TERRITORY_TYPE}} Territory Size: {{TERRITORY_SIZE}} accounts Quota: {{QUOTA_AMOUNT}} Fiscal Year Start: {{FISCAL_YEAR_START}} Average Deal Size: {{AVERAGE_DEAL_SIZE}} Average Sales Cycle: {{SALES_CYCLE_LENGTH}} CRM: {{CRM_SYSTEM}}
Target Industry: {{ICP_INDUSTRY}} Target Size: {{ICP_SIZE}} Target Use Case: {{ICP_USE_CASE}}
After /setup, these are customized to your specific market and selling motion.
Default signals (pre-/setup):
After /setup, these are customized to your specific disqualification patterns.
Default signals (pre-/setup):
Daily:
/today — tasks + deals needing attention/prep [Company] — intel brief/closeout — 6-Output Framework processing/end-of-day — review and previewWeekly:
/weekly — territory pipeline summary/forecast-update — CRM forecastAs needed:
/strategy, /battle, /pov for deal strategy/pipeline, /whitespace for territory management/research, /outreach, /email for account engagementAfter /setup, this section captures how the AE thinks, processes information, and makes decisions.
Default (pre-/setup):
On the first run of /deck, the user is asked how they prefer presentations (data-heavy, narrative, or visual). The preference is stored here:
This preference informs template selection and slide content density for all future /deck calls.
testing
PptxGenJS pipeline for generating native .pptx presentations with brand tokens, 5 deck templates, and visual QA
development
LinkedIn content framework with 3-Type post structure, hook formulas, cadence goals, and 6-point pre-publish checklist
documentation
Central reference for all Notion database schemas, read/write patterns, account resolution logic, and write failure handling
tools
8-element MEDDPICC qualification scoring rubric with Red/Yellow/Green definitions and discovery questions