research-content-router_skill

This skill orchestrates research to content production, delivering publishable conclusions with evidence chains and reusable material libraries.
  • Python

0

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill hexbee/hello-skills --skill research-content-router

  • openai.yaml293 B
  • SKILL.md5.0 KB

Overview

This skill organizes combined research and content production tasks into an A/B/C triage and runs a Research→Synthesis→Content pipeline to deliver publishable outputs with traceable evidence. It forces early convergence on audience, goal, format, angle, evidence level, and scale so writing proceeds from a stable brief. The result is conclusions plus evidence chains and a reusable asset library for future reuse.

How this skill works

The router first classifies the request as A (confirm then execute), B (execute then report assumptions), or C (archive silently) based on risk, need for sources, length, and data access. It fills six mandatory variables (audience, goal, carrier, angle, evidence level, scale), runs three stages—Research (collect conclusions with graded sources), Synthesis (one-line core argument, three evidence-backed supports, one contrarian risk), and Content (final deliverable plus titles, CTAs, and reusable micro-assets). Hard rules prevent progression without documented evidence and a stated counter-risk.

When to use it

  • You need publishable content grounded in evidence rather than raw notes.
  • The task must balance credibility, reach, and conversion (e.g., promotion vs. trust).
  • You want research outputs condensed into reusable assets (quotes, analogies, chart ideas).
  • Deliverables require traceable citations or one‑hand source verification.
  • You need a predictable workflow for multi-format repurposing (thread → longform → script).

Best practices

  • Always supply or confirm the six router variables before deep work to avoid rewrites.
  • Treat A-level tasks as interactive: present three directions and recommend one.
  • Require at least one contrarian risk in synthesis to surface failure modes.
  • Label every evidence item with S/A/B/⚠️ and never advance claims without sources.
  • Produce a small reusable asset pack (golden lines, analogies, chart suggestions) with each deliverable.

Example use cases

  • Research a market trend and publish a data-backed long article with source links and reusable quotes.
  • Turn interview notes into an evidence-backed 10-tweet thread with CTAs and alternate angles.
  • Archive a list of references and excerpts as C-level material for later content mining.
  • Create a short playbook (methodology) that converts research findings into actionable steps for customers.

FAQ

Risk factors like public publishing, legal/financial stance, need for primary sources, content length, or use of private data shift tasks to A; clear briefs with editing needs are B; simple archives or lists are C.

What minimum evidence is required to proceed?

Every candidate conclusion must have 2–4 supporting items labeled S/A/B/⚠️; claims without evidence are blocked from Stage 2.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational