Agent skill · writing content · jeremylongshore
blog-topic-research
Build a deduplicated editorial backlog from current, traceable demand and authoritative product evidence. Use when deciding which long-tail topics are worth writing before drafting begins. Trigger with "research blog topics" or "find evidence-backed content ideas".
Why this skill is useful
Adds a comprehensive framework for generating SEO-driven blog topics backed by verifiable user demand, including structured outputs and evidence links.
What it needs
About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Evidence-Backed Blog Topic Research Overview Find specific editorial opportunities supported by real user questions and current primary sources. Each accepted topic includes an evidence trail, search intent, version context, known-answer status, and duplicate-risk decision. This workflow does not invent search volume or treat autocomplete as proof of commercial value. It separates observed demand from editorial judgment. Prerequisites Target audience, product or subject boundary, business goal, locale, and preferred language Existing titles, canonical URLs, slugs, and planned backlog for cannibalization checks Approved topic clusters and formats, if the publication uses a taxonomy Current access to public search results, official documentation, changelogs, issue trackers, and relevant community sources A requested count between 1 and 100; default to 25 when omitted Tool Discipline Use Read for the supplied inventory and taxonomy. Use WebSearch to discover candidate questions and WebFetch to verify the actual source page, date, title, and context. Use Write or Edit only after the user approves backlog changes; do not store private community data, credentials, or unnecessary personal information. Instructions 1. Confirm scope, audience, locale, time horizon, count, excluded subjects, and the publication's definition of a useful conversion or reader outcome. 2. Read the existing coverage inventory. Normalize case, punctuation, product names, versions, error codes, and canonical URLs while preserving the original titles. 3. Search across at least three suitable signal classes: official docs or changelogs, public issue trackers, vendor forums, Stack Overflow, Reddit, or visible search suggestions. Respect access controls and site terms. 4. Fetch each candidate source. Capture its title, URL, publication or update date when available, exact short evidence excerpt, source type, and whether it is primary or community evidence. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/blog-topic-research