SKILL.md
Notte Functions Doctor
A user-triggered repair tool for a broken Notte Function. The user already knows a Function is failing - this skill's job is to find out why, fix it when it is fixable, verify the fix without disturbing the live Function, and promote it only with explicit approval.
The hard part of repair is not editing code - it is diagnosis. A broken scrape usually does not error; it silently returns [] or garbage because a selector or endpoint moved. This skill leans on the Function's health contract (stamped by notte-functions-build) and its last good run to know what "correct" looks like, then works backward from the failure.
Relationship to notte-functions-build. Doctor reuses that skill's two engines - exploration (find the new stable path) and self-test (verify against the contract) - pointed at an existing Function instead of a blank one. It also builds on the base notte-browser skill. Load those for the full command reference.
What this skill can and cannot fix
Be honest about the boundary. Not every failure is a code fix, and flailing on an unfixable one wastes runs and can make things worse.
| Failure class | Doctor's action |
|---|---|
| Selector / endpoint drift (runs OK, returns empty/wrong shape) | Fix - re-explore, patch, verify, promote |
Hard exception in run() |
Fix - re-explore the failing step, patch |
| Expired credentials / auth wall | Diagnose and report - the user must refresh the vault/persona; not a code fix |
| Anti-bot block / captcha | Diagnose and advise - suggest --proxy / a trusted profile; captcha solving is already on. Do not blindly retry |
| Site genuinely gone or restructured | Report - confirm the new target/intent with the user before rebuilding |
Notte Functions Doctor
A user-triggered repair tool for a broken Notte Function. The user already knows a Function is failing - this skill's job is to find out why, fix it when it is fixable, verify the fix without disturbing the live Function, and promote it only with explicit approval.
The hard part of repair is not editing code - it is diagnosis. A broken scrape usually does not error; it silently returns [] or garbage because a selector or endpoint moved. This skill leans on the Function's health contract (stamped by notte-functions-build) and its last good run to know what "correct" looks like, then works backward from the failure.
Relationship to notte-functions-build. Doctor reuses that skill's two engines - exploration (find the new stable path) and self-test (verify against the contract) - pointed at an existing Function instead of a blank one. It also builds on the base notte-browser skill. Load those for the full command reference.
What this skill can and cannot fix
Be honest about the boundary. Not every failure is a code fix, and flailing on an unfixable one wastes runs and can make things worse.
| Failure class | Doctor's action |
|---|---|
| Selector / endpoint drift (runs OK, returns empty/wrong shape) | Fix - re-explore, patch, verify, promote |
Hard exception in run() |
Fix - re-explore the failing step, patch |
| Expired credentials / auth wall | Diagnose and report - the user must refresh the vault/persona; not a code fix |
| Anti-bot block / captcha | Diagnose and advise - suggest --proxy / a trusted profile; captcha solving is already on. Do not blindly retry |
| Site genuinely gone or restructured | Report - confirm the new target/intent with the user before rebuilding |