---
name: "error-friendly"
description: "优化代码错误提示，让普通用户能看懂问题和解决方法。Invoke when there's a technical error message that needs to be made user-friendly."
title: error-friendly
canonical_url: https://skilld.dev/gh/steelan9199/wechat-publisher/error-friendly
last_updated: 2026-10-07T07:20:50.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install steelan9199/wechat-publisher/error-friendly`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/error-friendly`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/steelan9199/wechat-publisher/error-friendly) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/error-friendly`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/error-friendly --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/error-friendly --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Error-Friendly

优化代码中的错误提示，使普通用户（非技术人员）能够：
1. 看懂发生了什么问题
2. 知道应该怎么解决

## 原则

- **说人话**：避免技术术语（如 param.json、content 字段、object_string 等）
- **给出行动指引**：告诉用户具体该做什么
- **保持简洁**：一行能说清的不要用两句
- **语气友好**：用「请」「比如」等温和表达

## 使用场景

当你发现代码中有 `console.error` 或 `throw new Error` 时，检查是否：
- 包含技术名词（文件名、变量名、API 名）
- 没有告诉用户下一步该做什么
- 语气过于冰冷

## 修改示例

❌ 修改前（技术人员视角）：
```
console.error("COZE_API_KEY 环境变量未设置");
```

✅ 修改后（用户视角）：
```
❌ 发送失败：缺少 API Key
   请确保已在 .env 文件中配置 COZE_API_KEY
   获取方式：https://coze.cn/settings
```

## 输出格式

修改后的错误提示应包含：
1. **emoji 图标**：让错误更醒目（❌ 错误、⚠️ 警告、💡 提示）
2. **简短说明**：一句话说清问题
3. **解决建议**：告诉用户具体怎么做

如需更详细指引，可添加「更多信息」或「示例」。