メニュー
Plan content marketing strategy. Use when asked about content calendar, content ideas, campaign planning, content strategy, what to write about, or content themes. Triggers on "strategy", "calendar", "content plan", "ideas", "what should I write".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Scaffold a new submission folder under /submissions for a Simulation Bench run, named per the date__benchmark__harness__model[__run_tag] taxonomy, with the standard subdirectories and a starter metadata file. Use this skill whenever the user wants to create, set up, scaffold, prepare, register, or "make a folder for" a new submission, run, attempt, or benchmark trial — phrasings like "create a new submission folder for X harness using Y model", "set up a run for Opus 4.7 on the mine benchmark", "scaffold a vanilla Claude Code submission", "prep a folder for tomorrow's run" should all trigger it. Also trigger when the user describes a harness/model combo and clearly intends to record a run, even if they don't say the word "submission".
Run the Simulation Bench automated harness against a submission folder under /submissions and produce an evaluation_report.json plus a concise summary. Use this skill whenever the user asks to evaluate, score, grade, run the harness on, or check a submission to the Simulation Bench — phrasings like "evaluate submission X", "run the harness on Y", "score the latest run", "did model Z pass?", "check submissions/<folder>" should all trigger it. Also use when the user mentions a submission folder name that follows the date__benchmark__harness__model taxonomy, even if they don't say the word "evaluate".
Create long-form articles (blog posts and LinkedIn articles). Use when asked to write articles, blog posts, tutorials, deep-dives, thought pieces, or long-form content. Triggers on "article", "blog post", "blog", "tutorial", "deep-dive", "thought piece", "long-form".
Core writing engine. Automatically deploys rhetorical devices and voice styling for any copywriting task. Use for any writing request including website copy, ads, course descriptions, or general prose. Triggers on "write", "draft", "create content", "help me write", "copywrite".
Create visual wireframe designs for landing pages. Produces design specs that developers can implement. Use when asked to design a landing page, create a wireframe, plan page layout, or structure a web page. Triggers on "landing page design", "wireframe", "page layout", "design a page".
Create LinkedIn posts. Use when asked to write a LinkedIn post, social media content, or professional social content about simulation, Python, SimPy, engineering, or related topics. Triggers on "linkedin", "post", "social media".
| name | content-strategy |
| description | Plan content marketing strategy. Use when asked about content calendar, content ideas, campaign planning, content strategy, what to write about, or content themes. Triggers on "strategy", "calendar", "content plan", "ideas", "what should I write". |
Help plan and organise content.
| Pillar | Mix | Goal Alignment |
|---|---|---|
| Technical | 40% | Lead generation |
| Industry Commentary | 35% | Thought leadership |
| Personal Stories | 25% | Both (trust building) |
r/Python, r/learnpython, r/simpyr/OperationsResearch, r/engineeringr/Python, r/SideProject8 weeks before:
4 weeks before:
Launch week:
Post-launch:
New Year (January):
Back to Learning (September):
Week of: [DATE]
LINKEDIN:
- Mon: [Technical] Topic:
- Wed: [Industry] Topic:
- Fri: [Personal] Topic:
REDDIT:
- [Subreddit]: [Type] Topic:
EMAIL:
- [Day]: [Type] Subject line:
NOTES:
- [Any upcoming launches, events, or themes to align with]
When ideas come to you:
## [Tech] SimPy event monitoring
Hook: "The feature that took me years to find"
Context: Just discovered resource.count and resource.queue
Status: Ready to write
## [Industry] Why vendors hate Python
Hook: "Every engineer who learns SimPy is a customer lost"
Context: Thinking about incentive structures
Status: Needs more development
## [Personal] The model that almost got me fired
Hook: Delivered truth nobody wanted to hear
Context: Classic early-career mistake
Status: Ready to write
Better to post:
Signs you're forcing it:
What to do instead:
| Goal | Primary content type |
|---|---|
| Generate leads | Technical tutorials with CTA |
| Build authority | Industry hot takes |
| Build trust | Personal stories |
| Launch prep | Problem-aware content |
| Post-launch | Success stories |