written by Eric J. Ma on 2026-11-12 | tags: glosscard prompts ai teaching privacy workflows hosting prompt cards ai tools link sharing
In this post, I share GlossCard, a little tool I built for handing someone a prompt along with the lesson behind it. It makes a short explainer with the fill-ins marked and notes on why each blank matters. You drive it with your own agent, the whole card lives inside the link itself, and nothing is stored on my servers. You can even host your own copy on any static site. It made me wonder: when the lesson can ride along in the URL, what else could we share without ever needing a database?
For weeks I kept hitting the same wall when I shared prompts or taught people how to use AI tools. I could paste the prompt into chat or drop it in a doc, and they still would not know how to use it. The words were there. The lesson was not. I wrote about that gap in an earlier post. This one is about the little tool that grew out of it.
I am thrilled to share GlossCard, a small thing I made for the same job. It shares a prompt card: a short explainer with the fill-ins marked and notes on why each blank matters. Someone opening your link should see how you think about the task, where they need to supply context, and what "done" looks like. The next person gets the text and the rationale together.
Here is the kind of annotated card I mean. This is the ingest prompt from my prompt cards post, shown in the same teach-the-why style:
A prompt card is meant to be teachable. The part that still makes me smile is that the instructions for making one are themselves a prompt card. You drive GlossCard with your agent, not with a form on my server.
When you finish a workflow, open the card page and copy the starter prompt. The page is the UI; your agent still does the work of turning the session into a card. Tell your agent to read the instructions at https://glosscard.nonlinearlabs.ai/prompt-card/instructions.txt, study your chat history and what it remembers from the session, and build a prompt card someone else can use to learn that workflow. Open the preview URL it gives you, sanity-check the highlights, then send the link to whoever you want to teach. The live page also walks through a meta example called Make a prompt card if you want to tap through one before you build your own.
This is the meta example on the GlossCard site. You use the same pattern for your own workflow.
The share URL looks like https://glosscard.nonlinearlabs.ai/prompt-card#v1.<payload>. Everything after the # is the compressed card. Your browser unpacks it and draws the page. The server only serves the shell; it never looks up your card. The address bar looks long because the lesson rode along in the link, not because I stored it somewhere and handed you a short pointer. Your recipient sees the same card you previewed. If you still have an old agentindex.nonlinearlabs.ai link, that host should keep working. A redirect to the GlossCard host is planned.
I care about privacy here. I did not want a database of other people's prompts, so I designed the format so the URL carries what the page needs. Nothing about your card lives on my side.
The instructions file is part of that design. It deliberately steers your agent toward a good card, and I published the full text in instructions.txt so you can read exactly what it says. I am fine calling that a mild prompt injection as long as it stays in the open.
Anyone with the link can read the card. You decide who gets the link. That is the trade you make when you share a lesson instead of asking me to host the prompt.
When the work is done, ask your agent for the card and send the link to the person you want to teach. They get a short explainer they can reuse. I never see the prompt, and I have nothing to delete later. That is the small tool I wanted on the days I was the one trying to explain it.
You do not have to use my host. Anyone can run their own GlossCard, because the whole card lives in the link. Any static host works. You do not need a server that looks up cards or a database on the back end.
Hand your coding agent the prompt card below. It can build the site from scratch and deploy it to GitHub Pages, Vercel, Netlify, Cloudflare Pages, or a similar static host.
If you want your own domain, you still only serve static files. The cards stay in the links you share, just like on mine.
@article{
ericmjl-2026-a-little-tool-for-sharing-prompts,
author = {Eric J. Ma},
title = {A little tool for sharing prompts},
year = {2026},
month = {11},
day = {12},
howpublished = {\url{https://ericmjl.github.io}},
journal = {Eric J. Ma's Blog},
url = {https://ericmjl.github.io/blog/2026/11/12/a-little-tool-for-sharing-prompts},
}
I send out a newsletter with tips and tools for data scientists. Come check it out at Substack.
# TODO(eric): learn how to learn anything. feb 2027.
If you would like to sponsor the coffee that goes into making my posts, please consider GitHub Sponsors!