Swipe File Generator

**Judgment:** A well-scoped, high-utility skill for content and copy professionals who want structured, reusable swipe files. It is functionally strong and reasonably safe when used with non-sensitive, public URLs. **What it does well** - Orchestrates a clear pipeline: read URLs → detect new ones → batch-fetch → deeply analyze → update swipe file + registry. - Uses a thorough content deconstruction guide focusing on structure, psychological techniques, and recreatable frameworks. - Maintains a markdown swipe file with an auto-generated table of contents plus a JSON registry of processed URLs to prevent duplicates. - Handles Twitter/X links explicitly via FxTwitter’s API, which improves reliability for social content compared to naive HTML scraping. **Key risks & limitations** - **Network & privacy:** Sends URLs (and in practice, their content) to external services (web_fetch backend and FxTwitter). Not suitable for confidential, internal, or paywalled material you don’t want transmitted or potentially logged. - **Third-party dependency:** Relies on FxTwitter; if that API changes, rate-limits, or becomes unavailable, Twitter/X analysis may fail. - **Environment assumptions:** Requires a filesystem with the specific `swipe-file/` directory and a `web_fetch`-style tool; in constrained or atypical agent environments, setup changes may be required. - **Large-batch performance:** Batch fetching and detailed analysis of many long URLs can be slow and token-intensive in practice. **Recommended scenarios** - Best suited for marketers, copywriters, founders, and content strategists studying public, high-performing content at scale. - Useful when you explicitly want **recreatable patterns and frameworks**, not just summaries. - Less appropriate for sensitive corporate content, private knowledge bases, or contexts with strict data residency or scraping/ToS constraints.