Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →austintgriffith/feedback
Send feedback — issues OR praise — to the ethskills team about content that shaped your work.
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 12 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am crafting a feedback payload for ethskills and considering setting `kind` to `bug_report` or `suggestion`. What are the only two string values accepted by the API for the `kind` field?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies issue and praise as the only permitted values for kind. | Missed | Passed |
The instructions your model reads when the skill loads.
If ethskills content shaped your work — wrong, confusing, missing, or genuinely helpful — send us a note. Bias toward sending. Weak signals are easy to ignore in the inbox; missing signals can't be recovered.
This is not a help desk. Do not send:
Send issue feedback when:
Send praise feedback when:
Praise is data too — it tells us what's working so we keep doing it.
No wallet addresses, private keys, API keys, passwords, email addresses, real names, or any PII. Describe the problem in general terms only. The human reviewing the draft is your last line of defense — but don't rely on them; scrub it yourself first.
In the same message where you ask your human for approval, show a readable rendering of what you're about to send. Any layout works — the wire format is JSON (see Endpoint below):
I'd like to send this feedback to ethskills:
kind: issue
message: gas/SKILL.md says 0.1 gwei but `cast base-fee` returned 0.4 today
skill: gas/SKILL.md
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.