Add SuggestSkills: decide which skills to build from your work history - #1798
Open
rathko wants to merge 1 commit into
Open
Add SuggestSkills: decide which skills to build from your work history#1798rathko wants to merge 1 commit into
rathko wants to merge 1 commit into
Conversation
Signed-off-by: Radek <radek@dataminelab.com>
rathko
force-pushed
the
add-suggestskills
branch
from
August 8, 2026 13:48
87a4ebc to
b7d7f79
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds SuggestSkills, a read-only skill that tells you which new skills are worth building, from your own work history and satisfaction signals. It proposes a ranked shortlist and routes accepted items to CreateSkill. It never creates or edits a skill itself.
Why
CreateSkill covers building, validating, testing, and improving a skill. Nothing covers the step before it: deciding what to build. A plain topic scan of your sessions gives a false "nothing here", because the real gaps hide in two places a topic scan cannot see. First, frustration: a topic can look covered while you keep hitting the same wall inside it. Second, discipline gaps under a covered topic: a build skill owns "app work" while the recurring pain is an unowned discipline the build skill never touches. SuggestSkills reads the frustration signal LifeOS already captures via SatisfactionCapture, alongside work sessions, so it catches both.
Shape
Read-only and proposal-only. It has no capability to create a skill, which is what makes "never auto-create" a boundary rather than a promise in prose.
Deterministic gathering. Tools/CollectSignals.ts emits a normalized corpus (sessions, low-rating frustrations, the skill/loop/workflow registry, and warnings for any missing or malformed store). The model only clusters and judges what the tool returns, so two runs see the same evidence. Store paths are discovered via flag, env, or root, so it works across installs.
Two verification passes, reported as a union with an agreement tag. Requiring both passes to agree would hide the subtle gaps this exists to find.
Evidence
Blind test on real history: a topic-only pass missed a recurring state-modeling gap and reported nothing. The frustration-aware pass, run over the same window with the answer hidden, surfaced it in both passes independently. It also files behavior corrections such as verbosity or scope misreads as steering, not skills.
Contents
SKILL.md, Workflows/Scan.md, Tools/CollectSignals.ts. Generic, no external dependencies.
Credit
The idea comes from Hermes Agent by Nous Research, whose learning loop creates skills from experience. Hermes creates and grooms them autonomously. This takes the discovery half and inverts the risk: it is read-only, proposes only, and a human approves every skill before CreateSkill builds it.