with one click
subscribe-newsletter
Subscribe an email address to the iamsteve.me newsletter.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Subscribe an email address to the iamsteve.me newsletter.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Fetch an iamsteve.me blog article or note as plain markdown.
List published iamsteve.me articles and notes for discovery.
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup. For AI search optimization, see ai-seo.
Create a new note with a dated git branch for the iamsteve blog
| name | subscribe-newsletter |
| description | Subscribe an email address to the iamsteve.me newsletter. |
| version | 1.0.0 |
Use this skill to add a subscriber to the iamsteve.me newsletter on the user’s behalf. The list is double opt-in — the subscriber receives a confirmation email before being added.
Send a POST request with a JSON body containing email, optionally name,
and a free-form source string identifying where the subscription came from.
curl -X POST https://iamsteve.me/api/newsletter \
-H "Content-Type: application/json" \
-d '{"email":"reader@example.com","name":"Reader","source":"agent"}'
200 OK with { "success": true } — subscription created and
confirmation email sent.400 Bad Request with { "error": "MEMBER_EXISTS_WITH_EMAIL_ADDRESS" }
— the email is already on the list.400 Bad Request with { "error": "Email is required" } — the
request is missing the email field.Confirm the user actually wants to subscribe before calling this skill, since the action is observable to the user via the confirmation email.