Marketing & Growth

lensetek Skill

The Marketing Copywriter writes high-converting, SEO-optimized landing page copies, email templates, taglines, and social media announcements based on the positioning set by the CEO and Product Manager.

lensetek Skill

The Ops Growth & Analytics Specialist designs user event-tracking plans, monitors operational funnel metrics (CAC, LTV, churn), organizes A/B testing frameworks, and proposes growth loops.

lensetek Skill

The Marketing Content Planner (Social Media Specialist) designs 30-day content strategies, decides channels (LinkedIn, X, Instagram, TikTok), maps launch campaign schedules, and writes visual creative briefs for the marketing team.

lullabot Bundle

This skill should be used when users need SEO audits, website optimization recommendations, technical SEO analysis, or competitive research. Use when users request to analyze a website's search engine performance, identify SEO issues, or get prioritized action items to improve rankings. Ideal for tasks like 'audit this website for SEO' or 'what are the top issues affecting this site's SEO performance.'

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is navigating the relationship with their own manager, including a CEO, CRO, VP, or any person they report to directly. Trigger phrases include: "my CEO keeps changing priorities," "my manager is micromanaging," "how do I disagree with my boss," "my CRO doesn't understand marketing," "how do I get more autonomy," "I disagree with this directive," "my manager wants me to do X but I think Y is right," "how do I keep leadership informed without constant check-ins," "my boss is pulling me into every decision," or any situation where the user is trying to manage the dynamics of their upward reporting relationship. Also trigger when the user wants to proactively build trust with a new manager before friction develops, or when they are trying to present a recommendation they expect pushback on. Do NOT trigger for peer relationship issues, sales leader alignment (use sales-leader-alignment), or budget defense conversations (use marketing-budget-defense). This skill is spec

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is preparing for a quarterly business review where they will present marketing performance to executive leadership. Trigger phrases include: "QBR," "quarterly business review," "presenting to the CEO," "presenting to the CRO," "quarterly marketing review," "how do I present last quarter's results," "the quarter was below expectations," "preparing my Q review," "how do I present pipeline attribution," "leadership wants to see what marketing produced," or any situation where the user is preparing to account for marketing performance to senior leadership on a recurring basis. Also trigger when the user needs to handle a QBR where results missed targets, where attribution is contested, or where leadership is likely to question the ROI of specific programs. Do NOT trigger for the marketing budget defense conversation (use marketing-budget-defense for situations where funding is at risk), or for one-time presentations that are not part of a recurring review cycle. This s

matellez Skill

AUTO-TRIGGER: Apply this skill when the user wants to run, structure, or improve a win/loss analysis program. Trigger phrases include: "win/loss analysis," "why are we losing deals," "why do we win," "lost deal analysis," "closed lost reasons," "competitive losses," "deal debrief," "why did we lose to [competitor]," "what does sales say about why we lose," "our closed lost data is useless," "I want to interview lost prospects," or any situation where the user is trying to understand the patterns behind deal outcomes. Also trigger when the user has win/loss data they need to synthesize, or when they want to turn win/loss findings into changes to ICP, messaging, pricing, or channel strategy. Do NOT trigger for general competitive intelligence, battlecard creation, or sales coaching. This skill is specifically about the structured diagnostic practice of analyzing deal outcomes and feeding the findings back into GTM decisions.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user wants to build, fix, or evaluate a free trial program for a B2B SaaS product. Trigger phrases include: "free trial," "trial program," "PLG," "product-led growth," "trial to paid conversion," "trial isn't converting," "people sign up but don't convert," "trial length," "trial gate," or any request to design or improve a B2B SaaS product trial. Also trigger when the user asks how to improve trial conversion rates or how to build the nurture sequence for a trial. Do NOT trigger for general onboarding, user activation, or retention questions that are not specifically about a free trial program.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user wants to build, plan, or improve an account-based marketing program. Trigger phrases include: "ABM campaign," "named account targeting," "target account list," "account-based," "we want to go after specific accounts," "enterprise accounts," "1:1 or 1:few marketing," or any request to build a coordinated sales and marketing program around a defined account list rather than broad demand generation. Also trigger when the user asks how to align sales and marketing around specific accounts or how to measure account penetration rather than lead volume. Do NOT trigger for general demand gen, inbound, or broad campaign planning that is not account-specific.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is working with intent data signals from ZoomInfo, Bombora, G2, 6sense, Demandbase, or any similar platform, and needs to operationalize those signals into CRM workflows, campaign enrollment, rep alerts, or account prioritization. Trigger phrases include: "intent data," "ZoomInfo intent," "Bombora signals," "G2 buyer intent," "in-market accounts," "activating intent," "intent signals aren't doing anything," "we're paying for intent data but not using it," "how do I route intent accounts," "intent-based campaigns," or any situation where the user has intent data and needs to turn it into action. Also trigger when the user is evaluating which intent signals to act on, designing CRM workflows to handle signal ingestion, or trying to measure whether their intent activation is producing results. Do NOT trigger for general ABM strategy, ZoomInfo data enrichment questions, or lead scoring without intent signals. This skill is specifically about the workflow layer between

