Back to catalogue

Programme

AI Tools at Work: Generative AI, Agents and Orchestration

A programme on using AI assistants, agents and automation workflows at work, without depending on one product. Start with the Getting Unstuck method. Practise requests, response checks, permissions, action logs and human review before sending.

Courses
14
Estimated study time
67 hours
Assessment
Learning only. Completion is not a qualification.

Study time is a planning estimate, not a measurement with participants.

Who it is for

Working professionals in any field who use, or are about to use, chat assistants, agents or automation flows on a company computer, in Albanian or in English.

What it develops

You can structure requests and check responses; recognise fabrication and data boundaries; disclose AI assistance; use limited permissions for agents; read action logs; undo actions where possible; and place human review before sending.

Courses and sequence

  1. 01

    Microcourse

    The four part request

    Role, context, limits and output form: learn to structure a request for a routine text task and check the tool's response.

    Estimated study time: 4 hours

    Can be requested independently

  2. 02

    Microcourse

    Checking an AI output

    Facts, tone and organisational rules: three short checks after each AI output to look for common errors.

    Estimated study time: 4 hours

    Can be requested independently

  3. 03

    Microcourse

    Fabrication: The four kinds and how to catch them

    Numbers, citations, authorship, dates: the four fabrication types, the three early signs, and the ninety-second citation check.

    Estimated study time: 5 hours

    Can be requested independently

  4. 04

    Microcourse

    What you may paste: Data levels and the law

    Four data levels, two laws, a ten-second test before every paste, and what you do when the data have already gone out.

    Estimated study time: 5 hours

    Can be requested independently

  5. 05

    Microcourse

    Disclosing AI assistance

    One line that says an assistant helped, where it goes, the record that backs it, and how it becomes a team habit.

    Estimated study time: 4 hours

    Can be requested independently

  6. 06

    Microcourse

    Agents: Installing one and finding the stop button

    An agent acts, it does not only write. Before it acts on your laptop: the source, the dialog, the first run in a safe place, and the stop button.

    Estimated study time: 5 hours

    Can be requested independently

  7. 07

    Microcourse

    Agents: Permissions and scopes

    A scope is a sentence: who, what, where, how long. Least privilege, the permission screen, keys and tokens, and revoking as a habit.

    Estimated study time: 5 hours

    Can be requested independently

  8. 08

    Microcourse

    Agents: What an agent may touch

    The scope says what it may do; the boundary says where. The allow list, the test copy, the data levels for agents, and the dry run before any real run.

    Estimated study time: 5 hours

    Can be requested independently

  9. 09

    Microcourse

    Agents: Reading the action log

    The output tells you what the agent produced; the log tells you what it did. The ten-minute review after every run, the three signals, and what a missing log means.

    Estimated study time: 5 hours

    Can be requested independently

  10. 10

    Microcourse

    Agents: Undoing an action

    A read cannot be taken back, a write reverts with a version, a send cannot be unsent, a run depends. The copy before, the rollback after, and the incident when there is no undo.

    Estimated study time: 5 hours

    Can be requested independently

  11. 11

    Microcourse

    Trigger, action and connector

    A flow is a trigger, some actions and the connectors between them. Before any tool builds it, you draw it on paper and read it part by part.

    Estimated study time: 5 hours

    Can be requested independently

  12. 12

    Microcourse

    Credential, retry and log

    A flow fails at three in the morning. The credential that expired, the retry that sent five times, the log that did not exist. Three decisions before the flow is switched on.

    Estimated study time: 5 hours

    Can be requested independently

  13. 13

    Microcourse

    The human check before anything is sent

    A person before every send and every run. Where the check sits, the screen the person sees, the time they get, and what happens when nobody answers.

    Estimated study time: 5 hours

    Can be requested independently

  14. 14

    Microcourse

    A flow broken five ways

    One flow, five breakages, one method: from the symptom to the part. No trigger, wrong connector permission, expired credential, a loop running twice, output to the wrong place.

    Estimated study time: 5 hours

    Can be requested independently