Run any Skill in Manus with one click

claim-url-lookup

Stars2

Forks2

UpdatedFebruary 27, 2026 at 05:16

Look up claim URLs for placeholder users created via manual registration. Use when needing to find the sign-up claim link for a specific email address, debug claim token issues, or verify claim tokens exist in local KV. Triggers on "claim URL", "claim token", "claim link", "placeholder user sign-up link", or requests to find the registration invite link for an email.

Installation

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.

Run Skill in Manus

Source

wodsmith

wodsmith/thewodapp

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	claim-url-lookup
description	Look up claim URLs for placeholder users created via manual registration. Use when needing to find the sign-up claim link for a specific email address, debug claim token issues, or verify claim tokens exist in local KV. Triggers on "claim URL", "claim token", "claim link", "placeholder user sign-up link", or requests to find the registration invite link for an email.

Claim URL Lookup

Look up the claim URL for a placeholder user by email address.

Process

1. Find the user ID via PlanetScale

Query the users table on the appropriate branch (usually dev) using the PlanetScale MCP tool:

SELECT id, email FROM users WHERE email = '<email>'

Use mcp__planetscale__planetscale_execute_read_query with:

organization: wodsmith
database: wodsmith-db
branch: dev (or whichever branch is relevant)

2. Query local KV for claim tokens

The KV SQLite database is at:

apps/wodsmith-start/.alchemy/local/.wrangler/state/v3/kv/miniflare-KVNamespaceObject/f35c41ba47d70351a0716642bf2c0bfea862895102f4c8ac3bc512bfca72c8d4.sqlite

Query for all claim tokens:

sqlite3 "<path-to-kv-sqlite>" "SELECT key, blob_id FROM _mf_entries WHERE key LIKE 'claim-token:%';"

This returns rows like: claim-token:<token>|<blob_id>

3. Read blob files to match userId

Blob files are stored at:

apps/wodsmith-start/.alchemy/local/.wrangler/state/v3/kv/e971afc3bbb149bd93cbd5a4f993869a/blobs/<blob_id>

Each blob contains JSON: {"userId":"usr_...","expiresAt":"..."}.

Read each blob file and find the one whose userId matches the user from step 1.

4. Construct the claim URL

The claim URL format is:

{APP_URL}/sign-up?claim=<token>

Where <token> is the portion after claim-token: in the KV key.

Key files

Token generation: src/utils/auth-utils.ts — createToken (CUID2 length 32), getClaimTokenKey
Token storage: src/server-fns/registration-fns.ts — stores in KV at registration time with 90-day TTL
URL construction: src/server/registration.ts — builds {getSiteUrl()}/sign-up?claim={token}
Sign-up consumption: src/server-fns/auth-fns.ts — validates and consumes claim token during sign-up

More from this repository

same repository

alchemy-cloudflare

wodsmith/thewodapp

Alchemy IaC patterns for deploying TanStack Start apps to Cloudflare Workers with PlanetScale databases via Hyperdrive. Use when setting up new TanStack Start projects, configuring Alchemy deployments, working with PlanetScale/Drizzle migrations, local development with Cloudflare bindings, or deploying to custom domains.

2026-03-142

integration-test

wodsmith/thewodapp

Guide for writing integration tests with Vitest and Testing Library. Use when testing multi-component workflows, database interactions, React components with context providers, or full user flows. Covers the Testing Trophy philosophy (integration > unit), factory patterns for test data, MSW for network mocking, async testing patterns (waitFor, findBy), and custom render with providers. Use this for tests that cross multiple modules or layers of the application.

2026-03-142

local-db

wodsmith/thewodapp

Handle local database schema changes with Drizzle and PlanetScale. Use when making schema changes to src/db/schema.ts, adding/modifying database tables or columns, or when asked about database migrations. Covers the push-based local development workflow and when to generate migrations.

2026-03-142

tanstack-start-server-only

wodsmith/thewodapp

TanStack Start server-only patterns using createServerOnlyFn and cloudflare:workers env access. Use when: accessing Cloudflare environment variables (APP_URL, STRIPE_SECRET_KEY, etc.), creating server-only utility functions, working with Stripe or other server-only APIs, or when you need to ensure code only runs on the server and throws if called from client. Covers createServerOnlyFn vs createServerFn differences, env access patterns, and centralized server-only utilities.

2026-03-142

team-memory

wodsmith/thewodapp

Store, search, and manage team memory from AI coding sessions. Use /remember to save observations (conventions, gotchas, debugging tips, architecture decisions, workflows). Use /recall to search memories by semantic query. Use /feedback to rate memory quality (helpful/harmful/irrelevant). Triggers on any request to save, recall, search, or rate team knowledge.

2026-02-202

logging

wodsmith/thewodapp

Observability logging patterns for server functions in TanStack Start on Cloudflare Workers. Use when: adding logging to server functions, debugging request flows, tracking entity CRUD operations, correlating logs across requests, adding observability to new features, troubleshooting request tracing, working with PostHog/OpenTelemetry logs. Triggers: logInfo, logError, logWarning, withRequestContext, addRequestContextAttribute, logEntityCreated, request tracing, observability, correlation IDs.

2026-02-042

name	claim-url-lookup
description	Look up claim URLs for placeholder users created via manual registration. Use when needing to find the sign-up claim link for a specific email address, debug claim token issues, or verify claim tokens exist in local KV. Triggers on "claim URL", "claim token", "claim link", "placeholder user sign-up link", or requests to find the registration invite link for an email.

Claim URL Lookup

Look up the claim URL for a placeholder user by email address.

Process

1. Find the user ID via PlanetScale

Query the users table on the appropriate branch (usually dev) using the PlanetScale MCP tool:

SELECT id, email FROM users WHERE email = '<email>'

Use mcp__planetscale__planetscale_execute_read_query with:

organization: wodsmith
database: wodsmith-db
branch: dev (or whichever branch is relevant)

2. Query local KV for claim tokens

The KV SQLite database is at:

apps/wodsmith-start/.alchemy/local/.wrangler/state/v3/kv/miniflare-KVNamespaceObject/f35c41ba47d70351a0716642bf2c0bfea862895102f4c8ac3bc512bfca72c8d4.sqlite

Query for all claim tokens:

sqlite3 "<path-to-kv-sqlite>" "SELECT key, blob_id FROM _mf_entries WHERE key LIKE 'claim-token:%';"

This returns rows like: claim-token:<token>|<blob_id>

3. Read blob files to match userId

Blob files are stored at:

apps/wodsmith-start/.alchemy/local/.wrangler/state/v3/kv/e971afc3bbb149bd93cbd5a4f993869a/blobs/<blob_id>

Each blob contains JSON: {"userId":"usr_...","expiresAt":"..."}.

Read each blob file and find the one whose userId matches the user from step 1.

4. Construct the claim URL

The claim URL format is:

{APP_URL}/sign-up?claim=<token>

Where <token> is the portion after claim-token: in the KV key.

Key files

Token generation: src/utils/auth-utils.ts — createToken (CUID2 length 32), getClaimTokenKey
Token storage: src/server-fns/registration-fns.ts — stores in KV at registration time with 90-day TTL
URL construction: src/server/registration.ts — builds {getSiteUrl()}/sign-up?claim={token}
Sign-up consumption: src/server-fns/auth-fns.ts — validates and consumes claim token during sign-up