Install
openclaw skills install parking-ticket-response-packPrepare a deadline card, response checklist, evidence list, and short appeal draft for a parking ticket before the deadline passes.
openclaw skills install parking-ticket-response-packParking Ticket Response Pack helps a user respond to a parking ticket before the deadline. It organizes ticket facts, creates a deadline card, helps the user choose a practical pay or contest path, gathers evidence, and drafts a short factual appeal message when appropriate.
This skill is not legal advice. Parking rules, appeal windows, fine amounts, late penalties, evidence requirements, and filing methods vary by city, campus, private lot, agency, and country. The user must verify local rules, dates, portal instructions, and deadlines directly from the citation or official source.
Use this skill when the user says things like:
Ask for ticket facts only. The user should redact personal identifiers before sharing.
Useful facts:
Privacy note:
Redact plate number, full name, address, driver license number, full citation number, payment details, barcodes, QR codes, login details, and any private identifiers before sharing. Keep originals for your own official filing.
Create a factual summary from user-provided details. If a key fact is missing, use a placeholder and ask the user to check the citation or official portal.
Identify the earliest relevant date from the ticket facts:
If no deadline is provided, do not guess. Mark it as "verify immediately" and tell the user to check the printed citation, official portal, or issuing agency instructions.
Create a small card with:
Help the user select one of these administrative paths, without presenting it as legal advice:
Show tradeoffs: speed, evidence strength, late-fee risk, time cost, and uncertainty.
Create a checklist matched to the user's situation. Common evidence:
Remind the user not to alter evidence and to keep originals.
If the user chooses contest, appeal, review, or mitigation, draft a concise factual message:
Do not invent facts, cite laws not supplied by the user, or make threats. If the evidence is weak, say so and offer a neutral explanation-only draft.
List what to verify before submitting:
Create a tracker with date, channel, reference, submitted items, confirmation, and next step.
Return the pack in this order:
A short note that this is not legal advice and local rules, dates, and instructions must be verified.
| Field | Detail |
|---|---|
| Issuing agency or lot operator | |
| Citation date/time | |
| Location | |
| Violation description | |
| Fine amount | |
| Deadline shown | |
| User story |
| Item | Detail |
|---|---|
| Earliest deadline | |
| Days remaining | |
| Required next action | |
| Filing/payment method | |
| Late risk stated on ticket |
| Path | When it fits | Evidence needed | Tradeoff |
|---|
| Evidence | Why it matters | Status |
|---|
A concise draft only if the user is contesting, appealing, requesting review, or asking for mitigation. Otherwise provide a payment/admin checklist instead.
A short list to verify before payment or appeal.
| Date | Channel | Reference or confirmation | What happened | Next step |
|---|