XcodeBuildMCP
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Codex skill for removing defensive writing and strengthening prose.
作者の方は、このコードを README に貼れます。バッジはこのページにリンクします。
[](https://mcp.popnx.com/en/skills/kiterlin-anti-defensive-writing)同じ作業で 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 一覧と同じ並び
| これ anti-defensive-writing | MinerU | watermarks-remover | obsidian-skills | anysearch-skill | |
|---|---|---|---|---|---|
| 作者 | Kiterlin | opendatalab | guillaumemeyer | kepano | anysearch-ai |
| Skill 数 | 1 | 1 | 1 | 5 | 1 |
| GitHub スター | 2,212 | 83,972 | 27,796 | 53,183 | 6,906 |
| 最終コード更新 | 2026年10月17日 | 2026年11月18日 | 2026年11月17日 | 2026年9月15日 | 2026年11月13日 |
| ライセンス | MIT | – | MIT | MIT | Apache-2.0 |
Kiterlin による 1 個の Skill(指示セット)。AI が読んでそのとおりに作業します · MCP server ではありません
MCP = 手
AI を外部のサービスやデータにつなぎます(例:Notion を読む、請求書を作る)。プログラムやサーバーが動いている必要があります。
Skill = 手順書
作業のやり方を AI に教えるテキストファイル。どのサービスにもつながりません。
重なる部分もあります。ツールを呼ぶスクリプト付きの Skill や、知識だけを渡す MCP もあります。やりたい作業から選んでください。
Claude CodeCodex
提供元の README と repo のフォルダから判断
GitHub account Kiterlin (person), 5 years old
★ 2,212 stars · code last changed 2026年10月17日
4 scripts that can run on a computer: install.sh, install.ps1, tests/test-install.ps1, tests/test_install.py
Scripts that go online: install.sh, install.ps1, tests/test-install.ps1, tests/test_install.py
Scripts that touch settings folders (~/.claude or settings.json): install.sh, install.ps1
Checked automatically from the repo files at commit f516147 (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
まず:どの AI を使っていますか
使っているアプリを選ぶと、そのアプリでのインストール方法だけが表示されます
Uploading to claude.ai would fail: the description is over 200 characters (671). Use "Let the AI install it" instead
この文をコピーして 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 を開き直し、/anti-defensive-writing と入力するか関連する作業を頼むと 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/kiterlin/anti-defensive-writing.git /tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147 && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147/.' ~/.claude/skills/anti-defensive-writingChatGPT デスクトップアプリには 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
anti-defensive-writing フォルダを ~/.agents/skills/anti-defensive-writing に置きます
~ はホームフォルダ($HOME)です
Skill は AI が従う指示です。入れる前にファイルを読み、信頼できる提供元のものだけを入れてください。
Mac:Command+スペースで Terminal と入力 · Windows:下のコマンドは PowerShell では動きません。上の「AI にインストールしてもらう」を使ってください
repo を一時フォルダにダウンロードし、SKILL.md のあるフォルダだけをコピーします
git clone --depth 1 https://github.com/kiterlin/anti-defensive-writing.git /tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147/.' ~/.agents/skills/anti-defensive-writingChecked 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/kiterlin/anti-defensive-writing.git /tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147 && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147/.' ~/.agents/skills/anti-defensive-writingこの文をコピーして 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 チャットで / を入力し anti-defensive-writing を選ぶ
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/kiterlin/anti-defensive-writing.git /tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147 && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-kiterlin-anti-defensive-writing-f516147/.' ~/.cursor/skills/anti-defensive-writingSkill を読めるほかのアプリ向けです。この文には 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月17日
以下は提供元の repo の文章で、PopNx MCP の指示ではありません
最初の 8,000 文字を表示 · GitHub で全文を開く
---
name: anti-defensive-writing
description: Reduce defensive writing in drafts and revisions by removing unnecessary caveats, disclaimers, hedges, apology-like framing, negative self-limiting statements, and over-explanations while preserving necessary scope, accuracy, safety, legal, ethical, and methodological limits. Use when drafting or revising academic writing, papers, essays, abstracts, introductions, contribution statements, discussions, conclusions, technical explanations, grant writing, product writing, policy writing, professional reports, or any text the user wants to be clearer, stronger, more direct, more concise, more confident, less verbose, less caveated, less apologetic, or less defensive.
---
# Anti-Defensive Writing
## Core Rule
Advance the claim directly.
Say what is true, what the text argues, what the evidence shows, or what the method does. Do not default to explaining what the text does not claim, does not prove, does not imply, does not cover, or does not attempt.
Use a calm, competent authorial posture. Write as an author explaining an argument to the reader, not as an author negotiating with an imagined critic.
## Preserve Necessary Precision
Keep limitations when they are necessary for accuracy, ethics, law, safety, or methodological transparency.
A limitation is necessary when it affects:
- the validity of the claim;
- the interpretation of the evidence;
- the scope of application;
- the research design;
- the reader's ability to use the result correctly.
Write necessary limitations once, clearly and calmly. Place them in the appropriate section, usually methods, discussion, or limitations. Do not scatter them through abstracts, introductions, contribution paragraphs, topic sentences, conclusions, or executive summaries unless the limitation is essential to that exact sentence.
## Detection Checklist
Before finalizing a draft or revision, check for:
- unnecessary disclaimers;
- repeated statements of what the text does not claim;
- excessive hedging;
- caveats in high-impact positions;
- paragraphs that start with limitations;
- negative framing where positive framing would work;
- explanations added only to prevent hypothetical misunderstanding;
- self-undermining contribution statements;
- unnecessary "not X but Y" structures;
- redundant "however", "nevertheless", or "although" transitions.
Revise any item that weakens the text without improving accuracy.
## Rewrite Procedure
1. Identify the function of the defensive sentence.
Classify it as one of:
- unnecessary disclaimer;
- necessary scope condition;
- real methodological limitation;
- useful conceptual contrast;
- evidence-based qualification;
- redundant clarification.
2. Delete unnecessary disclaimers.
Remove any sentence that does not add evidence, scope, logic, conceptual precision, or necessary reader guidance.
3. Convert defensive limitation into positive scope.
Prefer:
> The analysis focuses on urban governance cases from 2015 to 2023.
Avoid:
> We do not claim that these cases are representative of all urban governance contexts.
4. Replace hedging with precision.
Prefer:
> The evidence indicates that X influences Y in these cases.
Avoid:
> This may suggest that X could potentially influence Y.
If uncertainty is real, specify its source:
> The available evidence supports this interpretation, although the design does not estimate population-level effects.
5. Rebuild the paragraph around the main point.
Ensure the paragraph has:
- a clear topic sentence;
- one main job;
- a logical sequence;
- no repeated caveats;
- no apology-like framing;
- a direct connection to the larger argument.
## Writing Principles
Lead with the claim. Start paragraphs with the point, not with a caveat.
Use positive scope. State what the text examines, explains, tests, compares, or contributes.
Strengthen with evidence, not apology. When a claim feels too broad, improve the concepts, evidence, causal logic, scope, or paragraph structure instead of adding protective caveats.
Keep one paragraph, one job. Do not mix argument, caveat, apology, exception, and clarification in the same paragraph.
Use contrast only when the contrast itself is part of the argument. Avoid reflexive "not X but Y", "rather than", "instead of", "to be clear", and "it should be noted that" structures.
## Technical Plans and SOPs
In Chinese technical plans, SOPs, reports, and presentations:
Remove redundancy and admonitory tone while preserving technical meaning, applicability conditions, prohibitions, and operational purpose. Do not change the operation to make the text sound more concise or specialized.
- **State the plan directly:** Give the procedure, parameters, prerequisites, and findings. Remove commentary about the writing only when it adds no substantive information. Keep phrases such as “用于阐明机制” when they state a real research purpose.
- **Name technical prerequisites:** Replace vague wording such as “在条件允许时” with concrete prerequisites supported by the draft, for example, “标定前提:……”. Keep necessary conditions expressed by “仅在……时” or “若欲……需要……”, or rewrite them equivalently. Do not replace them with an unconditional action; identify missing conditions when they are unspecified.
- **Use operational language:** State the required handling directly and remove admonitory wording such as “切记”, while retaining necessary prohibitions and technical conclusions. Keep “不可互相替代” when it expresses a real restriction. Use “两者独立记录并平行分析” only when the procedure calls for it; this does not convey non-interchangeability.
- **Choose precise verbs:** Simplify redundant phrasing such as “进行……的测量” to “测量……”. “测量” and “表征” are valid technical verbs. Use “标定”, “解耦”, “淬灭”, or “钳定” only when they describe the actual operation; do not substitute a different operation to sound more specialized.
## Preferred Patterns
Use patterns like:
- "This paper examines..."
- "This study shows..."
- "The analysis focuses on..."
- "The evidence indicates..."
- "This design allows..."
- "The results suggest..."
- "The central contribution is..."
- "In this setting, X shapes Y by..."
## Discouraged Patterns
Avoid these unless they are necessary for accuracy:
- "This paper does not claim..."
- "We do not attempt to..."
- "This is not to say that..."
- "This should not be taken to mean..."
- "The goal is not X but Y..."
- "Rather than arguing X, this paper argues Y..."
- "Although this study has limitations..."
- "Of course, this does not fully capture..."
- "It is worth noting that..."
- "To be clear..."
## Examples
Defensive:
> We do not claim that these cases are representative of all contexts.
Stronger:
> The cases show how the mechanism operates across three institutional settings.
Defensive:
> This paper is not intended to provide a comprehensive theory of platform governance, but rather to examine one specific mechanism.
Stronger:
> This paper identifies a mechanism through which platform governance reshapes participation.
Defensive:
> This does not mean that policy design alone determines implementation outcomes.
Stronger:
> Implementation outcomes depend on how policy design interacts with administrative capacity.
Defensive:
> While the sample is limited and cannot capture every variation, it still offers useful insights.
Stronger:
> The sample captures the variation most relevant to the study's theoretical question.
Defensive:
> We are not arguing that this model is superior in every situation.
Stronger:
> The model is most useful when the task requires interpretable comparisons across cases.
## Final Pass
Before producing the final answer, remove any sentence that exists mainly to protect against a hypothetical objection rather than to advance the text. Deliver text that is concise, direct, confident, logically organized, and free of unnecessary disclaimers.
# Additional Rules
Use the requested language, or retain the draft's language. Apply the paper rules to pa質問、コツの共有、使えないことの報告ができます。「役に立った」の多い順です。