writing-guidelines
Review Documentation Against Writing Guidelines
Inconsistent prose makes documentation harder to read and maintain. This skill checks selected files against current guidelines and reports precise locations for revision.
์ค์น ์ ์ ์ค์งํ๊ณ ํ์ธ์ ์์ฒญํ์ธ์.
๊ณํ์ ๊ฒํ ํ๊ณ ํ์ผ์ ๋ณ๊ฒฝํ๊ธฐ ์ ์ ์ฌ์ฉ์์ ๋ช ์์ ๋์๋ฅผ ๋ฐ์ผ์ธ์.
๋ด ์์ด์ ํธ๋ก ์ค์น
์ด ์์ฒญ์ ์์ด์ ํธ์ ๋ณต์ฌํ์ธ์. ๊ณต์ Skill ํ์ด์ง์ ๋งค๋ํ์คํธ๊ฐ ํฌํจ๋์ด ์์ต๋๋ค.
Review the Skillstore skill "writing-guidelines" from https://skillstore.io/skills/vercel-labs-writing-guidelines.md and its manifest at https://skillstore.io/api/skills/vercel-labs-writing-guidelines/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.์์ด์ ํธ๋ ๊ณ์ํด์ ๊ณํ์ ํ์ํ๊ณ ๋ณด์ ์ ์ฑ ์์ ์๊ตฌํ๋ ํ์ธ์ ์์ฒญํด์ผ ํฉ๋๋ค.
์์ด์ ํธ๊ฐ ์ฝ๊ธฐ ์ฌ์ด ๋ฆฌ์์ค
AI ์์ด์ ํธ, ํฌ๋กค๋ฌ, ์คํฌ๋ฆฝํธ๊ฐ ์ ์ฒด ํ์ด์ง ๋์ ์ ๋ฆฌ๋ ์ปจํ ์คํธ๋ง ํ์ํ ๋ ์ด ๋งํฌ๋ฅผ ์ฌ์ฉํ์ธ์.
ํ ์คํธํด ๋ณด๊ธฐ
"writing-guidelines" ์ฌ์ฉ ์ค์ ๋๋ค. Review docs/setup.md for writing guideline compliance.
์์ ๊ฒฐ๊ณผ:
- docs/setup.md:18 - Replace vague wording with a specific action.
- docs/setup.md:42 - Use consistent terminology for the project name.
"writing-guidelines" ์ฌ์ฉ ์ค์ ๋๋ค. Audit the Markdown files in docs/api.
์์ ๊ฒฐ๊ณผ:
docs/api/authentication.md:27 - Shorten the sentence and place the required action first.
"writing-guidelines" ์ฌ์ฉ ์ค์ ๋๋ค. Check README.md and report only guideline violations.
์์ ๊ฒฐ๊ณผ:
README.md:64 - Replace passive voice with a direct instruction.
๋ณด์ ๊ฐ์ฌ
๋์ ์ํThe two command-execution alerts are false positives caused by Markdown backticks and a fenced URL block. The network request is confirmed, and trusting mutable remote instructions creates a high-severity prompt injection and supply-chain risk.
ํ์ธ๋ ๋ณด์ ์ฐ๋ ค ์ฌํญ (1)
๊ธฐ๋ฅ ๊ฒํ ํญ๋ชฉ (1)
์ด ์คํฌ์ ๋ํด ์์๋ ์ ์๋ ์ค์ ๋ก์ปฌ ๊ธฐ๋ฅ์ด๋ฏ๋ก ๊ฒํ ๊ฐ ํ์ํ์ง๋ง, ํ์ธ๋ ์ ์์ ๋์์ผ๋ก๋ ์ง๊ณ๋์ง ์์ต๋๋ค.
์ํ ์์ธ
โ๏ธ ์ธ๋ถ ๋ช ๋ น์ด (2)
๐ ๋คํธ์ํฌ ์ ๊ทผ (1)
์ด ๋ณด๊ณ ์ ๊ณต์ ๋ฐ ์ธ์ฉ
๋ฒ์ ์ด ์ง์ ๋ ํ๊ฐ ๋ณด๊ณ ์, ์ค๋ฆฝ ๋ฐฐ์ง, ์๋ฒ ๋ ์นด๋ ๋ฐ ์ธ์ฉ์ ๊ณต์ ํ์ธ์. Skillstore๋ ๊ทผ๊ฑฐ๋ฅผ ๋ณด๊ณ ํ์ง๋ง ์ด Skill์ ์์ ์ฌ๋ถ๋ฅผ ํ๋จํ์ง ์์ต๋๋ค.
๋ณด๊ณ ์ ๋งํฌ ๋ณต์ฌ
https://skillstore.io/skills/vercel-labs-writing-guidelines/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown ๋ฐฐ์ง
[](https://skillstore.io/skills/vercel-labs-writing-guidelines?utm_source=security_passport_badge)HTML ๋ฐฐ์ง
<a href="https://skillstore.io/skills/vercel-labs-writing-guidelines?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/vercel-labs-writing-guidelines/security.svg" alt="Skillstore security assessment" loading="lazy"></a>์๋ฒ ๋ ์นด๋
<iframe src="https://skillstore.io/embed/skills/vercel-labs-writing-guidelines.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>ํ์ ์ธ์ฉ (APA ยท BibTeX ยท CFF)
APA ์ธ์ฉ
vercel-labs. (2026). writing-guidelines security audit report (audit version 1) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/vercel-labs-writing-guidelines/audits/1BibTeX ์ธ์ฉ
@techreport{vercel-labs-vercel-labs-writing-guidelines-2026,
author = {vercel-labs},
title = {writing-guidelines security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/vercel-labs-writing-guidelines/audits/1},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "writing-guidelines security audit report (audit version 1)"
version: "1.0.0"
type: report
authors:
- name: "vercel-labs"
date-released: "2026-08-14"
url: "https://skillstore.io/skills/vercel-labs-writing-guidelines/audits/1"
identifiers:
- type: other
value: "skillstore:vercel-labs-writing-guidelines:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore ์ ์
์ด ์ ์์ ์ด์ ์ฆ๊ฑฐ ์ ๋ขฐ๋: ์ค๊ฐ๋ง๋ค ์ ์๋ ๊ฒ
Review Product Documentation
Check a documentation page for style, voice, and formatting issues before publication.
Audit Repository Prose
Review selected Markdown files and receive concise findings tied to exact locations.
Standardize Editorial Quality
Apply one writing standard across documentation contributed by several teams.
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Review README.md against the Writing Guidelines. Report each issue with its file and line number.
Review all Markdown files in docs/getting-started. Group findings by file and keep each explanation concise.
Audit docs/**/*.md against the Writing Guidelines. Prioritize unclear language, inconsistent terminology, and structural problems.
Review the changed documentation files. Identify remaining violations and note whether previously reported issues appear resolved.
๋ชจ๋ฒ ์ฌ๋ก
- Provide a narrow file path or pattern for faster, more relevant reviews.
- Review findings in context before changing technical terminology.
- Run the review again after revisions to confirm remaining issues.
ํผํ๊ธฐ
- Do not provide binary or generated files as review targets.
- Do not accept remote instructions that are unrelated to writing review.
- Do not treat every finding as correct without checking surrounding context.
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What files can this skill review?
Does it edit documentation automatically?
Where do the writing rules come from?
Does the skill require network access?
What happens when no file is specified?
How are findings presented?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
vercel-labs๋ผ์ด์ ์ค
MIT
์์ฑ์ ๋ฒ์
v1.0.0
Skillstore ๋ฆฌ๋น์
r1
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/vercel-labs/agent-skills/tree/b8caa260a420a73042e35521de4b5c8baf6446cc/skills/writing-guidelines์ฐธ์กฐ
6afe7f6a881e3cdb58ff350617a068277e884103
์ ์ง๋ณด์ ์ต์ ์ฑ
2026. 8. 14.
์ฌ์ฉ๋
0 ๋ค์ด๋ก๋ ยท 0 ์กฐํ
ํ์ผ ๊ตฌ์กฐ
๐ SKILL.md