Agent Kunjani

List the learning outcomes on a Kunjani deck and the activities linked to each. Outcomes listed with kind "via_questions" belong to another deck and cannot be changed from here. Read-only.

list_outcomes

Create or update a Kunjani deck and publish a batch of training activities into it in one call. When deck.id targets an existing deck, supplied deck fields (name, description, visibility, collaborations, dice_option, picture_url) are applied and omitted fields are left untouched. mode "publish" persists; mode "validate" only previews and writes nothing (no deck, outcome, or activity is created or updated). Author using the Agent K method: (1) design 3-6 learning outcomes first (specific, observable, learner-facing, e.g. "Handle an unhappy customer without escalation") and tag every activity with the outcome(s) it advances via its outcomes field. (2) Each activity has three parts: text is what the player sees, a scenario or trigger that must NOT teach or reveal the answer; answer is the answer key the AI grader scores against (specific, bulleted key points); assessment_notes are grading rules and context (accept synonyms and real-world examples, state the minimum valid points, do NOT write rigid tier rubrics, and include any media transcript because the grader is text-only). (3) suit sets the activity type: Jolt (quick recall, 30-60s), Advance (praise a good action then unpack its benefits, 60-90s), Mystery (creative photo/video/lateral thinking, 90-300s), Oops (a mistake scenario then unpack the consequences, 60-90s), Explain (summarise/compare/analyse, 90-120s), Demonstrate (perform, role-play, or submit media, 90-300s). Keep each activity to the one thing it tests, and OMIT each activity name so Kunjani auto-numbers it within its suit (J1, A1, M1, O1, E1, D1); only set a name to pin a specific slot. After publishing, share a deck link from the response with the user: deck.teams_url when the user is in Microsoft Teams or M365 Copilot, otherwise deck.url.

publish_activity_batch

Set the display order of a Kunjani deck's activities, the order the deck overview and games use. question_order must list EVERY question on the deck; read the current order from get_deck first.

reorder_deck_questions

Change one activity on a Kunjani deck. Only the fields you supply change. The three-block rule still applies: text never reveals the answer, answer is the grader's answer key, assessment_notes are flexible grading rules plus any media transcript. outcome_ids or outcome_descriptions REPLACE the activity's outcome links when supplied. Media is URL-based (picture_url / picture_2_url are player-facing and facilitator_picture_url is response media; public image or audio, max 5 MB image / 16 MB audio or video). remove_picture, remove_picture_2, and remove_facilitator_picture clear them.

update_question

Update one Kunjani deck: name, description, visibility, collaborations, dice option, or thumbnail. Only the deck fields you supply are changed. Use create_deck to make a new one and publish_activity_batch to add activities. dice_option "loaded" plays activities in a fixed order (default, for scaffolded decks); "random" fires a random activity per suit, for pure-recall drills. Deck thumbnails are URL-based: deck.picture_url fetches a public image (jpeg/png/gif/webp, max 16 MB) and deck.remove_picture true clears it. A deck can also carry ONE learning resource that players are sent after the welcome message: deck.resource_url fetches a pdf or mp4 (max 16 MB), or deck.resource_link points at a video link; supply one or the other, and deck.remove_resource true clears the uploaded file. Share deck.teams_url from the response with the user when they are in Microsoft Teams or M365 Copilot, otherwise deck.url.

update_deck

Change one learning outcome on a Kunjani deck, including which activities it is linked to. outcome.question_ids REPLACES those links when supplied, and [] detaches all of them. Only outcomes the deck owns can be changed.

update_outcome