スキル who-am-i-writing-for

📦

who-am-i-writing-for

Name: who-am-i-writing-for
Author: prateeks367

コンテンツリビジョン r1 安全 ⚙️ 外部コマンド

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.

対応: Claude Codex Code(CC)

🥉 77 ブロンズ

Maintain this Skill? Claim it 🥉 77 ブロンズ

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の 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 エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/prateeks367-who-am-i-writing-for.md 署名済み manifest GET /api/skills/prateeks367-who-am-i-writing-for/manifest 署名済み lockfile GET /api/skills/prateeks367-who-am-i-writing-for/lockfile

テストする

「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.

セキュリティ監査

安全

v1 • 2026/10/2 バージョン別レポートを開く

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)

SKILL.md:81 SKILL.md:84 SKILL.md:86

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。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バッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/prateeks367-who-am-i-writing-for/security.svg)](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.

これらのプロンプトを試す

Identify Initial Reader Questions

Here are my posts and reader comments: [evidence]. What questions are readers asking? Use their wording and state where evidence is missing.

Compare Reader and Writer Vocabulary

Compare these posts [posts] with these responses [responses]. List reader terms beside my terms and explain mismatches without inventing audience traits.

Assess an Audience Mismatch

I intend to reach [audience]. Review [posts, responses, and engagement evidence]. Identify observed reader questions, supported audience differences, and evidence gaps.

Build a Connected Evidence Review

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?

Provide posts, comments, replies, messages, and available engagement data. Focus on people who engage rather than only on followers.

Can this skill create a traditional persona?

It produces reader questions and vocabulary comparisons instead of a fictional profile. It does not invent demographics or named characters.

What happens when I have no reader responses?

The skill states that evidence is missing and stops rather than inventing a persona. Gather real engagement and responses before requesting audience conclusions.

Do I need VoiceMOAT?

No. You can supply evidence directly. Optional VoiceMOAT access adds analytics, posts, and voice insights through a connected Pro or Enterprise account.

Which AI tools are supported?

The skill supports Claude, Codex, and Claude Code. Connector availability depends on your environment and account access.

How reliable are conclusions from a small sample?

Conclusions remain provisional when evidence is limited. The skill identifies missing evidence and explains what would strengthen the audience picture.

開発者情報

作成者

prateeks367

ライセンス

MIT

Skillstore リビジョン

バージョンに関する注意

作者はバージョンを宣言していません。

リポジトリ

https://github.com/prateeks367/voicemoat-skills/tree/b1749d2bf583cf8c78baf246f6007522e8c052a2/skills/who-am-i-writing-for

参照

5726d703fd79596f46a4232d911221f962d9af1d

メンテナンスの新しさ

2026/10/2

利用状況

0 ダウンロード · 0 閲覧

ファイル構成

📄 SKILL.md