swipe-file-generator

Analyze content from URLs and compile analyses into a swipe file.

62|8|Updated Jan 20, 2026

Search Tags:#content-analysis #pattern-recognition #content-marketing #twitter-api #url-ingestion #swipe-file #deconstruction

Ready to run

npx skills add https://github.com/vincentchan/AI-Content-Engine --skill swipe-file-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swipe-file-generator
Source: https://github.com/vincentchan/AI-Content-Engine/tree/main/.claude/skills/swipe-file-generator
Command: npx skills add https://github.com/vincentchan/AI-Content-Engine --skill swipe-file-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The swipe-file generator analyzes high-performing content from URLs to study structure, patterns, and ideas, and compiles a living swipe file that informs content creation.

Core Features & Use Cases

Ingests URLs from /swipe-file/swipe-file-sources.md and identifies new items by comparing against /swipe-file/.digested-urls.json.
Fetches content using WebFetch (and uses the FxTwitter API for Twitter/X content) and stores results for analysis.
Deconstructs content with a dedicated subagent at ./subagents/content-deconstructor.md and appends structured analyses to /swipe-file/swipe-file.md.
Regenerates a Table of Contents and maintains a searchable, updated repository of patterns, hooks, and templates.

Quick Start

Place your source URLs in /swipe-file/swipe-file-sources.md, then run the swipe-file workflow to process new content and append analyses to /swipe-file/swipe-file.md.

Frequently Asked Questions about swipe-file-generator

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

FAQPage Schema

How do I automate swipe file pattern discovery from high-performing content?▼

Swipe file pattern discovery is automated by ingesting URLs from a sources file, fetching content via WebFetch or FxTwitter API, and deconstructing structure to append analyses to a master file. It checks a digested URLs registry to identify only new items for processing.

Can I analyze Twitter content structure using the FxTwitter API?▼

Yes, Twitter content structure is analyzed using the FxTwitter API. The system fetches tweets via this API, then passes the text to a content-deconstructor subagent to study patterns, hooks, and templates before appending results to your swipe file.

How does the swipe file generator avoid processing duplicate URLs?▼

Duplicate URLs are avoided by tracking processed items in a .digested-urls.json registry. Before fetching new content, the workflow compares your swipe-file-sources.md list against this registry to ensure only new URLs are fetched and analyzed.

What is the best way to maintain a searchable swipe file of content templates?▼

A searchable swipe file is maintained by appending structured content analyses to a master markdown file and regenerating a Table of Contents. This compiles patterns and ideas into a continuously refined repository for content creation reference.

Do I need to format my URLs in a specific file before running the swipe file workflow?▼

Yes, URLs must be placed in a specific markdown file named swipe-file-sources.md. The workflow reads from this designated file to discover new content links for pattern deconstruction and analysis.

What limitations exist when deconstructing content from URLs without WebFetch access?▼

Without WebFetch access, general URL content cannot be retrieved for analysis. The system relies on WebFetch to ingest standard web pages and the FxTwitter API specifically for Twitter/X content to execute the deconstruction workflow.