ak-threads-booster

---
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."
allowed-tools: Read, Glob, Grep
---

# AK體-基於Threads演算法的優化skill

`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:

- find topic angles with real demand
- avoid obvious repetition and red lines
- draft from the user's own voice and history
- review outcomes and feed the learning back into the tracker

## Intent Routing

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.

- Setup / import / initialize / backfill history -> Glob `**/skills/setup/SKILL.md`
- Refresh tracker / update metrics / scrape own profile -> Glob `**/skills/refresh/SKILL.md`
- Analyze a finished post / inspect / AK-review / optimize / improve / 檢查 / 優化 / 診斷 a post the user has written -> Glob `**/skills/analyze/SKILL.md`
- Draft / write from a topic / 起草 / 寫文 (user has **not** written anything yet; generate from a topic) -> Glob `**/skills/draft/SKILL.md`
- Predict likely 24-hour performance / expectation check -> Glob `**/skills/predict/SKILL.md`
- Review actual post performance / compare against prediction -> Glob `**/skills/review/SKILL.md`
- Mine next topics / topic suggestions / 選題 -> Glob `**/skills/topics/SKILL.md`
- Build brand voice / voice analysis -> Glob `**/skills/voice/SKILL.md`

## Routing Rules

1. Do not answer from this file alone when a module exists for the request.
2. Open the matched module and follow its workflow.