What does this skill do, and when should you use it?
This skill guides AI assistants in integrating email sending into PinMe Worker (TypeScript) projects. It defines the Worker environment variables (API_KEY and optional BASE_URL) and instructs how to call PinMe's send_email API (POST /api/v4/send_email). The skill includes request and response formats, error handling patterns, and complete code examples, including a reusable sendEmail function and a unified error handler. It is for developers who need to send verification codes or notifications from their PinMe projects.
Reads the SKILL.md file in the Worker project, provides environment variable definitions and explanations (API_KEY, BASE_URL), shows how to make a POST request to {BASE_URL}/api/v4/send_email with the X-API-Key header, and provides TypeScript code examples. It guides AI to generate correct Worker TypeScript code, including error handling logic and a unified API invocation wrapper function.
- Developers needing to implement email sending (e.g., verification codes) in a PinMe Worker.
- AI assistants generating Worker TypeScript code that calls the PinMe email API.
- Integrating email notifications (e.g., user registration, password reset) into PinMe projects.
- Handling API errors (401, 400, 500) and returning appropriate responses in Worker code.
How do you install this skill?
- The skill depends on external services of PinMe platform (https://pinme.cloud), which may be inaccessible from mainland China; network reachability should be considered.
- The skill does not specify user confirmation mechanism; for external side-effects like sending emails, explicit user consent is recommended.
- API_KEY is the sole credential; ensure secure storage to prevent leakage.
- The skill lacks troubleshooting and known limitations; users may encounter uncovered issues in practice.
- Network access
Ensure the skill file is located at skills/pinme-email/SKILL.md in the repository. For PinMe projects, install the full skill collection via npx skills add glitternetwork/pinme (note: this installs the entire repository, which bundles 7 skills; this email skill is one of them).
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/glitternetwork/pinme.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/skills/pinme-email" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
In a PinMe Worker project, describe the requirement to the AI assistant, e.g., 'Please integrate email sending into my Worker using PinMe's send_email API.' The AI will generate code based on the skill. The user must ensure the API_KEY is automatically injected (no manual config), and optionally set the BASE_URL environment variable (defaults to https://pinme.cloud).
What are this skill's strengths and limitations?
- Zero configuration: API_KEY is auto-injected, no manual setup.
- Provides complete code examples, including error handling and unified API call functions.
- Clear request/response formats and error codes.
- Supports BASE_URL override for testing environments.
- Specific to the PinMe platform; not portable.
- No test cases or example projects mentioned, possibly lacking validation.
- Relies on external network calls to PinMe cloud services.
- Only applicable to Worker TypeScript projects; not for other languages or frameworks.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| PinMe Worker Email Integration Skill this page | 52 · Use with care | ★ 3.7k | 3mo ago | MIT |
| PinMe Worker Auth API Integration | 59 · Recommended | ★ 3.7k | 3mo ago | MIT |
| Codex CLI Builder ✓ OpenAI · Official | 55 · Use with care | ★ 28k | 3mo ago | — |
| MCP Server Builder Guide | 50 · Use with care | ★ 3k | 7mo ago | MIT |
| MCP Server Development Guide ✓ Microsoft · Official | 49 · Use with care | ★ 2.7k | 3mo ago | MIT |
How did FollowSkills review this skill?
Evidence shows the skill only guides calling the email API, clearly states API_KEY is the only credential, and all requests are over HTTPS. No sensitive data upload or destructive operations. However, it lacks explicit user confirmation or least-privilege implementation details, and depends on external service (PinMe platform) availability and security, hence deduction.
Code example is self-consistent, error handling pattern is clear including network, HTTP, and business errors. But lacks tests for edge inputs (e.g., empty strings, invalid emails), depends on external API stability, and static review cannot verify actual execution, hence deduction.
Skill objective is clear (integrate email sending in PinMe Worker), trigger conditions are well described. However, it does not state non-fit scenarios, and default dependency on overseas service (pinme.cloud) may be unreachable in some networks, limiting usability for Chinese users, hence deduction.
Documentation is well-structured with environment variables, API description, request/response formats, error handling, example code. But lacks versioning, changelog, known limitations, troubleshooting, and maintenance responsibility, hence deduction.
Core task (generate code to call email API) is well achieved, output is directly usable or requires minor adjustment. But no verification of actual usage, and functionality is relatively simple, marginal value limited, hence deduction.
No author claims or marketing content, provides complete code examples and test files, but tests mainly target CLI, not this skill. No third-party execution evidence, static review cannot independently reproduce, hence deduction.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →