Skip to content
SkillCheatSheet Sign in

todos

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

59/ 100C

Code score by group

  • Spec20/20
  • Description10/20
  • Procedure7/15
  • Done criteria0/15
  • Resources7/10
  • Scripts5/8
  • Safety7/7
  • Upkeep3/5

It loses the most points in Done criteria (15), the group that checks whether there is a checklist and a step that verifies the work.

What the author says it does

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 answers or checks, or one- to two-step work that is not already in the list.

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

Repository
JetBrains/thinkrail
Folder
packages/pi-todos/skills/todos
License
Apache-2.0
GitHub stars
8,187
SKILL.md lines
194
Other files
0

Add todos to your agent

npx skills add JetBrains/thinkrail --skill todos

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. 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
  7. 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
  8. managing-mcp-servers

    Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process,…

    56C

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.