pick-post-topic
/pick-post-topic
Wybiera temat kolejnego wpisu z najnowszych wiadomości o AI i proponuje go, gdy nie ma gotowego tematu.
- Autor
- duncan-wen ↗
- Repozytorium
- dwen-cms ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wybiera temat kolejnego wpisu z najnowszych wiadomości o AI i proponuje go, gdy nie ma gotowego tematu.
Oryginalny opis (EN)
Pick a Topic for the next Post from recent AI news. Use when asked what to write next, or asked for a new Post without a Topic.
Jak działa
- Steps
Podgląd SKILL.md
--- name: pick-post-topic description: Pick a Topic for the next Post from recent AI news. Use when asked what to write next, or asked for a new Post without a Topic. --- # pick-post-topic You turn recent AI news into a shortlist of Topics the Owner could write next, then hand the one they pick to `write-post`. Terms (Topic, Post, Tag, Draft, Owner) are `GLOSSARY.md`'s. The news is in the `ai-news` MCP server. Read it with `search` and `read_item` only: `whats_new` marks Items seen for every client that shares the server, and that can't be undone. ## Steps 1. **List what's covered.** Read the `title`, `description` and `tags` of every `content/posts/*/index.mdx`, and the open Drafts: `gh pr list --state open --search "head:post-" --json title,headRefName`. Done when you can name every Topic already written or in a Draft. 2. **Search.** Call `search` with `since` 7 days before today, `limit: 100` and `summary_length: 160`, leaving `categories` out so one call covers all four. When the Owner gave a range or a keyword, use it as `since`/`until` or `query` instead. A week often holds more than 100 Items: whenever a call returns exactly `limit` Items, call again with `until` set to the oldest returned `published_at`. Done when every call has come back short of `limit` and you've read every returned title and summary. 3. **Shortlist.** Group Items about the same subject into one candidate Topic. An Item whose only Category is News joins only with a technical angle (a model, API or tool the Owner can try). A candidate **fits** when: - a Reader who doesn't code can follow it: its finding and why it matters fit in plain words, with no code, table or experiment needed to understand it. This ranks above every other condition; - the Owner can try it hands-on in an afternoon and share what happened (use a new tool, compare two models' answers to one question, try a prompt), beyond retelling the news; a light try, never an eval suite or a multi-version experiment; - no Post or Draft from step 1 covers it; - an approved Tag in `content/tags.yml` covers it; a candidate that would need a new Tag ranks below every one that doesn't; - at most two candidates share a primary Tag. Done when you hold up to five fits, best first. 4. **Verify.** `read_item` every Item behind each candidate; when it comes back `truncated` before the part you need, call it again with a larger `max_length`. When `read_item` fails, read the same URL with the `web-fetch` agent, then look for another source reporting the same thing (`search` with a `query`, or a web search); a candidate whose text no route reaches is dropped, and you name it with the reason when you present. Keep a candidate only when its text backs its hook and shows the thing the Owner would use is available now (released, with a public API, open weights or a download). Replace a dropped candidate with the next fit and verify it too. Done when every candidate you will show rests on its source's text, read by you. 5. **Present** the candidates in the conversation, in Traditional Chinese, numbered, each with: - 暫定標題, written by `write-post`'s **Title** rule; - hook: the surprising finding or concrete result the Post would lead with; - 要動手做什麼: what the Owner builds, tries or measures; - 建議 Tag, from `content/tags.yml` (mark a new one 「新 Tag」); - 來源: each Item's title and URL. With fewer than three fits, show those you have, list the Items you dropped with the reason for each, and offer a wider range or a keyword. 6. **Hand off.** When the Owner picks one, invoke `write-post` with its Topic, hook, task and source URLs. Done when `write-post` has started.
Wersje
W bazie nie ma innych skilli o nazwie pick-post-topic.
Migawka bazy z 13.11.2026 · wersja paczki 3d89131e715b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100research-and-write
Prowadzi od pomysłu do gotowego posta na LinkedIn: najpierw bada temat, potem pisze wpis na podstawie ustaleń. - 100substack-post-drafter
Wybiera temat i pisze prywatny szkic wpisu na Substack w stylu autora, na podstawie danych rynkowych i pracy z repozytorium, nie publikując go. - 100write-post
Pisze, poprawia i przygotowuje wpisy w głosie autora, otwiera je jako Draft PR i udostępnia na LinkedIn lub Threads. - 100content-production
Prowadzi temat od pustej strony do gotowego tekstu, na przykład wpisu blogowego, artykułu lub poradnika. - 100twitter-post
Pisze wpis lub wątek na X na podstawie wyników researchu albo podanego tematu. - 100content-production
Prowadzi pełny proces tworzenia treści od tematu do tekstu gotowego do publikacji, na przykład wpisu blogowego, artykułu lub poradnika.