Investigation Pack (ACAS-aligned)

Generates ACAS-aligned investigation invite wording, neutral question sets, and evidence logs. USE WHEN starting a driver incident investigation/interview.

Security Scan

This is an instruction-only HR investigation template pack that is internally consistent with its stated purpose and does not request credentials, install code, or external endpoints.

Purpose & Capability

The name, description, and bundled templates (invite wording, question plan, evidence log, ACAS checklist) align with the stated purpose of producing ACAS-aligned investigation materials. Nothing in the skill requests unrelated system access or credentials. Note: the skill's source/homepage are missing which reduces traceability but does not make the content incoherent.

Instruction Scope

SKILL.md confines runtime actions to drafting documents from the provided templates and asking the user for required incident inputs. It explicitly instructs the agent to STOP AND ASK when the stage is unclear and warns not to give legal advice. It does not instruct reading system files, calling external endpoints, or exfiltrating data.

Install Mechanism

No install spec and no code files (instruction-only). This is the lowest-risk model: nothing will be downloaded or written to disk by the skill itself.

Credentials

The skill declares no required environment variables, credentials, or config paths. The optional inputs are case materials and internal policy text (user-supplied), which are appropriate and proportional for drafting investigation documents.

Persistence & Privilege

The skill does not request permanent presence (always:false) or any special privileges, and it does not instruct modifying other skills or system settings. Autonomous invocation is allowed by platform default but is not used to escalate privileges here.

Assessment

This skill appears coherent and low-risk from a technical perspective, but consider these practical points before installing or using it: - Verify templates with your organisation's HR/legal team before sending them to employees or using them in live cases — the skill explicitly says not to provide legal advice. - Do not paste unnecessary sensitive personal data (e.g., national IDs, medical records) into the tool when requesting outputs; supply only the incident details needed. - Confirm the matter is at an investigation (fact-finding) stage before using the templates — the skill correctly instructs to STOP AND ASK if the stage is unclear. - Because the skill’s source/homepage is not provided, consider vetting the content (templates/checklist) against your organisation’s policies and local employment law before wide adoption. - Keep audit/logs of any documents produced and shared, and ensure evidence handling and retention complies with your internal chain-of-custody practices.

PURPOSE

Create an ACAS-aligned investigation starter pack: invite wording, neutral question plan, and evidence log structure for transport incidents and potential misconduct.

WHEN TO USE

• “Draft an investigation invite letter for this incident and evidence list.”
• “Create investigation questions for this driver interview, ACAS aligned.”
• “Summarise these incident notes into a clean manager brief.” (when it feeds an investigation)

DO NOT USE WHEN…

• Generic HR queries like “What is a fair disciplinary process?” with no case artefact needed.
• You’re drafting outcomes/sanctions without an investigation stage.

INPUTS

• REQUIRED:
  • Incident summary (what/when/where), parties involved, and what’s alleged/being reviewed
  • Evidence available so far (CCTV, telematics, tacho extracts, witness notes, PCN, photos)
  • Proposed meeting date window and who will chair/note-take
• OPTIONAL:
  • Relevant internal policies (paste text), previous similar cases, union/companion info
• EXAMPLES:
  • “Allegation: falsified manual entry on [date]. Evidence: tacho report + supervisor note.”

OUTPUTS

• investigation-invite.md (Word-ready)
• question-plan.md
• evidence-log.md (Excel-ready table)
• Success criteria:
  • Neutral tone, no assumptions of guilt
  • Includes right-to-be-accompanied wording
  • Clear evidence handling and logging

WORKFLOW

1. Confirm this is an investigation (fact-finding), not a disciplinary hearing.
   • IF unclear → STOP AND ASK THE USER what stage they are at.
2. Draft invite using assets/invite-letter-template.docx-ready.md.
   • Include: purpose, date/time, attendees, right-to-be-accompanied, evidence access, and contact route.
3. Build a neutral question plan using assets/neutral-question-plan-template.md.
   • Start broad → then specifics → then mitigation/context → then closing.
4. Create an evidence log using assets/evidence-log-template.md.
   • Include chain-of-custody fields if needed.
5. Add ACAS alignment checks from references/acas-alignment-checklist.md.
6. If asked to edit existing documents → ASK FIRST.

OUTPUT FORMAT

# evidence-log.md
| Ref | Evidence item | Source | Date/time captured | Who captured | Storage location | Integrity notes | Relevance | Shared with employee (Y/N, date) |
|-----|---------------|--------|-------------------|-------------|------------------|-----------------|----------|----------------------------------|

SAFETY & EDGE CASES

• Don’t provide legal advice; keep to process and neutrality.
• If the allegation is serious and outcomes could be dismissal, flag that HR/legal review may be required per internal governance (ask for your policy text).

EXAMPLES

• Input: “Invite letter + questions for driver interview”
  • Output: invite + question plan + evidence log template populated with known items