---
name: selge-propose-solutions
description: Takes Selge feedback for a specific page, fetches the actual live page content, and produces a prioritized list of concrete changes - specific lines of copy to rewrite, specific UX moves to make, each citing the visitor quote that supports it. Use when the user wants actionable next steps from their feedback, asks "what should I do about this", wants to translate survey data into specific site changes, or is looking for solutions instead of a summary. Different from selge-review-results (analytical summary) - this is site-grounded recommendations tied to actual page content.
---

# Propose solutions from feedback

You translate Selge survey feedback into specific, site-grounded recommendations. The user gets 3-5 concrete changes tied to their actual page - not abstract advice.

## Workflow

### 1. Pick the page

If the user names a URL, use it. Otherwise:

1. Call `list_surveys` with `status: "active"`.
2. Pick the survey with the most responses in the last 30 days.
3. Read its `targeting.url_match` to find the primary page (e.g. `/pricing`).
4. Confirm with the user: "Working on <full URL>, based on the <survey-name> survey - sound right?"

### 2. Gather evidence in parallel

- `WebFetch` the full URL to read the actual current page copy.
- `get_results` for the survey on this page, `period: "last-30d"`.
- `list_responses` for the survey to capture verbatim open-text answers (cap at 50).

If `WebFetch` is unavailable in the assistant, or the page is behind auth, or returns an error: stop and ask the user to paste the page copy. **Do not proceed without the actual page content.** Generic advice without the page is exactly what this skill exists to avoid - if you can't see the page, you can't propose specific changes.

### 3. Cross-reference theme to page

For each major theme from the survey, find the matching content (or absence) on the page. The connection must be specific:

- Theme "Can't tell plans apart" + page has a comparison table → which row or column is unclear?
- Theme "Too expensive" + page leads with price → is price framing dominating value? Which headline?
- Theme "Not ready yet" + page has no soft path → no nurture CTA. What would catch a not-ready visitor?
- Theme "Confused by jargon" + page uses internal terminology → which exact words?
- Theme "Missing info" + page omits something they wanted → what specifically? Where would it go?

"Improve clarity" is not specific. "Line in the Pro tier card reads 'Advanced features' - rewrite as 'For teams of 5+ with multiple workspaces'" is specific.

### 4. Output contract

```
Page: <full URL>
Based on: <survey-name>, <n> responses, last 30 days

Top issue from feedback: <one sentence>

Proposed changes:

1. <Location on page - section name, headline text, or component>
   Current: "<exact quote from the page>"
   Visitor signal: "<verbatim survey quote>" (or "<theme>: <%>")
   Change to: "<concrete rewrite or specific UX move>"
   Confidence: <high / medium - based on how many responses point to this>

2. ...

(Cap at 5. Three strong changes beat five weak ones.)

These are drafts grounded in your data. Review before pushing live.
```

### 5. Read-only by design

This skill produces recommendations only. It does not edit pages, modify surveys, or call any mutating MCP tool. The user takes the output and edits their site themselves.

## Don'ts

- Don't propose more than 5 changes.
- Don't propose changes unsupported by feedback. If it's just your opinion, leave it off.
- Don't fabricate verbatim quotes. Use real responses, or mark a theme as paraphrased.
- Don't recommend full redesigns or strategic pivots - that's outside this skill's contract.
- Don't run if you couldn't fetch the page and the user didn't paste the content. Stop instead.
- Don't apply anything via MCP. Read + synthesis only.
- Don't suggest changes that require new MCP tools or product features. Stay within copy + UX moves the user can ship today.