matellez Skill

AUTO-TRIGGER: Apply this skill when the user wants to build, fix, or document the agreement between sales and marketing around lead quality, lead handoff, and follow-up expectations. Trigger phrases include: "MQL definition," "sales-marketing SLA," "lead handoff," "sales isn't following up," "marketing leads are bad," "what counts as an MQL," "sales and marketing alignment," "service level agreement," "lead routing," or any conversation where sales and marketing are in disagreement about lead quality or pipeline contribution. Also trigger when the user is setting up a new CRM or rebuilding the lead management process and needs to define how marketing hands leads to sales and what sales commits to doing with them. Do NOT trigger for general RevOps questions not related to the marketing-to-sales handoff, or for content strategy and copywriting requests. This skill is specifically about defining, documenting, and enforcing the agreement between marketing and sales around what a qualified lead is and what happens

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is planning, executing, or troubleshooting an AI tool rollout for a sales or marketing team. Trigger phrases include: "rolling out AI to our team," "getting our reps to use," "nobody is using the tool," "AI adoption is low," "how do I get buy-in," "rolling out HubSpot," "Salesloft rollout," "ZoomInfo training," "tool adoption," "change management," or any request about getting a GTM team to actually use a new tool or workflow. Also trigger when the user is evaluating which AI tools to roll out, or when they have been given responsibility for a company-wide AI initiative without a clear implementation plan. Do NOT trigger for general AI tool comparisons, software procurement questions, or requests to learn how a specific tool works. This skill is about the organizational adoption problem, not the tool itself.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user mentions a vendor renewal, SaaS contract, MarTech negotiation, or any conversation about renewing, renegotiating, or evaluating a marketing or sales technology subscription. Trigger phrases include: "our HubSpot renewal is coming up," "ZoomInfo contract," "renewing our," "vendor negotiation," "contract coming up," "too expensive," "right-sizing our stack," or any mention of a specific MarTech tool alongside pricing or contract concerns. Do NOT trigger for general tool comparisons or product research where no existing contract or renewal is involved.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is managing a small team of two to six direct reports in a marketing, demand gen, or RevOps function. Trigger phrases include: "my team," "one of my reps," "direct report," "someone on my team is struggling," "how do I give feedback," "my one-on-ones aren't working," "I think I need to let someone go," "how do I manage a team member who," "performance issue," "underperformer," "how do I build a team that," or any situation where the user is navigating the people management dimension of a Director-level role. Also trigger when the user is building a team from scratch, inheriting a team, or trying to get more out of a team that is not performing at the level the role requires. Do NOT trigger for HR policy questions, formal disciplinary processes, or organizational design at scale. This skill is specifically for a Director-level practitioner managing a small team directly, without formal HR management training and often without a dedicated HR business partner.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is navigating a difficult or adversarial relationship with a sales leader, VP of Sales, or CRO. Trigger phrases include: "sales doesn't trust marketing," "VP of Sales thinks our leads are bad," "sales leader is skeptical," "how do I get sales on my side," "sales is blaming marketing," "I can't get a seat at the pipeline review," "CRO doesn't value marketing," "sales thinks we're a cost center," or any situation where the marketing or RevOps leader needs to shift the dynamic with a sales leader who is resistant, skeptical, or actively undermining marketing's contribution. Also trigger when the user is starting a new role and wants to build the sales relationship proactively before friction develops. Do NOT trigger for general SLA design or MQL definition work. Use the sales-marketing-sla skill for those. This skill is specifically about the human relationship and organizational dynamic between the marketing or RevOps leader and the sales leader, not the systems and

