claude-chat-exporter: Skill for Claude Code

Adding a sponsor

Assets live in docs/sponsors/<name>.svg. Three edits, all by hand — there is no CI.

README — one block under the install badge, holding both tiers

Company first, Team after, the same height="28" for every logo, and no taglines (they force a vertical layout and push the project's own pitch off the screen). The label links to the Support section so the policy is one click away:

<p align="center">
  <sub><b><a href="#support-this-project">Supported by</a></b></sub><br>
  <a href="https://acme.example" rel="sponsored noopener"><img src="docs/sponsors/acme.svg" alt="Acme" height="28"></a>
  &nbsp;
  <a href="https://globex.example" rel="sponsored noopener"><img src="docs/sponsors/globex.svg" alt="Globex" height="28"></a>
</p>

Do not add a "still MIT / still private" line beside the logos. Both claims are already in the README's first sentence, above the badge.

Install page — Company tier only

A row in the footer of docs/index.html. The footer is also where the update notice sends returning users (d.onclick = window.open(P) in the shim), which is what the tier sells.

<span class="sponsors"><span class="lbl">Supported by</span>
  <a href="https://acme.example" target="_blank" rel="sponsored noopener"><img src="sponsors/acme.svg" alt="Acme" height="28"></a>
</span>

footer .sponsors { display: flex; align-items: center; gap: .5rem .9rem; flex-wrap: wrap; }
footer .sponsors .lbl { font-size: .8rem; color: var(--muted); }
footer .sponsors img { height: 28px; width: auto; max-width: 110px; opacity: .85; }
footer .sponsors a:hover img { opacity: 1; }

Accepting the asset — sanitise before committing

Committing the logo is the right call: it keeps the install page's promise that it makes no third-party requests. Hot-linking a sponsor's own domain would let them log every visitor's IP. (refined-github does the same; larger projects instead serve from their funding platform. Nobody loads a sponsor's server.)