菜单
This skill should be used when the user asks to "create a bash script", "write a shell script", or mentions shell scripting conventions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create and manage presentation decks. Two modes - Slidev markdown (default) and "conference" hand-built HTML. Use when user asks to "create slides", "make a presentation", "add slides to this project", "set up a slide deck", or mentions "slidev", "pitch deck", "conference talk", "conference deck", or "slides folder".
This skill should be used when the user asks to "create a skill", "write a skill", "build a skill", or wants to add new capabilities to Claude Code. Use when developing SKILL.md files, organizing skill content, or improving existing skills. Do NOT use for plugin development, hook creation, agent creation, or slash command creation — those have dedicated skills.
This skill should be used when the user says "solve problem", "solve this problem", or invokes /solve-problem. Applies a methodical, evidence-first approach to diagnosing a problem - understand intent, observe the problem first-hand, form multiple hypotheses, gather discriminating evidence to eliminate them, propose an evidenced solution, and verify the fix actually resolves the original symptom. Do NOT use for general how-to questions, explanations, or building new features.
This skill should be used when the user asks to "improve my setup", "learn from this session", "fix my config", "stop asking for permissions", or reports friction with skills, agents, hooks, or permissions. Analyzes conversation history and proposes configuration improvements.
Create a new GitHub project with standard configuration. Use when user asks to "create a project", "set up a new repo", "initialize a repository", or wants to start a new GitHub project.
This skill should be used when the user asks to "create a hook", "add a hook", "write a hook", or mentions Claude Code hooks. Also suggest this skill when the user asks to "automatically do X" or "run X before/after Y" as these are good candidates for hooks.
| name | shell-script-development |
| description | This skill should be used when the user asks to "create a bash script", "write a shell script", or mentions shell scripting conventions. |
Create shell scripts following consistent conventions.
#!/usr/bin/env bash
set -e -o pipefail
# Colors
green='\033[0;32m'
red='\033[0;31m'
yellow='\033[1;33m'
blue='\033[0;34m'
nc='\033[0m'
# Script logic here
echo -e "${green}✔${nc} completed successfully"
| Element | Convention |
|---|---|
| Shebang | #!/usr/bin/env bash |
| Safety | set -e -o pipefail |
| Local variables | Lowercase (model, dir, count) |
| Environment variables | Uppercase (PATH, HOME, USER) |
| Color variables | Lowercase (green, red, nc) |
| Status words | Lowercase (error, warning, note) |
echo -e "${green}✔${nc} task completed" # success
echo -e "${red}error${nc}: something failed" # error
echo -e "${yellow}warning${nc}: something to note" # warning
echo -e "${blue}info${nc}: informational message" # info
After creating or modifying shell scripts, inform the user:
Make executable. Run
chmod +x script.shbefore use.