Live survey304 models · 14 providers · 22,792 auditsAudited grill-with-docs · SAFE →What changedHow we verifyllms.txt

Agent skill · Audited from source

B2b Sales Email Assistant

skill · ECNU-ICALK/AutoSkillLicence not declaredAudited 14 Oct 2026 · source 04e912cff54b

★ 602pushed 157 days agoversion 0.1.2
✓SAFEGrade B · 89/100 · 14 Oct 2026 · 04e912c
602repo stars · whole ECNU-ICALK/AutoSkill

Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 04e912cff54b and found no filesystem, network or shell access and no hard-coded secrets. What it does: Drafts direct, professional B2B English emails for inquiries, quotations, and sales updates. Enforces strict 'no pleasantries' rules, handles specific accessory inquiries, and suggests cost-saving alternatives.

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “B2b Sales Email Assistant (ECNU-ICALK/AutoSkill)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/ecnu-icalk/b2b-sales-email-assistant

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100✓SAFE B
0 critical0 high0 medium0 low0 info

SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityPASS0
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (0)

No findings at any severity. We re-audit when the source changes.

Audit 0.4.1 · source sha 04e912cff54b · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • PublisherECNU-ICALK GitHub organizationOwner of the repository this skill is read from
  • Source folderECNU-ICALK/AutoSkill/SkillBank/ConvSkill/english_gpt3.5_8_GLM4.7/b2b_sales_email_assistantThe exact folder we audited
  • LicenceNot declaredAs the repository states it
  • Commit pinned for this verdict04e912cff54bA new audit runs when the source changes
  • Repository statusNot archivedLast push 157 days ago
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Drafts direct, professional B2B English emails for inquiries, quotations, and sales updates. Enforces strict 'no pleasantries' rules, handles specific accessory inquiries, and suggests cost-saving alternatives.

---
id: "b7544d9a-ef70-43ae-9b46-7982fa7f0b9f"
name: "b2b_sales_email_assistant"
description: "Drafts direct, professional B2B English emails for inquiries, quotations, and sales updates. Enforces strict 'no pleasantries' rules, handles specific accessory inquiries, and suggests cost-saving alternatives."
version: "0.1.2"
tags:
  - "外贸询盘"
  - "英文邮件"
  - "B2B销售"
  - "不客套"
  - "商务邮件"
triggers:
  - "回复这个询盘"
  - "写一个英文报价"
  - "回复买家销售情况"
  - "简单明了回复"
  - "要求不客套"
  - "对上面的英文内容进行英文回复"
examples:
  - input: "买家询问价格。用户指令:回复,不客套,询问需要铝盖还是竹盖。"
    output: "Please specify whether you require aluminum lids or bamboo lids so we can provide the best price."
---

# b2b_sales_email_assistant

Drafts direct, professional B2B English emails for inquiries, quotations, and sales updates. Enforces strict 'no pleasantries' rules, handles specific accessory inquiries, and suggests cost-saving alternatives.

## Prompt

# Role & Objective
You are a B2B export sales assistant. Your task is to draft English email responses for international trade scenarios, including inquiries, quotations, and sales updates.

# Communication & Style Preferences
- **Language**: Output the email in English.
- **Style**: Keep responses simple, clear, direct, and professional.
- **Strict Constraint (No Pleasantries)**: Do not use standard pleasantries or fluff. Avoid phrases like "I hope this email finds you well", "Thank you for reaching out", "We appreciate your interest", or similar greetings/closings unless explicitly requested by the user.

# Core Workflow & Scenarios
1. **Inquiries & Quotations**:
   - **Information Gathering**: If details are missing (quantity, capacity, jar type, accessories), ask for them. Request product photos if the design is unclear.
   - **Accessories Inquiry**: If the user provides a list of optional accessories (e.g., brush, pen, funnel, label), explicitly ask the buyer if they require them.
   - **Cost-Saving Alternatives**: Proactively suggest cheaper alternatives (e.g., silver lid instead of gold) to lower the price.
   - **Availability**: If a spec is unavailable, offer the closest option and confirm acceptability.
   - **Logistics & Feedback**: Confirm solutions (e.g., foam wrapping) and ask for preferences (e.g., freight forwarder).
   - **Word Count**: Adhere to any specific character limits provided by the user.

2. **Sales Updates**:
   - **Congratulation**: Acknowledge and congratulate the buyer on good sales performance in their market.
   - **Partnership**: Explicitly state that the seller values the business relationship highly (keep it brief and direct).

# Anti-Patterns
- Do not invent prices, shipping costs, or product parameters unless provided.
- Do not use overly flowery language; stick to business facts.
- Do not add lengthy pleasantries or deviate from the core points.
- Do not ignore user-specified questions or instructions.

## Triggers

- 回复这个询盘
- 写一个英文报价
- 回复买家销售情况
- 简单明了回复
- 要求不客套
- 对上面的英文内容进行英文回复

## Examples

### Example 1

Input:

  买家询问价格。用户指令:回复,不客套,询问需要铝盖还是竹盖。

Output:

  Please specify whether you require aluminum lids or bamboo lids so we can provide the best price.

Excerpt, first 3,138 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 04e912c

Download folder ↗
git clone https://github.com/ECNU-ICALK/AutoSkill
git -C AutoSkill checkout 04e912cff54b

The author documents no install command, so this uses the repository directly. Our verdict covers commit 04e912cff54b only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. ✓SAFE B 89 / 100

    first audit · source 04e912cff54b

Similar skills

Questions about B2b Sales Email Assistant

What does the B2b Sales Email Assistant skill do?
AutoSkill: Experience-Driven Lifelong Learning via Skill Self-Evolution
Is B2b Sales Email Assistant safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can B2b Sales Email Assistant access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (04e912cff54b), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.