Khazix WeChat Article Writer
KKKKhazix/khazix-skills
Writes long-form WeChat official account articles in the personal style of the Khazix account, from briefs, links, PDFs or rough notes, with a topic quality check.
Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms.
Install Emacs Blog Reviewer
$ npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install captainflasmr/ollama-buddy emacs-blog-reviewer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/emacs-blog-reviewer .claude/skills/emacs-blog-reviewer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "emacs-blog-reviewer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewer into .claude/skills/emacs-blog-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-blog-reviewer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install captainflasmr/ollama-buddy emacs-blog-reviewer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/emacs-blog-reviewer .agents/skills/emacs-blog-reviewer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "emacs-blog-reviewer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewer into .agents/skills/emacs-blog-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-blog-reviewer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install captainflasmr/ollama-buddy emacs-blog-reviewer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/emacs-blog-reviewer .cursor/skills/emacs-blog-reviewer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "emacs-blog-reviewer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewer into .cursor/skills/emacs-blog-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-blog-reviewer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/captainflasmr/ollama-buddy.git --path .agents/skills/emacs-blog-reviewer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install captainflasmr/ollama-buddy emacs-blog-reviewer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/emacs-blog-reviewer .gemini/skills/emacs-blog-reviewer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "emacs-blog-reviewer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewer into .gemini/skills/emacs-blog-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-blog-reviewer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install captainflasmr/ollama-buddy emacs-blog-reviewerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/emacs-blog-reviewer .github/skills/emacs-blog-reviewer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "emacs-blog-reviewer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewer into .github/skills/emacs-blog-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-blog-reviewer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install captainflasmr/ollama-buddy emacs-blog-reviewer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/captainflasmr/ollama-buddy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/emacs-blog-reviewer .opencode/skills/emacs-blog-reviewer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "emacs-blog-reviewer" agent skill from https://github.com/captainflasmr/ollama-buddy/tree/main/.agents/skills/emacs-blog-reviewer into .opencode/skills/emacs-blog-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "emacs-blog-reviewer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
emacs-blog-reviewer- GitHub stars
- 103
- Token cost
- ~751 tokens
- SKILL.md length
- 395 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms.
- Works in 6 steps: ONE issue per line. No multi-line… → Every line MUST end with a newline… → No introduction, no conclusion, no… → …
- Phrases like blog review
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Review this emacs blog
What it does
Emacs Blog Reviewer is an agent skill from captainflasmr/ollama-buddy. Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms. Trigger on phrases like "blog review", "review this emacs blog", "blog editing", "emacs article review", "check emacs blog post".
Its SKILL.md is about 750 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content, covering Blog and article writing. The repository describes itself as: A friendly Emacs interface for interacting with Ollama models. The licence is GPL-3.0.
When your agent uses it
- Phrases like blog review
- Review this emacs blog
- Emacs article review
- Check emacs blog post
Example prompts
- “blog review”
- “review this emacs blog”
- “blog editing”
- “/emacs-blog-reviewer”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- ONE issue per line. No multi-line issues. No sub-bullets. No blank lines between items.
- Every line MUST end with a newline before the next number begins.
- No introduction, no conclusion, no "overall impression", no praise.
- Skip issues that do not exist. Do not invent problems to fill the list.
- If uncertain about a technical claim, use [VERIFY] and explain what to check in the REASON.
- If the post has no issues, reply with exactly: No issues found.
What it can do on your machine
Read from SKILL.md and the folder at commit 12eaf7f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Emacs Blog Reviewer loads about 751 tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 395 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from captainflasmr/ollama-buddy at commit 12eaf7f, republished under its GPL-3.0 licence (© captainflasmr). 395 words, ~751 tokens.
Download SKILL.mdSave it as
.claude/skills/emacs-blog-reviewer/SKILL.md (or your agent's skills folder).- name
- emacs-blog-reviewer
- description
- Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms. Trigger on phrases like "blog review", "review this emacs blog", "blog editing", "emacs article review", "check emacs blog post".
Emacs Blog Reviewer
You are an experienced editor and Emacs power user reviewing a blog post about Emacs. Flag real issues only -- no padding, no praise, no introduction, no summary. Preserve the author's voice.
What to check
- Spelling, grammar, punctuation, awkward phrasing
- Emacs function/variable/command/package names spelled correctly and actually exist
- Key binding notation (
C-c C-c,M-x) and whether bindings match their commands - Elisp snippets: balanced parens, correct quoting, valid syntax, real bugs
- Built-in vs third-party claims (core / GNU ELPA / MELPA)
- Version-specific claims against Emacs release history
- Deprecated APIs (
cltocl-lib,point-at-eoltoline-end-position, etc.) - Conceptual errors about buffers, windows, modes, hooks, advice, overlays, text properties
Output format -- STRICT
Output a numbered list. Each issue is EXACTLY ONE LINE. After each line you MUST emit a real newline character (press Enter) before starting the next numbered item. Do NOT run numbered items together into a paragraph.
The format for each line is:
N. [CATEGORY] QUOTE to FIX (because REASON)
Where:
Nis the issue number, starting at 1[CATEGORY]is one of:[GRAMMAR],[SPELLING],[STYLE],[ELISP],[NAMING],[VERSION],[DEPRECATED],[CONCEPT],[VERIFY]QUOTEis the exact problematic text from the post, in double quotes or inline-codeFIXis the corrected version, in one short phraseREASONis a short explanation in under 15 words
Hard rules:
- ONE issue per line. No multi-line issues. No sub-bullets. No blank lines between items.
- Every line MUST end with a newline before the next number begins.
- No introduction, no conclusion, no "overall impression", no praise.
- Skip issues that do not exist. Do not invent problems to fill the list.
- If uncertain about a technical claim, use
[VERIFY]and explain what to check in the REASON. - If the post has no issues, reply with exactly:
No issues found.
Show full SKILL.md (97 more words)Show less
Example output
- [GRAMMAR] "what is the plan?, dired already draws" to "what is the plan? Dired already draws" (because a comma cannot follow a sentence-ending question mark)
- [ELISP]
(setq current (car entries))to(setq current (expand-file-name (car entries) current))(because directory-files returns relative names, losing path context) - [NAMING]
dired-after-readin-hooktodired-after-read-in-hook(because the canonical hook name has a hyphen between read and in) - [VERIFY]
tab-bar-history-done-commandto verify the exact name (because I cannot find this variable in Emacs 29 or 30 sources)
Stop after the last real issue. Brevity and one-line-per-issue are non-negotiable.
© captainflasmr, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/emacs-blog-reviewer of captainflasmr/ollama-buddy.
Open the folder on GitHubat commit 12eaf7f
Compare with similar skills
Emacs Blog Reviewer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Emacs Blog Reviewer this skillcaptainflasmr/ollama-buddy | 103 | — | ~751 | Automated safety check: Pass | GPL-3.0 | |
| Khazix WeChat Article WriterKKKKhazix/khazix-skills | 21k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Figurevectorize-io/hindsight | 48k | — | ~1.9k | Automated safety check: Pass | MIT | |
| SepiaNanako0129/sepia | 3.1k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Blog Post Draftingluongnv89/claude-howto | 42k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Notion To Blogwasp-lang/wasp | 19k | — | ~922 | Automated safety check: Pass | MIT |
Similar skills
Figure
vectorize-io/hindsight
Draw an animated figure (boxes, arrows, moving data) as one self-contained SVG for a GitHub README, PR, issue or blog post.
Sepia
Nanako0129/sepia
Make AI-generated writing read as human-written, in fiction and in professional prose.
Blog Post Drafting
luongnv89/claude-howto
Guides drafting a blog post from an idea and optional source material: research, brainstorming, outlining and version-tracked drafts, with user approval at each step.
Notion To Blog
wasp-lang/wasp
Transfer a blog post from Notion to the Wasp blog. An agent skill from wasp-lang/wasp.
Blog Post
nteract/semiotic
Author a new entry for the Semiotic blog. An agent skill from nteract/semiotic.
More from captainflasmr/ollama-buddy
All 12 skills in this repoBlog Writer
captainflasmr/ollama-buddy
Write an Emacs blog post in James Dyer's voice for www.emacs.dyerdwelling.family.
Elisp Dev
captainflasmr/ollama-buddy
Assist with Emacs Lisp (elisp) development, debugging, and parenthesis matching.
Elisp Review
captainflasmr/ollama-buddy
Review Emacs Lisp (elisp) packages for bugs, style/convention violations, and optimisation opportunities.
Annotate Project
captainflasmr/ollama-buddy
Analyse a project's source code and generate a simply-annotate database file with LLM-created annotations categorised by tag: defun for functions and large syntactical blocks, line for smaller…
Reddit Post Writer
captainflasmr/ollama-buddy
Write an r/emacs Reddit post in James Dyer's voice for announcing or discussing an Emacs package.
Code Refactoring
captainflasmr/ollama-buddy
Expert code refactoring and optimization with analysis, improvements, and documentation.
Related
Categories
Questions about Emacs Blog Reviewer
What does Emacs Blog Reviewer do?
Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms. Emacs Blog Reviewer is an agent skill from captainflasmr/ollama-buddy. Review Emacs blog posts for technical accuracy, naming conventions, and correct Emacs idioms.
When should I use Emacs Blog Reviewer?
Emacs Blog Reviewer fits situations like: phrases like blog review; review this emacs blog; emacs article review; check emacs blog post.
How do I install Emacs Blog Reviewer in Claude Code?
Run `npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a claude-code`. Or copy the skill folder (.agents/skills/emacs-blog-reviewer in captainflasmr/ollama-buddy) into .claude/skills/emacs-blog-reviewer in your project. Claude Code loads it when a task matches its description.
How do I install Emacs Blog Reviewer in Codex?
Run `npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a codex`. Or copy the skill folder (.agents/skills/emacs-blog-reviewer in captainflasmr/ollama-buddy) into .agents/skills/emacs-blog-reviewer in your project. Codex loads it when a task matches its description.
Can I use Emacs Blog Reviewer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add captainflasmr/ollama-buddy --skill emacs-blog-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/emacs-blog-reviewer, .gemini/skills/emacs-blog-reviewer, .github/skills/emacs-blog-reviewer and .opencode/skills/emacs-blog-reviewer in your project.
What does Emacs Blog Reviewer need to run?
SKILL.md names no scripts, command-line tools or credentials: Emacs Blog Reviewer is instructions for the agent only.
Does Emacs Blog Reviewer access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Emacs Blog Reviewer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Emacs Blog Reviewer use?
Emacs Blog Reviewer is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Emacs Blog Reviewer use?
About 751 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Emacs Blog Reviewer?
Skills that share tags, products or a category with Emacs Blog Reviewer: Khazix WeChat Article Writer (KKKKhazix/khazix-skills, 21k stars), Figure (vectorize-io/hindsight, 48k stars), Sepia (Nanako0129/sepia, 3.1k stars) and Blog Post Drafting (luongnv89/claude-howto, 42k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Emacs Blog Reviewer?
captainflasmr (a GitHub user) maintains it in captainflasmr/ollama-buddy, which has 103 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 10, 2026.
Source: captainflasmr/ollama-buddy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.