install
Skill0 starsChanged 5 months agoMITView on GitHub
Use when adding Lettr to a project for the first time. Detects the stack, installs the right SDK or framework integration, configures LETTR_API_KEY, verifies a sending domain, and optionally runs a test send.
- Reads credentials
22 other projects use a version of this.
Adopted by
Most recently taken up by
- Dariusplayer09/adaptive-skillstheir own version, first seen Nov 8, 2026
- kkrafft1999/snotratheir own version, first seen Nov 6, 2026
- tykimos/agent-native-agenttheir own version, first seen Nov 6, 2026
- crocotaste/crocotaste-plugintheir own version, first seen Nov 1, 2026
- BrainWeb/payload-mcp-oauththeir own version, first seen Nov 1, 2026
- grace-method/grace-plugintheir own version, first seen Oct 25, 2026
Used with
Projects with it also use update and release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- kubeshark/kubeshark★ 12ksame name
- PrimeIntellect-ai/prime-rl★ 2.2ksame name
- tykimos/agent-native-agent★ 130same name
- htlin222/openevidence-mcp★ 78same name
- jeremylongshore/claude-code-slack-channel★ 43same name
- BrainWeb/payload-mcp-oauth★ 9same name
- kkrafft1999/snotra★ 6same name
- WeDataLab-AI-Lab/cctrace★ 5same name
- gpambrozio/Gallager★ 4same name
- Pierry/harness-kit★ 4same name
12 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 0 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Use ../_shared/detect-stack.md to resolve <lang>.
- Very specific: line 16
Read ../_generated/sdk/<lang>/installation.md and follow it exactly — install command, client construction, where the key goes.
- Very specific: line 22
Ask the user for LETTR_API_KEY if it isn't already in the environment or .env.
- Very specific: line 30
Create it (POST /domains with domain).
- Very specific: line 32
When they confirm, run POST /domains/{domain}/verify and re-check.
- Very specific: line 44
No per-provider migration playbook ships here.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Install Lettr
Get Lettr into the user's project: add the dependency, configure the key, make sure there's a verified domain to send from, and leave them with a working first send call.
1. Detect the stack
Use ../_shared/detect-stack.md to resolve <lang>. If nothing matches, follow its fallback (raw HTTP or SMTP relay) — there's no SDK to install in that case.
2. Install the SDK
Read ../_generated/sdk/<lang>/installation.md and follow it exactly — install command, client construction, where the key goes. It's generated from the official SDK docs, so the package name and API surface are current; don't install from memory.
For Laravel, prefer the package's own init command if the reference shows one (it writes config + env in one step).
3. Configure the API key
Ask the user for LETTR_API_KEY if it isn't already in the environment or .env. Keys start with lttr_. Put it in .env (never hardcoded), and confirm .env is gitignored.
Validate it: GET /auth/check returns the team ID on success. On 401, the key is wrong or revoked — have the user recreate it at app.lettr.com/settings/api-keys.
4. Make sure there's a verified sending domain
Sending from an unverified domain returns 400 with error_code: unconfigured_domain, and this is the single most common first-send failure. Check GET /domains. If the user's intended from domain isn't verified:
- Create it (
POST /domainswithdomain). The response carries the DNS records to add (CNAME / DKIM / return-path). - Hand those records to the user to apply at their DNS provider — this skill does not touch their registrar.
- When they confirm, run
POST /domains/{domain}/verifyand re-check.
5. Offer a test send
Ask whether to send a real test (it sends an actual email and uses quota). If yes, send a minimal email with a verified from to an address the user controls, and confirm the response includes a request_id. For composing anything beyond a hello-world, hand off to the sending skill.
6. Report what changed
Summarize: dependency added, files edited, env vars expected, domain status, and where the first real send call should go.
Replacing an existing email provider
No per-provider migration playbook ships here. Run this install alongside the old code, then read the existing send calls and rewrite them using the sending skill + the generated SDK reference. Remove the old dependency last, after a successful send.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.