matellez Skill

AUTO-TRIGGER: Apply this skill when the user needs to defend, justify, or grow a marketing budget in front of a CEO, CFO, board, or executive team. Trigger phrases include: "budget review," "defending the budget," "CEO wants to cut marketing," "justify marketing spend," "prove ROI," "board presentation," "marketing budget," "can we do this with less," "what are we getting for this spend," or any situation where the user needs to make the financial case for marketing investment. Also trigger when the user is preparing for an annual planning cycle and needs to request budget, or when they have been asked to present marketing performance to leadership. Do NOT trigger for general campaign planning, financial modeling not related to marketing, or budget allocation between channels. This skill is specifically about preparing for and executing the conversation where marketing must justify its existence and investment to a skeptical executive audience.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is setting up, scoping, or pricing a consulting engagement as an independent practitioner. Trigger phrases include: "consulting engagement," "new client," "scoping the work," "what should I charge," "hourly versus retainer," "statement of work," "consulting proposal," "client wants to expand scope," "what to put in writing," or any situation where the user is transitioning from employee to consultant or managing the early stages of a client engagement. Also trigger when the user is preparing for a first client conversation and wants to understand what to clarify before agreeing to anything, or when a current engagement is drifting and the user needs to reset the scope. Do NOT trigger for general business development, agency pricing models, or large team consulting practices. This skill is specifically for an independent practitioner, typically a senior B2B marketing, demand gen, or RevOps leader, setting up a direct client engagement for the first time or early in

matellez Skill

AUTO-TRIGGER: Apply this skill when the user wants to build, audit, or improve a partner marketing program. Trigger phrases include: "partner program," "channel partners," "reseller program," "integration partners," "technology partners," "co-sell," "partner pipeline," "partner-sourced revenue," "partner tiers," "partner attribution," "we want to build a partner program," or any request to structure the operational infrastructure behind a B2B partner or channel program. Also trigger when the user asks how to measure partner pipeline contribution, how to attribute revenue to partner-sourced deals, or how to build a joint go-to-market playbook with a specific partner. Do NOT trigger for co-marketing content creation, referral programs aimed at end customers, or affiliate programs. This skill is specifically about the operational and attribution infrastructure of a B2B partner or channel program, not the content that supports it.

matellez Skill

AUTO-TRIGGER: Apply this skill when the user is preparing to present findings, recommendations, or results to a consulting client. Trigger phrases include: "presenting to my client," "client readout," "how do I present what I found," "delivering findings," "presenting my recommendations," "the client meeting is this week," "I need to show what I discovered in their HubSpot," "presenting my audit results," or any situation where the user is preparing to communicate findings or recommendations to someone who is paying them for consulting work. Also trigger when the user is preparing for a status update with a consulting client, or when they need to deliver bad news about what they found during an engagement. Do NOT trigger for internal presentations to leadership at a full-time employer (use marketing-budget-defense or managing-up for those), or for general presentation design. This skill is specifically for the independent consultant presenting findings or recommendations to an external client.

sorawit-w Bundle

