Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

topics-briefing

Sterne0

Forks0

Aktualisiert21. Mai 2026 um 07:09

Generate a weekly SWE+AI topic briefing (HN + Lobsters + RSS newsletters + Exa fresh news, merged and bucketed by recency) for LinkedIn post ideation. Use whenever the user asks "what should I post about", "LinkedIn topic candidates", "weekly briefing", "topic ideas this week", or wants a single markdown brief to paste into their LinkedIn Claude project. Combines all four sources in one run.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

teimurjan

teimurjan/linkedin-post-collector

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

Mehr aus diesem Repository

gleiches Repository

post-ideator

teimurjan/linkedin-post-collector

Find LinkedIn post angles that can reach technical builders right now, but only when the angle is specific, differentiated, and defensible. Use when the user says "what should I post about", "pitch me ideas", "give me post angles", "find a topic", "ideate a post", or asks for fresh material without supplying a thought. Returns 3 to 5 scored idea briefs and writes shortlisted ones into ideas/YYYY-MM-DD.md.

2026-05-260

post-image

teimurjan/linkedin-post-collector

Generate an image-generation prompt for a LinkedIn post in one of three selectable styles (1930s rubber-hose cartoon, black sketch on white, or white sketch on black) with the post's hook rendered into the image as overlaid text. Prompts for the style when none is given. Picks a tactile, content-specific metaphor by reasoning over the whole draft, never a generic stand-in. Use when the user says "image for this post", "make a cover image", "generate the post image", "draw an image for X", or picks a draft to illustrate. Saves the prompt to `concepts/<date>-<slug>/prompt.md`, updates the draft's `concept_path`, and prints the prompt for the user to paste into their image tool. Trigger phrases: "post-image", "cover image", "draw the post".

2026-05-260

post-writer

teimurjan/linkedin-post-collector

Turn one approved idea brief or one raw user thought into a finished LinkedIn post in the owner's voice. Use when the user says "write a post", "draft this thought", "turn this into a LinkedIn post", "polish this for LinkedIn", picks an approved idea from post-ideator, or hands over raw material. Works from that single input only, grounded in the post corpus and post-patterns for voice and shape.

2026-05-260

post-critic

teimurjan/linkedin-post-collector

Critique one draft against the approved idea brief, the archive winners, and the pattern report. Use when the user says "review this draft", "should I publish this", "critique this post", or after post-writer completes a draft. Approves only strong drafts and returns a single rewrite plan when rejecting.

2026-05-250

post-cycle

teimurjan/linkedin-post-collector

Run the full LinkedIn post pipeline end-to-end in one go — briefing (if missing), top-posts + patterns context, ideator shortlist, writer draft, critic verdict. Use when the user says "full cycle", "run the pipeline", "do the whole flow", "post-cycle", "give me a post end to end", or wants a single command that replaces invoking topics-briefing, post-ideator, post-writer, and post-critic separately. Optionally accepts an idea number to pick from a freshly generated shortlist.

2026-05-250

posts-postmortem

teimurjan/linkedin-post-collector

Generate retrospective failure analyses for the worst-performing published posts so the writer and critic learn from misses, not just wins. Reads the bottom-5 posts by impressions from `posts/`, classifies each, and writes one postmortem file per post to `retros/postmortems/<post-date>-<slug>.md`. Use when the user says "run postmortems", "analyze bottom posts", "what failed", "post-mortem the losers", or "refresh failure analyses". Also invoked by `post-cycle` when the postmortem corpus is stale.

2026-05-250

name	topics-briefing
description	Generate a weekly SWE+AI topic briefing (HN + Lobsters + RSS newsletters + Exa fresh news, merged and bucketed by recency) for LinkedIn post ideation. Use whenever the user asks "what should I post about", "LinkedIn topic candidates", "weekly briefing", "topic ideas this week", or wants a single markdown brief to paste into their LinkedIn Claude project. Combines all four sources in one run.

topics-briefing

The headliner skill of this folder. Pulls HN, Lobsters, the RSS newsletter list, and Exa fresh-news, and emits a single markdown briefing grouped by source and bucketed by recency (Today / Last 3 days / Earlier this week). Designed to be pasted directly into a LinkedIn-post Claude project as context for the week's ideation.

The Bun CLI cannot call MCP tools, so this skill orchestrates a two-step flow: the CLI handles HN + Lobsters + RSS, then the skill appends an Exa section via the mcp__exa__web_search_exa tool.

Workflow

Run the CLI to fetch HN, Lobsters, and RSS into the briefing file:
```
bun src/cli/briefing.ts --limit 20 --out "briefings/$(date +%Y-%m-%d).md"
```
The CLI:
- Filters RSS to items from the last 7 days (drops everything older).
- Buckets each section into Today (≤24h), Last 3 days (24–72h), Earlier this week (72h–7d).
- Omits empty buckets.
Call Exa for fresh tech news:
- Tool: mcp__exa__web_search_exa
- Query: "latest software engineering and AI news this week"
- numResults: 15
- Drop any result older than 7 days. Bucket the rest with the same 24h/72h/7d windows.
Append the Exa section to the briefing file under ## Exa — fresh news (N), with ### Today (N) / ### Last 3 days (N) / ### Earlier this week (N) subheaders that mirror the CLI sections. Each item:
```
- [Title](url) — exa · 2026-05-19
```
Use the Edit tool to append; do not rewrite the rest of the file.

Output (markdown)

# Topics briefing — 2026-05-19

## Hacker News (23)
### Today (8)
- [Title](url) — ★142 · 87 comments · alice · 2026-05-19
### Last 3 days (10)
- ...
### Earlier this week (5)
- ...

## Lobsters (...)
### Today (...)
- ...

## Newsletters & blogs (...)
### Today (...)
- ...

## Exa — fresh news (...)
### Today (...)
- [Title](url) — exa · 2026-05-19

CLI flags

--limit N — items per source for HN/Lobsters (default 20). RSS uses a small fixed per-feed cap after the time filter.
--out path — write to file (otherwise stdout).
--json — emit merged JSON instead of formatted markdown (skips bucketing; Exa step is not run in JSON mode).

Cadence

Run the briefing weekly via /loop weekly /briefing so each run lands at briefings/YYYY-MM-DD.md.
The post-ideator skill reads the newest file in briefings/ automatically.
Older files stay in the repo as a record of what was trending when.

When to use

Trigger phrases:

"give me topic candidates for this week"
"weekly briefing" / "topics briefing"
"what should I post about on LinkedIn"
"fetch all sources"

Per-source errors are logged to stderr but don't abort the run — you'll get whatever sources came back successfully. If Exa fails, append a single line under the section noting the failure and continue.