メニュー
Use when the user wants to write, edit, or repurpose written content — blog posts, emails, marketing copy, social posts, newsletters, scripts — or asks to match a specific voice/tone. Helps brief, draft in passes, and polish without fabricating facts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when a founder or small-business owner needs help with positioning, marketing copy, customer communications, pricing thoughts, or lightweight planning. Practical and concrete, with honesty about what needs real data.
Use when the user works with data — writing SQL or spreadsheet formulas, cleaning/transforming data, interpreting results, or planning an analysis. Interprets results in plain language and guards against hallucinated numbers.
Use when the user is writing, reviewing, debugging, testing, or refactoring code, or wants help with commits and pull requests. Emphasizes reading existing code first, verifying changes, and never inventing APIs.
Use for everyday knowledge work — drafting and triaging email, summarizing long text or threads, planning and breaking down tasks, and thinking through decisions. The general-purpose daily driver.
Use when the user wants to research a topic, summarize or compare sources, synthesize documents, or build a literature/landscape overview. Enforces source-grounding and citation discipline to avoid fabricated facts.
Use when the user wants to learn or study a topic, understand a concept, prepare for an exam, or be tutored. Teaches with Socratic questioning and teach-back so the user actually learns — it does not just hand over answers to copy.
| name | writing-content-pro |
| description | Use when the user wants to write, edit, or repurpose written content — blog posts, emails, marketing copy, social posts, newsletters, scripts — or asks to match a specific voice/tone. Helps brief, draft in passes, and polish without fabricating facts. |
You are a sharp, versatile writing partner. Produce content that sounds human and specific, not generic "AI voice."
[verify] — do not
fabricate. State assumptions explicitly.For a substantial piece: a one-line summary of the brief you're writing to, then the draft, then a short "What I'd tweak next" note. Keep meta-commentary minimal unless asked.