with one click
antipenalty-legal-skills-system
antipenalty-legal-skills-system contains 8 collected skills from sergekostenchuk, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Use this senior orchestrator whenever an agent must analyze, route, review, or draft strategy for Russian traffic-fine appeals in ANTIPENALTY. This skill coordinates traffic-case-router, traffic-evidence-auditor, traffic-court-router, traffic-admin-defense-lawyer, traffic-complaint-strategist, traffic-complaint-drafter, and legal-fail-closed-reviewer. Use it for multi-step legal defense workflows, case analysis, complaint generation planning, role-confusion risks, missing evidence, or any request where a traffic penalty must not become a blind auto-complaint.
Use this skill whenever ANTIPENALTY must review a traffic-fine strategy, complaint draft, court route, evidence audit, or legal claim before generation or user delivery. This reviewer blocks hallucinated courts, unsupported facts, role confusion, weak arguments promoted as strong, missing evidence, and legal claims without source support. Use it as the final gate after strategist or drafter output and whenever the user asks whether a legal output is safe.
Use this skill whenever ANTIPENALTY must analyze legal defenses for Russian traffic administrative penalties, including GIBDD/CAPAF auto-camera cases, MADI parking/standing cases, AMPP paid parking cases, camera verification, owner-not-driver arguments, photo quality, address errors, and evidence requests. This skill ranks defense lines by strength, requires evidence, marks weak or dangerous arguments as do_not_use, and must run after traffic-case-router and traffic-evidence-auditor.
Use this skill whenever ANTIPENALTY must classify a Russian traffic fine, постановление, protocol, parking fine, evacuation case, accident case, or authority document before legal analysis. This skill determines case_source and issuing_authority, flags missing facts, and blocks wrong playbooks such as applying GIBDD camera logic to MADI or AMPP cases. Use it before any evidence audit, defense strategy, court routing, or complaint drafting.
Use this skill whenever ANTIPENALTY must draft traffic-fine complaint text from an already confirmed strategy, confirmed facts, court/addressee route, and evidence list. This skill must not invent facts, legal grounds, courts, dates, drivers, camera defects, or evidence. Use it only after traffic-complaint-strategist and before legal-fail-closed-reviewer.
Use this skill whenever ANTIPENALTY must turn a traffic fine evidence audit and legal defense analysis into a focused complaint strategy. This skill selects 1-3 supported defense lines, keeps weak theories out, creates questions and motions, and decides whether generation is blocked. Use it after traffic-admin-defense-lawyer and traffic-court-router, before any complaint drafting.
Use this skill whenever ANTIPENALTY must decide where a Russian traffic-fine complaint should be filed or whether court/addressee routing must remain unresolved. This skill is mandatory before complaint drafting when a court, authority, address, jurisdiction, MADI/AMPP route, GIBDD route, or place-of-violation issue appears. It prevents invented courts and returns fail-closed unresolved output when location or routing source is insufficient.
Use this skill whenever ANTIPENALTY must audit evidence, extracted OCR/PDF facts, uploaded documents, user profile data, user statements, or missing proof before choosing a traffic-fine defense strategy. This skill separates confirmed facts from assumptions, detects owner/applicant/driver/postal-recipient/account-holder confusion, identifies evidence gaps, and blocks unsupported claims about cameras, verification, another driver, court routing, or procedural defects.