Results for “trigger”

Comprehensive competitor analysis, competitive intelligence, and comparison page creation. Use when analyzing competitive landscape, creating competitor comparison pages (alternative pages, vs pages, competitor A vs B pages), performing market research, building SWOT analysis, creating feature matrices, pricing comparisons, competitor teardowns, battle cards, or positioning maps. Covers research workflows, SEO-optimized comparison content, data-grounded reports with citations, 7-layer analysis framework, review mining, and sales enablement. Triggers include competitor analysis, competitive analysis, competitor teardown, vs page, alternative page, competitor comparison, market research, competitive intelligence, SWOT analysis, battle card, competitor pricing, market landscape, feature comparison, positioning map.

Re-onboard a churned customer with the same care they got the first time. Reads why they left and whether they left the door open, picks the ones worth winning back, and builds a warm re-onboarding sequence, not a "we miss you" discount blast. Built for any post-sale or growth team, customizable to your product and win-back window. Trigger on "win back churned customers", "re-engage a lost account", "build a win-back sequence", "which churned customers should we chase", "boomerang play", "re-onboard a customer who left", or any win-back question.

Turn a messy quarter into a GTM board update a director reads in two minutes. Leads with the number versus plan, surfaces the two or three things that actually matter, names the risks honestly instead of burying them, and ends with clear asks. Verdict first, short, no victory lap. Built for B2B GTM and revenue leaders, customizable to your metrics and your stack. Trigger on "write the board update", "GTM update for the board", "exec summary for the QBR", "what do I tell the board", "draft my leadership update", or any board or exec GTM write-up.

Audits any draft against Built GTM voice rules and returns specific, line-level violations with rewrites. Not a general style critique. A rule-based QA check. Every violation gets a specific fix. Trigger on "check this", "does this sound like me", "voice check", "is this on brand", "review this draft", "what's wrong with this", "flag the AI tells in this", "make sure this sounds like me", or any request to audit a draft against Heath's Built GTM voice before publishing. Can be used on posts, articles, newsletter editions, comments, or any Built GTM content.

Turn a pile of accounts into a stack-ranked priority list with a reason on every row. A layered score (gates first, then an evidence-weighted base rank over the signals you actually have, then bounded boosts for product usage and buyer intent) that stays fair across channels and never scores a blank field as a zero. Built for B2B GTM teams, customizable to your signals and your ICP. Trigger on "score these accounts", "rank by fit", "composite ICP score", "stack-rank my list", "who should I work first", "prioritize these leads", or any multi-signal account qualification.

Writes LinkedIn posts for Heath Barnett in the Built GTM voice. Five post types: Build Log (what I shipped + the receipt + the stack), Lens (GTM opinion — takes a position, no hedging), Scar (a mistake and what it cost), Field (what another operator is shipping), Signal (short forward-looking take). Trigger on "write a post about", "LinkedIn post on", "draft a post", "post idea", "turn this into a LinkedIn post", "help me write something about", or any request to create a LinkedIn post for Heath. Will not generate without a specific receipt or claim — asks for the detail first.

Turn scattered closed deals into a win/loss program that changes what you ship and what you say. Picks who to interview, gives you the question guide, codes themes across deals so a pattern beats a single anecdote, and turns the pattern into a specific messaging or product change. Built for B2B GTM, product, and RevOps leaders, customizable to your motion and your CRM. Trigger on "start a win-loss program", "why are we losing deals", "run win-loss interviews", "what patterns are in our closed-lost", "who should I interview", or any win/loss or closed-deal analysis.

Turn a pipeline target into a demand-generation plan that actually maps to the number. The ICP worth spending on, the offers by funnel stage, the channel mix that reaches them, the content that earns attention, and the pipeline math worked backward from the goal so you know if the plan can even hit it. Built for B2B marketing teams, customizable to your funnel and your channels. Trigger on "build a demand gen plan", "how do we hit our pipeline number", "what's our channel mix", "plan our content", "work the funnel math backward", or any demand-generation planning question.

Recruit a channel or tech partner and actually activate them, not just sign them. It scores who fits, writes the mutual-value pitch in their terms, builds the enablement that makes them productive, and plans the first co-marketing or co-sell motion so the partnership produces something in the first quarter instead of going dark after the kickoff. Built for B2B partnerships teams, customizable to your CRM and your partner program. Trigger on "recruit a partner", "does this partner fit", "pitch a partnership", "activate a new partner", "partner enablement plan", "first co-marketing motion", or any partner recruiting or activation request.

Turn a target account list into a real account-based play, not a spray. It tiers the accounts, sets the research angle per tier, builds the multi-thread across marketing and sales, and orchestrates the touches so the account feels one coordinated motion instead of a rep and a marketer working past each other. Built for B2B revenue teams, customizable to your CRM and your channels. Trigger on "build an ABM play", "account-based plan for this list", "how do I run ABM on these accounts", "tier my target list", "coordinate marketing and sales on these accounts", or any account-based planning request.

