Send founder-skills feedback
Help the user send feedback to the founder-skills maintainers (lool ventures). You never transmit anything. You draft a message and hand the user a link/text; they submit it themselves via their own browser or mail client.
Privacy hard-stop (non-negotiable)
- NEVER put session or artifact data in the draft: no company name, cap-table numbers, deck content, financials, valuations, or transcript excerpts.
- NEVER include file paths — they leak company slugs (e.g.
artifacts/acme-corp/...). - You MAY include, only after showing the user the exact final text: plugin version
(read
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json; if that path still begins with$, useGlobwith pattern**/founder-skills/.claude-plugin/plugin.jsonandpath/root/.claude/plugins, and read the one match; with no match, several, or a failed Read, write "unknown"), skill name, platform (Claude Code vs Cowork), and error class if it's a bug. Nothing else. - Show the complete payload and get an explicit "yes, send this" BEFORE producing any link.
Flow
-
Classify with AskUserQuestion (one question, these options): Bug · Idea or feedback · Question / help · Share a win
-
Gather briefly (1–3 prompts): which skill, what happened / what you'd want.
-
Draft + scrub a clean body per the hard-stop above. Show it in full for review/edit.
-
Offer private delivery: ask if they'd rather send it privately by email instead of posting publicly. If yes, use the mailto route below.
-
Produce the submit link (do not open or send it — the user clicks it):
Type Link Bug https://github.com/lool-ventures/founder-skills/issues/new?template=bug_report.md&title=<enc>&labels=bugIdea / feedback https://github.com/lool-ventures/founder-skills/discussions/new?category=ideas-feedbackQuestion / help https://github.com/lool-ventures/founder-skills/discussions/new?category=q-a-help-how-toShare a win https://github.com/lool-ventures/founder-skills/discussions/new?category=show-and-tell-founder-winsPrivate (any type) mailto:founder-skills@lool.vc?subject=<enc>&body=<enc>- URL-encode
<enc>values (spaces, newlines,#,&). - Discussions links don't reliably prefill the body — paste the drafted text into the thread after it opens. Issue and mailto links do prefill.
- If a prefilled URL would exceed ~6KB (GitHub) or ~1.5KB (mailto), skip the prefill and present the drafted text for the user to paste.
- URL-encode
-
Confirm: tell them to review on the opened page and submit. Thank them. If they shared a win, mention it may help other founders.


