Run any Skill in Manus with one click

consulting-research-miner

Stars1

Forks0

UpdatedJune 30, 2026 at 20:38

Mine the external AI & Agents research wiki for content. Use on "harvest research", "content ideas from research", "mine the research wiki", on the Friday cadence, or whenever the research wiki (../research) has new material. Turns its cited analysis into atomic signals (signals/) that show the practice's agent/skill expertise — read-only; never copies wiki pages in.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

sidneyswift

sidneyswift/consulting-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

SKILL.md

readonly

name	consulting-research-miner
description	Mine the external AI & Agents research wiki for content. Use on "harvest research", "content ideas from research", "mine the research wiki", on the Friday cadence, or whenever the research wiki (../research) has new material. Turns its cited analysis into atomic signals (signals/) that show the practice's agent/skill expertise — read-only; never copies wiki pages in.

Consulting Research Miner

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; this skill is only the harvest loop layered on top of it.

When to run

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

Steps

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.
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).
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).
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).
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.
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.
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.

More from this repository

same repository

consulting-content-recycler

sidneyswift/consulting-plugin

Squeeze every published winner — repost proven posts with a fresh hook, re-share your own winners with added context, and fan one outlier post into multiple new formats. Use on "what should I repost", "recycle my winners", "this post popped, what now", "turn this outlier into more posts", "wring the towel", after an engagement pull shows a post outperforming baseline, or on the Friday review's recycle step. Reads published bundles + engagement data; stages new drafts; never auto-posts.

2026-07-091

consulting-friday-review

sidneyswift/consulting-plugin

The weekly content + system review ritual. Use on "run the Friday review", weekly cadence, or "what should I write this week". Good candidate to wire as a scheduled task.

2026-07-091

consulting-linkedin-hooks

sidneyswift/consulting-plugin

Write or critique the first line of a LinkedIn post (the hook) using patterns reverse-engineered from real top-performing posts. Use on "write hooks for this", "give me 10 hooks", "fix this hook", "why won't this hook land", "what's a scroll-stopping opener", or whenever drafting/critiquing a post's line 1. This is the dedicated hook engine; consulting-linkedin-post-architect handles whole-post structure and defers here for the hook; consulting-copy-writer governs voice/anti-slop.

2026-07-091

consulting-linkedin-post-architect

sidneyswift/consulting-plugin

Structure a high-performing LinkedIn post — pick the archetype and founder format (build log, documented failure, value post, receipt, contrast hook, milestone chapter), write a scroll-stopping hook, shape the body, format for mobile, choose the in-post CTA, and decide whether to pair an infographic. Use on "write a LinkedIn post", "make this post perform/go viral", "what hook should I use", "structure this for LinkedIn", "turn this insight into a LinkedIn post", "write a build log / failure / receipt / milestone post", or right after consulting-content-drafter. This is the post-STRUCTURE layer; consulting-copy-writer still governs voice/anti-slop, consulting-linkedin-publisher ships it.

2026-07-091

consulting-content-distribution

sidneyswift/consulting-plugin

Distribute one finished pillar article across every channel the same way — republish the same copy to the owned blog + LinkedIn newsletter + X (as an article, never a thread), ship the always-on companions (a LinkedIn promo post + an email to the list), point every link at the owned canonical URL, then find the live post and monitor its engagement into leads. Use after an article is written or published, on "distribute this", "post it everywhere", "atomize this article", "where else should this go", or when promoting a piece in content/04-published/.

2026-07-051

consulting-copy-editor

sidneyswift/consulting-plugin

Editorial copy-edit pass on a finished draft, run through a fresh-context subagent reviewer. Use on "copy-edit this", "edit this article", "do an editor pass", "give it a hard edit", "review my draft", "check this for slop", or as the last gate before publishing any long-form article, pillar, post, or email. Dispatches a fresh-eyes subagent that returns structured editor's notes (AI slop, non-conversational phrasing, confusing rhetoric, simpler-rewrite and narrative/storyline opportunities, and anything an editorial-outlet editor would flag); the main agent then triages and implements the accepted edits, then re-checks against the house standard.

2026-07-051

name	consulting-research-miner
description	Mine the external AI & Agents research wiki for content. Use on "harvest research", "content ideas from research", "mine the research wiki", on the Friday cadence, or whenever the research wiki (../research) has new material. Turns its cited analysis into atomic signals (signals/) that show the practice's agent/skill expertise — read-only; never copies wiki pages in.

Consulting Research Miner

When to run

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

Steps

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.
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).
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).
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).
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.
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.
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.