Plan a field event, dinner, or conference presence that actually produces pipeline, not just badges scanned. It builds the right guest list, designs a draw worth showing up for, plans the on-site motion so conversations happen, and writes the follow-up that converts, because the pipeline is made after the event, not at it. Built for B2B field marketing and sales teams, customizable to your CRM and your event motion. Trigger on "plan a field event", "customer dinner plan", "conference presence", "how do I get pipeline from this event", "event guest list", "event follow-up plan", or any field-event or in-person pipeline request.

Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.

Answer Engine Optimization (AEO) skill — optimize content to be cited by AI language models (ChatGPT, Perplexity, Claude, Gemini, Mistral) as authoritative sources. Distinct from SEO — AEO optimizes for citation in LLM-generated responses, not search rankings. Use when planning content for AI-first search audiences, auditing existing content for E-E-A-T signals, tracking which pages get cited by which LLMs, or building a citation-friendly content strategy. Triggers — 'AEO audit', 'optimize for ChatGPT', 'get cited by Perplexity', 'LLM citation strategy', 'answer engine optimization', 'content for AI search', 'E-E-A-T audit'. Output is a markdown audit report (default) or JSON for pipeline integration. Stdlib-only Python tools.

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.

Turn a piece of analysis into the thing that ships it. Takes the output of a read (an account verdict, a usage story, a ranked list) and drafts the CRM update, the Slack post, the follow-up email, and the next touch, draft-first and fully logged. Built for any GTM team, customizable to your CRM, your channel tool, and your outreach stack. Trigger on "draft the CRM update for this", "post this to a channel", "write a follow-up to this person", "update the qualification fields on this account", "send this recommendation to a teammate", "draft an outreach sequence", or any write, send, or notify step at the end of a workflow.

Profiles 5 competitors, identifies white space, and delivers a positioning recommendation — not a feature comparison table. Use this skill — proactively and without waiting to be asked — whenever entering a new market, before defining bets in product strategy, when pricing needs a competitive anchor, or when losing deals to a specific competitor. Also triggers for: "competitive analysis", "competitor research", "who are my competitors", "market landscape", "white space", "differentiation angle", "competitive positioning", "market entry risk", "losing to X", "pricing strategy", "threat assessment", "who owns this segment", "competitive brief", "how do we differentiate", "what are competitors doing". Produces a decision-ready competitive map: 5 competitor profiles, white space analysis, and a Where-to-Win recommendation with explicit areas to ignore.

Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Use this skill whenever the user wants to set up a new project, onboard a brand, start from scratch, configure their marketing context, or initialize their workspace. Trigger on: bootstrap, onboard, set up my project, get started, configure my brand, initialize, new project setup, brand onboarding, set up my brand, create project structure, onboard my company, set up content folders, prepare my workspace, start a new GTM project. Also use when the user seems to be starting fresh and hasn't set up strategy/brand.md or about/me.md yet.

Route web design, motion, WebGL, and visual-styling requests into the narrowest matching sub-skill of the 79-skill MengTo/Skills web-design family — Style/Design-System Packs, Full-Site Quality & Direction, Motion & Scroll Systems, WebGL/3D Backgrounds & Shaders, Library Embeds & Integrations, Component & State Effects, and CSS Technique Primitives. Use when picking and fetching the right visual recipe for a marketing site, landing page, portfolio, or dashboard shell, then combining layers in direction → layout → background → motion → component-state → polish order. Triggers on: web design, landing page, awwwards, GSAP, Lenis, scroll animation, WebGL background, shader, glass UI, dark mode design system, editorial layout, cursor trail, progressive blur, gradient border, three.js background, vanta, globe.gl, unicorn studio, marketing site polish.

Build client case studies through a low-overwhelm, multiple-choice interview plus whatever files the user can dig up — producing web-ready case study copy with a media plan (what images/videos to provide, find, or generate). Use this whenever the user wants a case study, client success story, portfolio write-up, results page, testimonial feature, or says "write up what we did for [client]". Also trigger when the user mentions having clients but no case studies, wants to turn a finished project into marketing proof, or casually says "I should really do a case study for X" — even without the word "case study" (e.g. "I want to show off the work we did for that gym").

Turn vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works standalone with zero dependencies. Trigger for: "brag", "log work", "what did I do", "backfill my work history", "performance review", "self-review", "self assessment", "write impact statement", "review prep", "promo packet", "promotion case", "weekly update", "status report", "accomplishments", "what did I ship", "I forgot to log my work", "summarize my work", "track my wins", "what should I highlight", "end of half", "career growth", "work journal", or any request to document, summarize, or organize work accomplishments.

