who-am-i-writing-for
Identify Your Readers from Real Responses
Fictional personas can distract writers from the questions real readers ask. This skill uses engagement, reader responses, and posts to identify audience questions and vocabulary.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "who-am-i-writing-for" from https://skillstore.io/skills/prateeks367-who-am-i-writing-for.md and its manifest at https://skillstore.io/api/skills/prateeks367-who-am-i-writing-for/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «who-am-i-writing-for». Two readers ask, 'Does this work with no budget?' and 'What if we have no designer?' Our post describes 'resource-efficient creative operations.'
Ожидаемый результат:
- Reader questions: Does this work with no budget? What if we have no designer?
- Vocabulary comparison: readers say 'no budget' and 'no designer'; the post says 'resource-efficient creative operations.'
- Evidence strength: provisional, based on two responses. Collect more comments and compare responses across subjects before expanding the question list.
Использование «who-am-i-writing-for». Connected analytics show tutorial posts received 100 reactions across 2,000 impressions. Opinion posts received 150 reactions across 10,000 impressions.
Ожидаемый результат:
- Tutorial posts: 5% reactions relative to impressions. Opinion posts: 1.5%.
- Tutorials have the higher reaction rate despite fewer total reactions.
- Reader questions and vocabulary remain unknown without responses. These figures do not establish reader demographics.
Аудит безопасности
БезопасноAll three static findings are false positives: Markdown backticks format connector tool names, not executable shell expressions. No evidence found of prompt injection, credential extraction, or data exfiltration in SKILL.md. The optional VoiceMOAT connection describes analytics access without instructions to execute commands or transmit secrets.
Факторы риска
⚙️ Внешние команды (3)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/prateeks367-who-am-i-writing-for/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/prateeks367-who-am-i-writing-for?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/prateeks367-who-am-i-writing-for?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/prateeks367-who-am-i-writing-for/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/prateeks367-who-am-i-writing-for.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
prateeks367. (2026). who-am-i-writing-for security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/prateeks367-who-am-i-writing-for/audits/1Цитата BibTeX
@techreport{prateeks367-prateeks367-who-am-i-writing-for-2026,
author = {prateeks367},
title = {who-am-i-writing-for security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/prateeks367-who-am-i-writing-for/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: "who-am-i-writing-for security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "prateeks367"
date-released: "2026-10-02"
url: "https://skillstore.io/skills/prateeks367-who-am-i-writing-for/audits/1"
identifiers:
- type: other
value: "skillstore:prateeks367-who-am-i-writing-for:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Plan Posts Around Reader Questions
Turn real comments and replies into recurring questions and compare audience vocabulary with the language used in published posts.
Investigate Audience Mismatch
Review who engages and which subjects receive responses to distinguish the observed audience from the audience a business hoped to reach.
Review Topic Performance
Use connected VoiceMOAT posts and analytics to group subjects and compare reactions relative to impressions rather than raw counts.
Попробуйте эти промпты
Here are my posts and reader comments: [evidence]. What questions are readers asking? Use their wording and state where evidence is missing.
Compare these posts [posts] with these responses [responses]. List reader terms beside my terms and explain mismatches without inventing audience traits.
I intend to reach [audience]. Review [posts, responses, and engagement evidence]. Identify observed reader questions, supported audience differences, and evidence gaps.
Use my authorized VoiceMOAT connection to review posts, analytics, and voice insights. Combine these with [reader responses]. Group subjects and compare reactions relative to impressions. Produce six to ten evidence-based questions, vocabulary comparisons, and provisional conclusions. Identify existing reader conversations only when supported.
Лучшие практики
- Provide representative posts and actual responses, with sensitive personal details removed.
- Keep reader wording intact and separate directly observed facts from unsupported audience assumptions.
- Group posts by subject and report sample size, missing evidence, and provisional conclusions.
Избегать
- Inventing demographics, lifestyles, or named characters to make audience research appear complete.
- Treating follower counts or raw reaction totals as proof of reader needs.
- Presenting a few comments as a complete audience picture without stating uncertainty.
Часто задаваемые вопросы
What evidence should I provide?
Can this skill create a traditional persona?
What happens when I have no reader responses?
Do I need VoiceMOAT?
Which AI tools are supported?
How reliable are conclusions from a small sample?
Сведения для разработчиков
Автор
prateeks367Лицензия
MIT
Ревизия Skillstore
r1
Примечание о версии
Автор не указал версию.
Ссылка
5726d703fd79596f46a4232d911221f962d9af1d
Актуальность поддержки
02.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md