personal-blog
Use when researching, outlining, drafting, revising, or polishing a personal blog article—an explainer, idea essay, personal essay, cultural review, or technical post—or when asked to preserve voice in a personal blog draft, turn notes into a personal blog post, 写博客, or 写一篇博客. Not for newsletters, magazine profiles, manuscript editing, email, chat, repository documentation, marketing copy, fiction, academic papers, or generic grammar cleanup.
- Group
- Writing
- Version
- 0.8.4
- Licence
- MIT
Install
/plugin install writing@misoto22Then invoke the skill with:
/writing:personal-blogWhen it fires
The prompts CI scores this skill against — so they cannot drift from what it actually does.
Fires on
- Write a blog post that explains how heat pumps work for homeowners who know basic physics but not HVAC.
- 写一篇博客，讨论人为什么总想给人生找到意义；不要把结尾写成鸡汤。
- Turn these sparse notes into a personal blog essay: I left a long-term team; freedom felt quiet; I missed being seen. Do not add events I did not give you.
- Write a review of the film Past Lives for my blog. Discuss what the film earns emotionally, and mark spoilers if you need them.
- Write a technical blog post about diagnosing PostgreSQL connection exhaustion in Django. Verify current claims and cite the primary documentation in Markdown.
Stays out of
- Draft an email to the vendor asking whether the shipment can arrive on Friday.
- Make this Slack message less sharp: 'You ignored the agreed deadline again.'
- Rewrite this repository README so a new contributor can install and run the project.
- Turn these product-update notes into a publishable newsletter in Markdown.
- Edit this magazine profile while preserving the author's voice and narrative rhythm.
- Line-edit this nonfiction manuscript chapter and preserve the author's voice.
- Write conversion-focused copy for the pricing page, with a headline and three calls to action.
- Write a 1,500-word scene about a detective returning to her childhood home.
- Draft the literature review section for my academic paper on platform governance.
Personal Blog
Build the requested blog artefact from evidence the writer supplied or sources you verified. Preserve the writer's position and observable voice; never supply the life, certainty, or results the source material does not contain.
Workflow
- Resolve the artefact. Extract the topic, intended reader, purpose, source material, language, and constraints already present. Produce only what was requested: research notes, an outline, editorial findings, a revision, or a finished article. Do not turn a limited request into a full drafting cycle. Read shared/tone.md and shared/format.md before producing any artefact.
- Select one primary mode. Read Mode recipes, choose
explainer,idea-essay,personal-essay,review, ortechnical, and use that mode's structure and integrity check. For a genuine hybrid, borrow only the necessary checks from one secondary mode. - Establish the voice basis. Read Voice and evidence. Derive a task-local profile from the existing draft, representative samples, notes, or explicit directions. With no voice evidence, use a neutral provisional voice and make no personal claims.
- Separate the evidence. Keep four distinct working categories: supplied personal material, externally verifiable claims, interpretation, and open gaps. Never turn an interpretation into a supplied fact.
- Verify what needs support. Research externally checkable claims whose accuracy matters. Check any claim that could have changed against a current source. Prefer primary sources for technical or current claims, verify each citation before using it, state material versions and assumptions, and preserve disagreement between authoritative sources. Never invent an experience, memory, relationship, preference, belief, emotion, quotation, outcome, source, citation, command result, or test result.
- Choose earned structure. Organize around the mode, evidence, and thesis. Do not impose a hook, three-part body, recap, or call to action.
- Draft or edit. Preserve supplied facts, quotations, position, uncertainty, intentional roughness, repetition, fragments, and bilingual phrasing. If personal material is required but absent, remain impersonal or leave a visible bracketed Markdown gap for the writer.
- Run the mode-specific integrity check. Remove unsupported claims and generic filler. Confirm that links resolve to the sources actually used and that no unobserved result is presented as fact.
Delivery
Return the requested artefact without a process preface or delivery commentary. For a finished article, return raw Markdown directly: no enclosing code fence, no explanation outside the article, and no generic call to action. Use a different format only when the user asks for one.