Best use case
hexo-blog-update is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when creating, editing, or publishing Hexo blog posts
Teams using hexo-blog-update should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/hexo-blog-update/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How hexo-blog-update Compares
| Feature / Agent | hexo-blog-update | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when creating, editing, or publishing Hexo blog posts
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 ```bash # 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: ```markdown --- 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 ```bash # Start local server hexo server # Or with npm npm run server ``` Access 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 ```bash # Deploy (clean + generate + deploy) npm run release-blog # Or manually hexo clean && hexo generate && hexo deploy ``` **Deployment Output**: ``` INFO Deploy done: git To github.com:username/username.github.io.git xxx...xxx HEAD -> master ``` ## Standard Post Template ```markdown --- 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 clean` and 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: git ``` ## Version History - v1.0 (2026-02-11) - Initial release - Standard 4-step workflow - Chinese blog format support - Common commands reference
Related Skills
unity-mcp
Use when controlling Unity editor via AI, automating scene operations, or programmatically generating Unity assets and scripts
ue5-umg
Use when building HUDs, menus, inventory screens, settings panels, or any widget-based interface in Unreal Engine 5. Also use when connecting C++ logic to UMG Blueprint visuals, handling gamepad or keyboard focus navigation, managing UI state, creating widget animations, or troubleshooting UMG performance issues like frame drops, hitches, or widget memory leaks.
taskmaster-skill
Use when managing complex project plans, tracking multi-phase task progress, or prioritizing development tasks
research-to-practice
Use when applying academic research to practical workflows, optimizing existing processes based on papers, or extracting actionable insights from research
requirement-clarification
Use when receiving ambiguous instructions, preparing for state-changing operations, or needing explicit user confirmation
paper-first-principles
Use when converting academic papers into engineer-friendly documentation, extracting design patterns from research, or preparing technical knowledge sharing
mvp-design
Use when designing new modules from scratch, creating minimal viable prototypes, or establishing architectural decisions before implementation
msvc-build
Use when compiling MSVC C++ projects, debugging build errors, or performing clean and incremental builds
layered-first-principles-teaching
Use when explaining complex concepts to others, designing training materials, or preparing technical presentations with progressive disclosure
knowledge-base-cache
Use when managing large knowledge bases, reducing API costs, or implementing multi-tier caching for frequent queries
kimicode-vision-bridge
Use when the current Agent LLM cannot process images directly and visual analysis is needed — bridges images through KimiCode CLI print mode to a multimodal Kimi model for text description
git-workflow
Use when committing code, pushing changes, or managing Git operations that require safety checks