sales-bazzly

Name: sales-bazzly
Author: sales-skills

86stars9forks

How to install sales-bazzly?

sales-skills/sales/sales-bazzly

$npx -y skills add sales-skills/sales --skill sales-bazzly

Installs into the current project.

Summary

Bazzly platform help — AI-powered Reddit lead generation with intent scoring, contextual DM/reply drafting, high-karma autopilot accounts, a Chrome extension for posting from your own account, Reply Boost (smart upvotes), plus a REST API (api.bazzly.ai) and MCP server. Use when B

Files · 1

View on GitHub

SKILL.md

1	# Bazzly Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	Ask the user:
8
9	1. What do you need help with?
10	- A) Setting up monitoring (subreddits, keywords, targeting)
11	- B) Improving AI message quality (replies and DMs)
12	- C) Reducing false positive leads
13	- D) Credit optimization (getting more from the 100 monthly credits + top-ups)
14	- E) Account safety and ban prevention
15	- F) Chrome extension issues
16	- G) API / MCP integration (api.bazzly.ai, MCP server in Claude/Cursor)
17	- H) Something else — describe it
18
19	2. What's your setup?
20	- A) Paid "All in One" plan ($99/mo — 100 credits, unlimited leads, high-karma autopilot, API + MCP)
21	- B) Free start / evaluating
22	- C) Driving Bazzly via the REST API or MCP server
23
24	3. What's your goal?
25	- A) Lead generation (find people asking for recommendations)
26	- B) Brand awareness (get product mentioned in relevant threads)
27	- C) Competitor monitoring (watch competitor discussions to engage)
28	- D) Content promotion (share content in relevant communities)
29
30	If the user's request already provides context, skip to Step 2.
31
32	## Step 2 — Route or answer directly
33
34	- Multi-platform monitoring strategy or tool comparison → `/sales-social-listening [question]`
35	- Reddit monitoring with AI relevance scoring (0-100) and API access → `/sales-redship [question]`
36	- Reddit monitoring with auto-publish comments and virality detection → `/sales-keymentions [question]`
37	- Reddit + Quora with forced manual posting → `/sales-threadradar [question]`
38	- AI reply generation across Twitter + Reddit + LinkedIn → `/sales-replyguy [question]`
39	- Multi-platform monitoring (Reddit + X + LinkedIn + Quora + HN) → `/sales-parsestream [question]`
40	- Community monitoring across 15+ platforms with API → `/sales-syften [question]`
41	- Audience intelligence and pain point research → `/sales-reddinbox [question]`
42
43	Otherwise, answer directly from the platform reference below.
44
45	## Step 3 — Bazzly platform reference
46
47	Read `references/platform-guide.md` for the full platform reference — capabilities, pricing, credit system, Chrome extension setup, message optimization, and account safety guidance. For the REST API and MCP server (endpoints, auth, Claude/Cursor config), read `references/bazzly-api-reference.md`.
48
49	Answer the user's question using only the relevant section. Don't dump the full reference.
50
51	## Step 4 — Actionable guidance
52
53	Based on the user's situation:
54
55	1. Message quality — customize product context, review and edit every AI draft, vary style across replies
56	2. Credit optimization — prioritize high-intent leads, use AI drafts (0.1 credits) before committing to comments (10 credits)
57	3. Lead quality — narrow subreddit selection, refine targeting description, review intent scores before engaging
58	4. Account safety — always approve messages manually, limit daily sends, avoid generic templates, use personal Reddit account via Chrome extension
59	5. Coverage — if subreddit limits restrict you, prioritize highest-traffic communities for your niche
60
61	If you discover a gotcha not covered in `references/learnings.md`, append it there.
62
63	## Gotchas
64
65	Best-effort from research — review these, especially items about pricing and capabilities that may change.
66
67	- Chrome extension only. No Firefox, Safari, or mobile support. You must run the extension in Chrome (or Chromium-based browsers) for sending. No standalone desktop or mobile app.
68	- REST API + MCP, but NO webhooks/Zapier. Bazzly now ships a public REST API (`https://api.bazzly.ai`, Bearer `bzly_live_` keys, scopes read/write/top-ups) and an MCP server (`https://api.bazzly.ai/mcp`) for Claude/Cursor, so you CAN pipe opportunities into a CRM — but only by polling (e.g. `GET /public/v1/opportunities`), not via pus

