ledgestone-alias-generator

Generate unique @ledgestonehome.com email aliases and route incoming mail via ledgestone-email-router.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ammonfife/sakima.co --skill ledgestone-alias-generator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ledgestone-alias-generator
Source: https://github.com/ammonfife/sakima.co/tree/main/.claude/skills/ledgestone-alias
Command: npx skills add https://github.com/ammonfife/sakima.co --skill ledgestone-alias-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Turso, ledgestone-email-router, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation, persistence, and routing of unique email aliases for signups and login recovery processes, eliminating the need for manual email management.

Core Features & Use Cases

  • Unique Alias Generation: Generates unique aliases using a service-aware format, ensuring each alias is globally unique and easily recognizable.
  • Service-Aware Alias Routing: Routes emails received at @ledgestonehome.com to the correct service-specific agent or handler.
  • Integration with Email Router: Integrates with the ledgestone-email-router to deliver incoming mail to the right downstream workflow.

Quick Start

Generate a new alias for a service using the ledgestone-alias-generator skill.

Frequently Asked Questions about ledgestone-alias-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate email alias generation for new signups and login recovery?

Email alias generation can be automated by using service-aware naming conventions to create unique identifiers and route incoming mail. This eliminates manual email management by persisting aliases and directing them to appropriate service-specific handlers.

What is service-aware email routing and how does it work with alias generation?

Service-aware email routing directs incoming messages to the correct service-specific agent based on the generated alias format. It works by integrating with an email router to deliver mail to the right downstream workflow automatically.

Do I need Turso to handle unique email alias persistence?

Yes, Turso is required to persist generated email aliases. It stores the unique identifiers created during the alias generation process, ensuring each alias remains globally unique and available for future email routing.

Can I use this email automation approach without an integrated email router?

No, an integrated email router is required to route incoming mail to appropriate handlers. The alias generator creates unique identifiers, but the email router is necessary to deliver incoming messages to the correct downstream workflow.

What's the best way to ensure generated email aliases are globally unique?

To ensure generated email aliases are globally unique, use a service-aware format during alias generation and persist them in a Turso database. This approach guarantees each alias is unique and easily recognizable for routing.

Are there limitations when using service-specific naming conventions for email routing?

Service-specific naming conventions require both Turso for persistence and an integrated email router to function properly. Without these dependencies, the generated aliases cannot be persisted or routed to the correct downstream workflow.