Home › Contact

Contact

Found a migration problem the tool did not catch, or a rule that looks wrong? Reports like that are the most useful thing you can send.

Email address

What is worth writing about

In rough order of how much it helps:

Type of message	Why it matters
A migration gotcha this tool does not mention	Most valuable. It means another real person hitting the same wall
A validation rule that looks wrong or missing	Directly improves the checker's accuracy
The validator passed a file that then failed to upload	A real bug — please say what you pasted so it can be reproduced
The validator rejected a valid file	Same, in the other direction
Something broke on your browser	Include browser and OS

What to include

For a validation problem, the most useful thing is the smallest snippet that reproduces it. Something like:

---
name: your-skill-name
description: What it does. Use when the user asks about X.
---

Steps here.

Then say which line the validator flagged and what you expected instead.

⚠️ Please do not paste confidential or client material — a minimal example with invented text is usually enough to reproduce a problem. The validator runs in your browser, so your pasted text was never sent here; sending it by email would be the one way it leaves your machine.

What you will not get back

This is a one-person project with no support staff, so be aware of two things:

• There is no response guarantee. Most real reports do get answered, but not always quickly.
• Individual Gem migrations cannot be done for you. The site exists so you can do it yourself — the point is that you keep control of your own instructions.

Before writing

Some things are already answered and searching first is faster than waiting for a reply:

Your question	Look at
How do I actually do the migration?	Step-by-step guide
What are the exact format rules?	Format reference
Will my Gem convert cleanly?	Migration risks
Why did the validator flag something?	FAQ

Correction policy

If something on this site is factually wrong about Google's documentation, that is a priority. Corrections get made and the change is recorded in the site's public commit history on GitHub, so the record of what was changed and when is permanent.

What happens to your message

It arrives in an inbox, and that is all. Messages are not added to a mailing list, not shared, and not used for marketing. There is no newsletter to subscribe to.