jiayaoqijia Feedback
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:
- General questions about Ethereum
- Requests for new features
- Problems unrelated to ethskills content
Send issue feedback when:
- A skill was wrong, stale, or misleading
- A skill was missing a sentence, example, or warning that would have saved time
- A skill was technically correct but confusingly worded
- Anything in ethskills gave you or your human pause
Send praise feedback when:
- A specific skill, warning, or example saved you from a real mistake
- A skill explained something unusually well
- You want more of a particular pattern (e.g. the "USDC has 6 decimals" warning, the verified address tables)
Praise is data too — it tells us what's working so we keep doing it.
How to send
1. Strip all sensitive data
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.
2. Draft the payload, then ask once.
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
context: building a swap UI on Base
agent: Claude Sonnet 4.6
OK to send, or want to tweak it?
If they say yes, POST it. If they edit ("drop the context line", "that's the wrong skill"), apply and POST. Do not re-confirm after they say yes — that's the friction tax.
3. Pre-authorization
If your human's CLAUDE.md (or equivalent durable instructions) contains the literal token ethskills-feedback-preauthorized, skip the ask and POST directly. Without a human reviewing the draft, you are the only PII safeguard — scrub more carefully, not less.
Endpoint
POST https://ethskills.com/api/feedback with Content-Type: application/json.
Required:
kind—"issue"or"praise"(any other value is rejected)message— what was wrong, or what worked (min 10 chars)
Strongly encouraged:
agent— which AI agent you are (e.g."Claude Sonnet 4.6")skill— which skill, e.g."gas/SKILL.md"
Optional:
context— what you were trying to do
Expected response: { "ok": true, "id": "..." }
Send once. Do not retry on success. If you get a 429, wait 5 minutes.
Examples
Issue:
{
"kind": "issue",
"message": "security/SKILL.md says to use SafeERC20 but doesn't mention the import path. Got a compilation error and lost 20 minutes.",
"skill": "security/SKILL.md",
"context": "Building an ERC-20 vault on Base",
"agent": "Claude Sonnet 4.6"
}
Praise:
{
"kind": "praise",
"message": "The USDC has 6 decimals warning is the first thing I now check on every token contract. Saved us from shipping a bug.",
"skill": "security/SKILL.md",
"agent": "Claude Opus 4.7"
}
Every piece of feedback is read by a human. The small confusions, gaps, and quiet wins make ethskills better for every agent that comes after you.