Phased go-to-market for startup products. Builds a GTM playbook from upstream artifacts (validation-canvas, pitch-deck, brand-workshop), produces multi-channel content, schedules cadenced tasks, enforces compliance (CAN-SPAM/GDPR/FTC), emits handoff events. Trust ramp P1→P2→P3 (read-only → scheduled → autonomous). Project-local `.gtm/`. Kill switch via HALT file. Triggers on "set up GTM", "create a launch plan", "build a marketing playbook", "kick off go-to-market", "schedule social posts", "post-launch marketing", "growth ops", "draft launch content", or having pipeline output and asking "what's next for getting users". Single-channel asks for a startup product also trigger. NOT for brand identity (`brand-workshop`), pitch decks (`pitch-deck`), lean canvas (`validation-canvas`), adversarial review (`startup-grill`), one-shot non-startup content (`marketing:content-creation`), CRM/sales. NOT Google Tag Manager (different "GTM"). NOT the idiom "going to market with findings".

sorawit-w Bundle

Drafts messages sent AS the user, in their natural personal voice, with zero AI tells. Triggers whenever the user asks to write, draft, reply to, or respond to anything sent under their own name: "reply to this email", "write back", "message my coworker", "respond to them", "follow up with the recruiter", "answer this Slack message", plus DMs, LinkedIn messages, texts, and conversational GitHub PR/issue comments. Accepts an optional style argument — formal, friend, direct, diplomatic, storybook, eli5, or free-form ("warm but firm"); default is the user's own voice. A FORMAL request still triggers this skill (style=formal, human-formal — the AI-tell ban list still applies). Does NOT trigger for: formal documents, reports, specs, marketing copy, blog posts; code, commit messages, or technical docs; support-ticket replies, sales outreach, or brand-voice content (dedicated skills own those); or when the user explicitly asks for default AI style ("polished", "just write it normally").

thedecipherist Skill

Diagnose failures by root cause, not symptom. Use for crashes, stack traces, intermittent bugs, memory growth, race conditions, and "works locally, fails in prod" cases where you need a reproducible cause before a fix. Runs isolated and read-only, reports the root cause and fix.

thedecipherist Skill

Choosing how a web app renders and whether to use a framework, decided up front. Claude defaults to client-side rendering and hand-rolled vanilla HTML/JS, which is usually the wrong starting point for content sites and multi-page apps. Use when starting or scaffolding a site or app, deciding how pages render (SSR, SSG, CSR), or about to hand-build routing and state. Covers defaulting to server-rendered HTML for first paint and SEO, reaching for a framework when there are several pages, and not over-engineering a single page.

weorbitant Skill

Voice and tone reference for Orbitant blog content. Defines what Orbitant writing sounds like, what it values, and what it avoids — with concrete examples. Activate when user asks about Orbitant voice, tone, writing style, brand voice, or editorial guidelines. Also trigger when reviewing blog content for consistency, checking if text "sounds like Orbitant", or when creating/editing marketing content — even if they don't explicitly mention tone or voice.

weorbitant Skill

Drafts the monthly Orbitant newsletter from Slack links, Knowledge Sharing recaps, blog posts, and meetup updates. Activate when the user mentions "newsletter", "monthly email", "prepare the newsletter", "newsletter de [mes]", "borrador de newsletter", or provides materials for the monthly send (KS recap, Slack links, blog posts). Also triggers when asked to "draft the email for this month" or "prepare the MailerLite send". Curates Slack channel links autonomously, writes all copy in English, and outputs a complete Markdown draft ready for MailerLite layout.

weorbitant Skill

LinkedIn content planner for Orbitant. Takes a published blog post (markdown) and produces a full content plan with multiple LinkedIn pieces ready for scheduling: a standard post with link, a carousel structure proposal, and a multimedia asset recommendation (infographic or diagram). Each piece uses a different angle from the same source material. Output is ready for handoff to n8n or manual scheduling. Activate when user shares a blog post and asks for LinkedIn content, social media copy, a content plan, carousel proposals, or content repurposing for LinkedIn. Also trigger when asked to "turn this into LinkedIn posts", "create social media from this article", or "help me schedule this content" — even if they don't explicitly mention LinkedIn or social media strategy.

weorbitant Bundle

Generates blog post thumbnail images for Orbitant following the brand's visual identity, using Google's Gemini image API (Nano Banana 2). Activates when creating blog images, generating thumbnails, designing featured images for articles, or when someone needs a visual for an Orbitant insight/blog post. Use this skill even if the user just says "I need an image for this article", "create a thumbnail", "generate a hero image", or "make a featured image". Also triggers when the user mentions "Nano Banana 2", "image generation", or asks for a prompt for an AI image tool.

weorbitant Skill

YouTube video description generator for Orbitant Knowledge Sharing (KS) sessions. Takes a session transcript (.vtt or plain text) and produces a bilingual, SEO-optimised YouTube description — Spanish first, then English — built around a positionable keyword. The description is structured to rank in YouTube and Google search: keyword in the first line, natural repetition in the overview and takeaways, and hashtags chosen for search intent, not just labels. Use this skill whenever someone needs to write or generate a YouTube description for a KS session or any Orbitant video — even if they just say "escribe la descripción del vídeo", "I need the YouTube copy", or "help me upload this session". Also trigger when given a transcript and asked to prepare anything for a video upload.

weorbitant Bundle

Content generation skill for the Orbitant engineering blog. Activates when creating a blog post in Spanish from raw input — a Knowledge Sharing transcript, Slack thread, meeting notes, workshop draft, or bullet outline. Produces a structured, SEO-optimised article that matches Orbitant's narrative, tone, and content cluster strategy. Trigger on: "crear blog post", "redactar artículo", "convierte esto en un post", "blog post para Orbitant", "write a blog post", "turn this into an article". Also trigger when the user shares a long transcript, KS notes, or a Slack discussion about a technical decision — even if they don't explicitly say "blog post". When in doubt, ask if they want this turned into a post.

weorbitant Skill

Editorial review skill for Orbitant engineering blog posts. Activates when reviewing, editing, or providing feedback on blog articles. Produces structured reviews covering SEO, content quality, tone, and actionable improvements. Responds in the same language as the article being reviewed. Use this skill whenever someone asks to review a blog post, wants editorial feedback on a draft, needs SEO analysis for an article, or requests writing improvements for the Orbitant blog — even if they don't explicitly mention "review".

weorbitant Skill

Translation skill for validated Orbitant blog posts. Takes a Spanish article that has already been reviewed and approved by a human editor, and produces an English version optimised for English-speaking audiences. Keyword selection is not a literal translation but a search-intent-driven choice for the English market. Use this skill only on articles that have completed the full editorial and review process.

zarif3624 Bundle

Create or update the shared sales and go-to-market context used by other GTM skills. Use when starting work on a product, documenting the sales motion, defining buyers and value, capturing proof and competition, or when repeated sales tasks lack reliable background. Produces `.agents/gtm-context.md`.

zarif3624 Bundle

Analyze individual or aggregate B2B wins, losses, no-decisions, and disqualifications using CRM records, buyer interviews, call notes, proposals, and deal history. Use for win/loss reviews, loss-reason audits, segment comparisons, product and messaging feedback, sales-process learning, or deciding which GTM hypotheses to test without turning seller opinion into buyer truth.

zarif3624 Bundle

Develop, audit, or test B2B positioning and message architecture. Use for value propositions, category framing, audience-specific messaging, narrative pillars, proof mapping, competitive differentiation, website or sales-deck message briefs, or message experiments before writing channel copy without inventing customer outcomes, superiority, quotes, or market proof.

liujiayi3703 Bundle

Use when the user asks for AI stock picking, 选股, 找赛道, 风口行业, 产业链拆解, 股票池筛选, 价值因子, 质量因子, 最具潜力的股票, 五步法选股, 三高公司, high-growth high-margin moat companies, stock shortlist, or a sector-first company-picking workflow that combines macro, policy, earnings, fundamentals, capital flow, technicals, and risk validation.

liujiayi3703 Bundle

UZI investor-panel review. Use when the user asks which famous investors would buy, hold, avoid, or debate a stock; wants a multi-investor jury vote; or needs value/growth/quant/youzi perspectives on a holding.