Incident & PCN Handling Pack (UK)

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

Security Scan

The skill's instructions, templates, and requirements are consistent with its stated purpose (building PCN/incident evidence packs); there are no unexpected installs, credentials, or external endpoints — but provenance is unknown and you should handle personal data and legal submissions carefully.

Purpose & Capability

Name/description match the included templates and workflow. The SKILL.md and asset files provide templates for briefs, timelines, appeal covers, corrective actions and monitoring — all coherent with a PCN/incident evidence-pack builder. Note: the skill's source/homepage are missing, so provenance is limited even though the content matches its claimed purpose.

Instruction Scope

Runtime instructions stay within the stated purpose: build templates, label evidence, and stop-and-ask when data is missing. The instructions explicitly forbid fabricating evidence. They do ask that evidence storage paths and integrity notes be recorded (expected for chain-of-custody) — this is reasonable but means the agent may prompt for or record file locations and metadata, which can contain sensitive information.

Install Mechanism

No install spec and no code files that execute — instruction-only skill. This is the lowest-risk install footprint.

Credentials

No required environment variables, credentials, or config paths are declared or used. The skill does not request unrelated secrets or system access.

Persistence & Privilege

always:false and no install means it does not request persistent presence or elevated privileges. Model invocation is allowed (platform default) but that is normal for skills and not combined here with broad access.

Assessment

This skill appears coherent and limited in scope, but before installing: (1) note the skill source/homepage is missing — verify you trust the publisher or test in a safe environment; (2) do not paste sensitive personal data, medical records, or unnecessary PII into prompts — incident packs often contain personal data and you must comply with data-protection rules; (3) always verify the generated appeal text and evidence references against originals before submitting to authorities (the skill explicitly forbids fabricating evidence, but you must confirm accuracy); (4) preserve original evidence and chain-of-custody outside the assistant (the skill asks you to record storage paths and integrity notes but does not itself manage secure storage); (5) if you need stronger provenance/assurance, request a skill with a known homepage/maintainer or run the templates offline within your organization.

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