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의 Skill(지시 묶음) 1개, 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질문하고, 팁을 나누고, 안 되는 점을 알려 주세요. "도움이 됨"이 많은 순서예요.