nano-step/skills/reddit-workflow
skills/reddit-workflow/SKILL.md
Draft a Reddit post optimized for a specific subreddit's rules, tone, and spam filters
$ install --global
skillsauthnpx skillsauth add nano-step/skill-manager skills/reddit-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 22, 2026, 3:45 AM162.9s2 files scanned
SKILL.md
- description:
- Draft a Reddit post optimized for a specific subreddit's rules, tone, and spam filters
Draft a Reddit post that follows a target subreddit's rules, matches community tone, and minimizes the risk of removal by mods or spam filters.
Default language: English (unless the user explicitly requests another language).
Input: The argument after /reddit is either:
- A filled input form (see template below)
- A free-form description of what the user wants to post and where
If the user provides free-form input, extract as much as possible and ask for missing required fields.
Input Template
The user should provide these fields. Fields marked (required) must be collected before drafting.
A. Target
| Field | Required | Description |
|-------|----------|-------------|
| Subreddit | Yes | e.g. r/reactjs |
| Rules/guidelines | Yes | Paste key rules, or say "use defaults" if a common sub |
| Flair options | Yes | Paste the available flair list from the post creation screen |
| Tag options | No | e.g. NSFW, Spoiler, Brand affiliate |
B. Post Intent
| Field | Required | Description |
|-------|----------|-------------|
| Goal | Yes | share / ask feedback / discussion / help / announcement / meta / job |
| Post type | No | text (default) / link / image / video |
| Self-promo | Yes | yes / no |
| Commercial | No | yes / no (default: no) |
| AI-generated content | No | unknown / allowed / disallowed / must disclose |
C. Content
| Field | Required | Description |
|-------|----------|-------------|
| One-liner | Yes | 1 factual sentence describing the project/topic |
| Problem/pain | Yes | 2-4 sentences: what pain point does this address? |
| Key points | Yes | 3-8 bullets: features, arguments, or insights |
| How it works / evidence | No | 2-5 bullets: technical details, benchmarks, limitations |
| Install/Try steps | No | Short (3-4 lines) or detailed (6-8 lines) |
| Links | No | demo, repo, docs, blog (max 4) |
| Feedback questions | Recommended | 2-4 specific questions for the community |
| Tone | No | technical (default) / concise / story |
Steps
-
Collect missing required fields
If any (required) field is missing, use the AskUserQuestion tool to ask for them. Ask all missing fields in ONE prompt (do not ask one at a time).
IMPORTANT: Do NOT proceed to drafting without: Subreddit, Rules, Flair options, Goal, Self-promo flag, One-liner, Problem/pain, Key points.
-
Parse rules and extract constraints
From the pasted rules/guidelines, extract:
- Hard constraints: things that will get the post removed (banned content, required flair, link limits, promo policy, AI policy, specific post days like "Portfolio Sunday")
- Soft preferences: community tone, encouraged behaviors, formatting expectations
- Spam signals: account age requirements, self-promo ratio (e.g. 9:1 rule), link density limits
Summarize constraints internally before drafting.
-
Decide post strategy
Based on constraints + intent:
- Post format: text post (default for self-promo; safer vs spam filters) or link post
- Link placement: near the end (default) or inline (if sub expects it)
- Tone: match community (technical subs -> technical; casual subs -> conversational)
- Structure: Problem -> Solution -> Evidence -> Links -> Feedback questions
-
Select flair + tags
From the user's flair/tag options:
- Pick the most appropriate flair based on post intent and sub conventions
- Recommend tags only if relevant (default: no tags)
- Never select "Brand affiliate" unless user confirms it is commercial/brand content
- Provide 1-line rationale for flair choice
-
Draft the post
Generate:
- 3-5 title options (factual, no ALL CAPS, no opinion words like "best/ultimate", no vote-baiting)
- 1 complete post body (ready to copy-paste) following this structure:
[Hook: 2-4 sentences describing the pain point] [What I built / What this is: 1-2 sentences] **[Section: key points as bullets]** **[Section: how it works / technical details]** (if provided) **[Section: how to try / install]** (if provided) **[Section: looking for feedback]** [2-4 specific questions] [Links: repo, demo, docs - placed at the end] -
Run compliance check
Verify the draft against ALL extracted constraints:
- [ ] Title is factual, not editorialized
- [ ] No vote-baiting language ("upvote", "show some love", "please star")
- [ ] No ALL CAPS in title
- [ ] Self-promo content has substance (not just links)
- [ ] Link count is reasonable (2-4 max)
- [ ] Flair is appropriate for content type
- [ ] No "Brand affiliate" tag on non-commercial content
- [ ] Feedback questions are specific (not generic "what do you think?")
- [ ] Post matches community tone
- [ ] No violations of sub-specific rules (AI policy, post day restrictions, etc.)
If any check fails, fix the draft before presenting.
-
Present the output
Deliver all sections clearly labeled (see Output below).
Output
Always return these sections:
1. Titles (3-5 options)
1. [Title option 1]
2. [Title option 2]
3. [Title option 3]
2. Recommended Flair + Tags
Flair: [selected flair] - [1-line rationale]
Tags: [none / selected tags] - [rationale if any]
3. Post Body (ready to copy-paste)
[Complete post body]
4. Pre-post Checklist
Before posting, verify:
- [ ] Account has recent activity in this subreddit (not just self-promo)
- [ ] Flair is set to: [recommended flair]
- [ ] Post type is: [text/link]
- [ ] No rule violations detected
- [ ] [Any sub-specific check]
5. Risk Assessment
Spam risk: [Low / Medium / High]
Reason: [brief explanation]
Mitigation: [if medium/high, suggest actions like "comment helpfully in 2-3 threads first"]
Guardrails
- NEVER include vote-baiting language in any form
- NEVER use ALL CAPS in titles
- NEVER select "Brand affiliate" without user confirmation
- NEVER skip the compliance check
- NEVER draft without collecting all required fields first
- ALWAYS default to text post for self-promo content (safer)
- ALWAYS place links near the end of the post body
- ALWAYS include specific feedback questions (not generic)
- ALWAYS write in English unless user explicitly requests another language
- If the user's content seems to violate sub rules, warn them and suggest adjustments rather than silently fixing
- If flair options don't have a good match, recommend the closest option and explain why
Related Skills
nano-step/iamhumans
tools
VerifiedTrustedCommunity
Humanization layer for LLM conversation — makes the model sound and respond like a real, thoughtful, embodied human rather than an assistant or chatbot. Use whenever the reply will be read by a human and warmth, presence, or texture matter more than machine-readability. Triggers on any of: "human", "humans", "humanize", "humanization", "be human", "more human", "feel human", "people", "person", "real person", "real human", "friend", "friendly", "like a friend", "respond like a friend", "buddy", "talk", "talking", "talk to me", "talk like a person", "chat", "chatting", "conversation", "converse", "discuss", "discussion", "communication", "communicate", "listen", "just listen", "sit with me", "vent", "venting", "I just want to vent", "company", "presence", "stop being an AI", "stop sounding like a bot", "less corporate", "less robotic", "less formal", "warmer", "warm tone", "empathy", "empathetic", "comfort", "support me", "emotional support", "be honest with me", "be real with me", "real talk", "heart-to-heart", "deep conversation", "casual", "casual chat", "small talk", "chitchat", "say something", "tell me something", and on any emotional / relational / personal-decision / interpersonal context — grief, joy, anger, fear, shame, doubt, loneliness, dating, breakup, conflict, family, parents, sibling, friendship, marriage, divorce, in-laws, kids, parenting, work stress, burnout, career decision, quitting, firing, layoff, anxiety, depression, panic, sleep, dreams, identity, faith, doubt, meaning, mortality, celebration, milestone, achievement, gratitude, apology, forgiveness. Also loads when the user writes in non-English (any language) with emotional weight, when the user's message is shorter than 8 words and affect-laden, when the user types in lowercase fragments, when the user types in ALL CAPS with excitement, or when the user explicitly asks for a friend / mentor / older-sibling / wise-listener voice. Do NOT use for code generation, tool calls, structured data output, SQL, API contracts, or any task where machine-readability matters more than human warmth.
3SKILL.mdUpdated Jun 1, 2026
nano-step/open-design-mcp
tools
VerifiedTrustedCommunity
Use this skill whenever the user mentions open-design, od_generate_design, OD daemon, BYOK design generation, generating HTML mockups from a PRD, creating or managing Open Design projects, saving design artifacts, linting generated HTML, or any of the 10 `od_*` MCP tools (od_list_projects, od_get_project, od_create_project, od_update_project, od_delete_project, od_save_artifact, od_save_project_file, od_lint_artifact, od_compose_brief, od_generate_design). Also trigger on phrases like "generate a design", "create a mockup", "make a landing page", "list my OD projects", "the design daemon", "the streaming design tool", and on any 401/404/422 error coming from an `od_*` tool call. Covers env-var setup (`OD_DAEMON_URL`, auth modes, BYOK), the full PRD → generate → save → lint workflow, error diagnosis, and the safety rails (lint before save, never commit BYOK keys). Triggers even if the user doesn't explicitly say "open-design-mcp" — keyword matches on `od_*` tool names or "design generation" workflows are enough.
3SKILL.mdUpdated May 19, 2026
nano-step/od-workflow
tools
VerifiedTrustedCommunity
Use this skill whenever a user wants the **full Open Design experience** — discovery questions asked first, brand-spec extraction from URLs/files, TodoWrite planning with live updates, 5-dimensional self-critique, polished artifact at the end. Trigger phrases include "design with questions first", "OD-style workflow", "full interactive design brief", "make me a complete landing page" (when the user wants quality over speed), "design my pitch deck", "brand-aware multi-page site", "follow the Open Design playbook", or any request where the user is starting a new design project rather than tweaking an existing artifact. Also trigger on any request that mentions wanting brand consistency across multiple pages or that provides a brand URL/spec. Pair with the `open-design-mcp` tool-reference skill — both loaded together give an LLM the full picture (this skill = workflow choreography; that skill = tool catalog + errors). This skill explicitly does NOT trigger for one-off tweaks ("make the nav stickier", "swap slide 3 image") — use od_generate_design directly for those.
3SKILL.mdUpdated May 19, 2026
nano-step/sync-skill-to-manager
development
VerifiedTrustedCommunity
Sync a locally-developed OpenCode skill to the skill-manager npm package and (if private) the private-skills GitHub repo. Handles per-skill version bumps, public/private classification, build verification, and conventional-commit-style git push. Auto-publish to npm is handled downstream by nano-step/shared-workflows@v1 when the push to master lands. Use this skill whenever the user says 'sync skill', 'publish skill', 'push skill to manager', '/sync-skill-to-manager <name>', or asks to release/distribute a skill they just edited.
3SKILL.mdUpdated May 7, 2026