Use when auditing marketing, messaging, offers, funnels, or content strategy. Triggers on "audit my marketing", "review my landing page", "improve my funnel", "content strategy review", "messaging review", "offer feedback", "marketing checkup", "why isn't my marketing working", "audit my brand". Works at any budget or company size.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
A 5-question marketing audit framework that works at any scale - from $50/month solopreneurs to $50M enterprise budgets. Run sequentially: diagnose messaging, offer, funnel, and content, then build a 30-day fix plan.
Credit: Tuck Ross
Run these in order. Each builds on the previous findings.
Here's my homepage / bio / sales page: [paste it]. Pretend you're seeing it for the first time. In 5 seconds, can you tell: who it's for, what problem it solves, why I'm the right person? If not, rewrite it.
What this catches: Unclear positioning, jargon, missing value prop, "curse of knowledge" blind spots.
Here's my product: [describe it, price, what's included]. Rate it 1-10 for: clarity, perceived value, differentiation, ease of purchase. Be brutally honest. Then tell me what to change to make it a 9.
What this catches: Pricing misalignment, weak differentiation, friction in purchasing, unclear deliverables.
Here's my customer journey: [how people find you, what they see, how they sign up, how they buy]. Identify the 3 biggest drop-off points. Where am I losing people? Simplest fix for each?
What this catches: Leaky funnels, unnecessary steps, trust gaps, missing CTAs, broken handoffs between stages.
I post on [platforms] about [topics]. Best content: [3 examples]. Worst: [3 examples]. What patterns explain the difference? What should I do more of, less of, and stop entirely?
What this catches: Platform mismatch, topic drift, inconsistent quality, missed format opportunities.
Based on all the audit findings, build a prioritized 30-day plan. Week 1: quick wins. Week 2: structural fixes. Weeks 3-4: systems to build. Each action under 2 hours. No fluff.
What this produces: Actionable roadmap with time-boxed tasks, prioritized by impact.
| Mistake | Fix |
|---|---|
| Running audit 5 before 1-4 | The plan is only as good as the diagnosis. Do all 5 in order. |
| Vague inputs ("my website is fine") | Paste actual copy, actual prices, actual content links. Specifics yield specifics. |
| Ignoring brutal feedback | The point is honesty. If the rating is a 4, sit with that before defending. |
| Planning without doing | Week 1 quick wins exist for a reason. Ship something in 7 days. |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when evaluating, designing, or pressure-testing the business model of an AI agent product. Triggers on "agent business model", "agent economics", "agent canvas", "evaluate agent product", "agent pricing", "agent unit economics", "agentic business", "AI agent company", "agent cost structure".
The English summary is being prepared. Showing the original description.
Create user-facing App Store release notes by collecting and summarizing all user-impacting changes since the last git tag (or a specified ref). Use when asked to generate a comprehensive release changelog, App Store "What's New" text, or release notes based on git history or tags.
The English summary is being prepared. Showing the original description.
Use when someone wants to launch a content brand from scratch on any platform. Triggers on "launch a channel", "start a YouTube channel", "build a podcast", "start a newsletter", "content brand", "creator launchpad", "build my audience", "start creating content", "grow on TikTok", "start a blog".
The English summary is being prepared. Showing the original description.
Use when you have an existing pipeline DOT file that needs review, fixing, or validation. Use when validation produces warnings or errors, when a DOT file was hand-written or generated by another tool, or when you want to verify a pipeline covers 100% of a spec before running it.
The English summary is being prepared. Showing the original description.
Use when you want to build a project but don't have a spec yet and need to brainstorm the idea into a design doc structured for pipeline DOT generation. Use when starting from a vague idea, project concept, or feature request that needs to become a headless autonomous build pipeline.
The English summary is being prepared. Showing the original description.
Use when you have a spec, design doc, structured plan, or prompt_plan and need to generate a pipeline Graphviz DOT file for headless autonomous building. The agent reads the spec, extracts build pipeline phases, determines tech stack, asks about human gates and model preferences, generates a validated DOT digraph with rich self-contained prompts, and saves it to the project root. Handles any language or framework.
The English summary is being prepared. Showing the original description.