Consulting Research Miner

Workspace: use the selected project and its AGENTS.md; keep existing entity folders and Reality headings. Business paths below are relative to that project. Bundled resources are relative to this installed skill; sibling capabilities resolve by their installed names. Never search another private checkout for missing inputs. Use workspace identity, audience, pricing, and DESIGN.md fonts. Local _work adapters and evals are optional workspace tools, not bundled dependencies. Check presence and current help first; otherwise use an available connector for the same scoped operation. If neither exists, report that step incomplete. For missing scorers, perform the stated checks and label the result manual/unscored; never invent a numeric score or successful provider action.

Harvest the research wiki (a read-only, content-only source) into the content backlog. The mining protocol, path config, and boundary rules live in integrations/research/AGENTS.md — read that first if present; if no research source is configured, report it unavailable without searching neighboring repositories. This skill is only the harvest loop layered on top of it.

When to run

Friday cadence (via recoup-internal-consulting-friday-review), on demand ("harvest research"), or whenever the wiki's log.md has advanced since integrations/research/_work/LAST_MINED.

Steps

1. Follow the protocol. Read integrations/research/AGENTS.md → resolve the wiki path, then read the wiki's for-builders.md + CLAUDE.md QUERY operation. You are running a QUERY against the wiki.
2. Find the delta. Read the wiki's log.md; select pages added/changed since _work/LAST_MINED. First run (never): seed from the highest-signal pages — everything under patterns/ plus the paged artifacts/ + concepts/ (skip sources/, meta/, and tooling).
3. Read whole pages. For each selected page read the entire page — especially ## What we'd steal and ## Patterns demonstrated. Don't skim only the steal bullets (the wiki's own anti-rule).
4. Translate analysis → angles. Turn each portable idea into a first-person content angle that shows your expertise (teach it / argue it / show the receipts), not a third-person book report. Keep the strongest ~5–10 across the delta — quality over a dump (the weekly target is 15–20 ideas).
5. Write atomic signals to signals/ — one type: content-idea file per kept idea (YYYY-MM-DD-<slug>.md; schema in signals/AGENTS.md), each with: hook, intent (audience / TAM), formats ([linkedin] or [article]), status: new, and source: {type: research, ref: "[[wiki page]]"} so it traverses back to the page it came from.
6. Promote durable POVs. If a page yields a reusable explanation/framework (not just a hook), write it as a type: insight signal (status: evergreen) in signals/, its [[wiki page]] as source.
7. Stamp + report. Update _work/LAST_MINED to the newest harvested log.md date. Report: pages mined · ideas written · POVs promoted · any gaps (topics you expected but the wiki lacked).

Discipline

• Cite or omit. Every claim/figure/quote in a card carries its [[wiki page]] (and load-bearing [[sources/…]]). Anything you can't trace → label [UNVERIFIED], or leave it out.
• Read-only. Never write to the wiki; never copy its pages into this repo — only distilled cards
  • cited POVs cross the boundary.
• Content only. This never touches clients/ or pipeline/. Research is a content source.