- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add notque/vexjoy-agent --skill writing -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add notque/vexjoy-agent --skill writing -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add notque/vexjoy-agent --skill writing -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add notque/vexjoy-agent --skill writing -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/notque/vexjoy-agent/tree/HEAD/skills/content/writing來自發布者
Five modes. Match the request to the correct mode and follow its section.
13-phase pipeline for voice-profiled articles and blog posts. Each phase runs as a separate agent dispatch. Phase artifacts are files in .voice-phase/, not context between agents.
Set VOICE_WRITER_ACTIVE=1 before dispatching any phase agent.
LOAD: Identify voice profile. Run ls ~/.claude/skills/ | grep voice- for available profiles. Read profile.json, all references/, and the target site's CLAUDE.md. Output: .voice-phase/01-load.json.
GROUND: Anchor in lived experience. Identify: core problem, personal experience, the "vex" (frustration) and "joy" (resolution), 3-5 concrete details, single reader takeaway. Output: .voice-phase/02-grounding.md.
STATS-CHECKPOINT: Extract target ranges from profile (sentence/paragraph length, pronoun density, contraction rate, banned patterns). Output: .voice-phase/03-stats-baseline.json.
GENERATE: Draft from a substance brief (thesis, facts, quotes, outline) so the model isolates style from substance. When only a topic is given, gather the substance into a brief first. Write the full draft in target voice. Apply narrative structure guidance: let evidence speak, mix emotional registers, weave secondary threads, leave room for uncertainty, reference specifically, vary intensity, include one unpredicted event, acknowledge the reader, vary temporal structure, close with forward motion, subvert one expectation. Target 1200-2000 words. Output: .voice-phase/04-draft.md.
HOOK-GATE: Check opening for at least one concrete number, specific date, or unexpected detail. Score 1-10. If < 8, pull the most surprising finding from the body into the opening. Max 3 attempts. Output: .voice-phase/05-hook-score.json.
VALIDATE: Run Voice Validation below. Measure metrics against Phase 3 targets. Flag deviations > 1 stddev. Output: .voice-phase/06-validation-report.json.
REFINE: Fix failed metrics. Tighten prose. Verify code examples. Re-validate changed sections. Output: .voice-phase/07-refined-draft.md.
VARIETY-GATE: Sentence length clusters: short (1-7 words) 30-45%, medium (8-20) 35-50%, long (21+) 10-25%. Every paragraph 3 sentences or fewer. At least 1 single-sentence paragraph per 500 words. Variety score (stddev) >= 8.0. Max 3 attempts. Output: .voice-phase/08-variety-score.json.
JOY-CHECK: Call the Skill tool with joy-check. Ensure the article celebrates problem-solving, not grievance. Output: .voice-phase/09-joy-report.json.
ANTI-AI: Run the private de-AI editor skill. Strip generic transitions, hedge stacking, summary conclusions, self-narrating structure. Voice profile overrides anti-AI rules -- if a flagged pattern exists in the voice profile's corpus, preserve it. Output: .
7-phase pipeline to build a voice profile from writing samples. Each phase has a gate. Report progress with phase banners (load references/cv-phase-banners.md).
Gather 50+ writing samples across contexts and lengths. Mix sources: Reddit, HN, blog, forum, email, chat, social. Do not clean typos -- imperfections ARE the voice. Do not cherry-pick. Save to skills/voice-{name}/references/samples/*.md.
Run deterministic analysis:
python3 ~/.claude/scripts/voice-analyzer.py analyze \
--samples skills/voice-{name}/references/samples/*.md \
--output skills/voice-{name}/profile.json
Add stylometry bands: python3 scripts/voice-stylometry.py band --samples skills/voice-{name}/references/samples/*.md. Merge into profile.json.
Identify distinctive patterns from samples + profile.json. Load references/cv-pattern-identification.md for phrase fingerprints, thinking patterns, wabi-sabi markers, and linguistic architectures. Apply triple-validation rubric from references/cv-extraction-validation.md: every pattern must pass cross-domain recurrence, generative power, and distinguishing exclusivity. Verdict: KEEP / FOOTNOTE / DROP.
Transform KEEP/FOOTNOTE patterns into rules. Load references/cv-voice-rules-template.md. Build: positive identity (with dampening adverbs), contrastive table (This Voice vs Generic AI), hard prohibitions, wabi-sabi rules, anti-essay patterns, architectural patterns.
Generate the voice skill files. Load references/cv-skill-generation.md. Create skills/voice-{name}/SKILL.md and config.json. Most line count is SAMPLES, not rules (V7-V9 failed with rules-only; V10 passed with 100+ samples).
Generate 3 test pieces (short, medium, long). Run:
python3 ~/.claude/scripts/voice-validator.py validate \
--content /tmp/voice-sample-{name}-{N}.md \
--profile skills/voice-{name}/profile.json --voice {name} --format text --verbose
python3 ~/.claude/scripts/voice-validator.py check-banned \
--content /tmp/voice-sample-{name}-{N}.md --voice {name}
If validation flags natural imperfections as errors, adjust config.json thresholds, not the content. Max 3 iterations.
Triad eval (new or changed skill). Run the voice triad eval against the held-out set with a no-skill baseline arm. A skill that loses to no skill is worse than useless. Load references/cv-triad-eval.md for the method and commands. Keep the skill change only when it wins on held-out pieces; revert otherwise.
Authorship matching: present hold-out samples mixed with generated samples to 5 roasters. Target: 4/5 say SAME AUTHOR. Load references/cv-iteration-guide.md for the full procedure. If failing, add more samples (not more rules). Max 3 iterations.
Re-run the triad eval after each iteration that changes the skill. Stop after three rounds without a kept change.
Critique-and-rewrite loop for voice fidelity. Max 3 iterations: scan, revise, rescan.
Determine voice profile, mode, and content to validate. Load the target voice's checklist.
Step 0: Run deterministic stylometry checks if the voice has a profile.json:
python3 scripts/voice-stylometry.py check \
--profile skills/voice-{name}/profile.json --draft <content-file>
Checks: burstiness band, punctuation profile, corrective antithesis, temporal openers, uniform paragraph shapes, profile decay.
Step 1: Run negative prompt checklist across all categories: Tone, Structure, Sentences, Language (ban: amazing, terrible, revolutionary, perfect, game-changing, transformative, incredible, outstanding, exceptional, groundbreaking), Emotion, Questions, Metaphors. For 500+ word content, add Narrative category (load references/narrative-patterns.md).
Step 2: Check pass conditions: feels human-written, voice-specific patterns present, could NOT be posted on LinkedIn without edits (for casual voices).
Step 3: Document each violation with: category, quoted text, fix recommendation.
Apply the smallest change that resolves each violation. Preserve meaning. Keep substance and arguments intact.
Rescan revised content. If PASS: output with validation report. If FAIL and iteration < 3: return to Phase 3. If FAIL and iteration = 3: output with flagged concerns.
Transform dense technical communication into structured business formats.
Classify input type (technical update, debugging narrative, status report, dependency discussion). Extract ALL propositions: facts, implications, temporal markers, system references, blockers, emotional context. Document implicit context. Count propositions.
Categorize propositions: Status, Actions, Impacts, Blockers, Next. Prioritize by business impact: Business Impact > Technical Functionality > Timeline > Resources > Risk.
Apply standard template (load references/pc-templates.md for full library):
STATUS: GREEN|YELLOW|RED
KEY POINT: [single most important takeaway]
Summary: [3 bullets: accomplishment/issue + impact]
Technical Details: [2-3 sentences]
Next Steps: [specific actions with verb, scope, owner, timeline]
Tone rules: strip hedging, transform defensive language, preserve urgency markers, keep technical terms intact. Status: GREEN (complete, no follow-up), YELLOW (resolved with follow-up or blocked), RED (active critical issue). Always document reasoning.
Compare output against extracted propositions -- zero information loss. Verify technical accuracy. Confirm status matches severity. Validate action items have (verb, scope, owner, timeline). Check detail level for audience.
Translate documents using three modes: quick (single-pass), normal (analyze-then-translate), refined (full pipeline with polish). Core principle: rewrite as a skilled native writer, not word-for-word conversion.
Infer mode: "quick/fast/draft" = quick; "professional/polished/refined" = refined; default = normal. Detect source and target languages. Flag documents > 2000 words for chunked parallel translation. Load references/tr-modes.md.
Identify: language/dialect, register (academic/technical/narrative/marketing/casual/legal), document type, specialized terminology. For technical content, build glossary (load references/tr-glossary-template.md).
Translation principles: use idiomatic target-language word order; break long source sentences at natural target-language pauses; render metaphors by intent, not literally; annotate specialized terms on first use; match register from Phase 2; preserve proper nouns and brand names.
For documents > 2000 words: split at heading/paragraph boundaries, build session glossary, dispatch parallel subagent calls per chunk with glossary injected, reassemble, check term consistency.
Scan for register inconsistency. Rewrite literal-sounding constructions. Audit specialized term handling.
Report: source, target, mode, word count, chunks, untranslated terms.
Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication, translation.
---name: writingdescription: Writing: voice creation and validation, prose editing, anti-AI cleanup, professional communication…---# skills/content/writing/SKILL.md常見問題
從發布者下載 skills/content/writing/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/notque/vexjoy-agent。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。
.voice-phase/10-antiai-report.jsonCLOSE-GATE: Verify closing uses one of 5 modes (Honest Uncertainty, Practical Trailing Observation, Self-Deprecating Admission, Specific Next Step, Just Stops). Must not summarize, callback to opening, or use "In conclusion". Score >= 7. Max 3 attempts. Output: .voice-phase/11-close-score.json.
OUTPUT: Apply front matter, write to content/posts/YYYY-MM-DD-slug.md. Report all gate scores. Write .voice-pipeline-complete marker. Output: final file.
CLEANUP: Report word count, reading time, preview URL. Flag gates that required multiple attempts.