Cron script jobs and skill usage tracking for curator

NousResearch/hermes-agent · cluster 136030 · cron

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

One issue reports that the curator archives skills referenced only indirectly, and that no_agent script jobs record no skill usage. Two pull requests touch cron handling: one scans script files for skills/ references, and the other bumps declared-skill usage on the no_agent script path.

Open issues1

  • Issue#136030[Bug]: Curator archives skills that are only referenced indirectly — no_agent script jobs never record usage at all

Open PRs2

  • PR#136109fix(cron): bump declared-skill usage on the no_agent script path
  • PR#136886fix(cron): bump canonical skill usage for cron jobs

1 PR closed without merging

From the close comments: closed without comment 1

  • #136067 fix(cron): referenced_skill_names scans script jobs' script files for skills/ references · closed without comment
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
cron
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.