// Threads growth operating system for topic selection, drafting, analysis, prediction, review, and tracker refresh based on the user's own post history.
Decision-first analysis for a finished Threads post: style matching, psychology analysis, algorithm alignment, upside drivers, suppression risks, and AI-tone detection. Use after the user writes a post, or when they ask to analyze, check, inspect, or AK-review a draft.
Select a topic and generate a draft based on the user's Brand Voice. Draft quality depends on Brand Voice completeness. Trigger words: 'draft', 'write', '起草', '寫文'.
Self-contained compound loop: read threads_skill_learnings.log, cluster the misses, propose concrete sub-skill rule edits, and apply them with the user's approval. The fourth step after Plan / Work / Review. Trigger words: 'optimize', 'compound', '優化skill', '自我優化', '閉環'.
Launch or prepare the optional local visual panel for AK-Threads-Booster. Use when the user asks for a dashboard, visual panel, local UI, data cockpit, or quick way to view tracker/compiled data.
Estimate likely 24-hour post performance from the user's historical data. Use after the user writes a post and wants a range estimate, upside view, or expectation check.
Refresh threads_daily_tracker.json. Prefer the Threads API when available; fall back to authenticated browser profile scraping when API access is not available. Trigger words: 'refresh', 'update tracker', 'scrape profile', '更新貼文', '抓最新數據'.
| name | ak-threads-booster |
| description | Threads growth operating system for topic selection, drafting, analysis, prediction, review, and tracker refresh based on the user's own post history. |
| version | 2.0.0 |
| allowed-tools | Read, Glob, Grep |
ak-threads-booster remains the internal skill id for routing and installation.
Use this as the single entry point for the AK Threads workflow.
This skill is for creators who want to pick stronger topics, write posts with clearer upside, and improve over time using their own Threads history.
It is not a viral-post guarantee engine. It is a decision system:
Classify the user's request first, then open and follow one primary module unless the task clearly needs a short sequence.
Each sub-skill is located via Glob **/skills/<name>/SKILL.md so resolution works regardless of where the plugin is installed. Do not assume an absolute path or environment variable.
**/skills/setup/SKILL.md**/skills/refresh/SKILL.md**/skills/analyze/SKILL.md**/skills/draft/SKILL.md**/skills/predict/SKILL.md**/skills/review/SKILL.md**/skills/topics/SKILL.md**/skills/voice/SKILL.md**/skills/panel/SKILL.md**/skills/update/SKILL.mdthreads_skill_learnings.log misses into rule edits) -> Glob **/skills/optimize/SKILL.mdthreads_daily_tracker.json is missing, do not pretend the work is data-backed. Ask for fallback history or use the setup path./analyze. /analyze gives pointed diagnosis and preserves the user's format; it does not rewrite the post. Route to /draft only when the user has no existing text and wants something generated from a topic.brand_voice.md is a composition driver only in /draft. Every other module treats it as observation-only — for flagging drift, never for rewriting the user's submission toward a voice template./draft or /analyze with this offer unless the user asks about maintenance.Look in the working directory for:
threads_daily_tracker.json - canonical machine-readable trackerstyle_guide.md - produced by /setupconcept_library.md - produced by /setupbrand_voice.md - produced by /voice, referenced by /draftposts_by_date.md - human-readable archiveposts_by_topic.md - human-readable topic indexcomments.md - human-readable flat comment logthreads_freshness.log - audit log for /draft and /topics freshness gates, read by /reviewthreads_refresh.log - audit log for /refresh runs, read by /reviewLow-token runtime also looks for derived compiled memory in compiled/:
compiled/account_wiki.mdcompiled/account_state.mdcompiled/personal_signal_memory.mdcompiled/next_move_queue.mdcompiled/post_feature_index.jsonlcompiled/cluster_wiki.jsoncompiled/exemplar_bank.mdcompiled/recent_window.mdcompiled/voice_fingerprint.mdcompiled/voice_fingerprint.jsonThese files are runtime caches only. threads_daily_tracker.json remains the source of truth. If compiled memory is missing, stale, or contradicts the tracker, fall back to the tracker and recommend rebuilding compiled memory.
If legacy Chinese companion filenames already exist, treat them as equivalent companion files instead of forcing a rename.
If only the tracker exists, continue in tracker-only fallback mode when the chosen module allows it. If the tracker is missing, do not pretend the work is data-backed - ask for fallback history or use /setup.
This main SKILL.md declares only the read-only tools it actually uses (Read, Glob, Grep). Each sub-skill declares its own allowed-tools in its frontmatter; some require more:
/draft adds Write, WebSearch, WebFetch/review adds Write, Edit/voice, /setup, /refresh each extend the surface as needed/update uses git through shell commands and may create an opt-in Codex automation when the user explicitly accepts weekly auto-updateWhen auditing permissions, inspect the union of all sub-skill frontmatters, not just this file.
Any sub-skill that writes to threads_daily_tracker.json, style_guide.md, concept_library.md, brand_voice.md, or threads_booster_config.json must follow templates/FAILSAFE.md (backup + atomic rename + keep last 5 backups). Append-only logs (threads_freshness.log, threads_refresh.log, threads_skill_learnings.log) follow the append-only rules in the same file.
Compiled memory files under compiled/ are rebuilt views, not hand-edited state. Rebuild them with scripts/build_compiled_memory.py after tracker-changing runs.
Red-line (R) and signal (S) definitions live in knowledge/_shared/red-lines.md — the single source of truth for both /analyze and /draft. Do not inline R-lists in sub-skill SKILL.md files.
Next-post direction lives in knowledge/_shared/next-move-engine.md. Any "next move" recommendation must pass red-line filtering first, name the S signal it is trying to strengthen, and avoid becoming a formula bank or case-study imitation.
Runtime depth, compiled-memory behavior, and output-mode defaults live in knowledge/_shared/runtime-budget.md. In lite and standard, use knowledge/cards/* before full knowledge/*.md files.
If runtime.token_mode is absent or "ask", ask the user to choose 低 token 版 or 高 token 版 before heavy reading. The question must clearly state the tradeoff: low token is faster and cheaper but less detailed; high token is deeper but slower and more expensive.
Compound loop schema — threads_skill_learnings.log — is defined in knowledge/_shared/compound-log-format.md. /review writes misses to it; /optimize reads it, proposes rule changes, and appends supersedes entries when the user approves edits. No other sub-skill touches the log.
When guidance conflicts, use this order:
SKILL.md — routing and global disciplineskills/<name>/SKILL.md — module-specific workflowknowledge/_shared/*.md — definitions referenced by multiple sub-skills (red-lines, config, discovery, principles, runtime-budget, compound-log-format)knowledge/*.md — deeper knowledge bases (psychology, algorithm, ai-detection, data-confidence, chrome-selectors)templates/* — shape templates (tracker, style-guide, concept-library, FAILSAFE)Rules earlier in this list win. If a sub-skill rule contradicts the main SKILL.md (e.g. routes /analyze requests to /draft), the main SKILL.md wins and the sub-skill is the drift — fix the sub-skill.
A known cross-sub-skill conflict and its resolution:
brand_voice.md usage. /draft treats it as a composition driver. Every other sub-skill treats it as observation-only. This is stated here (Routing Rules #7) and re-stated in each sub-skill's Scope section. If those ever disagree, this file wins.