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,104 | 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 は Claude Code、Codex、Cursor など Agent Skills 対応アプリで使えます
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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
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 だけが使えます
この Skill を ChatGPT で使うには、上の方法で 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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
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 が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
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-englishSkill を読めるほかのアプリ向けです。この文には 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
Gemini CLI や GitHub Copilot など Agent Skills 対応の他のアプリはフォルダが違います。そのアプリのガイドを見て、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.
質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。