Implementation and taxonomy skill for analytics tracking — event naming, properties, tracking plans, GA4/GTM/Amplitude setup, and debugging. Use this for the "how do we actually wire this up" layer, not the "what should we measure and why" layer (that's `product-analytics` — use this skill alongside it, after the metrics/tracking-plan decisions are made). Use this — without waiting to be asked — whenever the user mentions "set up tracking," "GA4," "Google Analytics," "Amplitude," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "event taxonomy," "are my events firing," "why isn't this event showing up," "naming convention for events," or "instrument this feature." Produces a concrete tracking plan (event names, properties, triggers) plus implementation and debugging steps for the tools actually in use.

Generates a premium single-page HTML landing page with 3D CSS animations, GSAP scroll effects, and mouse-parallax depth. Forcing intake (product + elevator pitch, audience register, brand overrides, tone) locks down positioning before any copy or markup is written, so the page reflects the actual product rather than generic boilerplate. Use whenever the user says 'landing for X', 'create a landing page', 'build a landing page', 'make a landing page for X', 'I need a web page for Y', or provides product/service details and wants a polished website. Also triggers on 'promotional page', 'product page', 'one-pager', 'web presence', 'sales page'. Outputs a single self-contained HTML file (Claude Code) or HTML artifact (Claude.ai). Supports configurable brand colors via CSS custom property overrides.

Make sure to use this skill whenever the user mentions anything related to job searching on Akademikernes Jobbank, jobbank.dk, or looking for academic or highly educated positions in Denmark — even if they don't mention jobbank.dk explicitly. Also invoke this skill for questions about Danish job listings, graduate trainee positions, Ph.d. jobs, or finding work in specific industries or regions in Denmark. Trigger phrases include: jobbank, akademikernes jobbank, jobs denmark, academic jobs denmark, find job denmark, highly educated jobs, graduate job denmark, trainee position denmark, ph.d. position denmark, postdoc denmark, studiejob, fuldtidsjob, deltidsjob, vikariat, freelance job, praktikplads, job søgning, jobsøgning, søg job, ledige stillinger, nye jobs, it jobs denmark, engineering jobs denmark, marketing jobs denmark, finance jobs denmark, healthcare jobs denmark, remote job denmark, fjernarbejde, job københavn, job aarhus, job odense, nyuddannede job, job til nyuddannede, international job denmark, jo

Pre-writing interview that captures the author's real opinions, experiences, and stances on a blog topic before the post is written on their behalf — the companion that runs BEFORE seo-blog-writer. Use this skill automatically whenever a blog post or article is about to be drafted under the user's name or brand — run the topic interview first, then hand the resulting Opinion Packet to seo-blog-writer. Also use it when the user says "interview me about this topic", "get my take first", "ask me what I think", or "update my opinion bank". Scope: blog/article topics only — not emails, docs, social posts, or other writing. If a blog post is about to be written as the user's voice and their take on the topic hasn't been captured, this skill triggers — even if they only asked for "a blog post about X".

Use this skill whenever LMX is used, produced, reviewed, migrated, or modified. This includes composing campaigns, loops, lifecycle emails, or email-message bodies for the Loops editor or Content API. LMX (Loops Markup Language) is the format used for Loops email content. Trigger on phrases like "create a campaign", "generate an email", "write a welcome email", "draft a lifecycle email", "build an email template", "create an onboarding email", "copy this into LMX", "migrate this email", "convert this email to LMX", "design a new Loops email", "use imagegen for a Loops email", "use gpt-image for an LMX reference", "visual reference for a Loops email", "LMX", "Loops email", or any request to produce, copy, migrate, convert, review, or modify email body content intended for Loops. For net-new emails or major visual redesigns, follow this skill's Net-New Email Design Flow before generating or sourcing new visual assets. Source copy, existing HTML, MJML, Markdown, screenshots, and migration instructions do not byp

Your customer-interview target finder. Connect Salesforce (CSM-managed customer book) and a canonical ICP doc — turns "who should I interview to validate the ICP, test the positioning, learn how they found us?" into a ranked slate of ~20 customers, each with a verdict, three-bullet why, and one named buying-committee recipient ready for a CSM-mediated intro. Use when a founder, GTM leader, or PMM is starting an ICP-validation round, testing new positioning, building a win-story program, or scouting reference customers. Trigger on "find customers to interview", "ICP validation interviews", "test our positioning with customers", "customer interview targets", "who in my book matches the ICP", "build a customer research slate", "find reference customers", "who should we talk to about how they found us", "validate the ICP with real customers", or any request to convert a CSM or AE book into a prioritized interview slate. Also fires when a new ICP doc ships and needs socializing with the customers who define it.