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에서 보기