You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/skill-improve <query> generate a Gemini Flash improvement proposal for one skill
13
+
/skill-manager open an interactive menu to pick a skill and run actions
13
14
```
14
15
15
16
## Tool
@@ -28,6 +29,8 @@ Writes:
28
29
.pi/skill-audit/improve-<skill>.md
29
30
```
30
31
32
+
`improve-<skill>.md` includes review scores, main gaps, proposed changes, a suggested patch, lightweight eval scenarios, and approval questions. For symlinked skills it records both the display path and resolved source path.
33
+
31
34
## Scope
32
35
33
36
Scans the standard Pi skill locations:
@@ -55,4 +58,6 @@ Scans the standard Pi skill locations:
55
58
56
59
`/skill-audit` does not use an LLM and never edits skills.
57
60
58
-
`/skill-improve` uses `google/gemini-2.5-flash` through Pi's model registry to generate a proposal/diff only. It never edits skills. Review the proposal and explicitly ask Pi to apply changes if you approve.
61
+
`/skill-improve` prefers `google/gemini-3-flash-preview`, falls back to `google/gemini-2.5-flash`, then the current model. It uses a fixed rubric inspired by skill optimization workflows: completeness, actionability, conciseness, robustness, invocation clarity, safety/approval, and validation. It generates a proposal/diff only and never edits skills. Review the proposal and explicitly ask Pi to apply changes if you approve.
62
+
63
+
`/skill-manager` opens quickly by listing discovered skills without auditing them all. The skill picker uses a scrollable TUI list with compact labels, prefix filtering by typing, symlink badges, duplicate-count badges, and paths in descriptions. Pick a skill, then choose `Run audit`, `Generate improve proposal`, `Open latest proposal in nvim`, or `Show paths`. `Run audit` keeps the persistent widget compact and points to `/skill-audit <name>` for full details. After generating an improve proposal, the UI asks whether to open the proposal in Neovim. Symlinked skill directories are followed during discovery; path views and improve reports show the resolved source path to make future approved edits target the source.
0 commit comments