write-a-public-faq-answer
Write a public FAQ answer that directly resolves a real question with accurate scope, plain language, examples, limitations, and next steps. Use when readers repeatedly need the same trustworthy explanation.
ソース情報
- リポジトリ
- protosphinx/sphinxstack
- ソースの最終更新活動
- 2026年7月29日 13:55
- 検出された SKILL.md の言語
- 英語
- スター
- 3
- フォーク
- 0
インストール方法
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
ソースファイルを確認
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
ファイルエクスプローラー
2 ファイルSKILL.md を表示中
SKILL.md
ソースの指示 · 読み取り専用プレビュー- name
- write-a-public-faq-answer
- category
- write
- description
- Write a public FAQ answer that directly resolves a real question with accurate scope, plain language, examples, limitations, and next steps. Use when readers repeatedly need the same trustworthy explanation.
# write-a-public-faq-answer
Answer the question in the first sentence.
## When to use
- Use for product, service, policy, event, public-information, or support content.
- Do not expose private operations, security details, personal data, or promises beyond current authority.
## Procedure
1. Record the exact reader question, audience, context, source of truth, owner, and update trigger.
2. Write a direct one-sentence answer before explanation.
3. Add scope, conditions, steps, examples, deadlines, fees, or evidence only as needed.
4. State exceptions, limitations, and what the answer does not cover.
5. Provide accessible next steps, contacts, escalation, or authoritative links.
6. Test for plain language, translation ambiguity, accessibility, search phrasing, and mobile readability.
7. Verify current facts, links, dates, and owner approval before publication.
## Done
- A FAQ answer draft records question, direct answer, scope, conditions, limitations, next steps, sources, owner, and review date
- Fact, link, date, plain-language, accessibility, search, limitation, and approval checks verify publication
GitHubで見る