360 Secure SkillHub
360 安全技能中心
当前公开展示的是 测试skill。本作品已批准的版本仍可按原地址安装和更新。

Demo Note Polisher

将粗糙笔记、要点列表、聊天片段、会议记录和混合语言草稿整理润色为更清晰的消息、邮件、状态更新、公告、摘要或短备忘录;保留事实、名称、日期、数字、决策和下一步,不编造细节,必要时最多提一个澄清问题。

jin935150450-ctrl
jin935150450-ctrl
热度 0.00
最近更新 2026-05-11 17:43:38
分类:效率依赖:内部调用大模型应用场景:摘要总结 / 校对润色 / 邮件起草 / 会议纪要 ...

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add yourname-demo-note-polisher
Metadata
name
demo-note-polisher
description
Turn rough notes, bullet lists, chat fragments, meeting takeaways, and mixed-language drafts into polished writing. Use when the user asks to rewrite, polish, clean up, organize, or reframe messy text into a clearer message, email, status update, announcement, summary, or short memo without changing the underlying facts.

Demo Note Polisher

Goal

Turn incomplete or messy source text into clean, readable output while preserving the user's intent, facts, and level of certainty.

Workflow

  1. Identify the target output. Common targets: direct message, email, project update, meeting summary, announcement, short memo.
  2. Infer audience and tone from the request. Default to concise and professional when the user does not specify tone.
  3. 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.
  4. Rewrite for clarity. Remove duplication, filler, and private shorthand that would confuse the reader.
  5. 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.

Email

  • 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:

  1. Summary
  2. Progress
  3. Blockers
  4. Next steps

Meeting Summary

Use this structure when the notes come from a meeting:

  1. Purpose
  2. Decisions
  3. Action items
  4. 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."