Jonathan0516/sales-agent-skills

13 skills

• awesome-list-submit

  Submit a NetMind project (default NarraNexus) into an awesome-* GitHub list via a fully-automated fork→PR flow. Reads the target repo's README, adapts the entry to its format from a canonical press kit, places the image when supported, and opens a PR after a review gate. Use when the user wants to add/promote a project to an awesome list, submit to awesome-ai-agents or similar, or run a listing campaign.

  Reaches the webActs undeclared656 words
• cold-email

  Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement. For delivering the message on LinkedIn or Gmail and managing replies and follow-ups afterwards, see sales.

  Self-containedInstructions only1,006 words
• competitor-profiling

  When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.

  Self-containedActs undeclared1,958 words
• customer-research

  When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

  Reaches the webInstructions only2,123 words
• directory-submissions

  When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.

  Reaches the webInstructions only3,464 words
• launch

  When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas. For the offer being launched (bonuses, guarantees, scarcity, naming), see offers.

  Self-containedInstructions only2,214 words
• linkedin-post

  Draft and optionally publish LinkedIn posts for NetMind products or announcements from source URLs, notes, or product context. Use when the user wants LinkedIn copy, a first comment with tracked link, a reviewable markdown draft, or headed LinkedIn publishing after explicit approval.

  Reaches the webActs undeclared314 words
• marketing-loops

  When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.

  Self-containedInstructions only1,294 words
• product-marketing

  When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.

  Self-containedInstructions only1,323 words
• prospecting

  When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling. For finding and messaging the actual people at a target company (LinkedIn/Gmail) and running the follow-up conversation, see sales.

  Reaches the webActs undeclared2,418 words
• sales

  Run outbound sales end to end inside the user's logged-in Chrome (Claude in Chrome) — find the right people at a target company on LinkedIn, reach out (LinkedIn DM / connection note, or email via Gmail), then watch Gmail and LinkedIn for replies, keep every conversation going, and follow up on a cadence with a pipeline file per prospect. Use when the user says "sell <product> to <company>," "find people at <company> and reach out," "LinkedIn outreach," "建联," "触达," "找某公司的人," "领英私信," "check replies," "did anyone reply," "监控回复," "监听回复," "持续对话," "跟进," "有人回我了吗," "sales pipeline," or wants prospecting/cold-email output turned into real conversations. Dry run by default; never clicks Send without explicit per-message confirmation. For building the company list see prospecting; for email copy rules see cold-email; for collateral after interest see sales-enablement.

  Reaches the webActs undeclared1,900 words
• sales-enablement

  When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers.

  Self-containedInstructions only2,165 words
• x-kol

  Research X/Twitter KOLs from a provided account list or by topic discovery, save traceable intermediate data in the current working directory, and export a strict collaboration workbook. Use for X KOL screening workflows that only count article/post content and exclude quote, note, reply, retweet, and thread continuation.

  Reaches the webActs undeclared352 words