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.
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/0xpili-simplified-technical-english)MCP servers that connect the AI to services for the same work
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
Same kind of work, ordered like the Skills list
| This one simplified-technical-english | MinerU | watermarks-remover | obsidian-skills | anysearch-skill | |
|---|---|---|---|---|---|
| Maker | 0xpili | opendatalab | guillaumemeyer | kepano | anysearch-ai |
| Skills | 1 | 1 | 1 | 5 | 1 |
| GitHub stars | 1,031 | 83,919 | 27,723 | 53,183 | 6,905 |
| Last code change | Aug 16, 2026 | Nov 18, 2026 | Nov 17, 2026 | Sep 15, 2026 | Nov 13, 2026 |
| License | – | – | MIT | MIT | Apache-2.0 |
1 skills (instruction sets) by 0xpili that an AI reads and follows · not an MCP server
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Not stated by the maker · SKILL.md skills work in apps that support Agent Skills, such as Claude Code, Codex and Cursor
GitHub account 0xpili (person), 3 years old
★ 1,031 stars · code last changed Aug 16, 2026
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
First: which AI do you use?
Pick your app and this page shows only how to install it there
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 Nov 12, 2026 · Source: support.claude.com, support.claude.com, code.claude.com
Copy this sentence and paste it into a Claude Code 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
Restart Claude Code, then type /simplified-technical-english or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a 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-englishThe ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
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
Put the simplified-technical-english folder at ~/.agents/skills/simplified-technical-english
~ is your home folder ($HOME)
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a 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 Nov 15, 2026 · Source: learn.chatgpt.com
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
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 picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a 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-englishCopy this sentence and paste it into a Cursor 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
In Cursor’s Agent chat, type / and pick simplified-technical-english
Checked against official docs Nov 12, 2026 · Source: cursor.com
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
This downloads the repo to a temporary folder and copies only the folders that contain a 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-englishFor other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · 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 Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 18, 2026
The text below comes from the maker’s repo, not from PopNx MCP
6,900 characters · Open the full file on 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.
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.