subscope-tunelisted

# /subscope-tune Targeted feedback. You mark only the surfaces that stand out (wrong or great), the engine nudges per-sub weights, and your config gets sharper without re-running the full `/profile` interview. Anything you skip is left untouched. ## When to use The daily list (`/subscope-run`) is mostly fine but a few surfaces are off. Instead of editing YAML by hand: tune. Flag the wrong ones, optionally the great ones, ignore the rest. ## Procedure ### Step 1: Pull recent surfaces ```bash cd "$CLAUDE_PLUGIN_ROOT" && PYTHONPATH=engine python3 -c " import json from subscope.lib import store with store.connect() as conn: rows = store.hot_surfaces(conn)[:15] print(json.dumps([{ 'id': r['post_id'], 'subreddit': r['subreddit'], 'title': r['title'], 'url': r['url'], } for r in rows], indent=2)) " ``` If the pool is empty, tell the user: *"No surfaces in the recent pool yet. Run /subscope-run first, then come back."* ### Step 2: Present in chat (mark only what stands out) Render the recent surfaces as a clean numbered list. Make clear that marking is OPTIONAL and partial: the user flags only what is off (and any standouts), and skipping changes nothing. ``` Your recent surfaces. Mark only the ones that are off, or great. Skip the rest, they stay as-is. b = surface less of this g = surface more (skip = leave alone) 1. r/RevOps "Anyone else drowning in HubSpot ops debt?" 2. r/SaaS "Looking for a fra