skills$openclaw/incident-pcn-evidence-appeal-corrective-actions-uk
kowl649.3k

by kowl64

incident-pcn-evidence-appeal-corrective-actions-uk – OpenClaw Skill

incident-pcn-evidence-appeal-corrective-actions-uk is an OpenClaw Skills integration for writing workflows. Builds incident/PCN evidence packs with timelines, appeal drafts, corrective actions, and follow-up monitoring. USE WHEN handling PCNs or incidents needing documentation.

9.3k stars4.9k forksSecurity L1
Updated Feb 7, 2026Created Feb 7, 2026writing

Skill Snapshot

nameincident-pcn-evidence-appeal-corrective-actions-uk
descriptionBuilds incident/PCN evidence packs with timelines, appeal drafts, corrective actions, and follow-up monitoring. USE WHEN handling PCNs or incidents needing documentation. OpenClaw Skills integration.
ownerkowl64
repositorykowl64/incident-pcn-evidence-appeal-corrective-actions-uk
languageMarkdown
licenseMIT
topics
securityL1
installopenclaw add @kowl64/incident-pcn-evidence-appeal-corrective-actions-uk
last updatedFeb 7, 2026

Maintainer

kowl64

kowl64

Maintains incident-pcn-evidence-appeal-corrective-actions-uk in the OpenClaw Skills directory.

View GitHub profile
File Explorer
9 files
.
assets
appeal-pack-cover-template.docx-ready.md
547 B
follow-up-monitoring-template.md
210 B
incident-manager-brief-template.md
311 B
timeline-template.md
114 B
references
evidence-capture-standard.md
390 B
_meta.json
335 B
SKILL.md
2.8 KB
SKILL.md

name: incident-pcn-evidence-appeal-corrective-actions-uk description: Builds incident/PCN evidence packs with timelines, appeal drafts, corrective actions, and follow-up monitoring. USE WHEN handling PCNs or incidents needing documentation.

Incident & PCN Handling Pack (UK)

PURPOSE

Turn incident/PCN inputs into an evidence pack: clean manager brief, timeline, appeal cover draft, corrective actions, and follow-up monitoring.

WHEN TO USE

  • “Build a PCN appeal pack using CCTV and timeline notes.”
  • “Summarise these incident notes into a clean manager brief.”
  • “Create corrective actions and follow-up monitoring for this incident.”

DO NOT USE WHEN…

  • The request is general driving advice or admin tasks (invoice chasing, calendar, IT support).
  • No artefact is requested and details are too vague.

INPUTS

  • REQUIRED:
    • Incident/PCN basics: date/time, location, vehicle reg, driver, allegation/contravention
    • Evidence list (CCTV, photos, telematics, delivery notes, correspondence, portal screenshots)
    • Any deadlines (appeal window)
  • OPTIONAL:
    • Existing timeline notes, witness statements, customer communications
    • Internal policy/SOP excerpts for corrective actions (paste text)
  • EXAMPLES:
    • “PCN: bus lane; CCTV link notes; delivery timestamp proof; need appeal pack.”

OUTPUTS

  • incident-manager-brief.md
  • timeline.md
  • appeal-pack-cover.md (Word-ready)
  • corrective-actions.md
  • follow-up-monitoring.md (Excel-ready)
  • Success criteria:
    • Clear chronology and evidence references
    • Appeal pack is factual and consistent with evidence
    • Corrective actions have owners and review dates

WORKFLOW

  1. Confirm whether this is a PCN appeal, an internal incident, or both.
    • IF unclear → STOP AND ASK THE USER.
  2. Build manager brief using assets/incident-manager-brief-template.md.
  3. Construct a timeline using assets/timeline-template.md.
    • IF key dates/times are missing → STOP AND ASK THE USER for them.
  4. Evidence capture standard:
    • Apply references/evidence-capture-standard.md (label, store location, integrity notes).
  5. Draft appeal cover using assets/appeal-pack-cover-template.docx-ready.md.
    • Keep factual; cite evidence refs; avoid speculative claims.
  6. Propose corrective actions and monitoring using assets/follow-up-monitoring-template.md.
  7. If asked to edit existing packs → ASK FIRST.

OUTPUT FORMAT

# timeline.md
| Date/time | Event | Source/evidence ref | Notes |
|----------|-------|----------------------|------|

SAFETY & EDGE CASES

  • Don’t fabricate evidence or outcomes.
  • If evidence is weak or contradictory, present it as “unconfirmed” and list gaps.

EXAMPLES

  • Input: “PCN appeal with CCTV and notes”
    • Output: brief + timeline + appeal cover + actions + monitoring tracker
README.md

No README available.

Permissions & Security

Security level L1: Low-risk skills with minimal permissions. Review inputs and outputs before running in production.

Requirements

  • OpenClaw CLI installed and configured.
  • Language: Markdown
  • License: MIT
  • Topics:

FAQ

How do I install incident-pcn-evidence-appeal-corrective-actions-uk?

Run openclaw add @kowl64/incident-pcn-evidence-appeal-corrective-actions-uk in your terminal. This installs incident-pcn-evidence-appeal-corrective-actions-uk into your OpenClaw Skills catalog.

Does this skill run locally or in the cloud?

OpenClaw Skills execute locally by default. Review the SKILL.md and permissions before running any skill.

Where can I verify the source code?

The source repository is available at https://github.com/openclaw/skills/tree/main/skills/kowl64/incident-pcn-evidence-appeal-corrective-actions-uk. Review commits and README documentation before installing.