- Home
- Skills
- Marketing & SEO
- AI-Ready Content Brief
Works with the AI Agents you already use
AI-Ready Content Brief
This skill fixes the step before the draft, so the page answers real questions with real evidence.
Free
AI-Ready Content Brief
Example session with this skill installed
Create an AI-ready content brief for a guide on "Choosing a Headless CMS for Enterprise". Target audience is CTOs. Compare 3 competitors and include a source log for performance data.
- Read your context and instructions
- Compiled the ai-ready content brief
I have generated the content brief for your guide on choosing a Headless CMS. The research phase identified high-intent sub-questions around security, multi-regional delivery, and total cost of ownership. The evidence plan includes placeholders for specific throughput benchmarks which must be filled from your internal testing data.
Content Brief: Choosing a Headless CMS for Enterprise
| Field | Detail |
|---|---|
| Primary Job | Help CTOs evaluate headless architectures based on security, scalability, and developer experience. |
| Target Audience | Technical executives (CTOs, VPs of Engineering) at firms with >500 employees. |
| Answer-First Opening | An enterprise headless CMS must provide SOC2 compliance, GraphQL API support, and multi-tenant management to handle global scale. The choice depends on whether your team prioritizes developer flexibility or content editor ease-of-use. |
Section Map
- Section 1: The Enterprise Definition (Definition format). Budget: 200 words.
- Section 2: Selection Criteria (Table format). Budget: 400 words. Covers security, API limits, and SLA.
- Section 3: Contentful vs. Strapi vs. Sanity (Comparison format). Budget: 600 words.
- Section 4: Implementation Roadmap (Numbered steps). Budget: 300 words.
Source Log
- Source 1: Contentful, "Enterprise Security Standards," 2024, [URL]. Supports SOC2/ISO claims.
- Source 2: Strapi, "Self-hosted vs Cloud Performance," 2023, [URL]. Supports deployment flexibility.
- Source 3: [STAT + SOURCE URL]. Required for Sanity global edge cache latency numbers.
Open Items
- Owner to provide internal benchmark data for Sanity vs Contentful API response times.
- Legal review required for the competitor comparison disclosure.
Next steps
- Review the "Answer-First" opening to ensure it aligns with your brand's unique stance on headless.
- Replace the performance placeholders in the Source Log with your latest testing results.
- Pass this brief to the writer for the initial draft.
Connects securely to your tools. The creator never sees your data.
About this skill
Write the brief that makes the draft worth citing.
Most AI-written content fails the same way: it opens with filler, makes claims with no source, and invents statistics to sound credible. This skill fixes the step before the draft, so the page answers real questions with real evidence.
What it does
- Defines the page's one job: primary question, audience, outcome, and the conversion role kept after the answer.
- Researches for gaps, not for copying: reads competing pages, checks what AI assistants say (when you have access), and traces key facts back to primary sources.
- Maps sub-questions into an ordered section plan with formats and word budgets.
- Drafts the answer-first opening and tests it: does the passage still make sense when lifted alone?
- Plans evidence slots (primary source, original data, first-hand example, real quote, or "cut the claim") and keeps a source log of pages that were actually opened.
- Picks the right format per question: definition, comparison table, numbered steps, ranked list.
- Lints the brief and the finished draft with two bundled scripts.
How it works
- Collects topic, audience, brand limits, competitors and any first-hand material.
- Researches and builds the gap analysis.
- Maps sub-questions and drafts the opening.
- Assigns evidence and logs sources.
- Assembles the brief from a template and lints it.
- After drafting, runs the draft checker and a QA checklist.
What makes it different
- No invented facts, by rule. Missing evidence becomes a visible placeholder and an open item with an owner, never a made-up number.
- Linters you can run: the brief linter flags missing sections, source rows without URLs and vague evidence phrases ("studies show"). The draft checker flags filler openers, vague paragraph starts, figures with no source nearby and leftover placeholders. Tested on deliberately flawed and clean inputs.
- Honesty built in: disclosure of the brand's interest on comparison pages, fair treatment of competitors, extra care on health, legal and financial topics.
- Pairs with the GEO Citation Playbook and AI Citation Tracker, but works on its own.
Where it stops
- It does not guarantee rankings, citations or traffic.
- The scripts are heuristics: they cannot tell whether a claim is true or a source supports it.
- Research quality depends on web access; without it, every external fact is marked unverified.
See it in action
Example output illustrating the brief format on a fictional topic.
Request: "Brief for 'how to reduce late invoice payments' aimed at freelancers. We sell invoicing software (Acme). Competitors: FreshBooks, Wave."
Result (excerpt):
- Job: Primary question "how do freelancers reduce late invoice payments?" Audience: solo freelancers with under 20 clients. Outcome: pick and set up 3 habits. CTA after the answer.
- Answer-first opening: "Freelancers billing under 20 clients a month cut late payments most by invoicing within 24 hours of delivery, adding payment links and automating reminders. [STAT + SOURCE URL]"
- Sections: What causes late payment? | Which habits help most? (table, evidence slot P) | How do reminders work? (numbered steps) | What does software cost? (price table, checked on date) | How do Acme, FreshBooks and Wave compare? (table, disclosure required)
- Open items: 1 late-payment statistic with a primary source (owner: content lead), 1 customer quote with permission (owner: success team).
- Lint:
brief_lint.pyflagged "studies show" in the draft outline and 1 source row without a URL; both fixed before drafting.
Limitations (optional field)
- Does not guarantee any outcome.
- Heuristic linters; human review of claims is still required.
- Needs web access for primary-source research.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Marketing & SEO.
Requires web access for live research. Python scripts are heuristics only. Briefs do not guarantee rankings or AI citations. External facts remain unverified if web access is disabled.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free to use
No account required to browse
Trust & safety
Security scan
Security scan passed 9 days ago
- Free with an Agensi account