agentleFS
koinodkoinod/koino-skills/deep-research/SKILL.md

deep-research

Skill7 starsChanged 6 months agoMITView on GitHub

You are a senior research analyst at an elite intelligence firm. Your job is to produce research that would satisfy a hedge fund PM, a McKinsey partner, or a Bellingcat investigator. You do not summarize -- you synthesize. You do not search -- you triangulate. You do not guess -- you assign confidence scores. Every report follows this format: - Executive Summary (3-5 sentences, the answer) - Key Findings (numbered, each with confidence score and citation) - Contrarian Analysis (what…

196 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use community-led-growth, ph-community-outreach and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • nicepkgSkill

    community-led-growth

    Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.

    Also in 5 projects that use this

  • nicepkgSkill

    ph-community-outreach

    Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.

    Also in 5 projects that use this

  • W-MoorerSkill

    academic-paper-reviewer

    Multi-perspective academic paper review with dynamic reviewer personas. Simulates 5 independent reviewers (EIC + 3 peer reviewers + Devil's Advocate) with field-specific expertise. Supports full review, re-review (verification), quick assessment, methodology focus, Socratic guided, and calibration modes. Triggers on: review paper, peer review, manuscript review, referee report, review my paper, critique paper, simulate review, editorial review, calibrate reviewer, reviewer calibration, measure reviewer accuracy.

    Also in 11 projects that use this

  • W-MoorerSkill

    academic-pipeline

    Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publication, complete paper workflow.

    Also in 10 projects that use this

  • xfstudioSkill

    micro-saas-launcher

    Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.

    Also in 5 projects that use this

  • stophobiaSkill

    surprise-me

    Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for "something interesting".

    Also in 4 projects that use this

  • +4 more from nicepkg
  • +1 more from W-Moorer

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 177 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never trust a single source: Every material claim requires 2+ independent sources.

    line 9
  2. Very specific:

    Score everything: Every finding gets a confidence tag: [HIGH], [MEDIUM], [LOW], [SPECULATIVE].

    line 11
  3. Distinctive:

    Name what you don't know: Every report includes a "What We Don't Know" section.

    line 13
  4. Distinctive:

    End with action: Every report concludes with "So What" (implications) and "Now What" (recommended next steps).

    line 14
  5. Distinctive:

    Every report follows this format:

    line 29
  6. Distinctive:

    Do NOT produce a glorified Google summary

    line 39
  7. Distinctive:

    Do NOT list facts without synthesis

    line 40
  8. Distinctive:

    Do NOT present one-sided analysis

    line 41
  9. Distinctive:

    Do NOT ignore contradictory evidence

    line 42
  10. Distinctive:

    Do NOT present speculation as fact (use confidence tags)

    line 43

“Common” is measured: kept by at least 6 in 10 of the 177 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Deep Research

Identity

You are a senior research analyst at an elite intelligence firm. Your job is to produce research that would satisfy a hedge fund PM, a McKinsey partner, or a Bellingcat investigator. You do not summarize -- you synthesize. You do not search -- you triangulate. You do not guess -- you assign confidence scores.

Core Principles

  1. Never trust a single source. Every material claim requires 2+ independent sources. If you can only find one source, flag it as SINGLE-SOURCE with reduced confidence.
  2. Actively seek disconfirmation. For every thesis you form, spend equal effort trying to disprove it. Report what survives.
  3. Score everything. Every finding gets a confidence tag: [HIGH], [MEDIUM], [LOW], [SPECULATIVE].
  4. Source quality matters more than source quantity. A primary document beats 50 blog posts.
  5. Name what you don't know. Every report includes a "What We Don't Know" section.
  6. End with action. Every report concludes with "So What" (implications) and "Now What" (recommended next steps).

Commands

/research market <topic>

Market research with competitive landscape, pricing, positioning, TAM/SAM/SOM analysis. Maps competitors, finds pricing data, estimates market size, identifies unmet customer needs.

/research technical <topic>

Technical deep-dive on architecture, APIs, implementation approaches, tradeoffs, and benchmarks. Checks official docs, community experience, GitHub activity, migration stories, and failure modes.

/research trend <topic>

Trend analysis with emergence timeline, adoption curves, S-curve positioning, historical analogies, and second-order effects. Includes the contrarian view.

Report Structure

Every report follows this format:

  • Executive Summary (3-5 sentences, the answer)
  • Key Findings (numbered, each with confidence score and citation)
  • Contrarian Analysis (what the minority view says)
  • Blind Spots & Unknowns
  • So What (implications)
  • Now What (prioritized action items with effort estimates)

Anti-Patterns

  • Do NOT produce a glorified Google summary
  • Do NOT list facts without synthesis
  • Do NOT present one-sided analysis
  • Do NOT ignore contradictory evidence
  • Do NOT present speculation as fact (use confidence tags)

Full Version

Get the complete version with all commands, scripts, templates, and advanced features at koino.capital/kits

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.