Skip to content
SkillCheatSheet Sign in

asking-user-questions

An AI agent skill from JetBrains/thinkrail, scored 55 out of 100 by code.

55/ 100C

Code score by group

  • Spec20/20
  • Description5/20
  • Procedure8/15
  • Done criteria0/15
  • Resources7/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Description (15), the group that checks whether the description says what the skill does and when to use it.

What the author says it does

Use when composing an ask_user_question round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.

This is the description in the skill's own SKILL.md, written by its author, not by SkillCheatSheet.

Repository
JetBrains/thinkrail
Folder
packages/pi-thinkrail-workflow/skills/asking-user-questions
License
Apache-2.0
GitHub stars
8,187
SKILL.md lines
126
Other files
0

Add asking-user-questions to your agent

npx skills add JetBrains/thinkrail --skill asking-user-questions

The command uses the open skills CLI. A skill is instructions and scripts your agent will follow, so read it first: open the folder on GitHub at the commit that was scored.

More skills from JetBrains/thinkrail

  1. librarian

    Research open-source libraries with evidence-backed answers and GitHub permalinks. Use when the user asks about library internals, needs implementation details with source code re…

    73B
  2. writing-workflow-skills

    Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the…

    69C
  3. importing-a-codebase

    Use when asked to create the initial spec graph for an existing codebase that has source code but no specs. Normally reached via setting-up-a-project.

    67C
  4. starting-a-new-project

    Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.

    63C
  5. brainstorming

    Use before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or edits that change no behavior (typos, documentation or configu…

    61C
  6. todos

    Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot a…

    59C
  7. spec-graph

    Use when locating, reading, creating, updating, or validating project specs, or when work is governed by or may alter a documented boundary, contract, invariant, behavior, or arch…

    58C
  8. choosing-a-workflow

    Use at the start of new project onboarding, PR lifecycle work including PR checks, or any change to what the product does — a feature, a behavior change, or a bug fix. Not for con…

    57C

All skills in JetBrains/thinkrail

Scores come from a snapshot of 300 public GitHub repositories taken on 12 November 2026. Every score is the result of fixed checks run by code; no AI is involved. How scoring works.