content-brief

Generate structured content briefs from Notion and knowledge graph research.

1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/Mattyreed1/fractal-agent-skills --skill content-brief-mattyreed1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-brief
Source: https://github.com/Mattyreed1/fractal-agent-skills/tree/main/content-brief
Command: npx skills add https://github.com/Mattyreed1/fractal-agent-skills --skill content-brief-mattyreed1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of hollow, unresearched content creation by enforcing a rigorous, deliberation-first approach to brief writing that ensures every piece of content is built on a locked, defensible core claim.

Core Features & Use Cases

  • Deliberation-First Workflow: Forces a pressure-test of the core claim before any research begins, ensuring the argument is concrete and non-obvious.
  • Automated Retrieval Cascade: Aggregates context from Knowledge Graphs, Notion databases, and memory files to build a comprehensive, evidence-backed brief.
  • Standardized Handoff: Produces a structured, hook-agnostic brief that serves as a high-fidelity blueprint for subsequent content stages like scripting and visual design.

Quick Start

Use the content-brief skill to generate a detailed context brief for the locked concept regarding the new agent memory architecture.

Frequently Asked Questions about content-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an evidence-backed content brief from multiple research sources?

Generating an evidence-backed content brief requires aggregating multi-source research from Knowledge Graphs and local files into a unified, structured format. The system deliberates on core claims first, ensuring the final editorial plan is defensible and context-rich.

What is a deliberation-first approach for editorial content strategy?

A deliberation-first content strategy pressure-tests the core claim before any research begins, ensuring the argument is concrete and non-obvious. This prevents hollow, unresearched content creation by locking the foundational concept prior to drafting.

Can I use Notion APIs to build automated research retrieval for content briefs?

Notion APIs integrate directly into the content brief workflow to synthesize knowledge graph entities and prior work. This automated retrieval cascade aggregates context from Notion databases and memory files to build comprehensive editorial blueprints.

What's the best way to standardize content production workflows for scripting and visual design?

Standardizing content production workflows requires producing a structured, hook-agnostic brief that serves as a high-fidelity blueprint. This format ensures seamless handoff to subsequent content stages like scripting and visual design.

Do I need local project file systems to orchestrate high-impact content briefs?

Local project file systems are required to synthesize knowledge graph entities and prior work into the unified brief format. Integrating these local files with Notion APIs enables comprehensive, multi-source research aggregation.

Why does my content brief workflow require a locked core claim before research?

A locked core claim is required before research to enforce a rigorous, deliberation-first approach to brief writing. This ensures every piece of content is built on a defensible foundation rather than hollow assumptions.