sales-aviso

Name: sales-aviso
Author: sales-skills

86stars9forks

How to install sales-aviso?

sales-skills/sales/sales-aviso

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

Installs into the current project.

Summary

Aviso AI platform help — end-to-end AI revenue operating system with 98%+ forecast accuracy, conversation intelligence, relationship intelligence, MIKI AI Chief of Staff, pipeline inspection, deal acceleration, and 200+ integrations. Use when setting up Aviso forecasting for comp

Files · 1

View on GitHub

SKILL.md

1	# Aviso AI Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	1. What do you need help with?
8	- A) Setting up Aviso or connecting CRM (Salesforce, HubSpot, Dynamics 365)
9	- B) Revenue forecasting (models, accuracy, AI vs adjusted vs sales forecast)
10	- C) Conversation intelligence (transcription, sentiment, emotion analysis, coaching)
11	- D) MIKI AI agent or GTM Agent Studio workflows
12	- E) Pipeline inspection, deal acceleration, or deal health scoring
13	- F) Relationship intelligence (Aviso Graph, org charts, engagement tracking)
14	- G) Integrations (CRM writeback, data warehouse, conferencing, engagement tools)
15	- H) Pricing or plan evaluation
16	- I) Troubleshooting (dashboards, sync, scoring, forecast confusion)
17
18	2. Which CRM are you connecting?
19	- A) Salesforce
20	- B) HubSpot
21	- C) Microsoft Dynamics 365
22	- D) Other (Freshworks, Oracle, SAP, Zoho, Pipedrive)
23	- E) Not sure / evaluating
24
25	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
26
27	## Step 2 — Route or answer directly
28
29	\| Problem domain \| Route to \|
30	\|---\|---\|
31	\| Comparing Aviso to other note-takers or CI tools \| `/sales-note-taker {user's question}` \|
32	\| Comparing Aviso to other revenue forecasting tools \| `/sales-forecast {user's question}` \|
33	\| Reviewing a specific call for coaching feedback \| `/sales-call-review {user's question}` \|
34	\| Building a coaching program using Aviso data \| `/sales-coaching {user's question}` \|
35	\| General CRM-to-tool integration patterns \| `/sales-integration {user's question}` \|
36	\| HubSpot-specific configuration \| `/sales-hubspot {user's question}` \|
37	\| Salesforce-specific configuration \| `/sales-salesforce {user's question}` \|
38
39	When routing, provide the exact command.
40
41	## Step 3 — Aviso platform reference
42
43	Read `references/platform-guide.md` for the full platform reference — modules, pricing, integrations, data architecture, known issues.
44
45	Answer the user's question using only the relevant section. Don't dump the full reference.
46
47	## Step 4 — Actionable guidance
48
49	You no longer need the platform guide — focus on the user's specific situation.
50
51	Setup priority: Connect primary CRM first (Salesforce or Dynamics 365 is best-supported), then configure forecasting hierarchies, then enable conversation intelligence on conferencing tools (Zoom/Teams), then set up MIKI workflows.
52
53	Forecast selection: Use "AI Forecast" as the primary prediction (100+ variable model). "Sales Forecast" reflects manager judgment. "Adjusted Forecast" is the manual override. When they disagree, investigate the gap — AI may see signals managers don't, or managers may have context AI lacks.
54
55	Evaluation tip: Aviso is enterprise-only with custom pricing (~$1,000/user/yr). Request a pilot with historical data to validate the 98% accuracy claim against your actual pipeline. Insist on seeing accuracy metrics on YOUR data, not benchmarks.
56
57	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
58
59	## Gotchas
60
61	> Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
62
63	- No public API documentation. Aviso Connect exists as an integration layer but has no public developer docs, endpoints, or auth specs. You cannot build custom integrations without engaging Aviso's team.
64	- Three forecast types cause confusion. AI Forecast, Sales Forecast, and Adjusted Forecast serve different purposes — users frequently report not understanding which to trust. AI Forecast is the model's prediction; Sales Forecast is the manager's call; Adjusted Forecast is the manual override.
65	- Dashboard customizations may revert. Multiple G2 reviewers rep

