qq-email▌
shadowcz007/skills · updated Jun 3, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
用户要使用 QQ 邮箱 发邮件、收邮件、查邮件、代发邮件或配置 QQ 邮箱时使用本 skill。
何时使用
用户要使用 QQ 邮箱 发邮件、收邮件、查邮件、代发邮件或配置 QQ 邮箱时使用本 skill。
QQ 邮箱收发
面向 QQ 邮箱:通过 IMAP 收取邮件、SMTP 发送邮件。账号与授权码仅从环境变量读取,不在代码或配置中硬编码。
凭证(环境变量)
| 变量 | 说明 |
|---|---|
| QQ_EMAIL_ACCOUNT | QQ 邮箱账号(完整地址,如 [email protected]) |
| QQ_EMAIL_AUTH_CODE | QQ 邮箱授权码(在 QQ 邮箱「设置 → 账户」中开启 IMAP/SMTP 后生成,非 QQ 登录密码;勿提交到仓库) |
脚本会校验,缺失时报错并退出;请勿在终端用 echo 等方式检查,以免泄露授权码。
QQ 邮箱服务器
- IMAP:
imap.qq.com,端口 993(SSL) - SMTP:
smtp.qq.com,端口 465(SSL)
脚本
| 脚本 | 作用 |
|---|---|
scripts/send.js |
从环境变量读凭证,用 nodemailer 连接 QQ 邮箱 SMTP 发信;支持收件人、主题、正文(CLI 参数)。 |
scripts/receive.js |
从环境变量读凭证,用 imap + mailparser 连接 QQ 邮箱 IMAP 收信;支持「最近 N 条」或「最近 N 天」,输出主题、发件人、日期、UID、正文摘要。 |
scripts/get-body.js |
按 UID 获取指定邮件的完整正文(纯文本,无摘要截断)。必须传入 --uid(值为收信列表中的 UID)。 |
发信流程
在 skill 根目录下执行(需已 npm install):
node scripts/send.js <收件人> <主题> <正文>
正文若含空格,请用引号包裹;或只传收件人和主题,正文从 stdin 读入(见脚本 --stdin)。
示例:
node scripts/send.js "[email protected]" "测试主题" "邮件正文内容"
收信流程
# 收取最近 10 条(默认)
node scripts/receive.js
# 收取最近 N 条
node scripts/receive.js --limit 20
# 收取最近 N 天的邮件(如 7、30、90)
node scripts/receive.js --days 7
输出:每封邮件的主题、发件人、日期、UID(收件箱内唯一标识,用于按 UID 取正文)、正文摘要(前约 200 字),便于查看。
获取邮件正文
需要某封邮件的完整正文时,使用 get-body.js,传入收信列表中该邮件的 UID:
node scripts/get-body.js --uid 12345
未传 --uid 时会提示并退出。UID 与收件箱绑定,邮件移动或删除后可能失效。
- 输出:完整正文输出到 stdout(纯文本;若原邮件仅有 HTML,会做简单去标签后输出)。可重定向到文件或管道给其它命令。
- 环境变量:与收信相同,需
QQ_EMAIL_ACCOUNT、QQ_EMAIL_AUTH_CODE。
可选能力(与「收取选项」对应)
- 收取时间范围:通过
--days 7/--days 30/--days 90使用 IMAP SINCE 条件。 - 收取「我的文件夹」:当前脚本默认 INBOX;若需自定义文件夹,可扩展脚本中的
openBox(如openBox('我的文件夹', ...))。
安全提醒
- QQ 邮箱授权码需在「设置 → 账户」中开启 IMAP/SMTP 服务后生成,与 QQ 登录密码不同,不要混淆。
- 不要将
QQ_EMAIL_ACCOUNT、QQ_EMAIL_AUTH_CODE的真实值写入代码或提交到仓库;仅通过环境变量或本地.env配置。
How to use qq-email on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add qq-email
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches qq-email from GitHub repository shadowcz007/skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate qq-email. Access the skill through slash commands (e.g., /qq-email) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★56 reviews- ★★★★★Aisha Abbas· Dec 24, 2024
Keeps context tight: qq-email is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Amina Abbas· Dec 16, 2024
qq-email is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Evelyn Diallo· Dec 16, 2024
qq-email reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Yusuf Bhatia· Dec 8, 2024
I recommend qq-email for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Dhruvi Jain· Dec 4, 2024
Useful defaults in qq-email — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Amina Ghosh· Nov 27, 2024
Keeps context tight: qq-email is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Oshnikdeep· Nov 23, 2024
qq-email is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kabir Taylor· Nov 23, 2024
Registry listing for qq-email matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kabir Shah· Nov 23, 2024
Keeps context tight: qq-email is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Yuki Rahman· Nov 15, 2024
I recommend qq-email for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 56