Agent Skillsmohitagw15856/pm-claude-skills › fine-appeal-letter

fine-appeal-letter

GitHub

生成针对违停罚单或行政罚款的正式申诉信。基于标识、程序错误或从轻情节等有效理由,结合证据撰写简短理性信件,并评估胜诉概率,避免无效情绪化申诉。

exports/openclaw/fine-appeal-letter/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

收到停车罚单或行政罚款通知 需要撰写有理有据的罚款申诉信

Install

npx skills add mohitagw15856/pm-claude-skills --skill fine-appeal-letter -g -y
More Options

Non-standard path

npx skills add https://github.com/mohitagw15856/pm-claude-skills/tree/main/exports/openclaw/fine-appeal-letter -g -y

Use without installing

npx skills use mohitagw15856/pm-claude-skills@fine-appeal-letter

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill fine-appeal-letter -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "fine-appeal-letter",
    "homepage": "https:\/\/mohitagw15856.github.io\/pm-claude-skills\/skill\/fine-appeal-letter.html",
    "metadata": {
        "openclaw": {
            "emoji": "🗓"
        }
    },
    "description": "Appeal a parking ticket, penalty charge, or administrative fine with the grounds that actually get appeals granted — not indignation. Use when someone got a ticket\/fine\/penalty notice and either has a legitimate case or wants an honest read on whether they do. Produces a short formal appeal letter built on recognised grounds (signage, procedure, mitigation, first-offence discretion), the evidence checklist, and a candid win-likelihood note — or the honest advice to just pay it."
}

Fine Appeal Letter

Appeals officers read thousands of letters. Anger loses; length loses; the word "outrageous" loses. What wins is a short letter matching one recognised ground to attached evidence. This skill writes that letter — and tells you when you don't have one, because the second-best outcome is not wasting an afternoon.

Required Inputs

  • The notice — what for, when, where, the cited code/rule if shown, the deadline (appeals have clocks; state it back).
  • What actually happened — the honest version. The letter will be built only from defensible facts.
  • Evidence available — photos (signage, meter, bay markings), receipts, tickets, medical/breakdown documentation, prior clean record.

The Grounds That Work (match one, lead with it)

  1. Signage/markings defective or ambiguous — obscured, contradictory, missing at point of decision (photo-dependent; the strongest ground when real)
  2. Procedural error — wrong plate/location/time on the notice, issued outside rules, meter fault (the notice's own text is the evidence)
  3. The situation exempted you — loading, medical emergency, breakdown, valid permit not visible through no fault (documentation-dependent)
  4. Mitigation + first-offence discretion — no legal ground, but clean record + genuine circumstance + polite request for discretion; explicitly a request, not an argument (issuers grant more of these than people expect — but only to letters that don't pretend it's ground 1-3)

Output Format

  1. The honesty gate first — one short paragraph: which ground applies, its realistic strength (strong / arguable / discretion-only / none), and if none: "pay it; here's why fighting costs more."
  2. The letter — ≤250 words: reference numbers up top, ground stated in sentence one, facts in neutral past tense, evidence enumerated ("Photo A shows…"), the specific request (cancel / reduce to warning), deadline-respecting close. No adjectives about the issuer.
  3. Evidence checklist — exactly what to photograph or attach for the chosen ground, and what's missing that would upgrade the case.
  4. The realistic note — what happens next (timeline, escalation tier if refused) and whether escalation is worth it at this fine size.

Quality Checks

  • Exactly one primary ground, stated in the first sentence — letters that argue three grounds signal none is strong
  • Every factual claim is attachable-evidence-backed or clearly framed as the appellant's account
  • Zero emotional language survives — the tone test is "written by a calm lawyer with a train to catch"
  • The honesty gate is present even when the letter is written — strength stated, not implied
  • Reference number, date, and deadline appear correctly and the request is specific

Anti-Patterns

  • Do not fabricate or shade circumstances — beyond ethics, issuers cross-check timestamps and records, and a caught embellishment kills a real ground
  • Do not write the indignation draft "to feel heard" — this skill produces the version that wins, not the version that vents
  • Do not bury the ground under narrative — officers triage in the first sentence
  • Do not promise outcomes — likelihood language stays calibrated ("this ground succeeds regularly when photographed clearly")
  • Do not encourage appealing a fair fine on volume tactics — the honesty gate exists precisely for this

Version History

  • 54fad50 Current 2026-07-19 12:20

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
cffde6bc
Indexed
2026-07-19 12:20

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 12:25
浙ICP备14020137号-1 $방문자$