📦 测试skill — demo-note-polisher — 笔记润色工具
v1.0.0将粗糙笔记、要点列表、聊天片段、会议记录和混合语言草稿润色成专业的书面表达。当用户要求重写、润色、整理或重构混乱文本时使用，可在不改变事实的前提下生成更清晰的消息、邮件、状态更新、公告、摘要或简短备忘录。
0· 19·0 当前·0 累计
by 安全扫描
OpenClaw
安全
high confidence该技能的指令、要求和行为对于笔记润色工具来说内部一致，不请求无关凭据、安装或系统访问权限。
评估建议
该技能与其声明目的相符且风险较低。使用前，避免将敏感信息（姓名、令牌或私人PII）粘贴到待润色的文本中，并先用非敏感样本测试以确认输出风格。请注意，“无害”意味着技能与其描述相符，但它仍可能暴露或重新格式化您提供的任何敏感内容，因此在外部分享前请审查输出。详细分析 ▾
✓ 用途与能力
名称/描述（润色笔记）与 SKILL.md 匹配：所有指令都专注于重写、清晰度、语气和保留事实。无无关能力或请求（无云凭据、无二进制文件）。
✓ 指令范围
SKILL.md 将运行时行为限制在转换用户提供的文本，最多提出一个澄清问题，并保留事实。它不指示读取系统文件、环境变量或向外部端点发送数据。
✓ 安装机制
纯指令技能，无安装规范和代码文件。安装过程中不会写入磁盘或获取任何内容。
✓ 凭证需求
不需要环境变量、凭据或配置路径；请求的范围最小且适合文本润色技能。
✓ 持久化与权限
always 为 false，没有特殊持久化或系统级配置。技能可自主调用（平台默认），这对于此类技能是正常的。
安全有层次，运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.02026/4/16
首次发布
● 无害
安装命令
点击复制官方npx clawhub@latest install bisheng-demo-note-polisher
镜像加速npx clawhub@latest install bisheng-demo-note-polisher --registry https://cn.longxiaskill.com
技能文档
Goal
Turn incomplete or messy source text into clean, readable output while preserving the user's intent, facts, and level of certainty.
Workflow
- Identify the target output. Common targets: direct message, email, project update, meeting summary, announcement, short memo.
- Infer audience and tone from the request. Default to concise and professional when the user does not specify tone.
- Extract the factual content from the raw notes. Preserve names, dates, numbers, decisions, blockers, and next steps exactly unless the user explicitly asks for changes.
- Rewrite for clarity. Remove duplication, filler, and private shorthand that would confuse the reader.
- Mark uncertainty instead of inventing details. If key information is missing, surface it as an open question or a neutral placeholder.
Output Rules
- Keep the same language as the input unless the user requests another language.
- If the input mixes languages, normalize to the dominant language unless the user wants bilingual output.
- Do not fabricate timelines, metrics, owners, or outcomes.
- Keep the output shorter than the source unless the user asks for expansion.
- Preserve the user's stance and confidence level.
- If the notes are extremely rough, provide one polished version and one shorter version.
Format Heuristics
Message
- Keep it brief and direct.
- Lead with the main point.
- End with the requested action, if any.
- Use a clear subject line only when it helps.
- Open and close politely but keep the body compact.
- Group related details into short paragraphs or bullets.
Status Update
Use this structure when the user wants a weekly update or progress summary:
- Summary
- Progress
- Blockers
- Next steps
Meeting Summary
Use this structure when the notes come from a meeting:
- Purpose
- Decisions
- Action items
- Open questions
Clarification Rule
Ask at most one clarifying question only if the missing detail would materially change the output, such as the target audience or required language. Otherwise, make a reasonable default choice and proceed.
Example Requests
- "Polish these meeting notes into a short recap for the team."
- "Turn this rough draft into a professional email."
- "Clean up my weekly update and make it more concise."
- "Rewrite these mixed Chinese and English notes into one clear announcement."