ClawHub

Demo Note Polisher

v1.0.0

Turn rough notes, bullet lists, chat fragments, meeting takeaways, and mixed-language drafts into polished writing. Use when the user asks to rewrite, polish...

⭐ 0· 105·0 current·0 all-time
by@jin935150450-ctrl

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for jin935150450-ctrl/yourname-demo-note-polisher.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Demo Note Polisher" (jin935150450-ctrl/yourname-demo-note-polisher) from ClawHub.
Skill page: https://clawhub.ai/jin935150450-ctrl/yourname-demo-note-polisher
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install yourname-demo-note-polisher

ClawHub CLI

Package manager switcher

npx clawhub@latest install yourname-demo-note-polisher
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the content of SKILL.md: the skill is solely about rewriting and polishing user-provided text and does not request unrelated resources.
✓
Instruction Scope
SKILL.md only instructs the agent how to transform supplied notes (tone, structure, preservation of facts, when to ask one clarifying question). It does not direct reading system files, environment variables, or sending data to external endpoints.
✓
Install Mechanism
No install spec and no code files — instruction-only. Nothing is written to disk or downloaded during install.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths; its functionality (text rewriting) does not justify extra secrets or system access.
✓
Persistence & Privilege
always is false and there is no request for persistent system presence or alterations to other skills/config. Autonomous invocation is allowed by platform default but is not combined with other privileges here.
Assessment
This is a low-risk, instruction-only skill for rewriting text. It asks for no installs or secrets. Before using, avoid pasting highly sensitive data (passwords, API keys, personal identifiers) into notes you want polished, and remember platform-level logging/privacy rules still apply — review the host platform's data handling if you have confidentiality concerns. If you want the agent to preserve or remove specific details, state that in your request so it doesn't guess.

Like a lobster shell, security has layers — review code before you run it.

latestvk97er7g678f7eenjtcv16wq5s984z3vm
105downloads
0stars
1versions
Updated 1w ago
v1.0.0
MIT-0
@jin935150450-ctrl
latest
Download

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."

Comments

Loading comments...