jianshuo/claude-skills / wjs-promoting-skills
wjs-promoting-skills
UnverifiedUse when the user wants to set up automated daily promotion / marketing for their Claude Code skills — researching how top skills are promoted on marketplaces (ClawHub / openclaw / SkillsMP / agentskills.io), generating a per-skill marketing plan, auto-posting to X (Twitter) via xurl, and drafting community discussion posts (Reddit / HN / Discord). Triggers — "推广 skills", "营销 skills", "自动发推广", "每天自动推广", "skill marketing", "promote my skills", "/wjs-promoting-skills".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.5 KB |
| com.jianshuo.wjs-promoting-skills.plist.template | other | 1014 B |
| daily.shexecutable | script | 6.9 KB |
| list-skills.shexecutable | script | 1.3 KB |
| make-plan.shexecutable | script | 1.3 KB |
| outbox/.gitignore | other | 39 B |
| pick-next-skill.shexecutable | script | 2.3 KB |
| prompts/community-drafts.md | markdown | 2.6 KB |
| prompts/daily-post.md | markdown | 2.0 KB |
| prompts/make-plan.md | markdown | 3.9 KB |
| prompts/research-marketplaces.md | markdown | 3.2 KB |
| research-marketplaces.shexecutable | script | 616 B |
| setup.shexecutable | script | 3.5 KB |
| state/.gitignore | other | 109 B |
| state/README.md | markdown | 944 B |
| uninstall.shexecutable | script | 815 B |
prompts/daily-post.md
View on GitHub# Today's X post for ${SKILL}
## Inputs (read these)
- `~/.claude/skills/${SKILL}/SKILL.md`
- `~/.claude/skills/wjs-promoting-skills/state/plans/${SKILL}.md`
- `~/.claude/skills/wjs-promoting-skills/state/history.jsonl` (last 60 lines)
- `~/.claude/skills/wjs-promoting-skills/state/research.md`
## Task
Write **one** X post (≤ 280 chars) promoting `${SKILL}`. Output to `${OUT_TXT}` (a file path provided in env). Nothing else.
## Process
1. **Find which angle to use.** Look at `history.jsonl` — past entries for `${SKILL}` have an `angle` field. Pick the next angle in the rotation defined by the plan. If no history yet → Angle 1.
2. **Check the "what's new" override.** If `git -C ~/.claude/skills/${SKILL} log -1 --since=<last_post_date>` shows commits since last post → switch to Angle 8 (what's new) regardless of rotation.
3. **Draft the post following the chosen angle's template.** Pull concrete details from SKILL.md — never paraphrase to vagueness. Numbers, technical terms, file formats, before/after measurements all stay.
4. **Verify length.** X counts URL as 23 chars. Compute: `length(text_without_url) + 23 + 1 + 1 ≤ 280`. If over, cut bullets, not the hook.
5. **Verify voice.** Forbidden words: "game-changer", "supercharge", "AI-powered", "revolutionary". No rocket / 100 / fire emoji. Hashtag count ≤ 1.
6. **Output**:
- Write the final post text to `${OUT_TXT}` — just the text, no markdown wrapper, no JSON, no preamble.
- On stderr, print one line: `angle=<N> chars=<count> url=<repo URL>`.
## Format reminder
```
<line 1: skill name + one-line value>
<bullet 1>
<bullet 2>
[<bullet 3>]
<repo URL>
[<one hashtag>]
```
The blank lines are real — they render as paragraph breaks in X.
## Constraints
- ≤ 280 chars (URL counts as 23)
- Repo URL on its own line — X auto-renders a preview card
- Don't reveal local file paths
- Don't post if there is no repo URL — write `__NO_REPO__` to `${OUT_TXT}` and exit
- If `history.jsonl` shows `${SKILL}` was posted in the last 7 days → write `__SKIP_TOO_RECENT__` and exit
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |