Which Claude Code abilities is OrchestKit actually using?

29 abilities are sitting in the open queue. Most are not gaps. Six genuinely are, and they are not the ones the count points at.

01 · the queue, split by whether anyone answered it

Two thirds of the queue has never been looked at

Each new Claude Code release files one ticket per ability. A review answers a whole release at once, or nobody does.

one row per release · filled = reviewed, hollow = nobody has looked 2.1.2212 waiting 2.1.2224 waiting 2.1.2252 reviewed, tickets left open 2.1.2271 reviewed, ticket left open 2.1.2293 reviewed, tickets left open 2.1.2326 waiting 2.1.2333 waiting 2.1.2344 waiting 2.1.2351 waiting 2.1.2362 waiting 2.1.2381 waiting
What it means23 never reviewed. 6 reviewed, and the ticket stayed open anyway.
If we do nothingEvery release adds more, and the answers keep missing the tickets.
02 · the count is not the problem

Most unadopted abilities are things we correctly ignored

Seven tickets closed today were all answered two weeks ago, with the proving command written down.

where a reviewed ability actually lands does not touch us at allmost adopted, usually as docs real gap example: no agent declares the setting example: a command was renamed this is the only column worth your time
What it meansA big queue is mostly proof we checked, not proof we are behind.
If we do nothingThe number keeps reading as debt and hides the six that matter.
03 · the short list

Six abilities we could use and do not

Each was found and written down during a past review, then left without an owner.

turn the operating system guard ondecided today, not yet planned cap how deep helpers may spawn helperszero uses anywhere, only limit left stagger fan-out so siblings reuse cachewritten up, never switched on say how peer messages get approvednobody owns the policy let contributors install a local buildlogged as an opportunity, parked declare what the plugin depends onhas a ticket, no movement one more is blocked, not unused: credential masking cannot ship from a plugin at all
What it meansSix real ones, each already researched. None needs discovery.
If we do nothingThey stay found and unowned, which is how they got here.
04 · your call

Which of the six gets picked up?

All six are researched already. The question is which one becomes work this week.

after you pick:


    

      
      
      
    

  


  

    
So what?

    
The queue is not 29 problems. It is 23 unread, 6 answered but never closed, and six real abilities that were found, written down, and then left without an owner.