People who liked this also viewed

6 picks

Type

sales-aviso

86stars9forks

View on GitHub

How to install sales-aviso?

sales-skills/sales/sales-aviso

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Aviso AI Platform Help
2
3	## Step 1 — Gather context
4
5	If `references/learnings.md` exists, read it first for accumulated platform knowledge.
6
7	1. What do you need help with?
8	- A) Setting up Aviso or connecting CRM (Salesforce, HubSpot, Dynamics 365)
9	- B) Revenue forecasting (models, accuracy, AI vs adjusted vs sales forecast)
10	- C) Conversation intelligence (transcription, sentiment, emotion analysis, coaching)
11	- D) MIKI AI agent or GTM Agent Studio workflows
12	- E) Pipeline inspection, deal acceleration, or deal health scoring
13	- F) Relationship intelligence (Aviso Graph, org charts, engagement tracking)
14	- G) Integrations (CRM writeback, data warehouse, conferencing, engagement tools)
15	- H) Pricing or plan evaluation
16	- I) Troubleshooting (dashboards, sync, scoring, forecast confusion)
17
18	2. Which CRM are you connecting?
19	- A) Salesforce
20	- B) HubSpot
21	- C) Microsoft Dynamics 365
22	- D) Other (Freshworks, Oracle, SAP, Zoho, Pipedrive)
23	- E) Not sure / evaluating
24
25	Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
26
27	## Step 2 — Route or answer directly
28
29	\| Problem domain \| Route to \|
30	\|---\|---\|
31	\| Comparing Aviso to other note-takers or CI tools \| `/sales-note-taker {user's question}` \|
32	\| Comparing Aviso to other revenue forecasting tools \| `/sales-forecast {user's question}` \|
33	\| Reviewing a specific call for coaching feedback \| `/sales-call-review {user's question}` \|
34	\| Building a coaching program using Aviso data \| `/sales-coaching {user's question}` \|
35	\| General CRM-to-tool integration patterns \| `/sales-integration {user's question}` \|
36	\| HubSpot-specific configuration \| `/sales-hubspot {user's question}` \|
37	\| Salesforce-specific configuration \| `/sales-salesforce {user's question}` \|
38
39	When routing, provide the exact command.
40
41	## Step 3 — Aviso platform reference
42
43	Read `references/platform-guide.md` for the full platform reference — modules, pricing, integrations, data architecture, known issues.
44
45	Answer the user's question using only the relevant section. Don't dump the full reference.
46
47	## Step 4 — Actionable guidance
48
49	You no longer need the platform guide — focus on the user's specific situation.
50
51	Setup priority: Connect primary CRM first (Salesforce or Dynamics 365 is best-supported), then configure forecasting hierarchies, then enable conversation intelligence on conferencing tools (Zoom/Teams), then set up MIKI workflows.
52
53	Forecast selection: Use "AI Forecast" as the primary prediction (100+ variable model). "Sales Forecast" reflects manager judgment. "Adjusted Forecast" is the manual override. When they disagree, investigate the gap — AI may see signals managers don't, or managers may have context AI lacks.
54
55	Evaluation tip: Aviso is enterprise-only with custom pricing (~$1,000/user/yr). Request a pilot with historical data to validate the 98% accuracy claim against your actual pipeline. Insist on seeing accuracy metrics on YOUR data, not benchmarks.
56
57	If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there.
58
59	## Gotchas
60
61	> Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
62
63	- No public API documentation. Aviso Connect exists as an integration layer but has no public developer docs, endpoints, or auth specs. You cannot build custom integrations without engaging Aviso's team.
64	- Three forecast types cause confusion. AI Forecast, Sales Forecast, and Adjusted Forecast serve different purposes — users frequently report not understanding which to trust. AI Forecast is the model's prediction; Sales Forecast is the manager's call; Adjusted Forecast is the manual override.
65	- Dashboard customizations may revert. Multiple G2 reviewers rep

People who liked this also viewed

6 picks

Type