admin-cars

Adjudicates opt-in car-marketplace disputes and publishes signed Nostr kind 30430 decisions.

Updated May 2, 2026
One-click install
npx skills add https://github.com/DemidovVladimir/chaos --skill admin-cars-demidovvladimir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: admin-cars
Source: https://github.com/DemidovVladimir/chaos/tree/main/verticals/cars-pack/skills/admin-cars
Command: npx skills add https://github.com/DemidovVladimir/chaos --skill admin-cars-demidovvladimir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Decentralized car marketplaces on Nostr lack a trusted way to resolve disputes between buyers and sellers without a central platform. This Skill turns a Hermes agent into an opt-in admin-agent that receives encrypted dispute submissions, applies a structured rubric, and publishes signed, auditable decisions to the relay. ## Core Features & Use Cases - Encrypted dispute intake: Accepts NIP-44 encrypted submissions via MCP tools (submit_dispute, submit_response, appeal_decision) with signature and proof-of-work verification before decryption. - Rubric-based adjudication: Maps violation type, evidence quality, and value band to decisions (clear, warning, flag, escalated) with severity levels, escalating ambiguous or high-value cases to human review. - Prompt-injection hardening: Sanitizes all party-submitted text with input_safety, wraps evidence in untrusted blocks, and never follows instructions embedded in dispute content. - Use Case: A buyer claims a seller misrepresented a vehicle's odometer. The buyer submits an encrypted dispute; the admin-agent notifies the seller, waits for a response, applies the rubric, and publishes a signed kind 30430 decision that only users who trust this admin's pubkey will weight. ## Quick Start Configure this Hermes instance as the cars-pack admin-agent and have it process incoming dispute submissions according to the admin-cars rubric.

Frequently Asked Questions about admin-cars

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a dispute to the cars-pack admin agent?▼

Call the submit_dispute MCP tool with an encrypted evidence package and your signature. The submission must carry at least 24 bits of proof-of-work, and your pubkey must hold a completed-clean attestation or a verified NIP-58 badge to pass anti-abuse gates.

How does the admin agent decide dispute outcomes?▼

It applies a rubric mapping violation type, evidence quality, and value band to a decision (clear, warning, flag, or escalated) and severity (low, moderate, high). Ambiguous, high-value, cross-jurisdiction, or novel cases are always escalated to human review.

Can the admin agent issue or revoke NIP-58 badges?▼

No. The admin agent is explicitly forbidden from issuing or revoking NIP-58 badges, changing relay policy, or deleting relay events. Its published decisions may serve as evidence for a separate operator-run badge review process.

How does the skill defend against prompt injection in dispute evidence?▼

Every submitted text passes through input_safety (NFKC normalization, invisible-Unicode stripping, reserved-tag removal, length caps) and is wrapped in untrusted blocks attributed by pubkey. Instructions inside evidence are treated as data, never commands, and detected injection attempts are logged as soft negative signals.

What happens if the counterparty never responds to a dispute?▼

After a 7-day timeout, the default outcome is at most a low-severity warning. Higher severity requires the rubric to find a hard violation in the submitter's evidence alone plus a human co-signature before the decision is published.

What are the privacy and data retention limits of the admin agent?▼

Encrypted evidence is decrypted in memory only and plaintext is purged at decision time. Structured decision data is purged after 90 days, and published kind 30430 events contain at most 280 sanitized characters with no PII beyond pubkeys.