Skip to content
Founder Workflows
Browse
Browse by stage

Find content gaps with a Claude Code agent and then cross-check against your live archive

A creator ran a published content gap agent with Perplexity and Firecrawl, got a scored gap report, then discovered her local files missed 37 published posts and the real problem was distribution.

Evidence: The author reports this. We have not checked it beyond reading the source.

The business problem

A prolific publisher does not know which topics she has not covered, and an analysis built on incomplete files can mislead.

What was tried

Following another author's walkthrough, she ran the agent in Claude Code with two connectors, Perplexity for trend research and Firecrawl for competitor scraping, giving it three files about who she is, what she publishes and who her competitors are. It produced a 629-line report in about 90 seconds with ten scored gaps, positioning, trending topics, keywords, series ideas and a 90-day calendar. She then had Claude's desktop app check her live Substack archive, which found 62 or more pieces against 25 in her workspace, and a script created 13 draft pages in her site's CMS for review.

What was reported (mixed)

She reports 37 published posts with no matching workspace file and 7 'drafts' already published, and concluded she had a distribution problem rather than a content creation problem. She estimates $0.30 to $0.50 per run. No traffic or ranking results from acting on the findings are reported.

Limitations

The gap suggestions and scoring method are not shown, and counts are given inconsistently in places. Setup hit three problems (an installation not found, an outdated connector address and a connector saved in the wrong settings scope). It is not stated how the archive was accessed, whether the 13 synced drafts were checked, or what content was sent to the external tools. Costs and 'free' key claims are unverified.

What you need

A Claude subscription, Claude Code, free Perplexity and Firecrawl API keys, and three short context files. Estimated cost is $0.30 to $0.50 per run.

Sources

Source published: March 2, 2026. Last reviewed here: October 11, 2026. Spot a mistake? Tell us.

Tools in this workflow

Related workflows