skills/setup-hub/SKILL.md
Set up or update the Rental Ninja CRM plugin and CLAUDE.md instructions. Run this once after installing the plugin, or anytime to check for updates.
npx skillsauth add rental-ninja/rental-ninja-crm-agent setup-hubInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Keeps the Rental Ninja CRM plugin and project instructions up to date.
Installed plugin info:
!claude plugin list 2>&1 | grep -A3 "rental-ninja-crm" || echo "Plugin not found in installed list"
Run claude plugin update rental-ninja-crm (append the @marketplace suffix from the info above if present).
If the plugin was updated: tell the user the plugin was updated and they should restart Claude Code (or run /reload-plugins) to apply the new version.
If already up-to-date: continue to step 2.
If plugin not found or command fails: show the user the error output, then continue to step 2 anyway (CLAUDE.md setup still works independently).
Read CLAUDE.md in the current working directory (if it exists). Look for a <!-- setup-version: xxx --> HTML comment to extract the current version hash.
Call get_setup_instructions from the hub MCP server:
current_versionCLAUDE.md exists or no version comment found, call without current_versionIf up-to-date (tool says current version matches): tell the user their setup is already current. Done.
If new content returned: write the content to CLAUDE.md in the current working directory (overwrite if exists, create if not). Tell the user:
CLAUDE.md was written/updatedCLAUDE.md in the current working directory, not the plugin directoryCLAUDE.md is managed by the server — don't modify it manually/setup-hub anytime to check for both plugin and CLAUDE.md updatestesting
CRM operator for Rental Ninja Hub — manages inbox threads, customer replies, booking/rental research, sales pipeline, and accounting investigations. Use this skill whenever the user asks about CRM/HUB threads, inbox triage, customer emails, bookings, rentals, guests, company states, Rentals United tickets, payouts, settlements, payees, owner statements, commission calculations, payout mismatches, or any Rental Ninja Hub operation. Also triggers on thread IDs, ticket numbers, company lookups, draft replies, snooze/assign/close actions, pricing or availability questions, and any accounting/financial question related to a company's earnings. Even if the user doesn't mention "CRM" or "HUB" explicitly, use this skill for any customer support, property management, channel management, OTA (online travel agency), or accounting task.
business
File a Linear bug issue from a CRM thread or freeform description. Use when the user says "file bug", "linear issue", "create bug", "report bug", or when a thread reveals a platform bug.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
tools
# Lobster Lobster executes multi-step workflows with approval checkpoints. Use it when: - User wants a repeatable automation (triage, monitor, sync) - Actions need human approval before executing (send, post, delete) - Multiple tool calls should run as one deterministic operation ## When to use Lobster | User intent | Use Lobster? | | ------------------------------------------------------ | --------------------------