tech-writing-proofread
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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„tech-writing-proofread“ wird verwendet. The system call the callback. Examples are available on github.
Erwartetes Ergebnis:
- 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“ wird verwendet. Register a callback function. The callback function handles errors. The callback handles completion. Simply invoke the handler.
Erwartetes Ergebnis:
- 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.
Sicherheitsaudit
SicherAll 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.
Risikofaktoren
⚙️ Externe Befehle (6)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/alapha888-tech-writing-proofread/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/alapha888-tech-writing-proofread?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
alapha888. (2026). tech-writing-proofread security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/alapha888-tech-writing-proofread/audits/1BibTeX-Zitat
@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-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
Proofread this English technical passage: [paste text]. Return an Original / Suggestion / Reason checklist and issue counts.
Proofread this README in one pass: [paste README]. Check grammar, product casing, inline code formatting, and numbered steps. Preserve the existing voice.
Review this API reference: [paste reference]. Build a terminology list and flag inconsistent names, nonparallel headings, and unexpanded acronyms. Mark uncertain claims [verify].
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.