Edge Skills: rate a loaded skill
rate_skillRecords only an Edge rating of a skill you used: it does not change the user's files or task output and takes no action outside Edge. Retries with the same request_id never add a second rating. Rate only after completing the deliverable, once; if its result gives an Edge closing line, end your answer with it. Rate a skill you actually followed with helped, hurt, no_difference or unclear; unclear and no_difference are fine. If you applied the skill (helped, partly_helped, no_difference, hurt, broken), also send score, an integer 0-10: 0 made the result worse, 2 applied but did not work, 5 no meaningful difference, 6 small useful contribution, 7 clearly useful, 8 clearly improved the result, 9 major improvement, 10 the task would likely have failed or been materially worse without it. A failure is a low score, not a skipped rating. Omit score for wrong_skill, loaded_not_used and unclear. Every rating needs a note: one line specific to this task, up to 280 characters, that explains the judgment rather than repeating the outcome or score; a missing, blank or placeholder note leaves the rating incomplete and out of Edge's aggregates. Judge the outcome yourself; never ask the user. If the host blocks the call, finish without it; that host decision is not an Edge bug and needs no report_issue. The server identifies the skill from this request_id. Older outcomes remain accepted; partly_helped and wrong_skill take a reason, one of missing_steps, outdated, too_generic, wrong_domain, too_long or other (other when omitted). Notes over 280 characters are cut. If use_skill listed named parts for the skill and you applied any of them, send applied_component_ids with up to two; report only components you actually applied, and omit it when none of them apply rather than guessing. Keep the note free of the user's query, code, names and private data. With a Pro key, once the task is done and the skill was applied, you may include task: one UUID per logical task (reuse it for every skill and retry), revision 1, completed_at, the exact source@skill and one sentence on its concrete contribution. Raise revision only to correct a report. Edge returns the user's weekly tally; never invent or change that count. For a bug or idea about Edge itself, use report_issue instead.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Required for every rating: one line specific to this task on why (up to 280 characters; a longer note is cut) that explains the judgment, not a restatement of the outcome or score. A missing or placeholder note leaves the rating incomplete. Do not include the user's query, code, names or private information. | |
| task | No | Optional completed-task report, separate from legacy skill feedback. Pro key required. One report per logical task; revision replaces the prior report. Only report actual application. | |
| score | No | Integer 0-10 when you applied the skill (helped, partly_helped, no_difference, hurt, broken); omit for wrong_skill, loaded_not_used and unclear. 0 made it worse, 2 did not work, 5 no difference, 7 clearly useful, 8 clearly improved, 10 would likely have failed without it. | |
| reason | No | For partly_helped or wrong_skill: missing_steps, outdated, too_generic, wrong_domain, too_long or other. Defaults to other; free text becomes other. | |
| outcome | Yes | Once the task's outcome is known: helped, hurt, no_difference or unclear. Only for a skill you actually followed. | |
| request_id | Yes | ||
| applied_component_ids | No | Up to two ids from the skill's named parts listed in the use_skill result, only parts you actually applied in this task; send them whenever you applied any. Omit when none were listed or none were applied; never invent one. |