Research trending content ideas using Trigify + WebSearch, grounded in what's actually resonating in your niche. Use this skill when the user says "content ideas", "what should I post about", "trending topics", "what's working on LinkedIn", "find content ideas", or "research ideas". Also trigger automatically as Step 1 of the /content routine.
Find 5-10 ranked content ideas by pulling from live Trigify monitoring data (LinkedIn + YouTube + Twitter) and supplementing with WebSearch. Every idea is grounded in real engagement signals — not guesses.
This skill is Step 1 of the /content routine. Its output feeds into youtube-ideation and all downstream skills.
Pull a maximum of 3 results per search — we want the freshest, highest-signal items, not volume.
Read these files before anything else:
context/offers.md — what [YOUR_NAME] sells and positions aroundcontext/content-pillars.md — the 3 pillars and their mix (40/35/25)context/trigify-search-ids.md — all current search IDsRun via Bash:
trigify search results --id c5e37ac7-8233-486a-b4f1-8572fc1cb88f --limit 3 --job-title "Consultant" --seniority "Senior"
Remove the --job-title and --seniority filters if you want broader results (e.g. when the filtered set returns fewer than 3 results).
| Search | ID |
|---|---|
| LinkedIn AI Tools & Automation | c5e37ac7-8233-486a-b4f1-8572fc1cb88f |
For each result, note: post text snippet, author name/title, reaction count, comment count, post date.
If you need to create or modify a Trigify search, consult the
trigify-toolsskill first — it has Boolean query rules and keyword strategy patterns that prevent common mistakes.
Run via Bash for each channel (run in parallel if possible):
trigify search results --id <id> --limit 3
| Channel | ID |
|---|---|
| Nick Saraev | fa70f67a-f756-4be9-b3e5-c28dd47d48ea |
| Chase AI | da60a9ec-ea05-4c03-aca3-daaab6e3ff63 |
| Grace Leung | 63b46b1a-ae4a-4570-b00a-6afd8928aebd |
| Nate Herk | 577d6e5f-c847-420d-bd90-453686a274f2 |
For each result, note: video title, channel name, publish date.
If a search returns 0 results: The channel may not have published recently. Note it as "no recent data" and continue with what's available.
Run via Bash for each search (run in parallel if possible):
trigify search results --id <id> --limit 3
| Search | ID | What it monitors |
|---|---|---|
| Claude Code X posts | 5932f5da-4c52-43db-9652-81e2125a4a0f | Posts mentioning Claude Code |
| Boris Claude Code | ef5249ad-a9f6-4464-bb2f-dc2064a43f17 | Boris's profile feed |
For each result, note: post text, engagement (likes/retweets if available), post date.
Run 2 targeted WebSearch queries to catch anything Trigify missed:
"Claude Code" OR "context architecture" trending 2026 — angle validationAI automation solopreneur content ideas 2026 — topic performance signalsUse results to fill gaps, not to replace Trigify data.
For each item collected, score it silently on 3 factors (1-3 each):
| Factor | What it means |
|---|---|
| Signal strength | Engagement relative to the source's typical performance |
| Pillar fit | Does it map cleanly to one of your 3 pillars? (P1: AI Workflows, P2: Social Selling, P3: Solopreneur) |
| Uniqueness | Could [YOUR_NAME] add a distinct angle that doesn't already exist on the topic? |
Total score = Signal + Pillar fit + Uniqueness (max 9). Keep top 10.
Present 5-10 ranked ideas in this format for each:
## Idea #N — [Title / Topic]
**Pillar:** P1 / P2 / P3
**Source:** [LinkedIn | YouTube by X | Twitter | WebSearch]
**Signal:** [engagement data — reactions, comments, views, likes]
**Why it fits your audience:** [1 sentence connecting to ICP pain point]
**Suggested post type:** [one of the 6 LinkedIn types or YouTube]
**the user's unique angle:** [what makes HIS take different from what already exists]
End the report with:
Pillar balance check: X ideas for P1 / Y for P2 / Z for P3 (target: ~4/3/3)
Recommended starting point: [which idea has the best signal + lowest production friction]
Save to inbox/outputs/md/YYYY-MM-DD-acquisition-content-ideas.md
Tell the user:
"Ready. Run
acquisition-content-youtube-ideationto pick one and go deep on it, or call me again tomorrow for a fresh batch."
| Situation | Action |
|---|---|
| All Trigify searches return 0 results | Fall back fully to WebSearch for this run. Note in output. |
| Only some searches have results | Use what's available, note which searches returned nothing |
| Results are older than 2 weeks | Flag as stale. Run WebSearch harder to compensate. |
| No strong pillar P3 ideas emerge | Generate 1-2 P3 ideas manually from .claude/skills/acquisition-content-newsletter-repurpose/references/my-story-doc.md to maintain 40/35/25 balance |
| User runs this standalone (not in /content) | Same workflow — still reads context files, still saves output |