菜单
Use when creating, editing, or publishing Hexo blog posts
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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
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.
Use when working in a DevFlow project with .devflow/ directory and gate-based step-by-step workflows
Use when contributing new skills to the skill-lib repository, installing skills locally, or verifying skill compliance with repository standards
Use when analyzing unfamiliar code modules, understanding system architecture, or preparing for refactoring
Use when implementing new modules from design documents, adding features to existing code, or generating structured implementations
| name | hexo-blog-update |
| description | Use when creating, editing, or publishing Hexo blog posts |
| version | 1 |
Standardized workflow for creating, editing, and publishing Hexo blog posts.
Use this skill when you need to:
npm install -g hexo-cli)# 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
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:
<!--more--> to separate excerpt from full content# Start local server
hexo server
# Or with npm
npm run server
Access at: http://localhost:4000
Preview Checklist:
<!--more-->)# 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
---
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)
| 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 |
blog/
├── source/
│ └── _posts/
│ └── post-title.md # Post files
├── themes/ # Theme directory
├── _config.yml # Site config
├── package.json # Scripts & dependencies
└── public/ # Generated output (auto)
✅ 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't modify public/ directory directly ❌ Don't forget to set categories/tags ❌ Don't skip local preview ❌ Don't use special characters in filenames
source/_posts/hexo clean and regenerateUser: 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