← LeftLaneCONTENT HISTORY

Update to LeftLane

Snapshot Oct 24, 2026 · 13:16 UTC · version 2.0.0

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for add-dealership-note

Full description — Now says: CreateVehicleComment, CreateDealComment, or CreateAccountComment.

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save LeftLane and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Sep 30, 2026 · 23:11 UTC

CreateComment.

After

Oct 24, 2026 · 13:16 UTC

CreateVehicleComment, CreateDealComment, or CreateAccountComment.

Skill instructions

Before

Sep 30, 2026 · 23:11 UTC

CreateComment. Use when a user asks to record, add, attach, or save a dealership note or comment. Treat `CreateComment` as a non-idempotent write. Follow this sequence exactly: 5. Call `CreateComment` exactly once only after the user con...

After

Oct 24, 2026 · 13:16 UTC

CreateVehicleComment, CreateDealComment, or CreateAccountComment. Use when a user asks to record, add, attach, or save a dealership note or comment. Treat each create-comment tool as a non-idempotent write. Follow this sequence exactly: ...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,17 +1,20 @@
 ---
 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.
+description: Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateVehicleComment, CreateDealComment, or CreateAccountComment. 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:
+Treat each create-comment tool 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.
+5. After the user confirms, call exactly one matching write tool once:
+   - `CreateVehicleComment` for a vehicle
+   - `CreateDealComment` for a customer deal
+   - `CreateAccountComment` for a deal finance account
 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.
+Never call a write tool when discovery, an exact target, the body, or confirmation is missing. Never guess between multiple targets. Never use a write tool that does not match the confirmed target type. 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.
Full technical diff · 2 changed fields

changed /description

BEFORE
"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."
AFTER
"Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateVehicleComment, CreateDealComment, or CreateAccountComment. Use when a user asks to record, add, attach, or save a dealership note or comment."

changed /skill_md_contents

BEFORE
"---\nname: add-dealership-note\ndescription: 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.\n---\n\n# Add Dealership Note\n\nTreat `CreateComment` as a non-idempotent write. Follow this sequence exactly:\n\n1. 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.\n2. 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.\n3. Obtain the complete note body. Do not silently rewrite material facts; show any cleanup to the user.\n4. 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.\n5. Call `CreateComment` exactly once only after the user confirms the displayed target and body.\n6. Report the returned comment id, timestamp, and target relationship.\n\nNever 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.\n"
AFTER
"---\nname: add-dealership-note\ndescription: Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateVehicleComment, CreateDealComment, or CreateAccountComment. Use when a user asks to record, add, attach, or save a dealership note or comment.\n---\n\n# Add Dealership Note\n\nTreat each create-comment tool as a non-idempotent write. Follow this sequence exactly:\n\n1. 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.\n2. 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.\n3. Obtain the complete note body. Do not silently rewrite material facts; show any cleanup to the user.\n4. 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.\n5. After the user confirms, call exactly one matching write tool once:\n   - `CreateVehicleComment` for a vehicle\n   - `CreateDealComment` for a customer deal\n   - `CreateAccountComment` for a deal finance account\n6. Report the returned comment id, timestamp, and target relationship.\n\nNever call a write tool when discovery, an exact target, the body, or confirmation is missing. Never guess between multiple targets. Never use a write tool that does not match the confirmed target type. 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.\n"
Full snapshot data
{
  "description": "Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateVehicleComment, CreateDealComment, or CreateAccountComment. Use when a user asks to record, add, attach, or save a dealership note or comment.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 180
    }
  ],
  "name": "add-dealership-note",
  "skill_md_contents": "---\nname: add-dealership-note\ndescription: Add one confirmed private note to an exact LeftLane vehicle, customer deal, or deal finance account with CreateVehicleComment, CreateDealComment, or CreateAccountComment. Use when a user asks to record, add, attach, or save a dealership note or comment.\n---\n\n# Add Dealership Note\n\nTreat each create-comment tool as a non-idempotent write. Follow this sequence exactly:\n\n1. 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.\n2. 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.\n3. Obtain the complete note body. Do not silently rewrite material facts; show any cleanup to the user.\n4. 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.\n5. After the user confirms, call exactly one matching write tool once:\n   - `CreateVehicleComment` for a vehicle\n   - `CreateDealComment` for a customer deal\n   - `CreateAccountComment` for a deal finance account\n6. Report the returned comment id, timestamp, and target relationship.\n\nNever call a write tool when discovery, an exact target, the body, or confirmation is missing. Never guess between multiple targets. Never use a write tool that does not match the confirmed target type. 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.\n"
}

SHA-256 of public snapshot: 1068f1cdf30a9b4eb86922c4ba74b43270204b09bfa6fcbc082eccb9bfdeaeb1