Content Research Workflow skill

On-demand research bundle for the Aria Creative Suite.

by pawbytes·MIT license·★ 114 Stars on the repo·GitHub ↗

Use now

Inside this skill

SKILL.md · the author's own words
# Content Research Workflow

## Overview

This workflow produces an actionable research bundle — competitor analysis, trend spotting, and content opportunity identification — that f…

The output is not academic research. Every finding translates into a specific production recommendation: a design brief the Designer can ac…

**Args:** Accepts `--headless` or `-H` for autonomous execution. Supports scoped research via `--scope competitor`, `--scope trend`, `--sco…

## On Activation

Load available config from `{project-root}/.pawbytes/config/config.yaml` and `{project-root}/.pawbytes/config/config.user.yaml` (root level…

- `{user_name}` (null) — address the user by name
- `{communication_language}` (system) — use for all communications

Word-for-word excerpt, not a result. Read the full SKILL.md ↓

Files of Content Research Workflow

pawbytes/main1 file shown
SKILL.md
Show the full text191 lines

Content Research Workflow

Overview

This workflow produces an actionable research bundle — competitor analysis, trend spotting, and content opportunity identification — that feeds directly into visual and video production. It is a service workflow invoked on-demand by any Aria Creative Suite agent (Strategist, Designer, Video Producer, or Aria herself) when research context is needed to inform creative decisions.

The output is not academic research. Every finding translates into a specific production recommendation: a design brief the Designer can act on, a video format the Video Producer can storyboard, a content angle with hook and platform guidance. If a finding does not lead to a "make this" recommendation, it is context, not output.

Args: Accepts --headless or -H for autonomous execution. Supports scoped research via --scope competitor, --scope trend, --scope content, or --scope all (default).

On Activation

Load available config from {project-root}/.pawbytes/config/config.yaml and {project-root}/.pawbytes/config/config.user.yaml (root level and cra section). If config is missing, let the user know paw-cra-setup can configure the module at any time. Resolve:

  • {user_name} (null) — address the user by name
  • {communication_language} (system) — use for all communications
  • {document_output_language} (system) — use for generated document content
  • {default_brand} (null) — default brand to research if none specified

Load shared agency memory from {project-root}/.pawbytes/creative-suites/index.md. If a brand context is active or specified, load {project-root}/.pawbytes/creative-suites/brands/{brand-name}/guidelines.md and any existing research in {project-root}/.pawbytes/creative-suites/brands/{brand-name}/research/.

If --headless, complete the full pipeline without interaction using the active brand and scope from args. If interactive, greet and confirm research parameters before proceeding.

Pipeline

1. Research Brief Intake

Parse the research request:

Parameter Source Fallback
Brand Explicit request or --brand arg {default_brand} or active brand from index.md
Scope --scope arg or explicit request all (competitor + trend + content)
Focus areas Explicit questions or topics Derive from brand guidelines (industry, audience, competitors)
Target platforms Explicit or from brand guidelines Instagram, TikTok, YouTube, LinkedIn

If interactive: confirm parameters and ask if there are specific questions or competitors to prioritize. If headless: proceed with available context.

2. Brand Context Load

Load from {project-root}/.pawbytes/creative-suites/brands/{brand-name}/:

  • guidelines.md — brand identity, voice, visual style, industry, audience
  • research/ — any prior research reports (avoid redundant work, build on existing findings)

If no brand exists at the expected path, abort with a clear message suggesting brand onboarding through Aria.

3. Competitor Scan (scope: competitor or all)

Load ./references/competitor-scan.md for detailed research guidance.

Use Exa MCP tools to analyze 3-5 competitors across:

  • Content strategy and posting patterns
  • Visual style and design language
  • Video formats and production quality
  • Platform presence and engagement signals
  • Messaging and positioning

Production lens: For every competitor insight, note what it means for Designer and Video Producer. "Competitor X uses bold typography overlays on Reels" is more useful than "Competitor X has strong video presence."

4. Trend Analysis (scope: trend or all)

Load ./references/trend-analysis.md for detailed research guidance.

Search for trends relevant to the brand's industry and audience:

  • Trending content formats (carousel styles, video templates, interactive formats)
  • Visual and aesthetic trends (color palettes, typography, layout patterns)
  • Platform-specific trends (TikTok sounds, Instagram features, YouTube formats)
  • Topical trends and hashtag movements

Classify each trend: Fad (<3 months), Trend (6-18 months), Movement (2+ years), Declining (avoid).

5. Content Opportunity Identification (scope: content or all)

Cross-reference competitor gaps with trending topics to find exploitable angles:

  • What are competitors NOT doing that audiences want?
  • Which trends align with the brand's strengths but competitors have not adopted?
  • What content formats are under-served in this niche?
  • Where is engagement high but content quality low (opportunity to dominate)?

Produce an angle shortlist — 5-10 specific content angles, each with:

  • The angle (one sentence)
  • Why it works (gap + trend alignment)
  • Suggested format (carousel, reel, long-form video, etc.)
  • Target platform
6. Production Recommendations

This is the most critical output section. Translate every research finding into briefs that Designer and Video Producer can act on directly.

Load ./references/production-recommendations.md for recommendation templates.

For each recommended angle, produce:

Design briefs (for Designer):

  • Visual concept description
  • Reference style (e.g., "minimalist with bold type overlay," "before/after split")
  • Platform and dimensions
  • Suggested copy direction

Video briefs (for Video Producer):

  • Format and duration
  • Hook concept (first 3 seconds)
  • Scene structure outline
  • Audio/music direction
  • Subtitle style

Platform-specific notes:

  • Optimal posting context (time, hashtags, caption strategy)
  • Platform feature usage (Instagram collab, TikTok stitch, YouTube Shorts)
7. Report Generation

Produce research-report.md following the structure in ./references/report-template.md.

The report consolidates all findings into a scannable document with:

  • Executive summary (key findings in 3-5 bullets)
  • Competitor landscape
  • Trend landscape
  • Angle shortlist (the actionable core)
  • Production recommendations (the handoff to Designer/Video Producer)
  • Platform-specific playbooks
  • Sources with URLs
8. Save to Memory

Write the report to {project-root}/.pawbytes/creative-suites/brands/{brand-name}/research/research-report.md with frontmatter:

---
created: YYYY-MM-DDTHH:MM:SSZ
brand: {brand-name}
scope: {scope}
type: research
---

If scope-specific reports were generated, also save:

  • competitor-analysis.md (scope: competitor or all)
  • trend-analysis.md (scope: trend or all)
  • content-opportunities.md (scope: content or all)

Append to {project-root}/.pawbytes/creative-suites/daily/YYYY-MM-DD.md:

## [Strategist] HH:MM - Content Research Complete
- Brand: {brand-name}
- Scope: {scope}
- Key findings: {2-3 bullet summary}
- Angles identified: {count}
- Report: .pawbytes/creative-suites/brands/{brand-name}/research/research-report.md
9. Handoff

If interactive: present the angle shortlist and ask which angles to prioritize for production. Suggest routing to Designer or Video Producer with the relevant briefs.

If headless: report completion and file locations. The calling agent reads the report from memory.

Research Tools

Primary: Exa MCP
Tool Use
web_search_exa Competitor discovery, trend scanning, industry analysis
crawling_exa Deep page content extraction from competitor sites
get_code_context_exa Technical/platform documentation lookup

If Exa MCP is unavailable, use the Web Search tool for the same research queries.

Optional: Agent-Browser CLI

For social media content behind login gates (Instagram feeds, TikTok For You, LinkedIn). Only use if agent-browser is available and auth sessions exist at {project-root}/.pawbytes/creative-suites/.auth/.

Quality Standards

  • Every finding must cite a source URL
  • Every insight must connect to a production recommendation
  • Competitor analysis focuses on content strategy, not corporate profiles
  • Trend classification distinguishes fads from movements
  • The angle shortlist is the most important output — it must be specific and actionable
  • Production recommendations must be detailed enough for Designer/Video Producer to start work without further research
1---
2name: paw-cra-content-research
3description: On-demand research bundle for the Aria Creative Suite. Use when any agent needs competitor analysis, trend research, or content opportunity scanning to inform visual/video production.
4---
5 
6# Content Research Workflow
7 
8## Overview
9 
10This workflow produces an actionable research bundle — competitor analysis, trend spotting, and content opportunity identification — that feeds directly into visual and video production. It is a **service workflow** invoked on-demand by any Aria Creative Suite agent (Strategist, Designer, Video Producer, or Aria herself) when research context is needed to inform creative decisions.
11 
12The output is not academic research. Every finding translates into a specific production recommendation: a design brief the Designer can act on, a video format the Video Producer can storyboard, a content angle with hook and platform guidance. If a finding does not lead to a "make this" recommendation, it is context, not output.
13 
14**Args:** Accepts `--headless` or `-H` for autonomous execution. Supports scoped research via `--scope competitor`, `--scope trend`, `--scope content`, or `--scope all` (default).
15 
16## On Activation
17 
18Load available config from `{project-root}/.pawbytes/config/config.yaml` and `{project-root}/.pawbytes/config/config.user.yaml` (root level and `cra` section). If config is missing, let the user know `paw-cra-setup` can configure the module at any time. Resolve:
19 
20- `{user_name}` (null) — address the user by name
21- `{communication_language}` (system) — use for all communications
22- `{document_output_language}` (system) — use for generated document content
23- `{default_brand}` (null) — default brand to research if none specified
24 
25Load shared agency memory from `{project-root}/.pawbytes/creative-suites/index.md`. If a brand context is active or specified, load `{project-root}/.pawbytes/creative-suites/brands/{brand-name}/guidelines.md` and any existing research in `{project-root}/.pawbytes/creative-suites/brands/{brand-name}/research/`.
26 
27If `--headless`, complete the full pipeline without interaction using the active brand and scope from args. If interactive, greet and confirm research parameters before proceeding.
28 
29## Pipeline
30 
31### 1. Research Brief Intake
32 
33Parse the research request:
34 
35| Parameter | Source | Fallback |
36|-----------|--------|----------|
37| **Brand** | Explicit request or `--brand` arg | `{default_brand}` or active brand from index.md |
38| **Scope** | `--scope` arg or explicit request | `all` (competitor + trend + content) |
39| **Focus areas** | Explicit questions or topics | Derive from brand guidelines (industry, audience, competitors) |
40| **Target platforms** | Explicit or from brand guidelines | Instagram, TikTok, YouTube, LinkedIn |
41 
42If interactive: confirm parameters and ask if there are specific questions or competitors to prioritize. If headless: proceed with available context.
43 
44### 2. Brand Context Load
45 
46Load from `{project-root}/.pawbytes/creative-suites/brands/{brand-name}/`:
47 
48- `guidelines.md` — brand identity, voice, visual style, industry, audience
49- `research/` — any prior research reports (avoid redundant work, build on existing findings)
50 
51If no brand exists at the expected path, abort with a clear message suggesting brand onboarding through Aria.
52 
53### 3. Competitor Scan (scope: competitor or all)
54 
55Load `./references/competitor-scan.md` for detailed research guidance.
56 
57Use Exa MCP tools to analyze 3-5 competitors across:
58- Content strategy and posting patterns
59- Visual style and design language
60- Video formats and production quality
61- Platform presence and engagement signals
62- Messaging and positioning
63 
64**Production lens:** For every competitor insight, note what it means for Designer and Video Producer. "Competitor X uses bold typography overlays on Reels" is more useful than "Competitor X has strong video presence."
65 
66### 4. Trend Analysis (scope: trend or all)
67 
68Load `./references/trend-analysis.md` for detailed research guidance.
69 
70Search for trends relevant to the brand's industry and audience:
71- Trending content formats (carousel styles, video templates, interactive formats)
72- Visual and aesthetic trends (color palettes, typography, layout patterns)
73- Platform-specific trends (TikTok sounds, Instagram features, YouTube formats)
74- Topical trends and hashtag movements
75 
76Classify each trend: **Fad** (<3 months), **Trend** (6-18 months), **Movement** (2+ years), **Declining** (avoid).
77 
78### 5. Content Opportunity Identification (scope: content or all)
79 
80Cross-reference competitor gaps with trending topics to find exploitable angles:
81- What are competitors NOT doing that audiences want?
82- Which trends align with the brand's strengths but competitors have not adopted?
83- What content formats are under-served in this niche?
84- Where is engagement high but content quality low (opportunity to dominate)?
85 
86Produce an **angle shortlist** — 5-10 specific content angles, each with:
87- The angle (one sentence)
88- Why it works (gap + trend alignment)
89- Suggested format (carousel, reel, long-form video, etc.)
90- Target platform
91 
92### 6. Production Recommendations
93 
94This is the most critical output section. Translate every research finding into briefs that Designer and Video Producer can act on directly.
95 
96Load `./references/production-recommendations.md` for recommendation templates.
97 
98For each recommended angle, produce:
99 
100**Design briefs** (for Designer):
101- Visual concept description
102- Reference style (e.g., "minimalist with bold type overlay," "before/after split")
103- Platform and dimensions
104- Suggested copy direction
105 
106**Video briefs** (for Video Producer):
107- Format and duration
108- Hook concept (first 3 seconds)
109- Scene structure outline
110- Audio/music direction
111- Subtitle style
112 
113**Platform-specific notes:**
114- Optimal posting context (time, hashtags, caption strategy)
115- Platform feature usage (Instagram collab, TikTok stitch, YouTube Shorts)
116 
117### 7. Report Generation
118 
119Produce `research-report.md` following the structure in `./references/report-template.md`.
120 
121The report consolidates all findings into a scannable document with:
122- Executive summary (key findings in 3-5 bullets)
123- Competitor landscape
124- Trend landscape
125- Angle shortlist (the actionable core)
126- Production recommendations (the handoff to Designer/Video Producer)
127- Platform-specific playbooks
128- Sources with URLs
129 
130### 8. Save to Memory
131 
132Write the report to `{project-root}/.pawbytes/creative-suites/brands/{brand-name}/research/research-report.md` with frontmatter:
133 
134```yaml
135---
136created: YYYY-MM-DDTHH:MM:SSZ
137brand: {brand-name}
138scope: {scope}
139type: research
140---
141```
142 
143If scope-specific reports were generated, also save:
144- `competitor-analysis.md` (scope: competitor or all)
145- `trend-analysis.md` (scope: trend or all)
146- `content-opportunities.md` (scope: content or all)
147 
148Append to `{project-root}/.pawbytes/creative-suites/daily/YYYY-MM-DD.md`:
149 
150```markdown
151## [Strategist] HH:MM - Content Research Complete
152- Brand: {brand-name}
153- Scope: {scope}
154- Key findings: {2-3 bullet summary}
155- Angles identified: {count}
156- Report: .pawbytes/creative-suites/brands/{brand-name}/research/research-report.md
157```
158 
159### 9. Handoff
160 
161If interactive: present the angle shortlist and ask which angles to prioritize for production. Suggest routing to Designer or Video Producer with the relevant briefs.
162 
163If headless: report completion and file locations. The calling agent reads the report from memory.
164 
165## Research Tools
166 
167### Primary: Exa MCP
168 
169| Tool | Use |
170|------|-----|
171| `web_search_exa` | Competitor discovery, trend scanning, industry analysis |
172| `crawling_exa` | Deep page content extraction from competitor sites |
173| `get_code_context_exa` | Technical/platform documentation lookup |
174 
175### Fallback: Web Search
176 
177If Exa MCP is unavailable, use the Web Search tool for the same research queries.
178 
179### Optional: Agent-Browser CLI
180 
181For social media content behind login gates (Instagram feeds, TikTok For You, LinkedIn). Only use if `agent-browser` is available and auth sessions exist at `{project-root}/.pawbytes/creative-suites/.auth/`.
182 
183## Quality Standards
184 
185- Every finding must cite a source URL
186- Every insight must connect to a production recommendation
187- Competitor analysis focuses on content strategy, not corporate profiles
188- Trend classification distinguishes fads from movements
189- The angle shortlist is the most important output — it must be specific and actionable
190- Production recommendations must be detailed enough for Designer/Video Producer to start work without further research
191 

Discussion

Alternatives

Browser Automation SkillWeb browser automation with AI-optimized snapshots for claude-flow agentsCoding · MITDeepevalDeepEval evaluation workflow for AI agents and LLM applications. TRIGGER when the user wants to evaluate or improve an AI agent, tool-using workflow, multi-turn chatbot, RAG pipeline, or LLM app; add evals; generate datasets or goldens; use deepeval generate; use deepeval test run; send results to Confident AI; monitor production; run online evals; inspect traces; or iterate on prompts, tools, retrieval, or agent behavior from eval failures. AI agents are the primary use case. Covers Python SDK, pytest eval suites, CLI generation, traced evals, Confident AI reporting, and agent-driven improvement loops. DO NOT TRIGGER for unrelated generic pytest, non-AI test setup, or non-DeepEval observability work unless the user asks to compare or migrate to DeepEval; for instrumenting an app with DeepEval tracing, @observe, or framework integrations (use the `deepeval-tracing` skill); or for raw OpenTelemetry / OTLP export without the deepeval package (use the `deepeval-otel` skill).Business & ops · Apache-2.0Dev browserBrowser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", "open the browser", or any browser interaction request.Business & ops · MITTurn into appTurn visible project context, a proven thread, skill, or workflow into a runnable Agent-Native app with simple buttons, visible agent steps, preview, and deployment handoff. Use when a user invokes `/turn-into-app` or asks to make a workflow into an app, including from Claude or ChatGPT on the web, including when the source is a spreadsheet link or upload.Business & ops · MIT