스킬 tech-writing-proofread

📦

tech-writing-proofread

Name: tech-writing-proofread
Author: alapha888

콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어

Proofread English Technical Documents

Technical drafts can contain language errors and inconsistent terminology that make instructions harder to follow. This skill provides specific corrections, reasons, and issue counts while preserving the authorial voice.

지원: Claude Codex Code(CC)

🥉 77 브론즈

Maintain this Skill? Claim it 🥉 77 브론즈

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

Review the Skillstore skill "tech-writing-proofread" from https://skillstore.io/skills/alapha888-tech-writing-proofread.md and its manifest at https://skillstore.io/api/skills/alapha888-tech-writing-proofread/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/alapha888-tech-writing-proofread.md 서명된 manifest GET /api/skills/alapha888-tech-writing-proofread/manifest 서명된 lockfile GET /api/skills/alapha888-tech-writing-proofread/lockfile

테스트해 보기

"tech-writing-proofread" 사용 중입니다. The system call the callback. Examples are available on github.

예상 결과:

1. [Grammar] Original: The system call the callback. Suggestion: The system calls the callback. Reason: Singular subject requires calls.
2. [Proper noun] Original: github. Suggestion: GitHub. Reason: Use official product casing.
Statistics: 2 items; grammar 1, proper noun 1.

"tech-writing-proofread" 사용 중입니다. Register a callback function. The callback function handles errors. The callback handles completion. Simply invoke the handler.

예상 결과:

1. [Terminology] Original: The callback handles completion. Suggestion: The callback function handles completion. Reason: Use the most frequent term consistently.
2. [Style] Original: Simply invoke the handler. Suggestion: Invoke the handler. Reason: Remove filler.
Statistics: 2 items; terminology 1, style 1.

보안 감사

안전

v1 • 2026. 10. 6. 버전별 보고서 열기

All six static findings are false positives caused by Markdown backticks and plain-text example fences. No evidence found of executable commands, data exfiltration, or prompt injection in SKILL.md.

스캔된 파일

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

⚙️ 외부 명령어 (6)

SKILL.md:19 SKILL.md:22 SKILL.md:27 SKILL.md:35-37 SKILL.md:37-41 SKILL.md:41-49

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

https://skillstore.io/skills/alapha888-tech-writing-proofread/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 배지

[![Skillstore security assessment](https://skillstore.io/badges/skills/alapha888-tech-writing-proofread/security.svg)](https://skillstore.io/skills/alapha888-tech-writing-proofread?utm_source=security_passport_badge)

HTML 배지

<a href="https://skillstore.io/skills/alapha888-tech-writing-proofread?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/alapha888-tech-writing-proofread/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

임베드 카드

<iframe src="https://skillstore.io/embed/skills/alapha888-tech-writing-proofread.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 인용

alapha888. (2026). tech-writing-proofread security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alapha888-tech-writing-proofread/audits/1

BibTeX 인용

@techreport{alapha888-alapha888-tech-writing-proofread-2026,
  author = {alapha888},
  title = {tech-writing-proofread security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/alapha888-tech-writing-proofread/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "tech-writing-proofread security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "alapha888"
date-released: "2026-10-06"
url: "https://skillstore.io/skills/alapha888-tech-writing-proofread/audits/1"
identifiers:
  - type: other
    value: "skillstore:alapha888-tech-writing-proofread:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

Review a README

Find language errors, inconsistent product casing, and unclear procedural wording before publishing repository documentation.

Check an API reference

Review terminology, grammatical precision, acronym expansion, and parallel headings without changing technical claims.

Polish a technical tutorial

Identify filler words, sentence errors, and inconsistent instructions while preserving a conversational voice.

이 프롬프트를 사용해 보세요

Proofread a short passage

Proofread this English technical passage: [paste text]. Return an Original / Suggestion / Reason checklist and issue counts.

Review README instructions

Proofread this README in one pass: [paste README]. Check grammar, product casing, inline code formatting, and numbered steps. Preserve the existing voice.

Check API terminology

Review this API reference: [paste reference]. Build a terminology list and flag inconsistent names, nonparallel headings, and unexpanded acronyms. Mark uncertain claims [verify].

Audit a complete tutorial

Proofread this complete tutorial: [paste tutorial]. Check all six review categories, preserve its conversational tone, and avoid paragraph rewrites. Cite lines or short quotes. End with category counts.

모범 사례

Provide the complete document so terminology and tone can be checked consistently.
Identify whether the draft is a tutorial, API reference, blog post, or README.
Review each suggestion and confirm items marked [verify] before applying changes.

피하기

Requesting complete paragraph rewrites instead of specific proofreading suggestions.
Treating suspected factual errors as verified corrections.
Requesting repeated polishing passes without a defined stopping point.

자주 묻는 질문

What kinds of documents does this skill review?

It reviews English technical documents, including READMEs, tutorials, API references, and technical blog drafts.

Does it rewrite my document?

No. It provides specific corrections and reasons while preserving the existing voice and avoiding complete paragraph rewrites.

Does it check technical accuracy?

It flags suspected factual errors for verification. It does not establish technical correctness or silently change uncertain claims.

How does it handle inconsistent terminology?

It identifies multiple names for the same concept and recommends the most frequent form in the document.

What does the output include?

An Original / Suggestion / Reason checklist, line numbers or short quotes, verification flags, and issue counts by category.

Which AI tools are supported?

The report lists Claude, Codex, and Claude Code as supported tools.

개발자 세부 정보

작성자

alapha888

라이선스

MIT

Skillstore 리비전

버전 안내

작성자가 버전을 선언하지 않았습니다.

리포지토리

https://github.com/alapha888/agent-skills-en/tree/f248342d20ae1e47ecfb146ea112a3e76234ff27/skills/tech-writing-proofread

참조

9bbb9af75d2f5ea5acb8fac5aec75713670a067f

유지보수 최신성

2026. 10. 6.

사용량

0 다운로드 · 0 조회

파일 구조

📄 SKILL.md