メニュー
Create Reddit posts. Use when asked to write a Reddit post, Reddit content, or community discussion content about simulation, Python, SimPy, engineering, or related topics. Triggers on "reddit", "subreddit", "r/".
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".
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".
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".
| name | reddit-post |
| description | Create Reddit posts. Use when asked to write a Reddit post, Reddit content, or community discussion content about simulation, Python, SimPy, engineering, or related topics. Triggers on "reddit", "subreddit", "r/". |
Create engaging Reddit posts in Harry's witty, knowledgeable voice, adapted for Reddit's culture of authenticity, technical depth, and zero tolerance for marketing fluff.
This skill uses /copywrite as its core writing engine. The copywrite skill handles:
This skill adds Reddit-specific constraints on top of that foundation.
Reddit requires a fundamentally different approach:
| Aspect | ||
|---|---|---|
| Self-promotion | Soft CTAs acceptable | Instant downvotes, earn trust first |
| Tone | Professional polish | Raw, conversational, peer-to-peer |
| Formatting | Short paragraphs, line breaks | Markdown-rich, code blocks, headers |
| Credibility | Job titles, authority | Show your work, share your code |
| Engagement | Questions drive comments | Genuine value drives upvotes |
| Length | Short (1,000-1,300 chars) | Varies wildly, as long as needed |
The golden rule on Reddit: Give first, always. Promote never (or almost never).
Read ANTI_AI_DETECTION.md before writing any Reddit post. Those rules override the templates below.
Reddit is the most hostile platform for AI-generated content. Users actively hunt for it, downvote it, and call it out publicly. A post flagged as AI is dead, and may get you banned from the subreddit.
These go beyond the shared guide. On Reddit specifically:
Posts should read like forum comments, not essays. If your post could be submitted as a university assignment, it's too polished. It should read like someone typing their experience into a text box.
Headers are optional even on long posts. Plenty of good Reddit posts are just flowing paragraphs of text. Don't default to adding ## headers, use them only when the post genuinely needs them for navigation.
Perfect structure is the #1 giveaway. Real Reddit posts meander. They go on tangents. They circle back to something mentioned three paragraphs ago. They include details that aren't strictly relevant but are interesting.
TL;DRs are one lazy sentence, not crafted summaries. "TL;DR simpy does most of what Arena does and it's free". that's it. No semicolons, no careful phrasing. Just the gist.
Don't end every post with an engagement question. Sometimes you just... stop. When you're done saying what you wanted to say, stop saying it. If you do ask a question, make it specific and genuinely something you want answered, not "What do you think?"
Code and numbers are your credibility, not prose quality. A badly written post with real benchmarks beats a beautifully written post with vague claims. Every time.
Roughness IS the authenticity signal. A slightly disorganised post with genuine insight reads as human. A perfectly structured post with decent insight reads as AI. Reddit will take the messy one every time.
Run the rhetoric selector to get your rhetorical devices:
uv run python .claude/skills/shared/rhetoric_selector.py --type reddit_technical
# or --type reddit_discussion
# or --type reddit_showcase
Review the voice guide: See VOICE_GUIDE.md (or use copywrite's built-in checklist)
Check content pillars: See CONTENT_PILLARS.md
Identify target subreddit(s): tone and depth vary by community:
r/Python, technical, code-focused, moderate lengthr/simpy, niche, deep technical, beginner-friendly toner/learnpython, teaching-focused, patient, step-by-stepr/datascience, analytical, methodology-focusedr/OperationsResearch, academic, rigorous, theory + practicer/engineering, practical, industry-focused, real-world examplesr/SideProject / r/programming, project showcases, broader audienceThe primary format. Has a title and body.
Shares a URL (blog post, tutorial, tool). Title is everything, body is auto-generated from the link.
Contributing to existing threads. Often where the real value is on Reddit.
**bold**, *italic*, headers, bullet lists## for sections in longer posts when they genuinely help readability. Many great Reddit posts use none.[text](url), never bare URLsSee templates folder:
From VOICE_GUIDE.md, with Reddit adjustments:
Keep from the core voice:
Dial up for Reddit:
Dial down for Reddit:
Title: How I model hospital queues with SimPy in ~50 lines of Python
Body:
I keep seeing questions about discrete-event simulation libraries in Python,
and most answers point to heavy frameworks. For 90% of queuing problems,
SimPy is all you need.
I needed to model patient flow through A&E, arrival rates, triage,
treatment, discharge. The commercial quotes came in at £15k+. Which
seemed a bit much for what's essentially a glorified queue.
```python
import simpy
def patient(env, name, hospital):
arrival = env.now
with hospital.request() as req:
yield req
yield env.timeout(treatment_time())
wait = env.now - arrival
wait_times.append(wait)
That's the core of it. Everything else is configuration.
Few things I didn't expect:
Resource handles queuing logic automatically, you don't
build any of that yourselfenv.timeout() with a distribution function gives you stochastic
behaviour, which is most of what simulation actually isThe full model with plotting is about 120 lines. Happy to share if there's interest.
TL;DR: SimPy + basic Python replaces expensive simulation software for most queuing models.
### Discussion Starter (r/OperationsResearch)
**Title:** Genuine question: why is discrete-event simulation still dominated by proprietary tools?
**Body:**
I've been building simulation models for about 8 years now. Started with Arena, moved to Simul8, and three years ago switched entirely to Python/SimPy.
The thing I can't figure out: why does the industry still default to proprietary tools?
The arguments I hear:
The arguments I don't hear but suspect:
I'm not saying commercial tools are useless. But the gap has narrowed to the point where the default should probably be reversed.
## Self-Promotion Guidelines
Reddit has strict self-promotion rules. Follow the **10:1 rule**:
- For every self-promotional post, contribute 10 genuine value posts/comments
- Never post the same content across multiple subreddits simultaneously
- If sharing your own content (blog, tool), disclose it: "I wrote this" / "I built this"
- The post must stand on its own, the link should be supplementary, not required
## Quality Checklist
Before posting, verify:
- [ ] Title is specific, descriptive, and not clickbaity
- [ ] Voice is authentic (would a real person write this in a comment?)
- [ ] Anti-AI detection: would you flag this as AI-written? If yes, rewrite
- [ ] Structure is messy enough . not an essay outline
- [ ] No banned AI phrases (see [ANTI_AI_DETECTION.md](../shared/ANTI_AI_DETECTION.md))
- [ ] Ending is natural . not a manufactured engagement question
- [ ] No marketing language or CTAs
- [ ] Code examples included where relevant (with proper formatting)
- [ ] Subreddit rules checked (many have specific posting guidelines)
- [ ] Provides genuine value . would you upvote this if someone else posted it?
- [ ] TL;DR is one lazy sentence (not a crafted summary) for longer posts
- [ ] Self-promotion guidelines followed (if linking own content)
- [ ] British spellings used throughout