⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
getting-started
>-
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
saas-growth-agents
Hand your SaaS growth chores to an agent that runs them every day.
Spot new search terms, find who ranks for them, check competitor backlinks, submit to directories, and file good posts into a knowledge base. These jobs repeat daily and follow fixed steps, which makes them perfect SOPs for an agent. Create a bot, send it one sentence, and it reads this repo, asks you a few questions, and sets itself up.
Quick start · The bots · One-line setup · AGENTS.md · Grok Bot free for 14 days · English · 简体中文
These are the SOPs and scripts the author runs for their own SaaS tools aimed at overseas markets. Any agent that can run terminal commands and keep long-lived instructions can use them.
Coming from douyin-comments? This repo is the old douyin-comments, now merged into the full growth system. The Douyin comments skill is unchanged and lives in the social analysis pack at
bots/social-kb/douyin-comments/. See how to reinstall.
The whole system runs on three rules:
- Scripts do the deterministic work: collecting, deduping, scoring and logging. Results are reproducible and replayable, never a model's "feeling".
- The agent judges: it reads what the scripts produce, then analyzes, extracts, verifies and reports. If data is missing it says so instead of making things up.
- You decide: the agent only pushes conclusions. Spending money, sending anything out and deleting all need your OK. Every correction you make becomes a new rule in its skills.
The bots
| Bot | What you do | What it does |
|---|---|---|
| New-term radar | Nothing | Three reports a day on newly searchable terms: new AI products, models, memes, templates. Sources include Google Trends, competitor sitemaps, new directory listings, Product Hunt, GitHub Trending, Reddit and TikTok |
| Site ops | Give it keywords and your product | Finds every site competing for a keyword, checks their DR and backlinks, tracks your own site's metrics daily, submits to free directories by the rules, and logs everything |
| Social analysis pack | Drop a link when you see something good | Fetches the original (X, Douyin, RedNote, YouTube, WeChat, any web page) → summarizes → extracts "what could improve your SOPs" against your own workflow → files it by topic. For Douyin it can also pull the full comment section |
Plus an unrelated extra, Trade radar: watches price moves and breaking events and pushes an analysis. It analyzes only and never places orders.
Which agent
Grok Bot, Muse, Dot, Hermes and OpenClaw all work, and so do Claude Code and Codex. AGENTS.md has the generic steps; each product just has its own name for "routines" (scheduled tasks) and "vault" (secret storage).
The author recommends Grok Bot. It comes with a cloud computer, a vault, skills and routines. These SOPs were first built on Grok Bot, and once installed they run around the clock on routines.
No Grok Bot yet? Sign up with the author's invite link to get 14 days free: https://grok.com/refer/bot?code=NASHTX8NMYH3 (This is a referral link and the author is rewarded for sign-ups. Grok's official page has the current terms.)
Quick start
-
Create a new bot in your agent.
-
Send it the matching sentence from bootstrap.md, for example:
Read AGENTS.md in https://github.com/Pluviobyte/saas-growth-agents and set yourself up as the newterm (new-term radar) bot. Ask me one question at a time. -
It asks you to put your AIsa key in its vault, does one run by hand to show you, and only turns it into a routine once you're happy.
The whole process is do it once → tweak until it's right → save as a skill → schedule as a routine.
The job descriptions and SOP docs inside the repo are written in Chinese. Agents read them fine, and the bot will talk to you in your language.
Where the data comes from
All external data goes through AIsa: one key for thousands of APIs, pay per call, with MCP support. This repo uses:
- SEO: DataForSEO SERP and Google Trends, Ahrefs
- Social: Twitter, TikHub (Douyin, RedNote), DataForSEO YouTube (transcripts, video info)
- Web: Firecrawl, Tavily
- Trade radar: CoinGecko, Financial (US stocks), Polymarket, FRED, Perplexity
Each API maps to one function in lib/aisa/sources.py, with paths and parameters checked against AIsa's official OpenAPI spec.
Every request carries a price cap and anything over it is rejected. Not sure what a call costs? Add --quote to ask first; quotes are free.
The AIsa links are the author's referral links. The Douyin comments module doesn't use AIsa; it runs in your own logged-in browser for free.
Optional: run logs
For a sturdier setup where you can trace what went wrong, add the run log module. It records:
- whether each routine ran, whether it succeeded, and what it cost
- what you approved
- when a rule was changed, and why
A nightly health check lists failed, stuck and missed runs, plus cost spikes.
⚠️ It uses more of your bot's quota, so it's off by default and the bot asks during setup. There are three levels:
- Light: approvals and rule changes only, almost no extra quota.
- Standard: adds a record for every routine run.
- Full: adds the nightly check and weekly archiving.
Logs are local files only, so AIsa costs don't change. (The module's doc is in Chinese; agents read it fine.)
Repo layout
saas-growth-agents/
├── AGENTS.md setup steps for the agent
├── bootstrap.md the one sentence to send your bot
├── lib/aisa/ AIsa layer: client.py (stdlib), sources.py (data sources), aisa_cli.py (CLI)
├── lib/runlog/ optional: run log, approvals, rule changes, nightly health check (uses more bot quota)
├── bots/
│ ├── newterm/ new-term radar: job.md · routines.md
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
bots/newterm/skills/getting-started/SKILL.md2.0 KBb2006262d747upstream ↗
--- 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? 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.README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/pluviobyte-saas-growth-agents-bots-newterm-skills-getting-started.md