AGENT SKILL

gerhardt-founder-brand

Build a credible founder narrative, focused content, and a publishing and feedback plan using Dave Gerhardt's public method. Use for founder brand strategy, founder social drafts, or marketing support for a founder's expertise.

License 许可
Apache-2.0
所属仓库
getedgehq/skills
最近更新
2026-11-12
Stars
★ 5
Forks
0

01 前言 Front Matter

name
gerhardt-founder-brand
description
Build a credible founder narrative, focused content, and a publishing and feedback plan using Dave Gerhardt's public method. Use for founder brand strategy, founder social drafts, or marketing support for a founder's expertise.

02 资源文件 7

03 SKILL.md 正文

Dave Gerhardt's Founder Brand

Based on Dave Gerhardt's public method. Not affiliated with or endorsed by Dave Gerhardt.

When to use

Use this skill when a founder or supporting marketer needs to turn lived experience and useful beliefs into a recognizable relationship with prospective customers. It supports an audience before product launch, a founder narrative, social drafts, a recurring educational series, and a publishing and measurement plan. It also fits an established company whose founder knows the market but has little public visibility. The goal is relevant trust and business interest, with content that helps the audience. [S1] [S2]

Produce a founder-brand package sized to the request. For a single post, use the same reasoning but include only the necessary context and draft. For a strategy, include the narrative, evidenced beliefs, channel choice, starter content, operating cadence, and feedback decisions. Do not invent experiences, results, or opinions to fill gaps. Identify missing facts and keep provisional claims visibly provisional.

The procedure translates public interviews into an agent workflow. Its central cycle is story, publishing, and feedback. The exact deliverable fields, review gates, and example schedules are package adaptations, not a prescribed Gerhardt framework. Read references/method.md for the decision rules and consult references/sources.md for attribution and speaker boundaries.

Procedure

  1. Define the assignment and available facts. Gather the intended customer, recurring problem, product capabilities, founder experience, existing channels, and requested output. Separate confirmed facts from assumptions. Use the intake guidance in references/method.md and record gaps in templates/output-template.md.

  2. Check founder participation. Establish how the founder will supply ideas and review drafts. Offer writing, voice notes, or interviews according to comfort and capacity. If participation is absent, produce an interview brief rather than an invented persona. See references/method.md.

  3. Choose a useful niche. Write an audience, expertise, and credibility sentence. Keep personal details that build connection, while making the business-relevant expertise recognizable. Evaluate topics against the rules in references/method.md.

  4. Interview for the origin story. Connect the founder's backstory, experienced problem, dissatisfaction with current approaches, and reason for building. Choose a customer-relevant obstacle as the villain. Use references/method.md and compare the revisions in examples/worked-examples.md.

  5. Extract substantive beliefs. Capture two or three positions, the experience behind each, and the implication for customers. Return to interviewing if the material is generic. Follow references/method.md.

  6. Check the company promise. Match each material claim to product behavior, capability, or an explicitly future direction. Narrow unsupported promises before drafting. Use the alignment guidance in references/method.md.

  7. Choose distribution and format. Start with the founder's audience or the company's customer reach, whichever is available. Choose a channel based on buyer evidence and state the audience benefit before naming a series. See references/method.md.

  8. Capture and draft real thinking. Build an idea backlog and voice notes from interviews, existing writing, and customer conversations. Shape each draft around an observation, context, and useful implication. Use references/method.md and the content fields in templates/output-template.md.

  9. Set a sustainable operating rhythm. Assign capture, drafting, founder review, publishing, and response ownership. Choose frequency from capacity and available ideas; do not turn daily posting into a guarantee. Follow references/method.md.

  10. Design the feedback loop. Record audience questions, qualified replies, discovery mentions, and repeated themes. Specify which signal would justify the next post or longer asset. Apply references/method.md and the feedback table in templates/output-template.md.

  11. Review, deliver, and iterate. Apply checklists/review-checklist.md, repair failures, and deliver the requested package with open questions. Assess reach alongside relationship and inbound evidence. Revisit the weakest underlying decision before increasing volume, using references/method.md.

Files in this skill

04 同仓库更多 Skills

getedgehq
getedgehq/skills

zero-downtime-cloud-move

Runbook for moving a live app from one cloud to another (Google Cloud to AWS, AWS to Google Cloud, a PaaS to your own account, or one storage provider to another) without downtime. The agent inventories what is really running, builds the new stack next to the old one, keeps a one-line rollback for every phase, proves the new stack with real workloads before any traffic moves, cuts over with a checklist, watches a fixed window after the switch, copies data with an idempotent job whose second pass must report 0 left, and deletes the old cloud last. Use when someone asks to migrate, move or replatform a production app, switch cloud providers, move a backend, database files or object storage, plan a DNS cutover, or decommission an old cloud account.

★ 5
getedgehq
getedgehq/skills

zayats-ceo-branding

Build an evidence-based CEO positioning paper, Personal Branding Roadmap, and editorial workflow using Marina Zayats's public method. Use for executive branding, LinkedIn ghostwriting briefs, profile strategy, and recurring CEO-approved content planning.

★ 5
getedgehq
getedgehq/skills

yc-app-roast

YC App Roast: roast a YC or a16z Speedrun application. Use when a founder wants their YC or Speedrun answers scored, asks "what would a YC partner think", wants the weak answers found or rewritten, or wants their draft checked before they submit. Scores every answer 0-10 against public advice from YC and Speedrun partners, names the top issue with the exact words that cost points, and writes a rewrite from the founder's own facts. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.

★ 5
getedgehq
getedgehq/skills

yc-app-review

YC App Review: get a YC or a16z Speedrun application reviewed by people you trust. Use when a founder wants friends, mentors or alumni to review their YC or Speedrun application, or asks to share their draft for feedback. Builds a shareable review page (one HTML file, application-portal look) where reviewers leave notes per question and press "Send my notes" to send them back as text, then parses the notes into proposed rewrites. Optional tracked private links per reviewer. Works for YC and a16z Speedrun. Not affiliated with Y Combinator or a16z.

★ 5
getedgehq
getedgehq/skills

x-growth-playbook

X Growth Playbook. Analyse a person's own X (Twitter) posts and tell them what to post next, with the numbers behind every claim. Compares quote posts vs originals, links vs no links, short vs long, time of day in their timezone, media vs text and the topics they name, reports medians with n, then writes a 10-step plan and the next 7 posts in their voice. Use when the user says "analyse my X posts", "what works on my Twitter", "how do I grow on X", "what should I post next on X", "audit my X account", or shares an X data archive, X API export or a list of their posts. Runs on the user's computer.

★ 5
getedgehq
getedgehq/skills

workplan

Create, update, or close work plans for multi-step tasks. Use when starting refactors, bug lists, feature work, migrations, or any task with 2+ steps. Also use after auto-compaction to re-orient. Triggers: "workplan", "work plan", "create a plan", "what's the plan", "where was I", or when Claude detects a multi-step task that needs tracking.

★ 5