用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/htlin222/dotfiles --skill prompt-engineer命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
依 ticket/issue 產出初版實作 — 解析需求、從最新 develop 切出符合命名規範的分支、寫出實作、跑既有測試與 lint、conventional commit,然後交棒給 /simplify。Use when the user types /develop, or asks to start implementing a ticket, issue, or feature request end-to-end from requirement to first commit.
Put a website behind a Cloudflare Access (Zero Trust) login gate, or remove one, entirely from the CLI — no dashboard GUI. Use when the user wants to password/email-protect a hostname, gate a Cloudflare Pages or Workers site, restrict a site to specific emails, set up Zero Trust Access, or asks about "cf-gate". Manages Access applications and allow-email policies via the Cloudflare API using a token in the skill's .env. Note: wrangler does NOT manage Access — this uses the Cloudflare REST API directly.
Curate a GitHub repository's wiki (the separate repo.wiki.git) into a coherent, tightly written set of pages: Home, Introduction (project + features), Roadmap, Gotchas/Lessons, Tech Debt, and an Architecture page taught through the book *Head First Software Architecture* — with mermaid diagrams, in the repo's own language and style, then commit and push. Use when the user wants to create, update, curate, or document a GitHub repo's wiki; write or refresh wiki pages; add an architecture / design page to a wiki; enable a wiki; or asks for "/wiki-git". Handles both first-time wikis and updates to existing ones, and can fan out across many repos.
基于 SOC 职业分类
正在显示 SKILL.md
| name | prompt-engineer |
| description | Optimize prompts for LLMs. Use when crafting system prompts or improving agent performance. |
Craft effective prompts for LLM applications.
You are an expert [role] with [X] years of experience in [domain].
Your task is to [specific goal].
Think through this step by step:
1. First, analyze [aspect 1]
2. Then, consider [aspect 2]
3. Finally, determine [conclusion]
Show your reasoning before giving the final answer.
Here are examples of the expected format:
Input: [example 1 input]
Output: [example 1 output]
Input: [example 2 input]
Output: [example 2 output]
Now process this input:
Input: {user_input}
Output:
Respond in the following JSON format:
{
"analysis": "your analysis here",
"confidence": 0.0-1.0,
"recommendations": ["item1", "item2"]
}
Return valid JSON only, no additional text.
You are a senior code reviewer. Review the code for:
1. Security vulnerabilities
2. Performance issues
3. Code quality and readability
4. Best practices violations
For each issue:
- Severity: Critical/High/Medium/Low
- Location: file:line
- Issue: description
- Fix: suggested solution
Code to review:
{code}
Extract the following information from the text:
- Name: person's full name
- Email: email address
- Company: organization name
- Role: job title
If information is not found, use "NOT_FOUND".
Return as JSON.
Text:
{text}
Classify the following text into one of these categories:
- POSITIVE
- NEGATIVE
- NEUTRAL
Consider tone, sentiment, and overall message.
Respond with only the category name.
Text: {text}
Category:
| Practice | Do | Don't |
|---|---|---|
| Instructions | Be specific and explicit | Be vague |
| Format | Specify output format | Assume format |
| Examples | Include 2-3 examples | Zero-shot for complex |
| Constraints | Set clear boundaries | Leave open-ended |
| Length | Set max length if needed | Allow unlimited |
Input: "Create a prompt for summarization" Action: Design prompt with length constraint, key points extraction, format spec
Input: "Improve this prompt's output" Action: Add examples, clarify instructions, specify format, test iterations