I have been fixing up a 2011 Sony VAIO running Deepin 25, and most of what I
learned was not a package I could install - it was a way of measuring before
changing anything. So I wrote it down as four agent skills: single Markdown
files that UOS AI (or any agent that reads SKILL.md) picks up when the problem
matches.
laptop-power-diagnosis - the fan is loud, the battery lasts an hour, the
estimate says fourteen. Measure the draw, attribute it to a process, then
change the smallest thing and keep the revert command.
suspend-and-hibernate - the machine was flat again after the lid was shut.
A sleep hook with an RTC deadline, plus the 120-second experiment that proves
it resumed rather than rebooted.
battery-reporting-honesty - the percentage jumped to 100 and back. Gauge
confusion, worn cells and heavy load look identical from the tray; this
separates them, and says when calibration is the wrong answer.
bug-reporting-with-evidence - the report nobody has to ask a follow-up
question about: exact versions, one two-minute log window, one clean-config
test, redaction, send.
Steps 1-3 of every skill are read-only. The first change only appears in step 4,
and it comes with its revert.
Install (UOS AI):
tar xzf skills-pack.tar.gz -C /tmp
cp -r /tmp/skills/* ~/.uos-ai/skills/
The assistant picks them up on the next message. Remove one with rm -rf, that
is the whole uninstall.
What these are not: they are not fixes for Deepin. Where a defect belongs to the
distribution, the honest thing is still a bug report - that is what the fourth
skill is for. The sleep hook is a local safety net for firmware that will never
be patched, and it is described as one.
MIT licensed, no dependencies, no build step. If you try one and it does not fit
your machine, I would rather hear where it failed than where it worked - the
traps section is where the useful parts came from.
skills-pack.tar.gz
I have been fixing up a 2011 Sony VAIO running Deepin 25, and most of what I
learned was not a package I could install - it was a way of measuring before
changing anything. So I wrote it down as four agent skills: single Markdown
files that UOS AI (or any agent that reads
SKILL.md) picks up when the problemmatches.
estimate says fourteen. Measure the draw, attribute it to a process, then
change the smallest thing and keep the revert command.
A sleep hook with an RTC deadline, plus the 120-second experiment that proves
it resumed rather than rebooted.
confusion, worn cells and heavy load look identical from the tray; this
separates them, and says when calibration is the wrong answer.
question about: exact versions, one two-minute log window, one clean-config
test, redaction, send.
Steps 1-3 of every skill are read-only. The first change only appears in step 4,
and it comes with its revert.
Install (UOS AI):
The assistant picks them up on the next message. Remove one with
rm -rf, thatis the whole uninstall.
What these are not: they are not fixes for Deepin. Where a defect belongs to the
distribution, the honest thing is still a bug report - that is what the fourth
skill is for. The sleep hook is a local safety net for firmware that will never
be patched, and it is described as one.
MIT licensed, no dependencies, no build step. If you try one and it does not fit
your machine, I would rather hear where it failed than where it worked - the
traps section is where the useful parts came from.