Vibe Writing Skill for Claude
Use when drafting, rewriting, reviewing, or planning Chinese long-form content for public accounts, blogs, newsletters, professional analysis, product or technical writing, especially when preserving an author's voice, using personal material, or reducing formulaic AI-sounding prose.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/YiShu5/claude-skills --skill vibe-writingWhat comes with it
15 536 bytes besides the instructionThe instruction itself
8 sections, as written by the authorVibe Writing
Core Principle
Preserve truth, the author's voice, and the current task before optimizing style
or distribution.
Write natural Chinese for the author, audience, platform, and purpose. Treat
reduced formulaic AI-sounding prose as a result, not a score.
Task Routing
Classify the request, then load only its route and required checks.
| Request | Load | Deliver |
|---|---|---|
| New draft | drafting; voice profile when relevant; fact checking and quality rubric as needed | Draft and necessary notes |
| Edit or rewrite | editing; voice profile, fact checking, and quality rubric as needed | Revised text and brief change summary |
| Review or critique | editing, quality rubric, and fact checking when required | Diagnosis and recommendations; no rewrite unless requested |
| Build or update a voice profile | voice profile and profile template | Profile, confidence, and unresolved items |
| Quick consultation | No reference unless needed | Direct answer |
Do not start a full workflow, create a workspace, propose multiple topics, or
add images and distribution assets unless the request requires them.
Context Priority
Current instruction > current project samples > confirmed profile > memory-based
candidate traits > neutral default Chinese.
Apply the current instruction over the profile. Treat memory traits as
candidates, not confirmed voice or fact. With sparse evidence, use a neutral
voice instead of inventing a persona.
Ask Only When It Changes the Result
Ask one focused question only for an unclear thesis, audience-changing ambiguity,
unconfirmed personal experience, unsupported key fact, or material profile conflict.
Otherwise, make the smallest reasonable assumption and execute. Mention it only
when needed. Do not require topic, outline, workspace, or plan approval by
default.
Hard Gates
Never fabricate data, quotes, cases, achievements, or first-person experience.
Never expose protected personal material. Never promise an AI-detector score.
- Distinguish proposed work from completed results.
- Keep low-confidence inferences and unverified claims visibly uncertain.
- Do not force personality, short sentences, or anecdotes to appear human.
- Qualify only unsupported parts; continue supported work when possible.
Delivery Contract
Deliver only the requested artifact. Add source notes, assumptions, unverified
items, or a change summary only when the task makes them necessary.
Always include a brief change summary for edits and rewrites. Diagnose without
rewriting in review mode. Give conclusions and necessary grounds, not hidden
reasoning.
References
Load only the reference selected by the routing table; load fact checking and
quality review when the content requires them.
- Voice profile: learn or update project voice.
- Drafting: create new content.
- Editing: edit, rewrite, or review.
- Fact checking: verify claims by state.
- Quality rubric: apply gates and final review.
- Voice-profile template: format a
requested profile.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
How to use it
Take yishu5/vibe-writing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.