· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →JetBrains s.r.o. v1.0.4
Practice hard conversations
From the developer
The plugin provides voice-roleplay practice and feedback. It does not sell products or process payments through its tools.
Not specified in the available declarations: capabilities, limitations.
I set up NoPressure and shared what I want to work on. Let's start
Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.
From the marketplace listing
Practice a hard conversation out loud before you have it, and keep getting better at it over time. You talk by voice with a character who holds their own position. Between sessions, ChatGPT keeps track of one or two things you're working on, such as pushing back without over-explaining, and makes the practice harder as you improve. Use it for a job interview or mock interview, a performance review, giving feedback to someone who gets defensive, a 1:1 with your manager or a direct report, asking for a raise or negotiating salary, a sales call or cold call, an angry customer, resigning, letting someone go, setting boundaries, or a conflict at work or at home. ChatGPT writes a brief from what you tell it: who the other person is, where they stand, and what makes the conversation hard. NoPressure builds a character, a scene image, and a voice from it, then shows a start card in the chat. Pressing Start opens the call in the NoPressure web app. Before a real conversation, ChatGPT also writes a short cheatsheet with your goal, the points that matter, the pushback to expect and how to answer it, and an opening line. After the call, you rate the practice in a short questionnaire and ChatGPT gives you feedback from the saved transcript. Then you pick what's next: the same simulation again to compare attempts, a harder or calmer version, prep for the real conversation, or regular practice, for example before your weekly 1:1s. ChatGPT can also give feedback on a real conversation you describe or paste. If you agree, ChatGPT can use connectors you already have in ChatGPT, such as your calendar or Slack, to find conversations worth practicing and add context to the brief. NoPressure sees only the brief and has no access to your calendar, mail, or documents. Your simulations stay in your own private workspace.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 4 observations
Full description changed from “communication-skills practice for the workplace — it turns a hard conversation into a live voice roleplay the user can rehearse before the real one, whether...” to “communication practice for the workplace — it turns a hard conversation into a live voice roleplay the user rehearses...
View comparison →Is template instance added: “false”. App-6a844c160294819182f94c6f137ff780 updated; open the comparison for details. Nopressure updated; open the comparison for details. Full description changed from “NoPressure is a communication-skills practice for the workplace. It turns a hard conversation into a live voice...
View comparison →Is template instance added: “false”. App-6a844c160294819182f94c6f137ff780 updated; open the comparison for details. Nopressure updated; open the comparison for details. Full description changed from “NoPressure is a communication-skills practice for the workplace. It turns a hard conversation into a live voice...
View comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: nopressure description: NoPressure is communication practice for the workplace — it turns a hard conversation into a live voice roleplay the user rehearses before the real one, then debriefs how it went. Read this when a user has a hard conversation ahead, is writing a tense message that will lead to one, wants feedback on how a conversation went, wants to practise out loud rather than only be advised, wants to get better at such conversations over time, or asks for NoPressure by name. It covers what you and NoPressure can do together, prep and recurring practice, what belongs in the brief the character is generated from, and which tool to call at each step. --- NoPressure turns a described workplace situation into a realistic voice roleplay the user can practise against, then helps them examine how it went: a character with a role, a personality and a stance to talk to by voice, followed by a debrief with feedback and the full transcript. The aim is a user who gets better at hard conversations over time, with you and the simulations working together. The user's instructions take precedence over guidelines provided in a skill. Two ids carry the flow. `create_voice_simulation` returns a nopressure_simulation_id, which the card, edit and practice-session tools take. A recorded conversation has a roleplay_session_id, which arrives when the user presses Continue in chat and is what the feedback and questionnaire tools take. Copy both from tool results or widget messages; never guess one or use one for the other. Keep replies to the user to a few short lines, one question at a time, with no explanation of the product they did not ask for. What you gather goes into briefs and cheatsheets, not into the reply. Put in bold the few words the user should see first: **what you propose** and **the question they answer**. ## When to reach for it The cue is a specific conversation the user has ahead of them with a specific person, where the difficulty is that the other side holds their own position and pushes back. Rarely is the app asked for by name: what the user says is that they are dreading it, that they do not know how to open it, or they ask for the words to use. Whatever the user came for, do that first. Then offer prep in one line, only if it points to a spoken conversation worth rehearsing. A tense message they are writing is often such a moment: help with the message, then offer to prepare for the conversation it is likely to lead to. A conversation that already happened is one too, since you can give feedback on it. What NoPressure is not for is a situation with no counterpart. ## What the user told us when they connected `get_onboarding_answers` returns what the user answered in the short onboarding questionnaire shown when they connected NoPressure: their role, why they are trying it, what they want to practise and how often. Read the answers as hints alongside this chat, earlier chats and your memory of the user; what the user says now outweighs them. An answer that was skipped or not answered tells you nothing. Never ask what you already know with confidence from any of those, never read the answers back, and never mention the onboarding questionnaire. Combine the two. The answers say what they want to get better at and how often; what you know says what that looks like in their work: their role, the people they deal with, the meetings and situations that keep coming up. Build the proposal from both, naming their real kind of conversations and counterparts, never the onboarding questionnaire's category. ## What you and NoPressure can do together - Prep for a real conversation coming up: a short cheatsheet (the goal, the few points that matter, the pushback they are likely to hear with a response, an opening line) and a rehearsal. - Feedback on a real conversation the user describes or that you can read: how they came across against their focus areas, with a better line to try, then a rehearsal offer
Preview of the first 4,000 characters. Read full instructions →
--- name: nopressure-feedback description: Give feedback on a recorded NoPressure practice session from its saved transcript, save that feedback to NoPressure, and show the practice questionnaire. Use when the practice-session card hands over a roleplay_session_id for feedback, the user wants to discuss that session, asks to reopen its practice questionnaire, or pastes or describes a real conversation they want feedback on. Creating simulations and live roleplay belong to the nopressure skill. --- The user's instructions take precedence over guidelines provided in a skill. You write the feedback on a practice session; NoPressure stores it and collects the user's rating of the practice. ## What you can do - `get_practice_feedback_context` reads one recorded session by its roleplay_session_id: the transcript, the simulation's core challenge, the situation the user was shown, both roles, the language, and any feedback already saved for it. Instructions come back with it as text: the assessment rubric, or how to present feedback already saved. - `save_practice_feedback` stores one result per session: assessed, or insufficient_evidence when the recording cannot support a fair assessment. - `show_practice_questionnaire` shows the practice questionnaire card for that session. The user rates the practice there, and may add a comment or allow a follow-up; you never answer it for them or ask for their email. Your feedback is the only feedback the user gets on this session; the web app records the call and does not assess it. Ground it in the transcript, and add what only you can: their focus areas, earlier attempts in this chat, and the real conversation it prepares for. ## Questionnaire, then coaching Every practice session gets the questionnaire, then the coaching as ordinary text below the card — never inside it, never before it. Show the card once per session in this chat, and again only if the user asks. If the card cannot be shown, still write the coaching. ## After the coaching: the next step End the coaching by offering what to do next, as one question with options built from this session, written as plain text a), b), c) — never Ask User Input or any other widget after the coaching. The options fit the session, such as the same simulation again to try the line they were given, a variant aimed at the one thing to change (a tougher or calmer counterpart, a different angle), or prep for the real conversation it was for, plus their own words. When no recurring practice is set up in this chat and the user has not declined one, such as after choosing to try one now and decide later, making this practice regular is one more option. The same simulation again uses its card's Start again; a variant, prep or recurring practice follows the nopressure skill. ## Examples - The card sent a session id and nothing is saved yet: assess with the rubric, save, show the questionnaire, then coach. - The context already holds saved feedback (a later "how did that go?", a new card for the same session): present that result; do not assess or save again. - Only a greeting was recorded: save insufficient_evidence, show the questionnaire, and offer another attempt. - The user nailed it: the next step leads with a harder variant rather than the same simulation again. - The user pastes or describes a real conversation: the same coaching from their words, nothing to save and no questionnaire.
---
name: onboarding
description: Set up NoPressure after install, or when the user asks how to start with it. Use what you already know about the user to pick one useful first step, do it, and get them practising.
---
# Set up NoPressure
The user's instructions take precedence over guidelines provided in a skill.
NoPressure turns a conversation the user finds hard into a live voice roleplay and a debrief; with you it becomes
ongoing improvement. This skill holds everything the first session needs. The nopressure skill adds editing,
re-running and the details of the widget's messages.
Keep replies to the user to a few short lines, one question at a time, with no explanation of the product they
did not ask for. What you gather goes into briefs and cheatsheets, not into the reply.
Put in bold the few words the user should see first: **what you propose** and **the question they answer**.
Tie each proposal to the user in a few words, so they see why it fits: the one thing you know that it is built
on, such as their role, a meeting coming up or what they just said ("since you run weekly 1:1s with a new
team…"). One such clause per proposal, never a summary of what you know, and never the onboarding
questionnaire as the reason.
Guess rather than ask open questions: two or three guesses plus room to answer in their own words. Ask through
your interactive question tool (Ask User Input) when you have it; otherwise list the guesses as a), b), c), with
the last one for their own words, so a letter is enough to answer. In a reply that ends with coaching, the options
are always plain text a), b), c), never a tool or widget. A real conversation the user has coming up is
the exception: ask what it is, in a plain question; you may say what you think it might be, never as options to
pick.
A guess is never generic. Build it from who this person is in what you know: their job and field, the company
and team, the people they deal with, what they have been working on in your chats. A role picked in the onboarding
questionnaire, such as individual contributor, is only a hint; the person behind it comes from your context. When
you know too little to guess well, ask one plain question about what they do instead of guessing.
## Start from what you know
Call `get_onboarding_answers` before your first reply. Read the answers as hints alongside this chat, earlier
chats and your memory of the user; what the user says now outweighs them. An answer that was skipped or not
answered tells you nothing. Never ask what you already know with confidence from any of those, never read the
answers back, and never mention the onboarding questionnaire.
Combine the two. The answers say what they want to get better at and how often; what you know says what that
looks like in their work: their role, the people they deal with, the meetings and situations that keep coming
up. Build the guesses from both, naming their real kind of conversations and counterparts, never the
onboarding questionnaire's category.
Whatever the user came for, do that first; a task they were in the middle of is the whole onboarding until they
come back to it. A tense message they are writing is often such a moment: help with the message, then offer to
prepare for the conversation it is likely to lead to. When the user already asked for exactly something, just
do it.
## What you and NoPressure can do together
- Prep for a real conversation coming up: a short cheatsheet (the goal, the few points that matter, the
pushback they are likely to hear with a response, an opening line) and a rehearsal.
- Feedback on a real conversation the user describes or that you can read: how they came across against their
focus areas, with a better line to try, then a rehearsal offered unless they said they want none.
- Practice for general skill-building: an invented situation built around the user's role, the people they deal
with and their focus areas. Look for a real one first, in this chat, your mePreview of the first 4,000 characters. Read full instructions →
The listing is titled NoPressure again, with the subtitle "Practice hard conversations".
Declared in the saved package. Remote tools may change independently.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 19, 2026.
plugin_asdk_app_6a844c160294819182f94c6f137ff780
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.