Skip to content
Skills Library
Other · Writing

feedback

/feedback

Send feedback about founder-skills — report a bug, suggest an idea, ask for help, or share a win. Drafts your message and gives you a link to submit; nothing is sent automatically.

Licence
Apache-2.0
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
4
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Send feedback about founder-skills — report a bug, suggest an idea, ask for help, or share a win. Drafts your message and gives you a link to submit; nothing is sent automatically.

Arguments

/feedback [what you want to say]
Original author description

Send feedback about founder-skills — report a bug, suggest an idea, ask for help, or share a win. Drafts your message and gives you a link to submit; nothing is sent automatically.

How it works

  1. Privacy hard-stop (non-negotiable)
  2. Flow
Original SKILL.md headings · 45 lines, 372 words
SKILL.md preview
---
name: feedback
description: "Send feedback about founder-skills — report a bug, suggest an idea, ask for help, or share a win. Drafts your message and gives you a link to submit; nothing is sent automatically."
argument-hint: "[what you want to say]"
user-invocable: true
disable-model-invocation: true
---

# 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 `$`,
  use `Glob` with pattern `**/founder-skills/.claude-plugin/plugin.json` and `path` `/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

1. **Classify** with AskUserQuestion (one question, these options):
   Bug · Idea or feedback · Question / help · Share a win
2. **Gather** briefly (1–3 prompts): which skill, what happened / what you'd want.
3. **Draft + scrub** a clean body per the hard-stop above. Show it in full for review/edit.
4. **Offer private delivery:** ask if they'd rather send it privately by email
   instead of posting publicly. If yes, use the mailto route below.
5. **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=bug` |
   | Idea / feedback | `https://github.com/lool-ventures/founder-skills/discussions/new?category=ideas-feedback` |
   | Question / help | `https://github.com/lool-ventures/founder-skills/discussions/new?category=q-a-help-how-to` |
   | Share a win | `https://github.com/lool-ventures/founder-skills/discussions/new?category=show-and-tell-founder-wins` |
   | Private (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.
6. **Confirm:** tell them to review on the opened page and submit. Thank them. If they
   shared a win, mention it may help other founders.

Versions

RepositoryScoreLicence
This page · lool-ventures/founder-skills90Apache-2.0
shaunjones-gh/lilystack100MIT
superset-sh/superset100MIT
Embassy-of-the-Free-Mind/sourcelibrary-v2100AGPL-3.0
minanyang/10x-agent100MIT
Insilico-org/plsi100MIT
blackbeard-tech/pair100Apache-2.0
optimiziramsi/skills100MIT
AMDResearch/omniprobe100MIT

Database snapshot: 13.11.2026 · package version 15515ec7f648 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100submit-feedback
    Turn a title and markdown body you write into a prefilled GitHub new-issue link, which the user clicks to file feedback about the skills under their own account. Nothing is sent by the skill. Use when the user asks to report a bug, a suggestion, or other feedback about a skill.
  • 100report-issue
    Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.
  • 90sent-feedback
    Reports user-authorized feedback about Sent MCP tools to the Sent team. Use when the user asks to report a bug, request a missing feature, or pass along a confusing result or praise about Sent. Feedback is read by Sent staff; it does not open a support ticket or return an…
  • 100share-feedback
    Helps someone report a problem, suggest an improvement or request a new feature for Tejit's Non Profit Tools, and files it for the maintainer once they approve. Use when someone says "suggest an improvement", "report a problem", "something went wrong", "share feedback", "request…
  • 100moonpay-feedback
    Submit feedback, bug reports, or feature requests for the MoonPay CLI. Use when the user encounters issues, wants to suggest improvements, or has general feedback.
  • 90feedback-intake
    Help the user file a bug report or feature request for Nimbalyst. Activates when the user opens the in-app feedback flow or runs /feedback:bug-report or /feedback:feature-request. Coordinates evidence gathering, anonymization, and posting to GitHub Issues.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.