XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
An Agent Skill that makes an LLM write in ASD-STE100 Simplified Technical English. Rules, approved word list, and a check tool.
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/skills/0xpili-simplified-technical-english)在同一工作中把 AI 连到服务的 MCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
同类工作,排序与 Skill 列表相同
| 本项 simplified-technical-english | MinerU | watermarks-remover | obsidian-skills | anysearch-skill | |
|---|---|---|---|---|---|
| 作者 | 0xpili | opendatalab | guillaumemeyer | kepano | anysearch-ai |
| Skill 数 | 1 | 1 | 1 | 5 | 1 |
| GitHub 星标 | 1,031 | 83,919 | 27,723 | 53,183 | 6,905 |
| 最近代码更新 | 2026年8月16日 | 2026年11月18日 | 2026年11月17日 | 2026年9月15日 | 2026年11月13日 |
| 许可证 | – | – | MIT | MIT | Apache-2.0 |
0xpili 提供的 1 个 Skill(指令集),AI 读取后照做 · 不是 MCP server
MCP = 手
把 AI 连到外部服务或数据,例如读取 Notion 或开发票。需要有程序或服务器在运行。
Skill = 手册
教 AI 怎么做某项工作的文本文件,不连接任何服务。
有些会重叠:少数 Skill 带有调用工具的脚本,少数 MCP 只提供知识。请从你想完成的工作出发。
开发者未说明 · SKILL.md 形式的 Skill 可用于支持 Agent Skills 的应用,如 Claude Code、Codex 和 Cursor
GitHub account 0xpili (person), 3 years old
★ 1,031 stars · code last changed 2026年8月16日
1 scripts that can run on a computer: scripts/ste_check.py
No internet calls found in the scripts
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 1e148d6 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
第一步:你用哪个 AI?
选择你用的应用,本页只显示该应用的安装方法
This skill has no license, so we do not hand out a ZIP from our site. Download it from GitHub and arrange the folder yourself, or use "Let the AI install it" above, which is easier
Download from GitHub (whole repo) ↗
Unzip it, then zip only the simplified-technical-english folder again. The ZIP must have a simplified-technical-english folder with SKILL.md at the top level, no loose files
+Create skillUpload a skillpick simplified-technical-english.zip
SettingsCapabilitiesCode execution and file creation
Turn on Code execution and file creation first (newer menus: Create and edit files) · personal plans: Settings → Capabilities · Team/Enterprise: an admin turns it on under Organization settings → Plugins & skills · every plan, including Free
Upload once; it works in claude.ai and Claude Desktop, and in recent Claude Code signed in with a Claude account (not with an API key)
Cowork and cloud sessions use the skills turned on in your claude.ai account, not ~/.claude/skills on your computer (Claude Desktop scheduled tasks run locally and still load it)
Checked against official docs 2026年11月12日 · Source: support.claude.com, support.claude.com, code.claude.com
复制这句话,粘贴到 Claude Code 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
重新打开 Claude Code,输入 /simplified-technical-english,或直接提出相关任务,Claude 会自动选用
Checked against official docs 2026年11月12日 · Source: code.claude.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/0xpili/simplified-technical-english.git /tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6/.' ~/.claude/skills/simplified-technical-englishChatGPT 桌面应用内置 Codex,Codex 从 ~/.agents/skills 文件夹读取 Skill
在 ChatGPT 桌面应用中打开 Codex,把这句话粘贴到对话中
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
把 simplified-technical-english 文件夹放到 ~/.agents/skills/simplified-technical-english
~ 是你的主文件夹($HOME)
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/0xpili/simplified-technical-english.git /tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6/.' ~/.agents/skills/simplified-technical-englishChecked against official docs 2026年11月15日 · Source: learn.chatgpt.com
不能使用你自己安装的 Skill,只能使用目录中插件自带的 Skill
想在 ChatGPT 中使用这个 Skill,请按上面的方法使用 ChatGPT 桌面应用
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
复制这句话,粘贴到 Codex 的对话中 · 适用于 ChatGPT 桌面应用中的 Codex、Codex CLI 和 IDE 扩展
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex 会自动发现新安装的 Skill;如果没有出现,请重启 Codex · 使用方法:在 ChatGPT 中输入 @ 并选择 Skill · 在 Codex CLI 或 IDE 扩展中运行 /skills,或输入 $ 加 Skill 名称
Checked against official docs 2026年11月15日 · Source: learn.chatgpt.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/0xpili/simplified-technical-english.git /tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6/.' ~/.agents/skills/simplified-technical-english复制这句话,粘贴到 Cursor 的对话中
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
在 Cursor 的 Agent 聊天中输入 / 并选择 simplified-technical-english
Checked against official docs 2026年11月12日 · Source: cursor.com
Skill 是 AI 会照做的指令。安装前先阅读文件,只安装可信开发者的 Skill。
Mac:按 Command+空格输入 Terminal · Windows:下方命令在 PowerShell 中无法使用,请改用上方的“让 AI 帮你安装”
这条命令把 repo 下载到临时文件夹,只复制含 SKILL.md 的文件夹
git clone --depth 1 https://github.com/0xpili/simplified-technical-english.git /tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-0xpili-simplified-technical-english-1e148d6/.' ~/.cursor/skills/simplified-technical-english适用于其他能读取 Skill 的应用。这句话列出了 Claude Code、Codex 和 Cursor 的路径,AI 会按你的应用选择 · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 2026年11月12日 · Source: code.claude.com, learn.chatgpt.com, cursor.com
其他支持 Agent Skills 的应用(如 Gemini CLI、GitHub Copilot)使用不同文件夹,请查看该应用的指南,再把含 SKILL.md 的文件夹复制过去。
已于 2026年11月11日 对照 Claude Code、Codex 和 Cursor 官方指南核实 skill 文件夹
✓ 命令已检查 2026年11月18日
以下文字来自开发者的 repo,不是 PopNx MCP 的指令
6,900 个字符 · 在 GitHub 打开完整文件
---
name: simplified-technical-english
description: Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, and when the user asks to write, rewrite, review, or check technical documentation, procedures, manuals, instructions, warnings, or reports.
license: MIT for the text of this skill. The word list in references/word-list.md comes from the ASD-STE100 dictionary, which is the property of ASD. Refer to NOTICE.md.
metadata:
source-specification: ASD-STE100 Issue 7 (2017-01-25)
---
# Simplified Technical English
This skill makes you write in Simplified Technical English (STE).
STE is a controlled language for technical documentation.
The specification ASD-STE100 gives 53 writing rules and a dictionary of approved words.
Text in STE is clear to readers who do not know much English.
Obey the rules in this file for all the technical text that you write.
The rules in this file are the most important rules.
The full set of rules is in `references/writing-rules.md`.
The approved words are in `references/word-list.md`.
## Scope
Apply STE to technical output: documentation, procedures, manuals, instructions, reports, error messages, and answers about technical subjects.
Do not apply STE to:
- Marketing text or brand text
- Poems, stories, or conversation
- Code blocks, identifiers, commands, file paths, and quoted error messages
- Quoted text and official names of products, parts, and documents.
If the user asks for a different style, the request of the user wins.
## Step 1: Classify the text
Before you write, classify each part of the text:
- **Procedural text** tells the reader to do something. Example: "Remove the four bolts."
- **Descriptive text** gives information. Example: "The pump supplies fuel to the engine."
The two types have different limits. Do not mix the two types in one paragraph.
## Step 2: Obey the verb rules
- Use only these verb forms: infinitive, imperative, simple present, simple past, future with "will", and past participle as an adjective.
- Do not use the "-ing" form of a verb. Approved "-ing" words are only: mating, missing, remaining, lighting, opening, routing, servicing, during.
- Do not use a helping verb with a past participle. Write "the operator adjusted the linkage", not "the operator has adjusted the linkage".
- Use the active voice. Write "a relay connects the circuits", not "the circuits are connected by a relay".
- In procedures, use the imperative. Write "Set the switch to ON."
- If there is no agent, use "you" or "we" as the subject.
- Use only "can", "must", and "will" as helping verbs. Do not use "should", "would", "may", "might", or "shall".
- A past participle after "is" or "are" shows a condition and is permitted. "The wires are disconnected."
## Step 3: Obey the sentence rules
- Procedural sentences: maximum 20 words.
- Descriptive sentences: maximum 25 words.
- Paragraphs: maximum 6 sentences, and only one topic.
- Write only one instruction in each sentence. Two actions are permitted only when they occur at the same time.
- Write only one topic in each sentence.
- When a condition comes before a command, put a comma after the condition. "If the light comes on, stop the engine."
- Keep the articles, the subjects, the verbs, and the conjunction "that". Write "make sure that the file exists".
- Do not use contractions. Write "do not", not "don't".
- Do not use semicolons. Write two sentences.
- Use a vertical list for complex text. In a list of commands with "not", write "not" again in each item.
## Step 4: Obey the word rules
- Use only: approved words from `references/word-list.md`, technical names, and technical verbs.
- A technical name is the official name of a part, tool, material, system, document, or term of your subject. Examples: "engine", "firewall", "torque wrench", "SKILL.md".
- Use an approved word only as its given part of speech. "Test" is a noun, not a verb. Write "do a test", not "test the system".
- Use one name for one item in the full text. Do not change between names for the same item.
- Write noun clusters of maximum three words. Break long clusters with "of", "on", "in", or "for".
- Do not make phrasal verbs. Write "extinguish the fire", not "put out the fire".
- Do not use vague words. Write the specific quantity, name, or action.
- Use American English spelling.
- Common replacements are in `references/substitutions.md`.
## Step 5: Write safety instructions correctly
- Use "WARNING" for a risk of injury or death to persons.
- Use "CAUTION" for a risk of damage to objects.
- Start with a simple command or condition. Then give the risk.
- Example: "WARNING: Do not touch the connector. The connector can have a dangerous voltage."
## Step 6: Check your text
After you write, check your text. Do these steps:
1. If you can run scripts, run: `python3 scripts/ste_check.py --mode <procedural|descriptive> <file>`.
2. If you cannot run scripts, do a manual scan of the checklist below.
3. Correct each error.
4. Check the text again. Stop only when the text has no errors.
Manual scan checklist:
- Find semicolons and contractions. Remove them.
- Find "has", "have", and "had" before a past participle. Use the simple past tense.
- Find "should", "would", "may", "might", and "shall". Replace them or remove them.
- Find "-ing" words that are not approved and are not in technical names. Rewrite them.
- Find passive voice. Make the agent the subject, or use the imperative.
- Count the words in the longest sentences. Divide sentences that are too long.
- Count the sentences in each paragraph. Divide paragraphs that have more than 6 sentences.
- Find words that are not approved and are not technical names. Replace them.
The check tool cannot find all the errors.
The tool cannot know if a word has its approved meaning.
You must also compare your words with `references/word-list.md`.
## Reference files
- `references/writing-rules.md` — all 53 rules and 4 recommendations, with examples. Read this file when you rewrite a document or when a rule is not clear.
- `references/word-list.md` — the 869 approved words with their parts of speech and forms.
- `references/substitutions.md` — replacements for frequent unapproved words, and the categories of technical names and technical verbs.
- `examples/before-after.md` — examples of text before and after the change to STE.
## Basis
The source of this skill is ASD-STE100 Issue 7 (2017).
ASD releases new issues of the specification.
You can get the specification free of charge from https://www.asd-ste100.org.
This skill is not an official ASD document.
This skill cannot make sure that your text obeys the official specification fully.
Refer to NOTICE.md for the copyright information.
提问、分享技巧或报告无法使用。按“有帮助”数量排序。