Certifications · A Certificate Worth Earning
Delivering a certificate someone can verify
A certificate is only as good as the check behind it. When a client or an employer sees one, they need a way to confirm it without taking anyone's word for it.
Start with the record
Every certificate you issue gets a record, and the certificate points back to it. This script gives Claude what the certificate claims and asks what the record needs so a stranger could trust it:
"""Draft the record behind a certificate.
Takes the skills a certificate claims and asks Claude which fields
each issued certificate's record needs, so a stranger could check it.
python3 record.py skills.md
"""
import sys
import anthropic
BRIEF = """Here is what a certificate claims. I'll issue one to each learner who passes,
and put a public verify page on my site where anyone can type a certificate ID.
List the fields each certificate's record needs so a stranger could trust it,
one per line as "field: why". Then say in one line what the verify page should
show for a valid, an expired and a revoked certificate.
No product or platform names. Plain text, no markdown or code fences,
at most 16 lines, each under 80 characters."""
if __name__ == "__main__":
skills = open(sys.argv[1]).read()
print("Asking Claude what the record needs...\n")
response = anthropic.Anthropic().messages.create(
model="claude-sonnet-5-5",
max_tokens=4000,
messages=[{"role": "user", "content": f"{BRIEF}\n\n<skills>\n{skills}\n</skills>"}],
)
print("".join(b.text for b in response.content if b.type == "text"))
Here's what came back for the prompt-writing course, exactly as it ran:
certificate_id: long random string, so IDs can't be guessed or forged
learner_name: the person who earned it, shown as they agreed to
credential_title: names exactly what was certified (prompt writing)
skills_claimed: the four listed abilities, so the claim is specific
assessment_evidence: prompt, draft, check notes, quiz score; kept private
criteria_version: which version of the standard they were judged against
assessor: who or what graded the work, so the pass is accountable
issuer: your name and site, so a stranger knows who vouches
issue_date: when the learner passed
expiry_date: when the claim stops being current
status: valid or revoked, checked live on every lookup
revoked_date_and_reason: audit trail; show the date, keep the reason private
record_hash: fingerprint that reveals any later edit to the record
Verify: valid=details; expired=details+expired date; revoked=notice only
Two fields are easy to miss: criteria_version, which standard they were judged against, and assessor, who graded the work. And if a certificate is revoked, show the date but keep the reason private.
Then the check
Put a verify page on your site where someone types the ID and gets one of three answers: valid, expired or revoked. Revoked matters, because mistakes happen and you need a way to undo one. Keep a short revocation list, and check it on every lookup. Here's that check as a small script, reading a few sample records:
"""Check a certificate ID the way a public verify page would.
Looks the ID up in certs.json, checks the revocation list in
revoked.json (ID and date only; the reason stays private), then the
expiry date.
python3 verify.py PW-7Q4K-M2XD-9HTR
"""
import json
import sys
from datetime import date
certs = json.load(open("certs.json"))
revoked = json.load(open("revoked.json"))
cert_id = sys.argv[1]
cert = certs.get(cert_id)
if cert is None:
print(f"{cert_id} NOT FOUND")
elif cert_id in revoked:
print(f"{cert_id} REVOKED on {revoked[cert_id]}")
elif date.fromisoformat(cert["expires"]) < date.today():
print(f"{cert_id} EXPIRED {cert['name']}, {cert['credential']}, "
f"expired {cert['expires']}")
else:
print(f"{cert_id} VALID {cert['name']}, {cert['credential']}, "
f"issued {cert['issued']}, expires {cert['expires']}")
certs.json, three sample records:
{
"PW-7Q4K-M2XD-9HTR": {
"name": "Jordan Lee", "credential": "Prompt writing",
"issued": "2026-09-02", "expires": "2028-09-02"
},
"PW-B8NE-3WJP-K6VA": {
"name": "Priya Shah", "credential": "Prompt writing",
"issued": "2024-03-14", "expires": "2026-03-14"
},
"PW-H2TC-5RZL-QY4M": {
"name": "Tom Becker", "credential": "Prompt writing",
"issued": "2026-08-20", "expires": "2028-08-20"
}
}
revoked.json, one revoked ID and the date:
{"PW-H2TC-5RZL-QY4M": "2026-09-05"}
Run on the three sample IDs:
PW-7Q4K-M2XD-9HTR VALID Jordan Lee, Prompt writing, issued 2026-09-02, expires 2028-09-02
PW-B8NE-3WJP-K6VA EXPIRED Priya Shah, Prompt writing, expired 2026-03-14
PW-H2TC-5RZL-QY4M REVOKED on 2026-09-05
The revoked one says when, not why.
Deliver the link with the certificate
When someone passes, send them the certificate and the verify link together. The link is the part that matters to a client or an employer. Whatever tools you use to issue certificates, these are the fields and the check to ask for.
The common mistake
Short, counting IDs like CERT-0042. Anyone can guess the next one, or make one up. Use a long random ID, and let the verify page be the only thing that says a certificate is real.
Try these prompts
- Here is what my certificate claims. List the fields each issued certificate's record needs so a stranger could trust it, one per line with why, and say what a verify page should show for valid, expired and revoked.Open in ChatGPT (new tab)Open in Claude (new tab)
- Write the email I send a learner who just passed: their certificate, the verify link, and one line on why the link matters. Plain and warm, no exclamation marks.Open in ChatGPT (new tab)Open in Claude (new tab)
- Here are my certificate records and revocation list. Check them for missing fields, IDs that could be guessed, and any record that would show the wrong answer on the verify page.Open in ChatGPT (new tab)Open in Claude (new tab)
Ask me about this lesson
I'll answer from "Delivering a certificate someone can verify" and the rest of the academy.
I keep this chat with your account, so it's here on any lesson.
Sign in to keep your place and tick off lessons. Reading stays open either way.