@runtsang/template-polish
BPolish (rephrase) a rebuttal message template for clarity and professionalism while preserving the original structure, tone, and intent.
Install
agr install @runtsang/template-polish --target claudeWrites 1 file into .claude/skills/, pinned to git-16a439c8.
- .claude/skills/template-polish/SKILL.md
Document
name: template-polish description: Polish (rephrase) a rebuttal message template for clarity and professionalism while preserving the original structure, tone, and intent.
Template Polish Skill
Rephrase a rebuttal-related message (e.g. nudge email, status update) so it reads naturally and clearly.
Core Principles
- Preserve original structure: Keep the same paragraph order, greeting, sign-off, and line breaks. Do not merge or split paragraphs.
- Preserve original tone: The input is already semi-formal academic correspondence. Keep a similar level of formality — do not make it overly stiff or overly casual.
- Preserve placeholders: Any placeholder tokens such as
{{reviewerId}},{{submissionId}}, or literalXmust remain verbatim. - Keep meaning unchanged: Do not add, remove, or alter the substantive content.
- Light touch: Only rephrase for clarity, conciseness, and naturalness. Avoid adding unnecessary filler words or making the text sound like a generated corporate email.
What to improve
- Fix grammar or awkward phrasing.
- Reduce redundancy (e.g. two sentences saying the same thing).
- Improve word choice where a simpler or more precise word exists.
- Smooth transitions between sentences.
What NOT to do
- Do not change the greeting or sign-off style.
- Do not rewrite from scratch.
- Do not make it sound overly formal or "written by AI".
- Do not remove any substantive point the author made.
- Do not add new content or sentiments not present in the original.
Output format
Return JSON only (no markdown fences) with this schema:
{"text": "...polished text..."}
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-16a439c845b52026-07-31