hexo-blog-update
Skill22 starsChanged 7 months agoMITView on GitHub
Use when creating, editing, or publishing Hexo blog posts
- Installs packages
In this repository17 other files it gives its agents.
- code-analysisSkill
- code-generatorSkill
- contributingSkill
- daily-logSkill
- devflowSkill
- git-workflowSkill
- kimicode-vision-bridgeSkill
- knowledge-base-cacheSkill
- layered-first-principles-teachingSkill
- msvc-buildSkill
- mvp-designSkill
- paper-first-principlesSkill
- requirement-clarificationSkill
- research-to-practiceSkill
- taskmaster-skillSkill
- ue5-umgSkill
- unity-mcpSkill
The file
We split this skill into the rules it gives an agent
10 rules. About 0 are common, 8 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Use this skill when you need to:
- Distinctive: line 16
Create a new blog post
- Very specific: line 203
Check if file is in source/_posts/
- Distinctive: line 204
Verify front matter format
- Very specific: line 205
Run hexo clean and regenerate
- Distinctive: line 208
Check SSH key configuration
- Distinctive: line 209
Verify git remote is correct
- Distinctive: line 213
Use standard Markdown syntax
- Distinctive: line 214
Verify YAML front matter syntax
- Distinctive: line 219
User: Create a new blog post about AI tools
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hexo Blog Update Skill
Overview
Standardized workflow for creating, editing, and publishing Hexo blog posts.
When to Use
Use this skill when you need to:
- Create a new blog post
- Edit existing blog posts
- Preview blog locally before publishing
- Deploy blog to production
Prerequisites
- Node.js installed (>= 14)
- Hexo CLI installed globally (
npm install -g hexo-cli) - Blog repository cloned locally
- Git configured with SSH key for deployment
Workflow
Step 1: Create New Post
# Navigate to blog directory
cd /path/to/blog
# Create new post
hexo new post "post-title"
# Or use npm script
npm run new "post-title"Post will be created at: source/_posts/post-title.md
Step 2: Edit Post Content
Edit the generated markdown file with the following structure:
---
title: Post Title
date: YYYY-MM-DD HH:MM:SS
categories:
- Category 1
- Category 2
tags:
- Tag 1
- Tag 2
---
Post excerpt content, will be displayed in the homepage list...
<!--more-->
## Body Heading
Body content...
## Another Heading
More content...Important Rules:
- ✅ Use
<!--more-->to separate excerpt from full content - ✅ Set proper categories and tags
- ✅ Use Chinese for Chinese blogs
- ✅ Keep front matter (YAML between ---) at the top
Step 3: Local Preview
# Start local server
hexo server
# Or with npm
npm run serverAccess at: http://localhost:4000
Preview Checklist:
- Post appears in list with correct title
- Excerpt shows correctly (before
<!--more-->) - Full content displays properly
- Categories and tags are correct
- No formatting errors
Step 4: Deploy to Production
# Deploy (clean + generate + deploy)
npm run release-blog
# Or manually
hexo clean && hexo generate && hexo deployDeployment Output:
INFO Deploy done: git
To github.com:username/username.github.io.git
xxx...xxx HEAD -> masterStandard Post Template
---
title: Post Title
date: 2026-02-11 17:20:00
categories:
- Category 1
- Category 2
tags:
- Tag 1
- Tag 2
- Tag 3
---
Post excerpt, displayed in the homepage list. Briefly introduce the article content and value.
<!--more-->
## Preface
Detailed background introduction...
## Main Content
### Section 1
Content...
### Section 2
Content...
## Summary
Summary of key points...
---
*Related Links*:
- [Link Description](url)Common Commands Reference
| Command | Description |
hexo new post "title" | Create new post |
hexo new draft "title" | Create draft post |
hexo publish draft "title" | Publish draft |
hexo server | Start local server |
hexo clean | Clean cache and generated files |
hexo generate | Generate static files |
hexo deploy | Deploy to remote |
npm run release-blog | Full deploy pipeline |
File Structure
blog/
├── source/
│ └── _posts/
│ └── post-title.md # Post files
├── themes/ # Theme directory
├── _config.yml # Site config
├── package.json # Scripts & dependencies
└── public/ # Generated output (auto)Best Practices
Do's
✅ Always preview before deploying
✅ Use meaningful categories and tags
✅ Include <!--more--> for proper excerpt
✅ Check date format (YYYY-MM-DD HH:MM:SS)
✅ Verify deployment success message
Don'ts
❌ Don't modify public/ directory directly ❌ Don't forget to set categories/tags ❌ Don't skip local preview ❌ Don't use special characters in filenames
Troubleshooting
Post not showing in list
- Check if file is in
source/_posts/ - Verify front matter format
- Run
hexo cleanand regenerate
Deployment fails
- Check SSH key configuration
- Verify git remote is correct
- Ensure network connectivity
Formatting issues
- Use standard Markdown syntax
- Verify YAML front matter syntax
- Check theme compatibility
Example Session
User: Create a new blog post about AI tools
Agent:
Step 1: Create post
$ hexo new post "Recommended AI Development Tools"
INFO Created: source/_posts/Recommended-AI-Development-Tools.md
Step 2: Edit content
[Edit file with proper structure and <!--more-->]
Step 3: Preview
$ hexo server
INFO Hexo is running at http://localhost:4000/
[Verify post displays correctly]
Step 4: Deploy
$ npm run release-blog
INFO Deploy done: gitVersion History
- v1.0 (2026-02-11) - Initial release
- Standard 4-step workflow
- Chinese blog format support
- Common commands reference
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

