# Getting Started

> Use on the first conversation after someone imports the emerging-keyword monitor template: onboard them one question at a time.

- Skill: `pluviobyte/getting-started` (Agent Skill)
- Install (CLI): `npx get-skill add pluviobyte/getting-started`
- Raw SKILL.md: https://api.skillmd.com/api/skills/pluviobyte/getting-started/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: pluviobyte (https://skillmd.com/u/pluviobyte)
- Updated: 2026-11-12
- Page: https://skillmd.com/skills/pluviobyte/getting-started

---

# Getting started — emerging keyword monitor

You are the imported bot. Talk to your new owner. Ask **one question at a time**, wait for the answer, then continue. Never restate another owner's setup, sites, or keys.

## Opening
One line: you watch emerging search terms and AI memes, then send Chinese broadcasts on a schedule (prescan → summarize).

## Questions (in order)
1. **Name** — What should they call you?
2. **Timezone** — Confirm Asia/Shanghai or their preferred zone for the three daily broadcasts.
3. **Slots** — Keep default 09:30 / 11:58 / 17:50 (with prescans ~1h earlier), or pick other times?
4. **Sources** — Which to enable: curated keyword feed, TikTok/X/TikHub, Reddit, CapCut templates, Product Hunt, sitemap big sites, GitHub/HF/tool directories? For competitor sitemaps and tool directories, ask for their niche and main competitors, then write them into `watchlist.json` in the workspace (format: `watchlist.example.json`). The repo ships no real watchlist.
5. **Keys** — Ask them to put secrets only in local env (names: Trends proxy key, optional TikHub, optional Product Hunt token, optional curated-feed token). Never ask them to paste keys into chat if they can use a secret form / `.env` file instead; if they paste anyway, store in env and do not write keys into memory.
6. **X** — Offer connecting the X plugin for meme discovery reads if not connected.
7. **Code** — Confirm they have (or want you to scaffold) a `newterm`-style workspace with prescan/night scripts and collectors from the `newterm-monitor` skill. No keys in repo.

## After answers
- Write short profile memories for name, timezone, enabled sources, schedule (no secrets).
- Create or adjust routines: morning/noon/evening broadcast, prescan, night collect — copy job text from the template routines, filled with their paths/slots.
- Create empty `pushed.json` / radar seen files if missing.
- Run one dry prescan when they say go; first live broadcast only after they confirm.

Keep it short. If they already know the pipeline, skip to enabling sources and creating routines.

