vokser_add_challenge_action
ChatGPTWRITE — adds an action the user has committed to within a Challenge. Use this only when the user has stated something they will actually do. Do NOT turn every suggestion you make into an action, and do NOT add one the user has not agreed to. Returns the created action, including the id needed to complete or delete it later.
vokser_complete_challenge
ChatGPTWRITE — marks a Challenge complete. Use this only when the user has explicitly said they are done with it. Do NOT infer completion from them sounding positive about their progress, or from every action being ticked off. This cannot be undone: there is no way to reopen a completed Challenge. It stays readable afterwards through vokser_list_challenges with status='completed', but it can no longer be worked on and disappears from the user's Home page.
vokser_complete_challenge_action
ChatGPTWRITE — ticks off an action within a Challenge. Use this only when the user has said they have done it. Do NOT mark an action complete because it was discussed or planned. Reversible with vokser_reopen_challenge_action. Completing an already-completed action changes nothing.
vokser_create_challenge
ChatGPTWRITE — starts a new Challenge for the user against one or more framework behaviours. Use this only when the user has explicitly agreed to start one and the title and behaviours are settled. Do NOT create a Challenge speculatively because a coaching conversation touched on a difficulty, and do NOT invent the behaviours — confirm them with the user first. Behaviours may be any in the framework, not only the pillars the user has selected. Returns the new Challenge's id.
vokser_delete_challenge_action
ChatGPTWRITE — permanently removes an action from a Challenge. Use this only when the user has explicitly asked for it to be deleted. Deletion cannot be undone. If the user means they have finished the action, call vokser_complete_challenge_action instead; if they mean it is no longer done, call vokser_reopen_challenge_action. Only delete when they want the action gone entirely.
vokser_get_about
ChatGPTReturns background information about Vokser itself — what the platform is, the coach, the 3D framework, Challenges, the owl icon, and who created the frameworks. Use this to answer the user's questions about Vokser as a product, rather than questions about their own data or scores.
vokser_get_behaviour_score_history
ChatGPTReturns the history of how the user's score for a single behaviour has changed over time — each entry recording when it changed and the score before and after. Use this to discuss a behaviour's progress or trajectory with the user. Defaults to the 10 most recent changes (max 100).
vokser_get_behaviour_scores
ChatGPTReturns the user's self-assessment scores for the behaviours in the pillars they have selected to focus on — each identified by its framework behaviourKey (e.g. "1.1.4"), with its numeric score (1-5, or null if they have not scored it yet) and the behaviour's statement. Use this to see where the user rates themselves: to surface their strengths, their gaps, or behaviours they have not scored yet. Use scope to control grouping: 'all' (default) returns a flat list, and 'pillar' groups them by pillar. Optionally pass sort and limit. For behaviours outside the user's selected pillars, use vokser_get_framework. For the behaviours the user is actively working on in a Challenge — which can be any in the framework, not just their selected pillars — use vokser_list_challenges.
vokser_get_challenge
ChatGPTReturns a single open Challenge by id, with its behaviours and actions — the same shape as vokser_list_challenges. Use this to focus on one Challenge the user has named. Only open Challenges can be fetched this way. For one the user has already completed, call vokser_list_challenges with status='completed'.
vokser_get_framework
ChatGPTReturns the definition of the Vokser framework — its dimensions, pillars, and behaviours. Use this when you need to explain what a behaviour, pillar, or dimension means, or to ground coaching in the framework's own language, as opposed to the user's personal scores. Navigate by hierarchical key: call scope='index' first to list every dimension/pillar/behaviour key, then scope='dimension'|'pillar'|'behaviour' with a key for the full entry, or scope='overview' for the introduction.
vokser_get_motivator_definition
ChatGPTReturns the full definition of a single motivator, looked up by its definitionKey. Use this to explain what a specific motivator means when discussing it with the user.
vokser_get_motivator_history
ChatGPTReturns the history of how the user's score for a single motivator has changed over time — each entry recording when it changed and the score before and after, most recent first. Use this to discuss how the user's motivators have shifted. Defaults to the 10 most recent changes (max 100).
vokser_get_my_motivators
ChatGPTReturns the motivators the user has selected, each with its 1-5 score. Use this to understand what drives the user so you can frame coaching around their motivators. For the full set of motivators they could choose from, use vokser_list_motivators.
vokser_get_plan_progress
ChatGPTReturns the user's plan-progress snapshot: how many behaviours they have selected, how many they have scored, their average score (1-5), and the same breakdown per pillar. Use this to gauge how far through their self-assessment the user is and to decide which pillar to focus a coaching conversation on next. Also returns a challenges block — how many Challenges they have open and how many they have completed, plus the action counts for each open one — so "how am I doing?" can be answered on the work they are actually doing, not just their scoring progress.
vokser_get_profile_summary
ChatGPTReturns an AI-generated prose summary of the user — their job context, strengths, development areas, and motivators — as narrative text rather than raw fields. Use this when you want a quick qualitative read on the user to personalise coaching. Returns null if no summary has been generated yet, in which case suggest the user spends more time in Vokser first.
vokser_get_rating_scale
ChatGPTReturns the 1-5 behaviour rating scale (Novice→Expert), with a label and short description for each level. Use this to interpret or explain what a numeric score means when discussing the user's self-assessment.
vokser_get_selected_pillars
ChatGPTReturns the pillars the user has chosen to focus on for development, each with its framework key and title. Use this to scope a coaching conversation to the areas the user is actively working on, rather than the whole framework.
vokser_get_user_profile
ChatGPTReturns the user's profile — name, job function, years of management experience, direct reports, registration step, a snapshot of their current motivators and behaviour scores, and the Challenges they currently have open (with how many of each one's actions are done). Call this once at the start of a coaching conversation to prime yourself with the user's role, managerial context, and current Vokser standing before giving any guidance. openChallenges is a summary: for a Challenge's scenario, behaviour statements or individual actions, call vokser_list_challenges.
vokser_list_challenges
ChatGPTReturns the user's Challenges — the workplace situations they are working through with coaching support. Each has a title, the scenario they described, the framework behaviours it develops (with the user's current score for each), and the actions they have committed to. An action's completedDate is null while it is still outstanding. Defaults to their open Challenges: use this to see what the user is working on right now. Pass status='completed' for the ones they have finished, which additionally carry a closedDate — use that to reflect on past work or to notice a situation recurring.
vokser_list_motivators
ChatGPTReturns the full catalogue of motivators the user's company offers, each with a definitionKey, title, and category. Use this to see what motivators are available — for example to help the user explore or choose them. For the motivators this user has actually selected, use vokser_get_my_motivators instead.
vokser_reopen_challenge_action
ChatGPTWRITE — un-ticks a completed action, returning it to outstanding. Use this only when the user has said it is not actually done. Reopening an already-open action changes nothing.
vokser_update_behaviour_score
ChatGPTWRITE — sets the user's self-assessment score (1-5) for a single behaviour. Use this only when the user has explicitly stated the score they want to set (e.g. "I'd rate myself a 4 on that"). Do NOT infer or guess a score from the surrounding coaching conversation.
vokser_update_motivators
ChatGPTWRITE — replaces the user's entire motivator selection. Each item is a definitionKey with an optional 1-5 score (null keeps the motivator selected but unscored); any motivator not in the list is removed. Use this only when the user has explicitly stated which motivators they want and what scores to set. Do NOT infer their selection from a coaching conversation.
