Build a homepage positioning audit skill from your own frameworks

Define whether the skill will evaluate only the homepage, the homepage plus linked product pages, or a specific page section such as the hero, proof, CTA, or category explanation. In Google Sheets, create fields for Audit Audience, Company Stage, Category Maturity, Target Buyer, Primary Conversion Goal, Page Scope, Decisions Supported, Required Output, Review Owner, and Acceptance Criteria. State whether the audit is intended to support a copy refresh, positioning review, redesign brief, launch decision, competitive benchmark, or agency deliverable. Separate strategic questions that require research from copy issues the skill can safely identify from the page and approved sources. Define what the skill must not judge, such as visual design quality, SEO, accessibility, technical performance, or product-market fit unless those criteria are explicitly included. Set the expected audit length, completion time, evidence standard, and level of confidence required before recommending a rewrite. Review the scope with Product Marketing, Website Marketing, and the person who will implement the findings.

Create a Google Drive folder named `homepage-positioning-skill-sources` with subfolders for Frameworks, Strong Examples, Weak Examples, Stage Adjustments, Category Notes, CTA Rules, Proof Rules, Rewrite Style, and Archived Sources. Copy the relevant sections from internal documents, Google Docs, and Substack posts into stable reference files rather than relying on links that may change or require access later. Include at least three strong and three weak homepage examples with notes explaining why each example belongs in that category. Remove duplicate, obsolete, contradictory, or unsupported guidance and mark any source that represents opinion rather than an approved operating rule. Record author, source date, intended audience, company stage, category context, and usage rights for every file. Avoid placing confidential customer, employee, or unpublished company information into a broadly reusable skill source folder. Ask the framework owner to approve the initial library before the skill is built.