research-and-write

research-and-write is a skill for Claude Code, Codex from Arindam200/awesome-ai-apps. It costs 120 tokens per session (637 once invoked), scanned A, original, MIT.

A workflow that researches a topic and then turns the findings into a LinkedIn post.

In plain words
What is it for?
Use it when starting with a topic idea and needing both research and a completed LinkedIn post saved in an organized output folder.
Why use it?
It structures the work from source gathering to a finished post and makes the intended audience, angle, key points, and tone explicit.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it when starting with a topic idea and needing both research and a completed LinkedIn post saved in an organized output folder.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arindam200/awesome-ai-apps/research-and-write
About the project

Awesome AI Apps is a collection of 132 projects, tutorials, and recipes for building applications powered by large language models. Developers use it to explore text and voice agents, retrieval-augmented generation, workflows, MCP tools, memory, and fine-tuning.

Arindam200/awesome-ai-apps · 14,342 stars · on GitHub · dub.sh

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add Arindam200/awesome-ai-apps --skill research-and-write
Clone the repo
git clone --depth 1 https://github.com/Arindam200/awesome-ai-apps

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for research-and-write

README.md
[![agentmods](https://agentmods.dev/badge/skills/arindam200/awesome-ai-apps/research-and-write/github.svg)](https://agentmods.dev/skills/arindam200/awesome-ai-apps/research-and-write)
Your own site
<a href="https://agentmods.dev/skills/arindam200/awesome-ai-apps/research-and-write"><img src="https://agentmods.dev/badge/skills/arindam200/awesome-ai-apps/research-and-write/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for research-and-write

Your own site · 80×15
<a href="https://agentmods.dev/skills/arindam200/awesome-ai-apps/research-and-write"><img src="https://agentmods.dev/badge/skills/arindam200/awesome-ai-apps/research-and-write.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 120 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 637 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00120 $0.00637
Opus 5 $0.00060 $0.00318
Sonnet 5 $0.00024 $0.00127
Haiku 4.5 $0.00012 $0.00064

Measured 10d ago against content hash 8930244b1689, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

research-and-write scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

advance_ai_agents/deep_research_writing_agents_nebius_okahu/.agents/skills/research-and-write/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.mdmy-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:

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

Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 69 lines · 120 tokens per session scan A 8930244b1689

Subscribe to this mod's changes

research-and-write is a skill published in the GitHub repository Arindam200/awesome-ai-apps (14,342 stars, last pushed 2d ago), licensed MIT. It adds 120 tokens to every session and 637 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

api-docs

Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.

omnigent-ai/omnigent · 50 tokens

security-audit

Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.

omnigent-ai/omnigent · 64 tokens

Workspace Data Analyst

Analyze CSV files in the workspace and summarize insights.

VoltAgent/voltagent · 14 tokens

openkb-deck-editorial

A tool for creating a single-file HTML slide presentation from compiled knowledge-base content. Its visual style uses a warm cream background, serif typography, and brick-red accents.

VectifyAI/OpenKB · 117 tokens

openkb-html-critic

Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stack on top of every…

VectifyAI/OpenKB · 132 tokens