Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    crg privacy law25 risk

    1

    Triage Québec Law 25 privacy incidents and generate compliant risk assessments and register entries from a cybersecurity perspective.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    crg privacy law25 risk

    crg privacy law25 risk

    Example session with this skill installed

    A staff laptop, not encrypted, holding records of 800 patients (names, dates of birth, health card numbers) was stolen from a car in Montreal yesterday. Not recovered. We are a private clinic.

    • Read your context and instructions
    • Compiled the crg privacy law25

    I have assessed the incident involving the stolen laptop. Below is the structured triage based on the provided facts. # Confidentiality Incident Triage — Private Clinic, 2023-10-27 ## 1. Incident summary A staff laptop was stolen from a vehicle. The device was not encrypted and has not been recovered. The incident occurred on 2023-10-26 and was detected on the same day. Status: Ongoing (device at large). ## 2. Personal information and persons concerned | Category of information | Persons | Location | Protection | Evidence | | :--- | :--- | :--- | :--- | :--- | | Health records (Name, DOB, RAMQ) | 800 | Montreal | None (Unencrypted) | User assertion | ## 3. Candidate regimes (to confirm by legal counsel) | Regime | Signal from the facts | Provision to confirm | Status | | :--- | :--- | :--- | :--- | | Québec Private Sector | Clinic operating in Montreal | P-39.1 | Active - to confirm by legal counsel | ## 4. Risk of serious injury assessment | Factor | Facts and evidence | Reading | Basis and marker | | :--- | :--- | :--- | :--- | | Sensitivity | Health card numbers and DOB | High | **Analytical estimate — validation required** | | Consequences | Identity theft, medical fraud | High | **Analytical estimate — validation required** | | Likelihood of use | Unencrypted device in thief's hands | High | **Analytical estimate — validation required** | **Indicative reading:** serious injury risk indicated (P-39.1 s. 3.7). **Analytical estimate — validation required.** ## 5. Notification decision support | Recipient | Provision to confirm | Indicative reading | Checks still needed | Status | | :--- | :--- | :--- | :--- | :--- | | Commission (CAI) | P-39.1 s. 3.5 | Indicated | Verification of recovery | Open | | Persons concerned | P-39.1 s. 3.5 | Indicated | ID contact info | Open | Notification is a **Management decision required** after legal review. ## 6. Incident register entry | Field | Content | | :--- | :--- | | Date of incident | 2023-10-26 | | Date detected | 2023-10-26 | | Type of incident | Theft of unencrypted hardware | | Personal information | Names, DOB, Health card numbers | **Next steps** * Escalate to the Person in Charge of Personal Information immediately. * Contact legal counsel to confirm the notification timeline for the CAI. * Initiate remote wipe protocols if the device is managed via MDM.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Handling a privacy breach in Québec requires navigating specific legal obligations under Law 25. This skill triages suspected personal information incidents for organizations, providing a structured assessment of the risk of serious injury and supporting notification decisions. ## What it does - **Incident triage** builds a structured summary of the breach, including timelines, involved parties, and containment status. - **Risk assessment** rates the sensitivity, anticipated consequences, and likelihood of injurious use based on specific legal factors. - **Regime identification** flags applicable laws such as Québec's private-sector Act, PIPEDA, or health information regulations. - **Notification support** generates tables indicating whether the Commission d’accès à l’information or affected individuals should be notified. - **Register generation** produces a formatted incident register entry ready for organizational records. ## How it works 1. **Intake** where you provide incident facts, types of personal information, and organizational context. 2. **Analysis** where the agent evaluates if a confidentiality incident occurred and assesses the risk level. 3. **Review** of the generated triage report, including candidate legal regimes and decision support tables. 4. **Export** the completed incident register entry for compliance documentation. ## Frameworks & tools This skill uses the CyberRiskGuardian risk method and maps incidents against Québec's Law 25 (P-39.1) and PIPEDA. ## Why this beats prompting it yourself Generic prompts often miss the specific three-factor risk assessment required by Québec law or fail to distinguish between private and public sector regimes. This skill enforces the use of specific legal markers and templates, ensuring no mandatory register fields are overlooked during high-pressure incidents. ## Use cases - **Lost hardware triage** for evaluating the risk when an unencrypted company laptop or phone is missing. - **Misdirected data review** for instances where sensitive client lists were emailed to the wrong recipients. - **Breach compliance** for generating the required incident register entries after a suspected database exposure. - **Regulatory mapping** to determine if a specific event needs to be reported to the CAI. ## Known limitations This tool provides decision support and triage only. It does not provide legal advice, legal opinions, or final regulatory filings, which certified Legal counsel must confirm.

    Does not provide legal advice or final filings. Excludes public-sector and health-network programs. Does not provide technical forensics or notice deadlines. Confirmation by counsel is required.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    Permissions

    Read Files
    Write Files
    Network Access
    Listed7 days ago

    What's inside

    Frequently Asked Questions

    The skill specifically automates the three-factor risk assessment (sensitivity, consequences, and likelihood) required by Law 25, ensuring your incident register entries meet Québec's distinct regulatory formatting standards.

    This skill is designed for use within the CyberRiskGuardian ecosystem and is compatible with major LLM-based agent platforms that support custom structured workflows.

    You receive the specialized triage logic, the Law 25 risk assessment framework, and automated templates for both the CAI notification tables and the internal incident register.

    No, the skill is designed for immediate use; you simply follow the structured intake process to provide incident facts, and the agent handles the legal mapping and risk calculations.

    While it focuses on Law 25, the skill automatically flags when an incident may also fall under PIPEDA or specific provincial health information acts to ensure multi-jurisdictional visibility.

    The skill is regularly updated to reflect new guidelines from the Commission d’accès à l’information (CAI) and changes to Québec's private-sector privacy regulations.