Pluviobyte/saas-growth-agents / bots/newterm/skills/getting-started
getting-started
VerifiedUse on the first conversation after someone imports the emerging-keyword monitor template: onboard them one question at a time.
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)
- Name — What should they call you?
- Timezone — Confirm Asia/Shanghai or their preferred zone for the three daily broadcasts.
- Slots — Keep default 09:30 / 11:58 / 17:50 (with prescans ~1h earlier), or pick other times?
- 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.jsonin the workspace (format:watchlist.example.json). The repo ships no real watchlist. - 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 /
.envfile instead; if they paste anyway, store in env and do not write keys into memory. - X — Offer connecting the X plugin for meme discovery reads if not connected.
- Code — Confirm they have (or want you to scaffold) a
newterm-style workspace with prescan/night scripts and collectors from thenewterm-monitorskill. 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |