Content Research Brief

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

Audit 0.4.1 · source sha 2515ce9634da · 15 Oct 2026Report an issue or request a re-scan

• PublisherAffitor GitHub organizationOwner of the repository this skill is read from
• Source folderAffitor/affiliate-skills/skills/content/content-research-briefThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict2515ce9634daA new audit runs when the source changes
• Repository statusNot archivedLast push 2 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Research trending topics, collect source articles, and generate a structured research brief for content creation. Stop writing from thin air — write from real sources. Use this skill when the user wants to research a…

---
name: content-research-brief
description: >
  Research trending topics, collect source articles, and generate a structured research
  brief for content creation. Stop writing from thin air — write from real sources.
  Use this skill when the user wants to research a topic before writing, collect sources
  for an article, create a research-backed content brief, or says "research [topic] for
  me", "find sources about [keyword]", "content brief for [topic]", "what's the latest
  on [product]", "research before writing", "collect articles about [keyword]",
  "trending news about [topic]", "gather sources for my article", "brief me on [topic]",
  "what are people saying about [product]", "news roundup for [keyword]",
  "research brief", "source collection", "content research", "prep research for writing".
license: MIT
version: "1.0.0"
tags: ["affiliate-marketing", "content-creation", "research", "content-brief", "source-collection"]
compatibility: "Claude Code, ChatGPT, Gemini CLI, Cursor, Windsurf, OpenClaw, any AI agent"
metadata:
  author: affitor
  version: "1.0"
  stage: S2-Content
---

# Content Research Brief

Research a topic by collecting 5-10 real source articles, auto-tagging them by theme,
extracting key data points, and synthesizing unique content angles. The output is a
structured research brief that any downstream content skill can consume.

**The problem this solves:** Most AI-written affiliate content is generic because it's
written from the model's training data — not from real, current sources. This skill
forces research-first content creation: find real articles, extract real data, then
write from those sources. The result is content with specific stats, real quotes, and
current information that readers (and Google) actually value.

Inspired by the [content-pipeline](https://github.com/Affitor/content-pipeline) approach:
Topic → Search → Select sources → Synthesize → Write with context.

## Stage

This skill belongs to Stage S2: Content — but acts as the research foundation for all content skills.

## When to Use

- Before writing any article, blog post, or long-form content
- When you need current data and stats about a topic (not just AI-generated claims)
- When creating comparison content (need real feature/pricing data from sources)
- When writing about a product launch, funding round, or industry trend
- After `trending-content-scout` identifies a topic — research it deeper
- When you want unique angles: N sources → N different content pieces

## Input Schema

```yaml
topic: string                  # (required) "HeyGen AI video tool", "email marketing trends 2024"
source_count: number           # (optional, default: 7) How many sources to collect (3-10)
source_types: string[]         # (optional, default: ["news", "blog"])
                               # Options: "news" | "blog" | "linkedin" | "youtube" | "reddit" | "academic"
freshness: string              # (optional, default: "month") "day" | "week" | "month" | "year" | "any"
product: object                # (optional) Focus research on a specific product
  name: string                 # "HeyGen"
  url: string                  # "https://heygen.com"
language: string               # (optional, default: "en") "en" | "vi" | any ISO 639-1 code
angle_count: number            # (optional, default: 3) How many unique content angles to generate
```

## Workflow

### Step 1: Search for Sources

Execute multiple searches to find diverse, high-quality sources:

```
Primary search:
  web_search "[topic]" → top results
  
Source-type-specific searches:
  IF "news" in source_types:
    web_search "[topic] news [current year]" → recent news articles
  IF "blog" in source_types:
    web_search "[topic] blog review analysis" → in-depth blog posts
  IF "linkedin" in source_types:
    web_search "[topic] site:linkedin.com" → LinkedIn posts/articles
  IF "youtube" in source_types:
    web_search "[topic] site:youtube.com" → YouTube videos with descriptions
  IF "reddit" in source_types:
    web_search "[topic] site:reddit.com" → Reddit discussions with real user opinions
  IF "academic" in source_types:
    web_search "[topic] research study data statistics" → data-heavy sources

Product-specific (if product provided):
  web_search "[product.name] review [current year]"
  web_search "[product.name] alternatives comparison"
  web_search "[product.name] pricing features"
  web_search "[product.name] news launch update"
```

Collect 15-20 search results, then filter down to `source_count` best sources.

### Step 2: Fetch and Extract Source Content

For each selected source:
1. `web_fetch [url]` → extract full article text
2. If fetch fails (paywall, timeout) → use search snippet as summary, note limitation
3. Extract from each source:
   - **Title** and **URL**
   - **Published date** (if available)
   - **Key data points**: stats, numbers, percentages, dollar amounts
   - **Key quotes**: noteworthy statements from experts or users
   - **Main argument/thesis**: what is this source's core message?
   - **Unique information**: what does this source have that others don't?

### Step 3: Auto-Tag Sources

Tag each source with 1-3 theme tags:

| Tag | Trigger Keywords |
|-----|-----------------|
| **AI** | artificial intelligence, machine learning, GPT, neural, model |
| **Funding** | raised, funding, series A/B/C, investment, valuation, IPO |
| **SaaS** | software, subscription, platform, B2B, enterprise |
| **Tools** | tool, app, feature, integration, API, plugin |
| **Trends** | trend, growing, emerging, future, prediction, forecast |
| **Startup** | startup, founder, launch, early-stage, bootstrapped |
| **Growth** | revenue, ARR, users, growth, scale, market share |
| **Industry** | market, industry, sector, regulation, compliance |
| **Pricing** | pricing, cost, free tier, discount, plan, subscription |
| **Comparison** | vs, versus, alternative, compare, switch, migrate |
| **Tutorial** | how to, guide, step-by-step, tutorial, wa

Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-15
   ✓SAFE B 89 / 100

   first audit · source 2515ce9634da

Questions about Content Research Brief

• github.com/Affitor/affiliate-skills/tree/main/skills/content/con — the audited source at commit 2515ce9634da and every finding aboveObserved · 15 Oct 2026

Spotted something wrong? Report a correction · Methodology