DEDUPED Hot AI repos, turned into use cases Get 5 a day

Sales and marketing use cases

72 use cases from hot AI repos, best first. Each one has steps and a prompt.

Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full disclaimer

72 use cases

  • Get a GTM diagnosis for your developer tool

    Answer five questions and get one prioritized next move for your go-to-market.

    View prompt
    Install the skills from https://github.com/AIDevGTM/gtm-cofounder and run 00-start-here for <product name>, then run 01-strategy-and-roadmap. Expected output: docs/gtm-cofounder/gtm-roadmap.md with one Now move, a Next list, and a Later list. Verify that the Now move names a specific piece of evidence to collect, not a list of marketing tactics.
  • Render a product demo video from React code

    Install the repo and render the included 16-second demo as an mp4 without a screen recording.

    View prompt
    In the repo Alexwtlf/agentic-product-demo, run `npm install` then `npm run render`. Confirm the output mp4 and poster frame are written to out/ and that the frame gate passes. Report the output file paths.
  • Connect an agent to the growth.engineer catalog

    Add the read-only MCP server so an agent can search workflows, tools and companies.

    View prompt
    Use the growth-engineer MCP server at https://www.growth.engineer/mcp to search for workflows about <goal>. Return the title and key of each match and open the first one with get. Check that the returned file has a title, inputs and steps before you report back.
  • Stress-test a business idea before you launch

    Run a board review and a 100-buyer simulated panel on an idea before you spend money.

    View prompt
    Using the Jakeschincariol/founder-skill repo installed as Claude skills, run /founder-board and then /founder-consumer --quick on the idea described in <idea description>. Output the board vote, the top three objections and the reasons buyers would pass, saved under founder/. Verify that the panel answers are treated as simulated research and not as real customer evidence.
  • Turn one idea into a LinkedIn post you approve

    Write a full post from a single idea, with three hook options and a humanized draft.

    View prompt
    Install the skills from https://github.com/Jakeschincariol/linkedin-agent-skill, fill in voice.md from the three posts at <path to your posts>, then run /li-post on the idea: <your idea>. Expected output: three hook options and one full draft with no em dashes and no invented numbers. Verify that any figure you did not supply appears as {{your number}}.
  • Score a website's readiness for AI answer engines

    Get a free 0 to 100 AI visibility score with the three gates and biggest gaps.

    View prompt
    Using the geo-score repo at jianruntech/geo-score, run the free score on <target-domain> with geo_score.py, then list the three gate checks and the top three gaps by points. Expected output: the 0 to 100 score, band and gap list. Verify that the score is reported without any API key being used.
  • Track your brand's AI answer visibility against rivals

    Run one self-hosted pass that shows how often AI engines mention your brand versus competitors.

    View prompt
    Using the limelit-co/open repository, download the binary, start `limelit serve`, and complete the setup wizard for the domain <target-domain> with competitors <competitor-domains>. Press Run and report the visibility and share of voice per engine. Verify that each figure shows its answer count n.
  • Turn one idea into posts for several platforms from the terminal

    One source text becomes a draft for each chosen platform in a single command.

    View prompt
    Use the yominpost repo at git+https://github.com/mrlong0129/yominpost to run the yominpost run command with <your source text> for platforms x, linkedin and tiktok. Expected output: one draft per platform with a chosen format. Verify that each draft is platform-specific and that no post was published.
  • Launch a business website from a starter site

    Install Kaleta on your hosting and publish a working business site from a starter in under an hour.

    View prompt
    Using the kaletacms repository on GitHub, guide me through installing Kaleta on <hosting-domain> with PHP 8.3 or newer. Report the install.php URL and the starter site I chose, then confirm the home page loads over HTTPS.
  • Run a full SEO audit from your own Search Console data

    Get indexation issues, CTR anomalies, decaying pages and quick wins from your real GSC and GA4 data.

    View prompt
    Using the open-seo-mcp-skills seo-audit skill through the Ryze MCP, run a full site audit on <target-domain> covering indexation, CTR anomalies, decaying pages and quick wins. Return a ranked list of findings with the data source for each. Verify that every figure comes from the connected Search Console or GA4 account, not an estimate.
  • Transcribe live-stream speech and separate speakers

    Turn a live-commerce audio track into a transcript that labels who said what, using TLive Omni's ASR features.

    View prompt
    Using the TLive-Omni repo at https://github.com/TaoLiveAIGC/TLive-Omni and its model card on Hugging Face, produce a speaker-attributed transcript of <path to live-stream audio>, with timestamps where the model provides them. Verify that speaker labels stay consistent across the first five minutes of the transcript before reporting the result.
  • Check a live site's SEO foundation in one run

    Give the agent a URL and get a crawler's-eye pass/fail report on 26 structural SEO checks.

    View prompt
    Using the tigerless-labs/seo-ops skill, check the SEO foundation of <target-url> as a live site. Return the pass/fail report for the 26 checks with evidence for each red item. Verify that the report lists every check as pass or fail and does not guess at checks it could not run.
  • Run the CRM locally with a sample pipeline

    Clone the repo, start Postgres in Docker, and open a seeded CRM on your own machine.

    View prompt
    Clone the trycompai/crm repo, copy .env.example to .env, set BETTER_AUTH_SECRET and ALLOWED_SIGN_IN, then run bun install, docker compose up -d, bun run db:deploy, bun run db:seed and bun run dev. Report the URL that serves the app. Verify that http://localhost:3001 responds before you finish.
  • Draft launch announcement posts for every social channel

    Ask the team lead for launch posts and get X, LinkedIn, and Bluesky drafts waiting in Typefully.

    View prompt
    Using the marketing team template in vercel-labs/marketing-team-eve-template, ask the lead agent to draft launch announcement posts for <product launch>. Expected output: an X thread, a LinkedIn post, and a Bluesky post in the Typefully queue, unscheduled. Verify that no post is scheduled until a human approves it.
  • Diagnose ACOS problems in an Amazon ad account

    Run the ACOS diagnostics Skill to find whether ACOS comes from clicks, conversion, traffic mix, or profit.

    View prompt
    Using the sealeap-amazon-skills repo, run sealeap-amazon-acos-diagnostics for <marketplace> over <time range>, with the goal of finding whether ACOS comes from click cost, conversion, traffic structure, or profit structure. Expect a list of required data, a diagnosis, the evidence gaps, and verifiable optimization options. Check that every conclusion names the data it used and marks missing data as unknown.
  • Score a website funnel and get prioritized fixes

    Get a weighted 0-100 funnel audit with a ranked list of fixes in one agent session.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the audit module on <target URL> and return the weighted 0-100 score with prioritized fixes. Verify that the report includes a what-I-couldn't-determine section and that the score is labeled as a heuristic.
  • Catch new AI names the day they appear

    Get a daily report of new model, product and repo names from X, Hugging Face, GitHub and sitemaps.

    View prompt
    Using the new-term-radar repo, run the daily radar with my config at <config path> and return the new names it reports, each with the signal that caught it. Verify that every name has a source (X, Hugging Face, GitHub, sitemaps or sellers) before you list it.
  • Find the communities where your users already talk

    Map the named places your target users gather, with links, and launch examples.

    View prompt
    Run research-the-market in the gtm-cofounder skills for <product name> and <target user role>. Expected output: docs/gtm-cofounder/market-research.md with linked communities ranked by fit and the rules each room has for self-promotion. Verify that every finding has a link and is tagged [researched], not treated as a real user statement.
  • Have a coding agent build a demo clip for your product

    Point Claude Code or Cursor at your product and let the skill file drive a shot list and render.

    View prompt
    In the repo Alexwtlf/agentic-product-demo, read AGENTS.md and the product-demo skill, then read the product at <product-path> and propose a shot list before writing code. After approval, build a composition named <name>, render it, and output out/<name>.mp4 and out/<name>-preview/contact.jpg. Verify that the frame gate passes and that button labels match the real UI.
  • Run a funding-signal outbound workflow with an agent

    Paste a workflow file into an agent that asks for inputs before it sends or spends.

    View prompt
    Read the funding-signal-outbound workflow from https://www.growth.engineer/workflows/funding-signal-outbound.md, ask me for every input it lists, and run its steps in order. Before any message is sent, money is spent or data is changed, stop and ask me, then report each completed step with its result.
  • Calculate real margins, break-even and payback

    Run unit economics on your numbers to see profit per sale, break-even and cash needed.

    View prompt
    Using the Jakeschincariol/founder-skill repo, build founder/numbers.json for <business name> from the prices and costs I give you, then run `python3 skills/founder-cfo/unit_economics.py founder/numbers.json --out founder/cfo.md`. Output the contribution per sale, break-even per day and year 1 totals from cfo.md. Verify that every number traces to an input and that missing fields produce an error rather than a guessed value.
  • Strip AI tells from a draft and score it before posting

    Clean invisible characters and stock phrases from any draft, then get a five-check human score.

    View prompt
    Use the li-human scripts in https://github.com/Jakeschincariol/linkedin-agent-skill on <path to draft file>. Run humanize.py with --report, then detect.py, and return the cleaned text, the change report and the HUMAN SCORE. Verify that the score is shown for both the original and the cleaned file.
  • Check whether AI engines cite your site for one question

    Ask one buyer question to AI engines and see whom the answers cite.

    View prompt
    Using the geo-score repo at jianruntech/geo-score, run geo_score.py on <target-domain> with --ask set to <buyer-question>, using the API key already present in the environment. Expected output: each engine's answer and its cited sources. Verify that the report lists whether <target-domain> is cited.
  • Let Claude answer AI visibility questions from your data

    Connect Claude to a local Limelit instance so it can read your visibility data in plain language.

    View prompt
    In the limelit-co/open repository, register the MCP server with `claude mcp add limelit -s user -- sh -c 'cd ~/limelit && exec ./limelit mcp'`. Then ask it for the visibility of <brand-name> against <competitor-name> across all engines. Expected output is a plain-language summary with the sample size behind each figure. Verify that the first tool call reports the instance state.
  • Let a coding agent draft and risk-check posts through MCP

    Claude Code or Cursor generates and checks posts, then saves drafts for a human to approve.

    View prompt
    Using the yominpost MCP server from github.com/mrlong0129/yominpost, call generate_posts for <your launch material>, run check_post on each draft, and save the passing drafts with save_draft. Expected output: saved drafts with risk check results. Verify that no publish action was taken, since the MCP server has no publish tool.
  • Have Claude draft site changes over MCP for approval

    Connect Claude to your Kaleta site so it drafts pages, site parts and design changes you review before publishing.

    View prompt
    Using the kaletacms repository and its MCP support, ask Claude to convert the HTML in <source-file> into a draft page on my Kaleta site at <site-url>. Expected output: the draft's name and a list of changed elements, and confirm nothing is published until I approve it.
  • Find keywords a competitor ranks for that you do not

    Compare a competitor's keyword footprint with your own Search Console queries to find gaps.

    View prompt
    Using the open-seo-mcp-skills competitor-gap skill through the Ryze MCP, list keywords that <competitor-domain> ranks for and <target-domain> does not. Return the gap list with the data source for each row, sorted by opportunity. Verify that your-site rankings come from Google Search Console before you call a keyword a gap.
  • Locate products and read on-screen text in frames

    Find products in live-stream frames and read the text shown on screen, using the image tasks TLive Omni covers.

    View prompt
    Using the TLive-Omni repo at https://github.com/TaoLiveAIGC/TLive-Omni, find the products visible in the frames at <path to frame folder> and return each product's location and any on-screen text as a table. Verify by checking three frames by eye against the table before reporting.
  • Turn red SEO items into a P0, P1, P2 fix list

    Have the agent explain each failed check and rank the fixes so the team knows what to do first.

    View prompt
    Using the tigerless-labs/seo-ops skill, run the check on <target-url> and group every red item into P0, P1, and P2. For each item, give the fix and point to the evidence in the report. Verify that every red item appears exactly once in the priority list.
  • Have an agent fill contact gaps from your own email threads

    Run the research agent so it reads your CRM's threads, meetings and signature blocks and records strong facts.

    View prompt
    In the trycompai/crm repo, use the apps/agent research agent to run read_crm_history and record_fact for the contact <contact-name>, with no outside API keys set. Report the facts recorded and any suggestions left for a human. Verify that every recorded fact cites an observed source such as a signature block or thread.
  • Write a long-form blog post and get a Notion page link

    Have the content marketer draft a blog post or landing page and return a Notion page to edit.

    View prompt
    Using vercel-labs/marketing-team-eve-template, ask the lead agent to have the content marketer write a blog post about <topic> for <audience>. Expected output: a Notion page link to the draft. Verify that the draft uses the product claims in the brand context document.
  • Review and revise an Amazon listing with the listing optimizer

    Use the Listing optimizer Skill to get a revised listing draft and a list of claims to verify.

    View prompt
    Using the sealeap-amazon-skills repo, run sealeap-amazon-listing-optimizer on the current listing for <product or listing name> in <marketplace>. Expect a revised draft, a change log with reasons, and a list of claims needing verification. Confirm that each change is tied to a stated reason and that no claim is presented as verified without a source.
  • Diagnose ad fatigue and brief the next creatives

    Find which ad concepts are fatigued and get a ranked brief for the next batch.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the paid-ads module on the performance data for <campaign name> and return a concept-level fatigue diagnosis with a ranked production brief. Verify that each ranked brief item names the concept it replaces and that no winner is declared from a handful of conversions.
  • Find the search terms behind a new AI name

    Turn a new name into the generic searches people make, sized and checked for page-one room.

    View prompt
    In the new-term-radar repo, produce the keyword table for today's new names and return the rows with their decision and page-one status. Verify that no prioritize row has a crowded page one, since the README relabels those as watch with a down arrow.
  • Plan your first 50 users and a launch

    Choose the channels to try first and decide how to launch without fear of getting flamed.

    View prompt
    Run first-50-users and then launch-it in the gtm-cofounder skills for <product name>. Expected output: a short channel plan for the first 50 users and a launch checklist with one recommended channel. Verify that the plan matches the Now move in gtm-roadmap.md.
  • Match demo colours and easing to your product stylesheet

    Use the adopt script to copy your app's design tokens into the demo theme.

    View prompt
    In the repo Alexwtlf/agentic-product-demo, run `npm run adopt ../src/app/globals.css --curves --dry-run` and report which tokens matched, which were derived and which are placeholders. Do not write files until the report is reviewed. Verify that no placeholder token appears in the preview stills.
  • Add a company and its tools to the catalog

    Open a pull request that adds a company file and its tool files, checked by pnpm.

    View prompt
    In the growth-engineer repository, use the research-company skill to add a company file and its tool files for <vendor>, citing the vendor's own documentation for each tool. Run pnpm content:check and report the result, and do not finish until it passes.
  • Find an acceptable price range from buyer answers

    Turn four price answers per buyer into a range and check your planned price against it.

    View prompt
    Using the Jakeschincariol/founder-skill repo, run `python3 skills/founder-pricing/van_westendorp.py founder/panel/answers --price <planned price>` and report the acceptable price range, the optimal and indifference prices and whether the planned price falls inside the range. Verify that the input is either panel answers or a real survey CSV and say which one was used.
  • Score your LinkedIn profile and fix the weakest parts first

    Get a 100-point profile score and a rewrite ordered by what loses the most points.

    View prompt
    Using the li-profile skill from https://github.com/Jakeschincariol/linkedin-agent-skill, score the profile text I paste from <path or paste of profile> and return the total out of 100 plus rewrites in fix-first order. Verify that no metric, client or outcome appears unless I supplied it.
  • Track how often AI engines cite your site each week

    Run a fixed question set weekly and compare cited rates and share of voice.

    View prompt
    Using the geo-score repo at jianruntech/geo-score, run `geo_score.py watch run` against the question set for <target-domain> using my own API keys. Expected output: a weekly report with cited rate, its 95% interval and share of voice. Verify that the diff between this week and last week is labelled as a real change only when the paired test supports it.
  • Find which sites AI engines cite for your category

    See which pages engines trust, classified as your own, competitor, social, informational or other.

    View prompt
    Using limelit-co/open, run one pass for the brand <target-brand> in the category <category>. Export the citation data and list the top 10 cited sites with their source type. Verify that each classification matches the stored citation rows.
  • Screen existing drafts for account-risk signals before posting

    Run the pre-publish risk gate on drafts you already wrote to catch leaks, bait and duplicates.

    View prompt
    Using the yominpost repo at github.com/mrlong0129/yominpost, run check_post on each draft in <your draft file or list> and report the findings. Expected output: one risk result per draft. Verify that the findings name the rule that fired, such as hashtag limits or duplicate detection.
  • Move a WordPress site into Kaleta

    Import an existing WordPress site into the Kaleta page builder instead of rebuilding it by hand.

    View prompt
    Using the kaletacms repository, help me import the WordPress export at <export-file> into my Kaleta site at <site-url>. Expected output: a list of imported pages and any items that did not import, and verify that each imported page opens in the builder before I publish.
  • See which AI engines send traffic and which pages they cite

    Report ChatGPT, Perplexity, Claude and Gemini referrals from GA4 and the pages they cite.

    View prompt
    Using the open-seo-mcp-skills ai-visibility skill through the Ryze MCP, report which AI engines (ChatGPT, Perplexity, Claude, Gemini) send traffic to <target-domain> and which pages they cite. Return a table of engines, sessions and cited pages from GA4. Verify that the figures come from GA4 AI-referral reports and not from prompt-sampling estimates.
  • Summarize a long live-stream video by timestamp

    Produce a timestamped summary of a long stream video, using TLive Omni's grid layout and 256K context.

    View prompt
    Using the TLive-Omni repo at https://github.com/TaoLiveAIGC/TLive-Omni, create a timestamped summary of the live-stream video at <path to video>, listing time, what happens, and any product mentioned. Verify that three timestamps match the source video before reporting.
  • Audit a site before launch, regardless of its framework

    Test a React, Vue, Next, WordPress, or static site with the same checks before it goes live.

    View prompt
    Using the tigerless-labs/seo-ops skill, check <target-url> and save the pass/fail report as a baseline. After the migration, check the new URL with the same skill and list every check whose result changed. Verify that both reports cover the same 26 checks before comparing them.
  • Pull brand data and a LinkedIn profile into a prospect record

    Add a Context key in Settings → General so accounts show real logos, names and LinkedIn roles.

    View prompt
    In the trycompai/crm CRM, confirm that the Context key is set under Settings → General, then trigger enrichment for the company <company-domain> and the contact <linkedin-url>. Report the logo, industry, current title and employer that were recorded. Verify that the startup list shows both Company brand data and LinkedIn as on.
  • Audit a page's SEO and get a ranked fix list

    Ask the SEO specialist to review a page for structure, internal links, and schema and return recommendations.

    View prompt
    Using vercel-labs/marketing-team-eve-template, ask the lead agent to have the seo specialist audit <page URL> for hierarchy, internal linking, and JSON-LD schema. Expected output: prioritized recommendations, with a long audit as an artifact if it is large. Verify that each recommendation names the specific element on the page it refers to.
  • Screen a product idea with the Douyin selection Skills

    Load the Douyin public-knowledge Skills to check a product idea before buying inventory.

    View prompt
    Using the sealeap-amazon-skills repo, run a selection Skill from amazon-skills/douyin/ on the product idea <product idea> for <marketplace>. Expect an input checklist, the decision basis, a step-by-step screen, and a list of unknown data. Check that the agent marks every missing number as unknown rather than estimating it as fact.
  • Generate and grade 20 copy variants before review

    Produce 15-20 copy variants, score them with an expert panel, and strip AI-sounding phrasing.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the copy module on the brief for <product or offer> and return 15-20 variants with expert-panel scores and de-slopped text. Verify that the top variants are ranked by score and that the scores are described as heuristics.
  • Spot paid AI products and new sellers early

    Find AI products with verified revenue and sites that just added a payment link.

    View prompt
    Using the new-term-radar repo, run the weekly revenue and sellers signals with my config at <config path> and return the products and sites they report. Verify that each product entry shows its source and that the revenue figures match the TrustMRR data before you quote them.
  • Set a price for your developer tool

    Stop guessing a number and see how to charge without giving the product away.

    View prompt
    Run pricing and market-to-devs-sell-to-buyers in the gtm-cofounder skills for <product name>. Expected output: a pricing recommendation with the reasoning and the evidence still missing. Verify that the recommendation names what real users need to confirm before the price is locked.
  • Ship a muted page loop or a scored launch video

    Choose the silent mp4 for autoplay or add a sound pass for a launch video.

    View prompt
    In the repo Alexwtlf/agentic-product-demo, render the composition <name> and confirm the silent mp4 exists in out/. If a launch video is needed, write beat files in scripts/beats/ and run `bash scripts/add-sfx.sh <name>`. Verify that out/<name>.mp4 is unchanged and that out/<name>-sound.mp4 exists.
  • Give an agent the full catalog in one document

    Load llms-full.txt, or run the site locally, so an agent can reason over every file.

    View prompt
    Read the catalog at https://www.growth.engineer/llms-full.txt and list every workflow whose inputs match <the inputs you have>. Report the workflow titles and the tools each one uses, and confirm that each title appears in the document before you list it.
  • Compile a business plan with a computed verdict

    Assemble all the founder files into one plan with a verdict from the numbers.

    View prompt
    Using the Jakeschincariol/founder-skill repo, run `python3 skills/founder-plan/compile.py --dir founder` and report the verdict (Profitable, Not yet or Incomplete) and the reason for it from founder/business-plan.md. Verify that the verdict comes from the computed checks on unit economics, year 1 profit, break-even against capacity and the share of the panel that buys, and not from prose.
  • Plan a week of LinkedIn posts and 10 engagement targets

    Get a weekly plan of what to post, when to post it, and who to comment on.

    View prompt
    Run the li-plan skill from https://github.com/Jakeschincariol/linkedin-agent-skill for the week of <date>, using my voice file and the topics: <topics>. Expect a plan written to ~/.claude/linkedin/plan.md with posts, timing and 10 engagement targets. Verify that the file exists and that no target was invented without my input.
  • Fail a build when a site's AI readiness regresses

    Score the site on every push and fail the build on a regression or a zero gate.

    View prompt
    Using the geo-score repo at jianruntech/geo-score, add its GitHub Action to a workflow that scores <target-domain> on each push. Expected output: a build that passes with the score in the job summary and fails on a regression or a gate at zero. Verify that a deliberately broken robots.txt line causes the build to fail.
  • Export all visibility data as JSON or CSV

    Pull the whole instance into one JSON file or a folder of CSVs for your own analysis or board material.

    View prompt
    In the limelit-co/open repository, run `limelit export` for the instance in ~/limelit and write the output to <output-path>. Expected output is a JSON document or CSV directory covering all answers. Verify that the row count for <engine-name> matches the dashboard count for that engine.
  • Schedule and publish approved posts to your own social accounts

    Connect your accounts, approve drafts in the studio, and let the scheduler publish them on time.

    View prompt
    Using the yominpost repo at github.com/mrlong0129/yominpost, start the studio, connect <platform name> with its OAuth client, and schedule the approved draft <draft id> for a time you set. Expected output: the post in the scheduled queue with a status. Verify that a person approved the post in the UI before it was published.
  • Collect enquiries and newsletter sign-ups without cookies

    Add an enquiry form and double opt-in newsletter to a business site, then send confirmed subscribers to your mailing service.

    View prompt
    Using the kaletacms repository, set up the enquiry form and double opt-in newsletter on my Kaleta site at <site-url>. Expected output: a list of the form fields and the mailing service I connected, and verify by submitting one test enquiry and one test sign-up.
  • Find paid queries you already rank for organically

    Compare Google Ads spend with Search Console rankings to find clicks you could get free.

    View prompt
    Using the open-seo-mcp-skills seo-vs-ads skill through the Ryze MCP, list queries that <target-domain> pays for on Google Ads and already ranks for organically in Google Search Console. Return each query with its ad cost and organic position. Verify that both the ad data and the organic positions come from connected accounts before you recommend any change.
  • Brief the content team on the inputs SEO needs

    Use the T checklist to tell writers and designers which titles, descriptions, and alt text SEO depends on.

    View prompt
    Using the tigerless-labs/seo-ops repo, read references/content/content-checklist.md and write a content brief for <content-type> that lists each SEO input, the reason it matters, and the C check it feeds. Verify that every input in the T set appears in the brief and that each one names at least one C check.
  • Audit what the agent did on a deal before you trust it

    Open the Agent tab on a deal to see each step, discarded leads and open questions.

    View prompt
    In the trycompai/crm CRM, open the Agent tab for the deal <deal-name>, list each step, each discarded lead with its reason, and each open question. Report those items in a short table. Verify that every schedule_recheck entry includes a stated reason.
  • Build and send an email campaign after approving each step

    Have the email specialist turn copy into a Resend campaign and send it only after you approve.

    View prompt
    Using vercel-labs/marketing-team-eve-template, ask the lead agent to have the email specialist prepare a campaign for <segment> from <copy source>. Expected output: a Resend campaign link, with the send held for approval. Verify that the send does not run until an approve action is given.
  • Build a hook matrix from 18 hook tactics

    Turn one offer into a hook matrix and a diagnostic funnel for testing openings.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the hooks module on <product or offer> and return the 18-tactic hook matrix and the diagnostic funnel. Verify that no hook claims proof that is absent from brand-context.md.
  • Stress-test your GTM claims before you ship

    Have the agent review your landing page or launch copy as a skeptic.

    View prompt
    Run review-the-work and value-prop-that-converts in the gtm-cofounder skills on this draft for <product name>. Expected output: a list of flagged claims and a revised value prop. Verify that every remaining claim can be backed by something the user can check.
  • Find which of your past posts actually worked

    Rank your published posts by engagement rate and reach multiple, not raw impressions.

    View prompt
    Use the li-audit skill from https://github.com/Jakeschincariol/linkedin-agent-skill on the post data I paste from <source of post data>. Expect a ranking by engagement rate and reach multiple, with a short note on each. Verify that every number in the output comes from the data I supplied.
  • Check how citable a page is for AI search

    Assess a page for AI-search citability across ChatGPT, Perplexity and AI Overviews.

    View prompt
    Using the marketing-os skill in the Yuzzyuk/marketing-os repo, run the geo module on <target URL> and return a citability assessment with specific edits. Verify that the report separates what was determined from what could not be determined.