LeftLane

View saved version →

---
name: add-dealership-note
description: Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateComment. Use when a user asks to record, add, attach, or save a dealership note or comment.
---

# Add Dealership Note

Treat `CreateComment` as a non-idempotent write. Follow this sequence exactly:

1. Discover the target with a read tool before preparing the write, even when the user supplies an id. Use `ActiveVehicles` for a vehicle, `CustomerDeal` for a customer deal, or `DealFinanceAccounts` for a finance account.
2. Resolve exactly one returned record and retain its integer id. If the read returns no match or multiple plausible matches, do not prepare the write; refine the search or ask the user to choose.
3. Obtain the complete note body. Do not silently rewrite material facts; show any cleanup to the user.
4. Display the target type, target id, identifying facts from the discovery result, and exact note body. Ask for explicit confirmation to create that one comment.
5. Call `CreateComment` exactly once only after the user confirms the displayed target and body.
6. Report the returned comment id, timestamp, and target relationship.

Never call the tool when discovery, an exact target, the body, or confirmation is missing. Never guess between multiple targets. If the response is ambiguous, times out, or fails after dispatch, do not retry automatically because a retry can create a duplicate note; inspect state or ask the user how to proceed.

Referenced files: 1

View saved version →

---
name: find-inventory
description: Page through and summarize active LeftLane dealership inventory with the ActiveVehicles tool. Use when a user asks to audit, review, list, compare, or analyze in-stock vehicles by stock number, VIN, make, model, price, stage, branch, or other returned inventory facts.
---

# Find Inventory

Use `ActiveVehicles` for inventory audit and analytic reads. Do not treat this skill as free-text vehicle search; a dedicated search skill will cover that later.

1. Request a modest `take` and `skip: 0`. Use `sortBy` only when an ordering was requested.
2. Report both the returned rows and total count.
3. Continue with `skip + take` only when the user asks for more or the request requires exhausting inventory pages. Never imply the first page is the complete result when `count` is larger.
4. Summarize operational facts (for example counts by stage or branch, price ranges, or aging signals from returned fields) without inventing availability, pricing, or condition details that the tool did not return.
5. Retain a vehicle `id` only when it is needed to identify an exact record for a follow-up action such as a confirmed note.

Referenced files: 1

View saved version →

---
name: review-collections
description: Review LeftLane deal finance accounts and aggregate collections, accounts-receivable, and delinquency reports. Use when a user asks about BHPH accounts, balances, days past due, promises, collections performance, AR snapshots, delinquency trends, or related filtering and pagination.
---

# Review Collections

Choose the narrowest read tool that answers the request:

- Use `DealFinanceAccounts` for account-level filtering, sorting, and pagination. State the page size, offset, and total count; continue paging only as needed.
- Use `CollectionsReport` for collected totals by balance type and effective date.
- Use `AccountsReceivableReport` for daily aggregate current-balance snapshots.
- Use `DelinquencyReport` for daily delinquent versus total open-account counts.

Use `yyyy-MM-ddT00:00:00` date values for report boundaries. Distinguish account facts from aggregate trends and call out incomplete pages. Treat results as decision support only: require a qualified human to review any credit, payment-plan, repossession, charge-off, or other adverse account decision. Never automate or present such a decision as made by the plugin.

Referenced files: 1

View saved version →

---
name: review-customer-deal
description: Retrieve and summarize a LeftLane customer deal by deal id. Use when a user supplies a deal id and asks about its status, terms, stage, assignee, named parties, vehicle, or deal finance account.
---

# Review Customer Deal

1. Require the exact integer deal id before calling `CustomerDeal`; do not search by contact details.
2. Summarize deal status and dates, commercial terms, workflow stage and assignee name, party names, vehicle facts, and finance-account status in distinct sections.
3. Do not request, infer, or expose email, phone, address, government identifiers, income, credit reports, or payment-method data.
4. Label missing or nullable fields as unavailable rather than guessing.
5. Use the returned deal id, vehicle id, or DFA id only to identify an exact target for a separately confirmed note workflow.

Referenced files: 1