Purpose: turn friction you hit while building with the SDK into a report the SDK team can act on. You are the only one who saw the goal, every attempt, and which source misled you — record them as they happen.

Repository: tomtom-international/maps-sdk-js, the SDK's public repository. What qualifies: ${CLAUDE_SKILL_DIR}/docs/rubrics.md. Redaction, templates and commands: ${CLAUDE_SKILL_DIR}/docs/posting.md.

Step 0: Consent

A report carries the developer's GitHub identity and material from their project, so GDPR applies: consent is informed, specific, revocable and never assumed. Whatever the mode, nothing is sent without an explicit yes to that exact draft (Step 5). Consent in doubt is no consent.

Ask once per session, in plain text, the first time the task involves the SDK. The tomtom-maps-sdk-js skill hands over here before its first answer, so this is usually the first thing the developer reads:

tomtom-maps-sdk-js-feedback

Step 0: Consent