threads-distribution-module
Specialized skill for Threads distribution. Short-form text amplification Spoke.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Specialized skill for Threads distribution. Short-form text amplification Spoke.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this skill whenever the user asks to implement, build, fix, ship, add, refactor, migrate, or change ANY code — features, bugs, plugins, skills, migrations, hooks, rules, configs, in any repo. Triggers on 'build X', 'fix Y', 'implement Z', 'ship this to <plugin>', a ticket id with code work. This is the Agentic SDLC pipeline; do NOT hand-roll `codex exec` or ad-hoc git/PR shipping — route through Stage 0 (claim), the 9 core stages, the Gate-A.5 change-manifest gate, Gate-A.7 design-review gate, Stage 5.5/5.6/5.7/5.8 quality gates, and Stage 10 (completion).
Activate real-time prompt sharpening and persona detection. Use when the user says "co-dialectic", "cod", "codi on", "improve my prompts", "prompt sharpening", "teach me to prompt", or wants to improve their AI communication skills. Provides status line, persona system, caliber enforcement, prompt improvement, context management, auto-codification protocols, and auto-verification by stakes (Protocol 8 — fires hallucination-detector / judge-panel / unknown-unknown / canonical-claim verifier automatically before every substantive output, scaled to the stakes of the artifact).
Surfaces one-week and two-week follow-up nudges for applications that are applied and awaiting response, with a plain-text draft ready for the human to approve. Draft-only: never sends. Use when the user asks what to follow up on, stale applications, application nudges, or job-search follow-ups.
Detects explicitly shareable career milestones in the job pipeline and surfaces draft-only brand-post prompts. Fail-closed by firewall design: no shareable flag means no suggestion. Use when the user asks for milestone brand moments, career-to-brand prompts, or shareable pipeline milestones.
Career OS home screen and central router. Two jobs: show the dashboard and route every action to the correct skill. Mission Control reads and presents but never directly edits persistence files.
Maps your network to target companies. Discovers warm intro paths, scores connection strength (5-level scale), ingests new contacts from conversation, and recommends who to reach out to and how. Also detects relationship origin (where/when you met) and cohort clusters (people from the same company/era). Records inbound recruiter DMs that came from the user's public posts as brand-attributed pipeline opportunities. Say "who do I know at [Company]", "how do I know [Name]", "tell me about [Contact]", or "a recruiter DM'd me after seeing my post".
| name | threads-distribution-module |
| description | Specialized skill for Threads distribution. Short-form text amplification Spoke. |
| triggers | ["post to threads","threads distribution"] |
Threads serves as a short-form, conversational Spoke. It operates similarly to X/Twitter but with a different community graph, driving engagement back to the Hub.
Update the campaign tracker with status and execution time.
Content-readiness gate (social-content-readiness-check): three parallel LLM judges
(tone/authenticity, IP/patent firewall, narrative clarity) + metadata completeness.
OAuth CLIs, no API key (claude → gemini → codex fallback). This gate lives in
career-intelligence and is called cross-plugin (same as the other distribution modules).
GATE=$(ls -v ~/.claude/plugins/cache/xos/career-intelligence/*/rules/social-content-readiness-check/HOW.py 2>/dev/null | tail -1)
if [ -z "$GATE" ]; then
echo '{"verdict":"BLOCK","reason":"social-content-readiness-check script not found — plugin may need reinstall","remediation":"Run: claude plugin update career-intelligence@xos --scope user"}'
exit 1
fi
python3 "$GATE" \
'{"text":"<post body>","platform":"threads","title":"<campaign title>","metadata":{"audience":"<target audience>"}}'
Exit 0 = PASS → post. Exit 1 = BLOCK → revise and re-run. Exit 2 = WARN → human approval before posting.