founder-brand-onboarding
First-run interactive setup for the founder-brand skill pack. Walks the operator through brand-config.json (audience, 4-pillar topic pools, cadence, drive-to URLs) and SOUL.md (voice fingerprints, phrases-I-refuse, stories reservoir, won't-write boundaries) in ~15 minutes. This is THE most important file in the pack — the whole point is sounding like the operator, not ChatGPT.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- founder-brand-onboarding
- license
- MIT
- description
- First-run interactive setup for the founder-brand skill pack. Walks the operator through brand-config.json (audience, 4-pillar topic pools, cadence, drive-to URLs) and SOUL.md (voice fingerprints, phrases-I-refuse, stories reservoir, won't-write boundaries) in ~15 minutes. This is THE most important file in the pack — the whole point is sounding like the operator, not ChatGPT.
- allowed-tools
- Read Write - Grep
- user-invocable
- false
02 资源文件 1
- 参考文档skill-report.json31.0 KB
03 SKILL.md 正文
Founder-Brand Onboarding — first-run setup
The most important setup in this pack. The point of founder-brand content is that it sounds like YOU. Without SOUL.md, the skill produces LinkedIn-influencer-voice slop.
Activation
Loaded automatically by founder-brand on missing brand-config.json
or SOUL.md.
Also user-invocable: "Set up founder-brand onboarding", "Configure voice".
Workflow
Step 1 — Voice in 3 sentences
Describe how you actually write — in 3 sentences. Not "professional yet
approachable." Specific.
Examples of useful answers:
"I write declarative, with one claim per sentence."
"I lead with the receipt before the explanation."
"I don't soften with hedges — I either claim it or cut it."
Don't generalize. Tell me what's true about YOUR writing.
Save to SOUL.md (top section).
Step 2 — Phrases I use a lot (5-10)
Pull up your last 10 emails / posts / messages. What phrases show up
repeatedly? These are your voice fingerprints.
Examples (not yours — yours will differ):
"The lever is..."
"Specifically:"
"Here's the receipt:"
"What actually moved the number..."
5-10 phrases. These show up naturally in every output.
Save to SOUL.md.
Step 3 — Phrases I refuse (5-10)
What phrases would you NEVER write? Be specific. These get banned in
addition to the framework's banned-patterns list.
Common refuses:
"Synergy"
"Leverage" (as verb)
"Circle back"
"Delve into"
"Game-changing"
YOUR refuses might include things others use freely. Capture them.
Save to SOUL.md.
Step 4 — Voice settings
Pick your settings:
Formality: Casual / Professional / Direct
Sentence length: Short (≤15w) / Medium / Mixed
Confidence: High (outright) / Hedged / Calibrated
Humor: Dry / Never / Often
Profanity: Never / Sparingly / Often
First-person: I / We / Both
Emoji: Never / Sparingly (≤1/post) / Often
Save to SOUL.md.
Step 5 — Stories reservoir (3-5)
Give me 3-5 specific receipts you can cite. Anonymized but specific.
These become the case-study reservoir every Proof-pillar post pulls from.
Examples:
"The Series-B SaaS that hit 14 SQLs in 30 days from a PSP rewrite"
"The bootstrapped agency that went 2% → 11% reply rate"
"The DevTools company that closed $80k ACV in 90 days after EVP retier"
Each story needs:
- A specific (anonymized) client/company descriptor
- A specific number / metric / outcome
- A specific lever that drove it
Save to SOUL.md.
Step 6 — Won't-write boundaries
Hard nos. What topics will you NOT touch?
Common:
Political topics
Personal life specifics
Hot-takes-for-engagement
Industries you don't actually serve
Capture yours.
Save to SOUL.md.
Step 7 — Audience + 4-pillar topic pools
Now the brand-config side.
AUDIENCE:
1. Primary ICP (1 sentence)
2. What they already know
3. What they don't know yet
4-PILLAR TOPIC POOLS (3+ topics each):
PILLAR pool — big claims / POVs / contrarian takes
• Topic 1
• Topic 2
• Topic 3
PROOF pool — specific receipts / case studies / metrics
• <draws from your stories reservoir>
PROCESS pool — how you do the work / SOPs / frameworks
• <Process you teach>
• <Framework you use>
PERSON pool — human stories / stakes / why you care
• <Your story 1>
• <Your story 2>
Save to brand-config.audience + brand-config.pillars.
Step 8 — Cadence + business outcomes
CADENCE:
Posts per week (default 4 — 1 per pillar)
Rotation order (default: pillar → proof → process → person)
Default platform (linkedin / x / both)
Auto-critique before post (yes/no)
BUSINESS OUTCOMES:
Drive-to URL (the primary CTA destination)
Lead magnet URL (the soft offer for skeptical readers)
Call URL (booking link for hot replies)
Save to brand-config.cadence + brand-config.business_outcomes.
Step 9 — Write the files + smoke test
✓ brand-config.json — audience + 4 pillars (×3 topics each) + cadence + outcomes
✓ SOUL.md — voice + 8 phrases used + 7 refused + 5 stories
Try a smoke test:
> Generate a Proof pillar post about <one of your stories>
The output will:
- Use your phrases-I-use list naturally
- Refuse your phrases-I-refuse list
- Cite the actual story (not invent one)
- Match your voice settings
- Be ≤200 words, 1-sentence opener, scannable body, no engagement bait
Step 10 — Refresh cadence
Voice evolves. Re-run onboarding when:
- You catch yourself using phrases not in your fingerprint list (add them)
- The audience shifts
- Quarterly minimum
Re-run: `/founder-brand onboarding refresh`
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.