Skip to content
Back to skills

Research And Write

ASecurity

End-to-end workflow: research a topic and then write a LinkedIn post about it. Use this skill whenever the user wants the full pipeline — from a topic idea to a finished LinkedIn post. Triggers on: 'research and write a post about', 'create a LinkedIn post about [topic]', 'I want to post about', 'write about [topic] for LinkedIn', or any request that implies both researching a subject and producing a LinkedIn post from it. This is the go-to skill when the user gives you a topic and expects a ...

  • 17 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 30, 2026
documentationgo

Works with

  • mcp

Security analysis

A100/100

Scanned May 30, 2026

npx -y skills add gabrielmoreira/agent-skills-mirror --skill research-and-write --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Research And Write?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Research And Write
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/gabrielmoreira-research-and-write/badge)](https://www.skillsdirectory.com/skills/gabrielmoreira-research-and-write)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: research-and-write
description: "End-to-end workflow: research a topic and then write a LinkedIn post about it. Use this skill whenever the user wants the full pipeline — from a topic idea to a finished LinkedIn post. Triggers on: 'research and write a post about', 'create a LinkedIn post about [topic]', 'I want to post about', 'write about [topic] for LinkedIn', or any request that implies both researching a subject and producing a LinkedIn post from it. This is the go-to skill when the user gives you a topic and expects a finished post."
---

# Research and Write

End-to-end workflow: research a topic, then write a LinkedIn post from it. Chains the `deep-research` and `linkedin-writer` MCP servers.

## Input Preparation

Gather from the user:
1. **Topic** — what to research
2. **Guideline** — how the post should be written (becomes `guideline.md`)

If the user only gives a topic, ask for the guideline details (angle, audience, key points, tone) or suggest a default based on the topic.

## Working Directory

All output goes into `outputs/{slug}/` relative to the project root. Derive the slug from:
- The dataset seed/guideline filename if the user references one (e.g., `my-topic_seed.md` → `my-topic`)
- Otherwise, slugify the topic (lowercase, hyphens, no special chars, max 60 chars)

Create the directory if it doesn't exist.

Create `guideline.md` in the working directory:

```markdown
# LinkedIn Post Guideline

## Topic
[Core topic]

## Angle
[Perspective]

## Target Audience
[Who reads this]

## Key Points to Cover
[3-5 bullets]

## Tone
[How it should sound]
```

## Execution

### Phase 1: Research

Load the `research_workflow` MCP prompt from the `deep-research` server and follow the workflow instructions using the available tools:
- `deep_research` — for web research queries
- `analyze_youtube_video` — for any YouTube URLs the user provides
- `compile_research` — to produce the final research.md

Use `outputs/{slug}/` as the `working_dir` for all tool calls. This produces `research.md`.

Tell the user when research is complete.

### Phase 2: Write

Read the `WORKFLOW_INSTRUCTIONS` from `src/writing/routers/prompts.py` and follow those steps exactly, using the `linkedin-writer` MCP tools. The working directory `outputs/{slug}/` already has `guideline.md` and `research.md` from Phase 1.

The `generate_post` tool internally runs 4 evaluator-optimizer iterations (review + edit cycles) to refine the post before producing the final version.

## After Completion

Present the final `outputs/{slug}/post.md` and `outputs/{slug}/post_image.png` to the user. Offer to edit with feedback.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.