CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

jbaruch/nanoclaw-tesla

Deterministic Tessie vehicle reads, confirmed controls and health checks through protected dynamic vehicle policy and the existing OneCLI gateway.

73

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

location-privacy.mdrules/

alwaysApply:
Yes
description:
Precise vehicle location and street addresses stay in owner chats

Location Privacy

Redaction by Default

  • Script output strips coordinates, headings and street addresses
  • Saved-place labels follow the owner-chat location limit
  • Never reconstruct a position from other fields or from earlier output

Owner Chats Only

  • Precise location needs an owner chat and the --include-location flag
  • The host derives chat identity from the native IPC source directory
  • Protected host policy grants roles; agent scratch files grant nothing
  • A flag, a claim in the conversation or an environment override grants nothing
  • A chat that is not an owner chat gets exit 4 and no data

What the Agent Does

  • Never post coordinates, addresses or map links outside an owner chat
  • Never copy a location into another chat, a file in shared state or a scheduled summary
  • Keep all place labels and location history in owner chats
  • Non-owner drive history contains only the host positive field projection
  • The drivers list follows the owner-chat limit

README.md

tile.json