Unclear labels and inconsistent messages leave people unsure what to do next. This skill writes and reviews interface copy using your existing vocabulary and voice.
Review the Skillstore skill "better-writing" from https://skillstore.io/skills/jakubkrehel-better-writing.md and its manifest at https://skillstore.io/api/skills/jakubkrehel-better-writing/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
All 26 static findings are false positives: Markdown formatting, interface-copy examples, and writing-review labels do not execute commands or collect system information. No evidence found of prompt injection, credential access, data exfiltration, or malicious intent in the reviewed files. Publication decisions remain code-owned.
jakubkrehel. (2026). better-writing security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/jakubkrehel-better-writing/audits/1
BibTeX形式の引用
@techreport{jakubkrehel-jakubkrehel-better-writing-2026,
author = {jakubkrehel},
title = {better-writing security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/jakubkrehel-better-writing/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: "better-writing security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "jakubkrehel"
date-released: "2026-10-09"
url: "https://skillstore.io/skills/jakubkrehel-better-writing/audits/1"
identifiers:
- type: other
value: "skillstore:jakubkrehel-better-writing:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore スコア
このスコアの理由証拠の信頼度: 中
55
アーキテクチャ
85
保守性
87
コンテンツ
65
コミュニティ
83
仕様準拠
作成できるもの
Review Copy Before Release
Review component and locale strings for misleading labels, missing error recovery, and inconsistent terminology.
Draft Product Flow Messages
Write onboarding, empty-state, status, and destructive-confirmation copy that matches the product's established voice.
Prepare Strings for Localization
Identify fragmented sentences, English-only plural logic, and manually formatted dates before translation work begins.
これらのプロンプトを試す
Improve One Error
Rewrite this error with a clear recovery step: [message]. The action is [action], the cause is [cause], and recovery requires [step].
Write an Empty State
Draft empty-state copy for [screen] using these existing strings: [examples]. Include a heading, useful context, and one action that the interface supports.
Review a Destructive Flow
Review [flow] against its actual behavior. Check consequences, affected people, confirmation or undo, action labels, and vocabulary. Provide before-and-after copy with severity and reasons.
Audit Interface and Locale Strings
Inspect [components] and [locale files]. Inventory terminology and voice first. Review recovery, consistency, placeholders, plurals, and locale formatting. Report locations and mark unavailable strings unverified.
ベストプラクティス
Provide surrounding strings, the product vocabulary, and any content style guide before requesting new copy.
Explain actual behavior, recovery options, and irreversible consequences so suggested wording remains accurate.
Review components and locale files together, and explicitly record any unavailable content.
回避
Inventing a new voice or terminology for one isolated screen.
Promising recovery, undo, or actions that the product does not support.
Building sentences from fragments or assuming every language has only singular and plural forms.
よくある質問
What kind of writing does this skill cover?
It covers interface labels, links, errors, empty states, confirmations, status messages, and the vocabulary connecting them.
Does it preserve an existing brand voice?
Yes. It starts with existing copy and flags voice differences only when they cause inconsistency, ambiguity, translation risk, or unsuitable tone.
Can it help prepare copy for translation?
Yes. It recommends complete messages, placeholders, locale-aware plural rules, and Intl formatting. It does not guarantee translation quality.
Does it fix accessibility markup or layout?
No. It addresses accessible wording, but delegates markup, announcements, typography, colors, and translated-string layout to other skills.
How are writing-review results presented?
Findings include severity, location, original text, proposed text, and rationale. Unavailable strings are marked unverified rather than approved.
Which assistants are listed as supported?
The marketplace report lists Claude, Codex, and Claude Code. This package supplies Markdown guidance and examples rather than executable tooling.