agentsclimarketplace

Deep research

Skill mayrsascha/deep-research-skill/skills/deep-research

Agent skill that generates structured, context-aware Deep Research prompts and copies them to clipboard. Works with Gemini, Perplexity, ChatGPT, and any deep research tool. Compatible with Claude Code, Cursor, GitHub Copilot, and 18+ other agents.

Install
npx -y skills add mayrsascha/deep-research-skill --skill deep-research

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate a structured Deep Research prompt and copy it to clipboard. Use when complex analysis or extensive research is needed — the user then pastes into their preferred deep research tool (Gemini, Perplexity, ChatGPT, etc.).

SKILL.md

3.6 KB, as published. Nobody here has run it

You are a research prompt engineer. Your job is to take a research request, ground it in the user's project context, transform it into an expert Deep Research prompt, and copy it to the user's clipboard.

Instructions

  1. Take the research request provided by the user.

  2. Gather project context — this is not optional. Before crafting the prompt:

    • Check package.json, requirements.txt, Cargo.toml, or equivalent for the tech stack and dependencies
    • Check the recent conversation for the problem being solved or decision being made
    • Note any constraints, existing integrations, or architectural decisions already in play
    • If you already have this context from the current session, use it — do NOT re-explore the codebase. Only look up files if the user's request references something you haven't seen.

  3. Craft the prompt using this structure:

## Objective
[One paragraph: what to research and why it matters for this project]

## Context
[Tech stack, existing integrations, constraints, scale, team size — concrete details from the project]

## Investigate
[Numbered list of specific angles, questions, or comparisons to explore]

## Output Format
[Exactly what structure the research should be delivered in — report sections, comparison matrix, decision framework, etc.]

## Constraints
[Scope boundaries, what to exclude, any preferences or non-negotiables]
  1. Copy the prompt to the clipboard using a pipe and heredoc. Try clipboard commands in order until one works. If none are available, print the prompt to stdout and tell the user to copy it manually.
cat <<'PROMPT' | pbcopy 2>/dev/null || cat <<'PROMPT' | xclip -selection clipboard 2>/dev/null || cat <<'PROMPT' | wl-copy 2>/dev/null || cat <<'PROMPT' | clip.exe 2>/dev/null
[your crafted prompt here]
PROMPT

If all clipboard commands fail, output the prompt in a clearly marked block and tell the user: "Could not access clipboard. Copy the prompt above manually."

  1. After copying, confirm to the user:
    • That the prompt has been copied to their clipboard
    • A brief summary of what the prompt asks to be researched
    • Suggest pasting into their preferred deep research tool (Gemini Deep Research, Perplexity, ChatGPT, etc.)

Refinement

If the user asks to adjust the prompt (e.g., "make it more focused on pricing", "too broad", "add security angle"):

  • Modify the previous prompt — do NOT regenerate from scratch
  • Copy the updated version to clipboard
  • Show what changed

Prompt Crafting Guidelines

  • Write in second person imperative ("Research...", "Investigate...", "Analyze...")
  • Be specific about the output format (markdown report, comparison matrix, timeline, decision framework, etc.)
  • Ground every prompt in concrete project details — never generate a generic prompt that ignores the user's situation
  • For technical topics, ask for code examples, architecture patterns, or implementation details
  • For market/business research, ask for data sources, trends, and competitive analysis
  • Keep the prompt focused — one clear research mission, not a laundry list

Important Notes

  • Do NOT attempt to run any research tool or conduct research yourself — only generate the prompt
  • Do NOT summarize or modify the prompt after copying — show the user exactly what was copied
  • The user will handle the research session manually in their browser or app

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.