Pilot Service Agents Vehicles

NHTSA vehicle records — VIN decoder, makes, models, recalls, consumer complaints. Use this skill when: 1. Decoding a VIN to manufacturer / model / year / spe...

Security Scan

The skill's declared requirements and runtime instructions match its stated purpose (VIN decoding / NHTSA lookups) and it does not ask for unrelated credentials or perform unexpected operations.

Purpose & Capability

Skill name/description (NHTSA VIN decoding, recalls, complaints) align with required components: it needs pilotctl, a running pilot-protocol daemon, and discovery of service agents on the overlay. These dependencies are coherent for a skill that talks to other agents on the Pilot overlay.

Instruction Scope

SKILL.md only instructs the agent to discover agents, send messages via pilotctl, and read the inbox; it does not ask to read local files, environment variables, or exfiltrate data to external endpoints outside the Pilot network. Use is scoped to vehicle data queries and summaries.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is downloaded or written by the skill itself. It relies on an existing pilotctl binary and a running daemon, which is a low-risk install profile for this type of skill.

Credentials

No environment variables, credentials, or config paths are required. The lack of requested secrets is proportional to the described purpose.

Persistence & Privilege

always is false and the skill does not request elevated persistence or to modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but is not combined with other concerning privileges.

Assessment

This skill appears internally consistent for querying NHTSA data via the Pilot overlay. Before installing, verify you trust the pilot-protocol daemon and pilotctl binary you will use (they handle network traffic to overlay agents). When using the skill, avoid sending sensitive personal data unnecessary to your query. Confirm the discovery results (list-agents) and the agent hostnames before submitting VINs or other data, and verify the pilot-protocol project's reputation and release sources if you will run its daemon on a production machine.

NHTSA vehicle records — VIN decoder, makes, models, recalls, consumer complaints.

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)

Hostname	Description
nhtsa-allmakes	NHTSA all vehicle makes
nhtsa-complaints	NHTSA consumer complaints by make/model/year
nhtsa-decodevin	NHTSA VIN decoder (140+ fields)
nhtsa-decodevinvalues	NHTSA VIN decoder flat values
nhtsa-modelsformake	NHTSA models for a given make
nhtsa-recalls	NHTSA vehicle recalls by make/model/year

What you can expect

• Full NHTSA vPIC VIN decoder (140+ fields) and vehicle-catalog lookups
• Recall and complaint history from the US DOT

What NOT to expect

• International (non-US) vehicle records
• Insurance claims or title history

Commands (same pattern for every agent in the category)

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape

send-message returns an ACK envelope immediately ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"vehicles","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message nhtsa-decodevinvalues --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message nhtsa-decodevinvalues --data '/data {"vin":"1HGCM82633A004352","modelYear":2003}'
pilotctl --json inbox

Dependencies

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.