sales-rimo
Rimo Voice platform help — Japanese-optimized AI meeting transcription and summarization with ISO 27001/27017 compliance and Japan-hosted data. Use when evaluating Rimo Voice for a Japanese-first team, setting up bot recording for Zoom/Teams/Meet/Webex, configuring custom dictionaries for domain terminology, troubleshooting transcription accuracy for Japanese or English, comparing Rimo to other note-takers for Japanese meetings, or understanding Rimo pricing (Solo $9/mo, Business $15/mo launch). Do NOT use for general note-taker comparison across all tools (use /sales-note-taker) or sales coaching program design (use /sales-coaching).
What this skill does
# Rimo Voice Platform Help ## Step 1 — Gather context If `references/learnings.md` exists, read it first for accumulated platform knowledge. Ask the user: 1. **What do you need?** - A) Evaluate Rimo Voice for my team (features, pricing, fit) - B) Set up Rimo for Japanese meeting transcription - C) Troubleshoot an issue (bot not joining, accuracy, credits) - D) Compare Rimo to another note-taker - E) Other 2. **Which plan are you on (or considering)?** - A) Free trial - B) Solo ($9/mo launch) - C) Business ($15/mo launch) - D) Corporate (custom) - E) Not sure yet Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2. ## Step 2 — Route or answer directly | If the question is about... | Route to | |---|---| | Choosing between multiple note-takers | `/sales-note-taker [user's question]` | | Building a coaching program around call recordings | `/sales-coaching [user's question]` | | Connecting tools via Zapier/webhooks/API in general | `/sales-integration [user's question]` | | CRM data quality or field mapping | `/sales-data-hygiene [user's question]` | | Anything Rimo-specific | Continue to Step 3 | When routing to another skill, provide the exact command. ## Step 3 — Rimo platform reference **Read `references/platform-guide.md`** for the full platform reference — pricing tiers, integrations, calendar setup, dictionary configuration, and known limitations. Answer the user's question using only the relevant section. Don't dump the full reference. ## Step 4 — Actionable guidance You no longer need the platform guide — focus on the user's specific situation. - **Evaluating?** Rimo's strength is Japanese transcription accuracy with ISO 27001/27017 compliance and Japan-hosted data. Key gaps: no API, no CRM integration, no Zapier/Make, AI credits are limited per plan. - **Setting up?** Guide through calendar connection, voiceprint registration, custom dictionary entries. Do voiceprints before the first real meeting. - **Troubleshooting?** Check calendar connection, bot join timing (30-60s delay is normal), AI credit balance. - **Comparing?** For Japanese-first teams with compliance needs, Rimo is strong. For API/CRM integration needs, recommend Fathom or Fireflies instead. If you discover a gotcha, workaround, or tip not covered in `references/learnings.md`, append it there. ## Gotchas - **No public API** — Rimo has no API, webhooks, Zapier, or Make connectors. "API" is listed as upcoming but undated. If you need programmatic access to transcripts, use a tool with an API (Fathom, Fireflies, MeetGeek). - **No CRM integration** — no HubSpot, Salesforce, or any CRM connector. Meeting insights must be manually exported (CSV/Excel/PDF) and pasted into CRM. - **AI credits are limited** — Solo gets 100/mo, Business gets 1,000/mo. AI summaries and AI chat consume credits. When credits run out, only raw transcription is available (no AI features). Monitor usage. - **iOS app only for mobile** — no Android app. Desktop is web-only. If your team is Android-heavy, this is a blocker. - **Launch pricing is temporary** — Solo $9/mo and Business $15/mo are 50% off introductory prices. Regular prices are $18/mo and $30/mo. Price is locked while subscription stays active. - **Bot takes 30-60 seconds to join** — the recording bot won't appear instantly when a meeting starts. Calendar integration must be connected first. ## Related skills - `/sales-note-taker` — Compare note-takers, plan API integrations, choose between bot-based and bot-free tools - `/sales-coaching` — Build coaching programs, onboard reps, design scorecards - `/sales-integration` — Connect tools via Zapier, webhooks, or APIs - `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install: `npx skills add sales-skills/sales --skill sales-do -a claude-code` ## Examples **User prompt**: "Our Tokyo sales team needs accurate Japanese meeting notes with ISO compliance. Is Rimo Voice a good fit?" **What the skill does**: Confirms Rimo is optimized for Japanese transcription with ISO 27001/27017 and Japan-hosted data. Notes the lack of API and CRM integration as limitations. Recommends Business plan ($15/mo) for team features. Suggests pairing with manual CRM export workflow. **User prompt**: "Can I pull Rimo transcripts into our Snowflake warehouse via API?" **What the skill does**: States Rimo has no API (upcoming but undated). Suggests manual CSV/Excel export as a workaround. Recommends Fathom or Fireflies if API integration is a hard requirement. **User prompt**: "What's the difference between Rimo Solo and Business plans? We have a 5-person team." **What the skill does**: Explains Business adds team management, shared folders, and team-wide analysis that Solo lacks. Notes AI credit difference (100 vs 1,000/mo). Recommends Business for teams since Solo lacks collaboration features. ## Troubleshooting ### Bot not joining meetings **Symptom**: Rimo bot doesn't appear in Zoom/Teams/Meet/Webex meetings **Solution**: Verify calendar is connected (Settings → Google Calendar or Outlook). Check the meeting has a video link in the calendar event. Bot takes 30-60 seconds to join after meeting starts — wait before troubleshooting. For ad-hoc meetings not on the calendar, manually invite the bot. ### English or non-Japanese transcription accuracy is poor **Symptom**: Transcription errors for English or other non-Japanese speakers **Solution**: Rimo is optimized for Japanese — English and other languages have lower baseline accuracy. Register voiceprints for all speakers (Settings → Speaker Separation). Add domain-specific terms to the Dictionary. For teams primarily speaking English, consider Fathom or Fireflies instead. ### AI credits running out mid-month **Symptom**: AI summaries and AI chat stop working before the billing cycle resets **Solution**: Check credit usage in account settings. Solo plan has only 100 credits/mo — heavy usage burns through this quickly. Options: upgrade to Business (1,000 credits/mo), reduce AI chat usage (each query consumes credits), or rely on raw transcripts without AI summaries until credits reset.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.