email-163-com SKILL.md skillA
email-163-com from qualcomm/qai-appbuilder is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qualcomm/qai-appbuilder/email-163-com@git:20260822.fbacac1Pins git:20260822.fbacac1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qualcomm/qai-appbuilder
- Path
tools/qaiappbuilder/skills/email-163-com/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260822.fbacac1, committed Aug 22, 2026
- Size
- 1,402 bytes
- Repository stars
- 252
- License
- a license file GitHub does not identify
163 email tool for sending, reading, searching, and replying to emails via 163.com (NetEase Mail).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 163 Mail
## CRITICAL: You MUST call the exec tool
When this skill is active, you MUST immediately call the exec tool based on the user's request. Do NOT output code blocks or describe steps.
## 1. Read Emails
Read the latest 5 emails:
<tool_call>
{"name":"exec","arguments":{"command":"python ${SKILL_DIR}/main.py read"}}
</tool_call>
Read a specific number of emails:
<tool_call>
{"name":"exec","arguments":{"command":"python ${SKILL_DIR}/main.py read --count 10"}}
</tool_call>
Read a full email (including body):
<tool_call>
{"name":"exec","arguments":{"command":"python ${SKILL_DIR}/main.py read --id 123"}}
</tool_call>
## 2. Send Email
Simple send:
<tool_call>
{"name":"exec","arguments":{"command":"python ${SKILL_DIR}/main.py send --to friend@example.com --subject \"Hello\" --body \"Hi!\""}}
</tool_call>
## 3. Reply to Email
Reply to a specific email (use the original sender's address as recipient, prefix subject with "Re:"):
<tool_call>
{"name":"exec","arguments":{"command":"python ${SKILL_DIR}/main.py send --to <sender_email_address> --subject \"Re: <original_subject>\" --body \"<reply_body>\""}}
</tool_call>Read the whole file at its exact version.
How to install
mdr add qualcomm/qai-appbuilder/email-163-com@sha256:ecb485529db116c6The line at the top of this page pins the label git:20260822.fbacac1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_3t6im7ho4bldp3ex)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 22, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1402 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qualcomm/qai-appbuilder · 252 stars · license a license file GitHub does not identify · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3t6im7ho4bldp3ex GET https://markdownregistry.com/api/v1/resolve?ref=qualcomm/qai-appbuilder/email-163-com GET https://markdownregistry.com/api/v1/blob/ecb485529db116c66b7dba3624a565cc04e2bed15e038d1eeec2a4061981f77b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.