tuzi-post-to-wechat
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChinesePost to WeChat Official Account
发布到微信公众号
Language
语言
Match user's language: Respond in the same language the user uses. If user writes in Chinese, respond in Chinese. If user writes in English, respond in English.
匹配用户语言:使用用户输入的语言回复。如果用户用中文提问就用中文回复,如果用户用英文提问就用英文回复。
Script Directory
脚本目录
Agent Execution: Determine this SKILL.md directory as , then use .
SKILL_DIR${SKILL_DIR}/scripts/<name>.ts| Script | Purpose |
|---|---|
| Image-text posts (图文) |
| Article posting via browser (文章) |
| Article posting via API (文章) |
| Markdown → WeChat-ready HTML with image placeholders |
| Verify environment & permissions |
Agent执行:将此SKILL.md所在目录定为,后续使用路径。
SKILL_DIR${SKILL_DIR}/scripts/<name>.ts| 脚本 | 用途 |
|---|---|
| 图文消息发布 |
| 通过浏览器发布文章 |
| 通过API发布文章 |
| Markdown转换为带图片占位符的微信兼容HTML |
| 校验环境与权限 |
Preferences (EXTEND.md)
偏好配置(EXTEND.md)
Use Bash to check EXTEND.md existence (priority order):
bash
undefined使用Bash检查EXTEND.md是否存在(优先级顺序):
bash
undefinedCheck project-level first
先检查项目级别
test -f .tuzi-skills/tuzi-post-to-wechat/EXTEND.md && echo "project"
test -f .tuzi-skills/tuzi-post-to-wechat/EXTEND.md && echo "project"
Then user-level (cross-platform: $HOME works on macOS/Linux/WSL)
再检查用户级别(跨平台:$HOME在macOS/Linux/WSL都可用)
test -f "$HOME/.tuzi-skills/tuzi-post-to-wechat/EXTEND.md" && echo "user"
┌────────────────────────────────────────────────────────┬───────────────────┐
│ Path │ Location │
├────────────────────────────────────────────────────────┼───────────────────┤
│ .tuzi-skills/tuzi-post-to-wechat/EXTEND.md │ Project directory │
├────────────────────────────────────────────────────────┼───────────────────┤
│ $HOME/.tuzi-skills/tuzi-post-to-wechat/EXTEND.md │ User home │
└────────────────────────────────────────────────────────┴───────────────────┘
┌───────────┬───────────────────────────────────────────────────────────────────────────┐
│ Result │ Action │
├───────────┼───────────────────────────────────────────────────────────────────────────┤
│ Found │ Read, parse, apply settings │
├───────────┼───────────────────────────────────────────────────────────────────────────┤
│ Not found │ Run first-time setup ([references/config/first-time-setup.md](references/config/first-time-setup.md)) → Save → Continue │
└───────────┴───────────────────────────────────────────────────────────────────────────┘
**EXTEND.md Supports**: Default theme | Default color | Default publishing method (api/browser) | Default author | Default open-comment switch | Default fans-only-comment switch | Chrome profile path
First-time setup: [references/config/first-time-setup.md](references/config/first-time-setup.md)
**Minimum supported keys** (case-insensitive, accept `1/0` or `true/false`):
| Key | Default | Mapping |
|-----|---------|---------|
| `default_author` | empty | Fallback for `author` when CLI/frontmatter not provided |
| `need_open_comment` | `1` | `articles[].need_open_comment` in `draft/add` request |
| `only_fans_can_comment` | `0` | `articles[].only_fans_can_comment` in `draft/add` request |
**Recommended EXTEND.md example**:
```md
default_theme: default
default_color: blue
default_publish_method: api
default_author: 宝玉
need_open_comment: 1
only_fans_can_comment: 0
chrome_profile_path: /path/to/chrome/profileTheme options: default, grace, simple, modern
Color presets: blue, green, vermilion, yellow, purple, sky, rose, olive, black, gray, pink, red, orange (or hex value)
Value priority:
- CLI arguments
- Frontmatter
- EXTEND.md
- Skill defaults
test -f "$HOME/.tuzi-skills/tuzi-post-to-wechat/EXTEND.md" && echo "user"
┌────────────────────────────────────────────────────────┬───────────────────┐
│ 路径 │ 位置 │
├────────────────────────────────────────────────────────┼───────────────────┤
│ .tuzi-skills/tuzi-post-to-wechat/EXTEND.md │ 项目目录 │
├────────────────────────────────────────────────────────┼───────────────────┤
│ $HOME/.tuzi-skills/tuzi-post-to-wechat/EXTEND.md │ 用户根目录 │
└────────────────────────────────────────────────────────┴───────────────────┘
┌───────────┬───────────────────────────────────────────────────────────────────────────┐
│ 结果 │ 操作 │
├───────────┼───────────────────────────────────────────────────────────────────────────┤
│ 找到文件 │ 读取、解析并应用配置 │
├───────────┼───────────────────────────────────────────────────────────────────────────┤
│ 未找到 │ 运行首次设置流程 ([references/config/first-time-setup.md](references/config/first-time-setup.md)) → 保存配置 → 继续执行 │
└───────────┴───────────────────────────────────────────────────────────────────────────┘
**EXTEND.md支持配置项**:默认主题 | 默认颜色 | 默认发布方式 (api/browser) | 默认作者 | 默认开启评论开关 | 默认仅粉丝评论开关 | Chrome配置文件路径
首次设置指引:[references/config/first-time-setup.md](references/config/first-time-setup.md)
**最低支持配置键**(不区分大小写,接受`1/0`或`true/false`取值):
| 键 | 默认值 | 映射规则 |
|-----|---------|---------|
| `default_author` | 空 | 当CLI/前置元数据未提供作者时的兜底值 |
| `need_open_comment` | `1` | 对应`draft/add`请求中的`articles[].need_open_comment`字段 |
| `only_fans_can_comment` | `0` | 对应`draft/add`请求中的`articles[].only_fans_can_comment`字段 |
**推荐EXTEND.md示例**:
```md
default_theme: default
default_color: blue
default_publish_method: api
default_author: 宝玉
need_open_comment: 1
only_fans_can_comment: 0
chrome_profile_path: /path/to/chrome/profile主题选项:default, grace, simple, modern
颜色预设:blue, green, vermilion, yellow, purple, sky, rose, olive, black, gray, pink, red, orange(也支持十六进制颜色值)
取值优先级:
- CLI参数
- 前置元数据(Frontmatter)
- EXTEND.md配置
- 技能默认值
Pre-flight Check (Optional)
预检查(可选)
Before first use, suggest running the environment check. User can skip if they prefer.
bash
npx -y bun ${SKILL_DIR}/scripts/check-permissions.tsChecks: Chrome, profile isolation, Bun, Accessibility, clipboard, paste keystroke, API credentials, Chrome conflicts.
If any check fails, provide fix guidance per item:
| Check | Fix |
|---|---|
| Chrome | Install Chrome or set |
| Profile dir | Ensure |
| Bun runtime | |
| Accessibility (macOS) | System Settings → Privacy & Security → Accessibility → enable terminal app |
| Clipboard copy | Ensure Swift/AppKit available (macOS Xcode CLI tools: |
| Paste keystroke (macOS) | Same as Accessibility fix above |
| Paste keystroke (Linux) | Install |
| API credentials | Follow guided setup in Step 2, or manually set in |
首次使用前,建议先运行环境检查,用户也可选择跳过。
bash
npx -y bun ${SKILL_DIR}/scripts/check-permissions.ts检查内容:Chrome、配置文件隔离、Bun、无障碍权限、剪贴板、粘贴快捷键、API凭证、Chrome冲突。
如果任何检查未通过,按以下对应项提供修复指引:
| 检查项 | 修复方案 |
|---|---|
| Chrome | 安装Chrome,或设置 |
| 配置文件目录 | 确保 |
| Bun运行时 | 执行 |
| 无障碍权限(macOS) | 系统设置 → 隐私与安全性 → 无障碍 → 启用对应终端应用的权限 |
| 剪贴板复制权限 | 确保Swift/AppKit可用(macOS安装Xcode命令行工具: |
| 粘贴快捷键(macOS) | 与上述无障碍权限修复方案一致 |
| 粘贴快捷键(Linux) | 安装 |
| API凭证 | 按照第2步的引导设置,或手动写入 |
Image-Text Posting (图文)
图文消息发布
For short posts with multiple images (up to 9):
bash
npx -y bun ${SKILL_DIR}/scripts/wechat-browser.ts --markdown article.md --images ./images/
npx -y bun ${SKILL_DIR}/scripts/wechat-browser.ts --title "标题" --content "内容" --image img.png --submitSee references/image-text-posting.md for details.
适用于带多张图片的短内容(最多9张):
bash
npx -y bun ${SKILL_DIR}/scripts/wechat-browser.ts --markdown article.md --images ./images/
npx -y bun ${SKILL_DIR}/scripts/wechat-browser.ts --title "标题" --content "内容" --image img.png --submit查看references/image-text-posting.md了解详情。
Article Posting Workflow (文章)
文章发布工作流
Copy this checklist and check off items as you complete them:
Publishing Progress:
- [ ] Step 0: Load preferences (EXTEND.md)
- [ ] Step 1: Determine input type
- [ ] Step 2: Select method and configure credentials
- [ ] Step 3: Resolve theme/color and validate metadata
- [ ] Step 4: Publish to WeChat
- [ ] Step 5: Report completion复制以下检查清单,完成对应步骤后标记:
发布进度:
- [ ] 步骤0:加载偏好配置(EXTEND.md)
- [ ] 步骤1:确定输入类型
- [ ] 步骤2:选择发布方式并配置凭证
- [ ] 步骤3:确认主题/颜色并校验元数据
- [ ] 步骤4:发布到微信公众号
- [ ] 步骤5:上报完成结果Step 0: Load Preferences
步骤0:加载偏好配置
Check and load EXTEND.md settings (see Preferences section above).
CRITICAL: If not found, complete first-time setup BEFORE any other steps or questions.
Resolve and store these defaults for later steps:
- (default
default_theme)default - (omit if not set — theme default applies)
default_color default_author- (default
need_open_comment)1 - (default
only_fans_can_comment)0
检查并加载EXTEND.md配置(参考上文偏好配置章节)。
重要提示:如果未找到配置文件,必须先完成首次设置流程,再执行后续步骤或回答用户问题。
解析并存储以下默认值供后续步骤使用:
- (默认值
default_theme)default - (未设置则省略,使用主题默认颜色)
default_color default_author- (默认值
need_open_comment)1 - (默认值
only_fans_can_comment)0
Step 1: Determine Input Type
步骤1:确定输入类型
| Input Type | Detection | Action |
|---|---|---|
| HTML file | Path ends with | Skip to Step 3 |
| Markdown file | Path ends with | Continue to Step 2 |
| Plain text | Not a file path, or file doesn't exist | Save to markdown, continue to Step 2 |
Plain Text Handling:
- Generate slug from content (first 2-4 meaningful words, kebab-case)
- Create directory and save file:
bash
mkdir -p "$(pwd)/post-to-wechat/$(date +%Y-%m-%d)"| 输入类型 | 判定规则 | 操作 |
|---|---|---|
| HTML文件 | 路径以 | 直接跳转到步骤3 |
| Markdown文件 | 路径以 | 继续执行步骤2 |
| 纯文本 | 不是文件路径,或对应文件不存在 | 保存为Markdown文件,继续执行步骤2 |
纯文本处理规则:
- 从内容生成slug(取前2-4个有意义的单词,转为kebab-case格式)
- 创建目录并保存文件:
bash
mkdir -p "$(pwd)/post-to-wechat/$(date +%Y-%m-%d)"Save content to: post-to-wechat/yyyy-MM-dd/[slug].md
保存内容到:post-to-wechat/yyyy-MM-dd/[slug].md
3. Continue processing as markdown file
**Slug Examples**:
- "Understanding AI Models" → `understanding-ai-models`
- "人工智能的未来" → `ai-future` (translate to English for slug)
3. 作为Markdown文件继续后续处理
**Slug示例**:
- "Understanding AI Models" → `understanding-ai-models`
- "人工智能的未来" → `ai-future`(slug统一翻译为英文)Step 2: Select Publishing Method and Configure
步骤2:选择发布方式并配置
Ask publishing method (unless specified in EXTEND.md or CLI):
| Method | Speed | Requirements |
|---|---|---|
| Fast | API credentials |
| Slow | Chrome, login session |
If API Selected - Check Credentials:
bash
undefined询问用户发布方式(除非EXTEND.md或CLI参数中已经指定):
| 方式 | 速度 | 要求 |
|---|---|---|
| 快 | 需要API凭证 |
| 慢 | 需要Chrome、已登录公众号会话 |
如果选择API方式 - 检查凭证:
bash
undefinedCheck project-level
检查项目级别
test -f .tuzi-skills/.env && grep -q "WECHAT_APP_ID" .tuzi-skills/.env && echo "project"
test -f .tuzi-skills/.env && grep -q "WECHAT_APP_ID" .tuzi-skills/.env && echo "project"
Check user-level
检查用户级别
test -f "$HOME/.tuzi-skills/.env" && grep -q "WECHAT_APP_ID" "$HOME/.tuzi-skills/.env" && echo "user"
**If Credentials Missing - Guide Setup**:
WeChat API credentials not found.
To obtain credentials:
- Visit https://mp.weixin.qq.com
- Go to: 开发 → 基本配置
- Copy AppID and AppSecret
Where to save?
A) Project-level: .tuzi-skills/.env (this project only)
B) User-level: ~/.tuzi-skills/.env (all projects)
After location choice, prompt for values and write to `.env`:
WECHAT_APP_ID=<user_input>
WECHAT_APP_SECRET=<user_input>
undefinedtest -f "$HOME/.tuzi-skills/.env" && grep -q "WECHAT_APP_ID" "$HOME/.tuzi-skills/.env" && echo "user"
**如果缺少凭证 - 引导设置**:
未找到微信API凭证。
获取凭证步骤:
- 访问https://mp.weixin.qq.com
- 进入:开发 → 基本配置
- 复制AppID和AppSecret
保存位置选择:
A) 项目级别:.tuzi-skills/.env(仅当前项目生效)
B) 用户级别:~/.tuzi-skills/.env(所有项目生效)
用户选择保存位置后,提示输入对应值并写入`.env`文件:
WECHAT_APP_ID=<用户输入>
WECHAT_APP_SECRET=<用户输入>
undefinedStep 3: Resolve Theme/Color and Validate Metadata
步骤3:确认主题/颜色并校验元数据
-
Resolve theme (first match wins, do NOT ask user if resolved):
- CLI argument
--theme - EXTEND.md (loaded in Step 0)
default_theme - Fallback:
default
- CLI
-
Resolve color (first match wins):
- CLI argument
--color - EXTEND.md (loaded in Step 0)
default_color - Omit if not set (theme default applies)
- CLI
-
Validate metadata from frontmatter (markdown) or HTML meta tags (HTML input):
| Field | If Missing |
|---|---|
| Title | Prompt: "Enter title, or press Enter to auto-generate from content" |
| Summary | Prompt: "Enter summary, or press Enter to auto-generate (recommended for SEO)" |
| Author | Use fallback chain: CLI |
Auto-Generation Logic:
- Title: First H1/H2 heading, or first sentence
- Summary: First paragraph, truncated to 120 characters
- Cover Image Check (required for API ):
article_type=news- Use CLI if provided.
--cover - Else use frontmatter (,
coverImage,featureImage,cover).image - Else check article directory default path: .
imgs/cover.png - Else fallback to first inline content image.
- If still missing, stop and request a cover image before publishing.
- Use CLI
-
确认主题(优先匹配第一个取值,解析成功则无需询问用户):
- CLI 参数
--theme - EXTEND.md中配置(步骤0已加载)
default_theme - 兜底值:
default
- CLI
-
确认颜色(优先匹配第一个取值):
- CLI 参数
--color - EXTEND.md中配置(步骤0已加载)
default_color - 未设置则省略,使用主题默认颜色
- CLI
-
校验元数据:从Markdown的前置元数据或HTML的meta标签中提取:
| 字段 | 缺失处理 |
|---|---|
| 标题 | 提示:"输入标题,或按回车自动从内容生成" |
| 摘要 | 提示:"输入摘要,或按回车自动生成(有利于SEO)" |
| 作者 | 兜底优先级:CLI |
自动生成逻辑:
- 标题:取第一个H1/H2标题,或第一句话
- 摘要:取第一段内容,截断为120字符
- 封面图检查(API方式必填):
article_type=news- 优先使用CLI 参数指定的图片
--cover - 其次使用前置元数据中的配置(、
coverImage、featureImage、cover字段)image - 其次检查文章目录默认路径:
imgs/cover.png - 其次取正文中第一张内嵌图片
- 仍未找到则终止流程,要求用户提供封面图后再发布
- 优先使用CLI
Step 4: Publish to WeChat
步骤4:发布到微信公众号
CRITICAL: Publishing scripts handle markdown conversion internally. Do NOT pre-convert markdown to HTML — pass the original markdown file directly. This ensures the API method renders images as tags (for API upload) while the browser method uses placeholders (for paste-and-replace workflow).
<img>API method (accepts or ):
.md.htmlbash
npx -y bun ${SKILL_DIR}/scripts/wechat-api.ts <file> --theme <theme> [--color <color>] [--title <title>] [--summary <summary>] [--author <author>] [--cover <cover_path>]CRITICAL: Always include parameter. Never omit it, even if using . Only include if explicitly set by user or EXTEND.md.
--themedefault--colordraft/add- Use endpoint:
POST https://api.weixin.qq.com/cgi-bin/draft/add?access_token=ACCESS_TOKEN - :
article_type(default) ornewsnewspic - For , include
news(cover is required)thumb_media_id - Always resolve and send:
- (default
need_open_comment)1 - (default
only_fans_can_comment)0
- resolution: CLI
author→ frontmatter--author→ EXTEND.mdauthordefault_author
If script parameters do not expose the two comment fields, still ensure final API request body includes resolved values.
Browser method (accepts or ):
--markdown--htmlbash
npx -y bun ${SKILL_DIR}/scripts/wechat-article.ts --markdown <markdown_file> --theme <theme> [--color <color>]
npx -y bun ${SKILL_DIR}/scripts/wechat-article.ts --html <html_file>重要提示:发布脚本内部会自动处理Markdown转换,不要提前将Markdown转为HTML,直接传入原始Markdown文件即可。这样可以保证API方式将图片渲染为标签(用于API上传),而浏览器方式使用占位符(用于粘贴替换工作流)。
<img>API方式(支持或文件):
.md.htmlbash
npx -y bun ${SKILL_DIR}/scripts/wechat-api.ts <文件路径> --theme <主题名> [--color <颜色>] [--title <标题>] [--summary <摘要>] [--author <作者>] [--cover <封面图路径>]重要提示:必须始终携带参数,即使使用主题也不能省略。仅当用户或EXTEND.md明确设置了颜色时,才携带参数。
--themedefault--colordraft/add- 调用接口:
POST https://api.weixin.qq.com/cgi-bin/draft/add?access_token=ACCESS_TOKEN - :
article_type(默认)或newsnewspic - 类型为时,必须携带
news(必填封面图)thumb_media_id - 必须传入以下字段:
- (默认
need_open_comment)1 - (默认
only_fans_can_comment)0
- 取值优先级:CLI
author参数 → 前置元数据--author字段 → EXTEND.mdauthor配置default_author
如果脚本参数没有暴露两个评论字段,仍需确保最终API请求体中包含解析后的取值。
浏览器方式(支持或参数):
--markdown--htmlbash
npx -y bun ${SKILL_DIR}/scripts/wechat-article.ts --markdown <Markdown文件路径> --theme <主题名> [--color <颜色>]
npx -y bun ${SKILL_DIR}/scripts/wechat-article.ts --html <HTML文件路径>Step 5: Completion Report
步骤5:完成结果上报
For API method, include draft management link:
WeChat Publishing Complete!
Input: [type] - [path]
Method: API
Theme: [theme name] [color if set]
Article:
• Title: [title]
• Summary: [summary]
• Images: [N] inline images
• Comments: [open/closed], [fans-only/all users]
Result:
✓ Draft saved to WeChat Official Account
• media_id: [media_id]
Next Steps:
→ Manage drafts: https://mp.weixin.qq.com (登录后进入「内容管理」→「草稿箱」)
Files created:
[• post-to-wechat/yyyy-MM-dd/slug.md (if plain text)]
[• slug.html (converted)]For Browser method:
WeChat Publishing Complete!
Input: [type] - [path]
Method: Browser
Theme: [theme name] [color if set]
Article:
• Title: [title]
• Summary: [summary]
• Images: [N] inline images
Result:
✓ Draft saved to WeChat Official Account
Files created:
[• post-to-wechat/yyyy-MM-dd/slug.md (if plain text)]
[• slug.html (converted)]API方式结果,包含草稿管理链接:
微信公众号发布完成!
输入:[类型] - [路径]
发布方式:API
主题:[主题名] [已设置颜色则展示]
文章信息:
• 标题:[标题]
• 摘要:[摘要]
• 图片:[N]张内嵌图片
• 评论:[开启/关闭],[仅粉丝/所有用户]可评论
结果:
✓ 草稿已保存到微信公众号
• media_id:[media_id]
后续步骤:
→ 管理草稿:https://mp.weixin.qq.com(登录后进入「内容管理」→「草稿箱」)
生成的文件:
[• post-to-wechat/yyyy-MM-dd/slug.md(如果输入为纯文本)]
[• slug.html(转换后的HTML文件)]浏览器方式结果:
微信公众号发布完成!
输入:[类型] - [路径]
发布方式:浏览器
主题:[主题名] [已设置颜色则展示]
文章信息:
• 标题:[标题]
• 摘要:[摘要]
• 图片:[N]张内嵌图片
结果:
✓ 草稿已保存到微信公众号
生成的文件:
[• post-to-wechat/yyyy-MM-dd/slug.md(如果输入为纯文本)]
[• slug.html(转换后的HTML文件)]Detailed References
详细参考
| Topic | Reference |
|---|---|
| Image-text parameters, auto-compression | references/image-text-posting.md |
| Article themes, image handling | references/article-posting.md |
| 主题 | 参考文档 |
|---|---|
| 图文消息参数、自动压缩 | references/image-text-posting.md |
| 文章主题、图片处理 | references/article-posting.md |
Feature Comparison
功能对比
| Feature | Image-Text | Article (API) | Article (Browser) |
|---|---|---|---|
| Plain text input | ✗ | ✓ | ✓ |
| HTML input | ✗ | ✓ | ✓ |
| Markdown input | Title/content | ✓ | ✓ |
| Multiple images | ✓ (up to 9) | ✓ (inline) | ✓ (inline) |
| Themes | ✗ | ✓ | ✓ |
| Auto-generate metadata | ✗ | ✓ | ✓ |
Default cover fallback ( | ✗ | ✓ | ✗ |
Comment control ( | ✗ | ✓ | ✗ |
| Requires Chrome | ✓ | ✗ | ✓ |
| Requires API credentials | ✗ | ✓ | ✗ |
| Speed | Medium | Fast | Slow |
| 功能 | 图文消息 | 文章(API方式) | 文章(浏览器方式) |
|---|---|---|---|
| 纯文本输入 | ✗ | ✓ | ✓ |
| HTML输入 | ✗ | ✓ | ✓ |
| Markdown输入 | 仅标题/内容 | ✓ | ✓ |
| 多图支持 | ✓(最多9张) | ✓(内嵌) | ✓(内嵌) |
| 主题支持 | ✗ | ✓ | ✓ |
| 自动生成元数据 | ✗ | ✓ | ✓ |
默认封面兜底( | ✗ | ✓ | ✗ |
评论控制( | ✗ | ✓ | ✗ |
| 依赖Chrome | ✓ | ✗ | ✓ |
| 依赖API凭证 | ✗ | ✓ | ✗ |
| 速度 | 中等 | 快 | 慢 |
Prerequisites
前置要求
For API method:
- WeChat Official Account API credentials
- Guided setup in Step 2, or manually set in
.tuzi-skills/.env
For Browser method:
- Google Chrome
- First run: log in to WeChat Official Account (session preserved)
Config File Locations (priority order):
- Environment variables
<cwd>/.tuzi-skills/.env~/.tuzi-skills/.env
API方式要求:
- 微信公众号API凭证
- 按第2步引导设置,或手动写入文件
.tuzi-skills/.env
浏览器方式要求:
- Google Chrome
- 首次运行:登录微信公众号(会话会自动保留)
配置文件优先级:
- 环境变量
<当前工作目录>/.tuzi-skills/.env~/.tuzi-skills/.env
Troubleshooting
故障排查
| Issue | Solution |
|---|---|
| Missing API credentials | Follow guided setup in Step 2 |
| Access token error | Check if API credentials are valid and not expired |
| Not logged in (browser) | First run opens browser - scan QR to log in |
| Chrome not found | Set |
| Title/summary missing | Use auto-generation or provide manually |
| No cover image | Add frontmatter cover or place |
| Wrong comment defaults | Check |
| Paste fails | Check system clipboard permissions |
| 问题 | 解决方案 |
|---|---|
| 缺失API凭证 | 按第2步引导完成设置 |
| Access token错误 | 检查API凭证是否有效、是否过期 |
| 未登录(浏览器方式) | 首次运行会自动打开浏览器,扫码登录即可 |
| 未找到Chrome | 设置 |
| 标题/摘要缺失 | 使用自动生成功能,或手动提供 |
| 无封面图 | 在前置元数据中配置封面图,或在文章目录下放置 |
| 评论默认值错误 | 检查EXTEND.md中的 |
| 粘贴失败 | 检查系统剪贴板权限 |
Extension Support
扩展支持
Custom configurations via EXTEND.md. See Preferences section for paths and supported options.
通过EXTEND.md自定义配置,查看偏好配置章节了解路径和支持的配置项。