People who liked this also viewed

6 picks

Type

sales-bazzly

86stars9forks

View on GitHub

How to install sales-bazzly?

sales-skills/sales/sales-bazzly

$npx -y skills add sales-skills/sales --skill sales-bazzly

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Bazzly Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	Ask the user:
8
9	1. What do you need help with?
10	- A) Setting up monitoring (subreddits, keywords, targeting)
11	- B) Improving AI message quality (replies and DMs)
12	- C) Reducing false positive leads
13	- D) Credit optimization (getting more from the 100 monthly credits + top-ups)
14	- E) Account safety and ban prevention
15	- F) Chrome extension issues
16	- G) API / MCP integration (api.bazzly.ai, MCP server in Claude/Cursor)
17	- H) Something else — describe it
18
19	2. What's your setup?
20	- A) Paid "All in One" plan ($99/mo — 100 credits, unlimited leads, high-karma autopilot, API + MCP)
21	- B) Free start / evaluating
22	- C) Driving Bazzly via the REST API or MCP server
23
24	3. What's your goal?
25	- A) Lead generation (find people asking for recommendations)
26	- B) Brand awareness (get product mentioned in relevant threads)
27	- C) Competitor monitoring (watch competitor discussions to engage)
28	- D) Content promotion (share content in relevant communities)
29
30	If the user's request already provides context, skip to Step 2.
31
32	## Step 2 — Route or answer directly
33
34	- Multi-platform monitoring strategy or tool comparison → `/sales-social-listening [question]`
35	- Reddit monitoring with AI relevance scoring (0-100) and API access → `/sales-redship [question]`
36	- Reddit monitoring with auto-publish comments and virality detection → `/sales-keymentions [question]`
37	- Reddit + Quora with forced manual posting → `/sales-threadradar [question]`
38	- AI reply generation across Twitter + Reddit + LinkedIn → `/sales-replyguy [question]`
39	- Multi-platform monitoring (Reddit + X + LinkedIn + Quora + HN) → `/sales-parsestream [question]`
40	- Community monitoring across 15+ platforms with API → `/sales-syften [question]`
41	- Audience intelligence and pain point research → `/sales-reddinbox [question]`
42
43	Otherwise, answer directly from the platform reference below.
44
45	## Step 3 — Bazzly platform reference
46
47	Read `references/platform-guide.md` for the full platform reference — capabilities, pricing, credit system, Chrome extension setup, message optimization, and account safety guidance. For the REST API and MCP server (endpoints, auth, Claude/Cursor config), read `references/bazzly-api-reference.md`.
48
49	Answer the user's question using only the relevant section. Don't dump the full reference.
50
51	## Step 4 — Actionable guidance
52
53	Based on the user's situation:
54
55	1. Message quality — customize product context, review and edit every AI draft, vary style across replies
56	2. Credit optimization — prioritize high-intent leads, use AI drafts (0.1 credits) before committing to comments (10 credits)
57	3. Lead quality — narrow subreddit selection, refine targeting description, review intent scores before engaging
58	4. Account safety — always approve messages manually, limit daily sends, avoid generic templates, use personal Reddit account via Chrome extension
59	5. Coverage — if subreddit limits restrict you, prioritize highest-traffic communities for your niche
60
61	If you discover a gotcha not covered in `references/learnings.md`, append it there.
62
63	## Gotchas
64
65	Best-effort from research — review these, especially items about pricing and capabilities that may change.
66
67	- Chrome extension only. No Firefox, Safari, or mobile support. You must run the extension in Chrome (or Chromium-based browsers) for sending. No standalone desktop or mobile app.
68	- REST API + MCP, but NO webhooks/Zapier. Bazzly now ships a public REST API (`https://api.bazzly.ai`, Bearer `bzly_live_` keys, scopes read/write/top-ups) and an MCP server (`https://api.bazzly.ai/mcp`) for Claude/Cursor, so you CAN pipe opportunities into a CRM — but only by polling (e.g. `GET /public/v1/opportunities`), not via pus

People who liked this also viewed

6 picks

Type