korean-report-style
From the author
Korean-language conventions for technical reports, progress updates, meeting agendas, software handoffs, architecture documents, runbooks, API references, model evaluations, and consortium deliverables — prose register, framing of shortfalls and risks, terminology accuracy, and structural integrity after edits. Use this whenever writing or revising any Korean document intended for colleagues, partners, clients, or evaluators — 진행현황, 중간보고, 기술보고, 연구노트, 코드베이스 인수인계, 운영 문서, 협의 아젠다, 회의록, 제안서 — and also when the user asks to soften, reframe, tighten, or "말투를 바꿔달라" on Korean text. Apply it even for internal-only documents; the register rules are not about audience politeness but about the document reading as a report rather than as speech.
Install
npx skills add JangHyun-bin/korean-report-skills --skill korean-report-style -a claude-code
Installs to .claude/skills/korean-report-style/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
- Ships scripts we have not reviewedLow
Why 77
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- korean-report-docJangHyun-bin/korean-report-skillsCreate Korean technical and business document artifacts as self-contained HTML and optional PDF — progress reports, technical reports, research notes, meeting decks, benchmark write-ups, intermediate reports, and proposals. Use only when the user requests a document artifact rather than an explanation or chat answer, including requests for a 보고서 · 진행현황 · 기술보고 · 연구노트 · 협의 자료 · 중간보고 · 제안서 · HTML · PDF. A review (검수 · 점검) of existing Markdown keeps the Markdown — run the checks and report; typeset only when HTML or PDF is requested. Provides paper and deck templates, SVG figure builders, build-time KaTeX, a bundled Pretendard body font, and browser render QA. Pair with korean-report-style for prose, framing, accuracy, and edit consistency.Testing★ 76
- tech-doc-style-chinesetaxueseek/plainspoken-writing在撰写、改写、校对或审阅中文技术文档、产品文案、界面文案、Markdown 文档、API 说明、操作手册、故障排查或运维文档时使用。采用克制、准确、可扫读的中文技术写作风格;保留原文事实、限制和机器可读内容;按任务读取术语排版、API 状态文案、项目覆盖或受控中文技术写作参考。Engineering★ 68
- technical-writingmichael-denyer/pstack-claudeLayered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.Writing★ 3.4K
- plain-koreanOutlineDriven/outline-driven-developmentUse when Plain English·Plain Language 원칙으로 한국어 작성·교정·검토, 쉽게 써 줘·명확하게 고쳐 줘·관료적인 표현 줄이기·쉬운 한국어/plain Korean·독자 중심 설명문·이메일·공지·README용, 의미·조건·전문용어 보존, 엄격 통제·절차는 ste-korean 우선, 원문보존·맞춤법만 요청 시 문체 유지Other★ 54
- ste-koreanOutlineDriven/outline-driven-developmentUse when Korean tech docs need unofficial ASD-STE controlled wording, single-step procedures, unified terms; not for plain readability (use plain-korean), official or English STE.Other★ 54
- writing-guidelinesrohitg00/pro-workflowApply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".Writing★ 2.9K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in