Index of every page on this site: llms.txt
All skills
austintgriffith avatar

/feedback

@47779e7
Run it yourself

Send feedback — issues OR praise — to the ethskills team about content that shaped your work.

  • 1 file
  • 3.6 KB
  • Updated 7 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/austintgriffith/ethskills/feedback

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈27 tokens for metadata: the name and description. ≈879 when used: this file.

SKILL.md has missing or invalid fields
  • The name in the SKILL.md header is missing or is not text.
Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 47779e7. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 weeks ago.

Activeupdated 7 months ago
title
Feedback

README badge

README badge for austintgriffith/ethskills/feedback