Swipefile Compiler

Reads recent signal tracking notes and memory logs, then produces one structured swipefile artifact summarizing patterns, hooks, CTA types, and reuse notes.

When to Use

• Weekly or on-demand signal synthesis.
• When asked to "compile the swipefile", "summarize creator signals", or "what patterns are we tracking?"
• Before content planning sessions to ground packaging decisions in observed data.

What This Skill Does

1. Reads the most recent memory logs from ~/.openclaw/workspace/memory/ (last 7 days).
2. Extracts: hooks, CTAs, format patterns, platform tactics, and recurring themes.
3. Classifies each item by category (hook, CTA, format, tactic, insight).
4. Outputs one structured markdown file with pattern counts and reuse notes.

What This Skill Does NOT Do

• Does not fetch new URLs or external content.
• Does not generate new content — only compiles and classifies observed signals.
• Does not publish or distribute the swipefile.
• Does not overlap with x-link-best-effort (no fetch logic here).

Output Format

# Weekly Swipefile — [date range]

## Summary
[X] signals compiled. [Y] unique patterns identified.

## Hooks (top 10)
1. [hook text] — source: [date], pattern: [curiosity | contrarian | data-shock | story]
...

## CTA Types
- [CTA pattern]: [frequency], [example]
...

## Format Patterns
- [format]: [platform], [notes]
...

## Reuse Notes
- [Which patterns to apply to current content pipeline items]
- [Which hooks to test next]

Save to: ~/.openclaw/workspace/mission-control/operations/swipefile-[date].md

Acceptance Test

• Given the last 3 days of memory logs contain at least 10 tracked signal entries with hooks and CTAs.
• When the skill is invoked.
• Then the output file contains categorized hooks, CTA types, format patterns, and at least 3 reuse notes.
• Pass: file saved, all 4 categories present, no uncategorized items >20%.

Edge Cases

• If memory logs are sparse (<5 signal entries), report "insufficient signals for compilation" rather than padding.
• If a signal entry has no clear hook or CTA, classify as "insight" rather than forcing a category.
• Skip memory entries that are purely operational (system logs, build notes) — only extract content/distribution signals.