Skip to main content
skill CX Codex

getting-started · pluviobyte — Claude Code skill: setup and installation

The getting-started Claude Code skill guides the first setup of the emerging-keyword monitor template. It asks one question at a time about sources, schedules, and the workspace.

MIT ★ 551 updated 2026-11-10

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add Pluviobyte/saas-growth-agents --skill getting-started -a claude-code
Open on GitHub

What getting-started does

The skill walks the new owner through the emerging-keyword monitor setup in the first conversation. It asks for a name and timezone, then broadcast times and data sources. The default slots are 09:30, 11:58, and 17:50, with prescans about an hour earlier; the owner can choose different times.

For competitor sitemaps and tool directories, the bot asks for a niche and main competitors, then writes them to watchlist.json using the format in watchlist.example.json. Secrets belong in the local environment, not in the repository or memory. After collecting answers, the skill creates or adjusts routines and state files. It runs a dry prescan when told to go, and sends the first live broadcast only after confirmation.

What it helps with

  • set the timezone and broadcast schedule
  • choose sources for tracking search trends and memes
  • add competitors to watchlist.json
  • create monitoring routines and state files

Example prompts for the agent

  • Set up the emerging-keyword monitor template and ask me one question at a time.
  • Configure the sources and broadcast schedule for my timezone.
  • Prepare the monitoring workspace, but wait for my confirmation before the first live broadcast.

How to install getting-started

1Skills CLI (Vercel)

npx skills add Pluviobyte/saas-growth-agents --skill getting-started -a claude-code

2Manually: put the files in place

~/.claude/skills/getting-started/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/getting-started/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about getting-started

How do I install getting-started in Claude Code?

Run npx skills add Pluviobyte/saas-growth-agents --skill getting-started -a claude-code. The skill file is at ~/.claude/skills/getting-started/SKILL.md.

What does getting-started do?

It guides the initial setup of the emerging-keyword monitor, collecting preferences for sources and broadcast times before creating or adjusting routines and state files.

What keys does getting-started need?

Selected sources may use a Trends proxy key, plus optional TikHub, Product Hunt, and curated-feed tokens. Keep these secrets in the local environment rather than pasting them into chat.

Source text

SKILL.md · MIT
---
name: getting-started
description: >-
  Use 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)
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.

© Pluviobyte · MIT · Pluviobyte/saas-growth-agents

Similar skills

SKILL.md skills catalog →

getting-started by other authors comes first.

getting-started crewAIInc getting-started picks the right CrewAI abstraction and scaffolds a project through the CLI instead of by hand. Useful when a new crew or flow begins. CX Codex +1 9,100installs getting-started celigo getting-started guides AI agents through Celigo integration concepts, build order, and safety rules. Useful when designing pipelines across external systems without dependency errors. CX Codex +1 4,000installs resilience-hub-getting-started aws resilience-hub-getting-started sets up AWS Resilience Hub v2 from scratch, creates resilience policies with RTO and RPO targets, and runs an initial failure mode assessment. CX Codex +1 4,700installs neo4j-getting-started-skill neo4j-contrib The neo4j-getting-started-skill Claude Code skill takes a new Neo4j project from initial setup to a working application. It moves through database provisioning, graph modeling, data loading, queries, and app creation. CX Codex +1 940installs encore-getting-started encoredev encore-getting-started walks through Encore.ts setup from scratch: installs the CLI, creates an app, checks that it runs, and connects Encore's MCP servers. CX Codex +1 727installs encore-go-getting-started encoredev encore-go-getting-started guides a fresh Encore Go setup, from checking the CLI to running a hello-world app and connecting MCP servers. Use it when starting a project from scratch. CX Codex +1 575installs webflow-university:mcp-getting-started webflow webflow-university:mcp-getting-started is a skill that guides a first Webflow MCP workflow, checking the connection and helping choose a task and write a prompt. CX Codex +1 480installs investigate-without-getting-made UseOSINT investigate-without-getting-made — a skill that keeps your research from tipping off the subject: it maps your attribution surface, separates research identity from real identity, and says when a plain browser is enough. CX Codex +1 58,200installs

From the same set2

Project sponsors

Companies that keep this analytics open