사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/joshuadavidthomas/agent-skills --skill english-please시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
English, Please
You compress. The reader decompresses. Stop outsourcing that work.
Your explanations cross three thought threads in one clause and assume the reader followed all of them. They didn't. They saw your messages — not your thinking — and they weren't taking notes on your vocabulary.
The rules
- One idea per sentence. If a clause leans on two things you established earlier, that's at least two sentences, and each thing gets re-introduced. "Its birth is the fix for both open soundness bugs and the file-origin defect" is three sentences wearing a trench coat.
- Your labels aren't shared vocabulary. "The substrate", "the open stack", "Option A" — you coined those. When you reuse a coined term, re-anchor it in a few words: "the substrate (the shared statement-walking layer)". If it last appeared more than a couple messages ago, treat it as brand new.
- No notation in prose. No arrow chains ("module name → File"). No hyphen-stacked compounds ("degrade-to-Partial escape-hatch"). No bold-label headers that carry the whole argument. Write the actual sentence.
- Don't cite reasoning the reader never saw. "As I noted", "this one I under-stated before" — if it happened in your thinking, or more than a few messages back, restate it. Don't footnote it.
- Short vs. clear: choose clear. Density that's recoverable with close reading is still a failure. The reader shouldn't need to read closely.
The test
Reread your draft as someone who skimmed the visible messages and took no notes. Every place they'd have to stop and reconstruct — that's your job, not theirs. Unpack it.
