Social
coreyhaines31/marketingskills
When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.
Mine insights from comments and historical data to recommend the next worthwhile topics.
Install Topics
$ npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install akseolabs-seo/AK-Threads-booster topics --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/akseolabs-seo/AK-Threads-booster.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/topics .claude/skills/topics && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "topics" agent skill from https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/topics into .claude/skills/topics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topics", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/topicsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install akseolabs-seo/AK-Threads-booster topics --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akseolabs-seo/AK-Threads-booster.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/topics .agents/skills/topics && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "topics" agent skill from https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/topics into .agents/skills/topics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topics", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install akseolabs-seo/AK-Threads-booster topics --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akseolabs-seo/AK-Threads-booster.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/topics .cursor/skills/topics && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "topics" agent skill from https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/topics into .cursor/skills/topics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topics", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/akseolabs-seo/AK-Threads-booster.git --path skills/topics--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install akseolabs-seo/AK-Threads-booster topics --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akseolabs-seo/AK-Threads-booster.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/topics .gemini/skills/topics && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "topics" agent skill from https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/topics into .gemini/skills/topics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topics", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install akseolabs-seo/AK-Threads-booster topicsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/akseolabs-seo/AK-Threads-booster.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/topics .github/skills/topics && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "topics" agent skill from https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/topics into .github/skills/topics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topics", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install akseolabs-seo/AK-Threads-booster topics --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/akseolabs-seo/AK-Threads-booster.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/topics .opencode/skills/topics && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "topics" agent skill from https://github.com/akseolabs-seo/AK-Threads-booster/tree/main/skills/topics into .opencode/skills/topics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "topics", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
topics- GitHub stars
- 275
- Token cost
- ~1.8k tokens
- SKILL.md length
- 761 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
Mine insights from comments and historical data to recommend the next worthwhile topics.
- Works in 6 steps: Mine Comment Demand → Read Historical Performance → 5: Read Semantic Freshness → …
- Writing & Content work in your project
- SKILL.md covers Principles and Knowledge, User Data Paths, Execution Flow and Special Scenarios, plus 1 more section
- Calls python
What it does
Topics is an agent skill from akseolabs-seo/AK-Threads-booster. Mine insights from comments and historical data to recommend the next worthwhile topics. Trigger words: 'topics', 'topic', '選題', '寫什麼'.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Writing & Content. The repository describes itself as: AK體 · 數據驅動的 Threads 寫文決策系統。用你的歷史貼文、演算法與社媒心理學，協助選題、起草、發文前診斷、表現預估與復盤。Data-driven Threads writing advisor — topic selection, drafting, diagnosis, prediction & review based on your… The licence is MIT.
When your agent uses it
- Writing & Content work in your project
Example prompts
- “topics”
- “/topics”
Requirements
- Python 3
- Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash, WebSearch
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit cc08954. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrepGlobBashWebSearch
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Topics loads about 1.8k tokens when it runs. Until then it costs about 36 tokens; SKILL.md has 761 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Grep, Glob, Bash, WebSearch
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from akseolabs-seo/AK-Threads-booster at commit cc08954, republished under its MIT licence (© akseolabs-seo). 761 words, ~1,809 tokens.
Download SKILL.mdSave it as
.claude/skills/topics/SKILL.md (or your agent's skills folder).- name
- topics
- description
- Mine insights from comments and historical data to recommend the next worthwhile topics. Trigger words: 'topics', 'topic', '選題', '寫什麼'.
- allowed-tools
- Read, Write, Edit, Grep, Glob, Bash, WebSearch
- version
- 2.0.0
AK-Threads-Booster Topic Recommendation Module
You are the topic recommendation consultant for the AK-Threads-Booster system. Your job is to recommend the next most worthwhile topics for the user's Threads account.
The goal is not to chase generic traffic. The goal is to find topics that fit the user's audience, still have freshness left, and give the next post a better chance to travel.
Principles and Knowledge
Load knowledge/_shared/principles.md before recommending. Follow discovery order in knowledge/_shared/discovery.md. For /topics, also load:
_shared/config.mdand_shared/runtime-budget.md_shared/next-move-engine.mdpsychology-card.mdalgorithm-card.mddata-confidence.md
Load full psychology.md or algorithm.md only in deep mode, when external freshness or suppression risk is ambiguous, or when the user asks for a deep topic audit.
Comment mining matters because it reveals what the audience genuinely cares about, not just what looks broadly popular.
User Data Paths
Search the working directory for:
threads_daily_tracker.jsoncompiled/account_wiki.mdcompiled/account_state.mdcompiled/personal_signal_memory.mdcompiled/next_move_queue.mdcompiled/post_feature_index.jsonlcompiled/cluster_wiki.jsoncompiled/recent_window.mdstyle_guide.mdconcept_library.md
If the tracker is missing, tell the user to run /setup first.
Before loading history or knowledge, resolve runtime.token_mode per knowledge/_shared/runtime-budget.md. If absent or "ask", ask whether this run should use low-token or high-token mode and show the pros/cons. Low-token uses compiled memory + quick cards; high-token reads deeper tracker and knowledge context.
Execution Flow
Step 1: Mine Comment Demand
Read comments from the tracker and analyze:
- recurring questions
- audience pain points
- recurring misconceptions
- promising topic angles
- topics that trigger the strongest emotional reactions
Validated demand from the user's own replies
If the tracker captures the user's own replies, treat them as stronger demand signals than anonymous comments:
- user replied and the commenter asked a follow-up -> highest confidence
- user replied with a long answer -> high confidence
- similar question appears across multiple posts -> medium confidence
- one-off question -> weak signal
Surface validated-demand topics before generic frequency counts.
Step 2: Read Historical Performance
Analyze:
- recent topic distribution
- performance by content type
- topics with the best view / reply / share behavior
- topics with strong DM-share potential if available
Use compiled memory first when fresh; read tracker details only for the clusters or source post IDs that drive the recommendation.
Step 2.5: Read Semantic Freshness
If compiled memory exists, use compiled/cluster_wiki.json and compiled/recent_window.md first. If scripts/update_topic_freshness.py has been run and tracker excerpts are needed, use:
algorithm_signals.topic_freshness.semantic_clusteralgorithm_signals.topic_freshness.freshness_scorealgorithm_signals.topic_freshness.fatigue_riskalgorithm_signals.topic_freshness.days_since_last_similar_postalgorithm_signals.topic_freshness.recent_cluster_frequency
Use these fields to:
- map each candidate into a likely semantic cluster
- suppress candidates with
fatigue_risk = highunless the reframe is strong - boost candidates whose cluster has been untouched for 14 or more days and historically performs well
If those fields are null, tell the user they can run:
python scripts/update_topic_freshness.py --tracker ./threads_daily_tracker.json
python scripts/build_compiled_memory.py --tracker ./threads_daily_tracker.jsonContinue with comment demand and historical performance if freshness fields are unavailable.
Show full SKILL.md (322 more words)Show less
Step 3: Build Candidate Topics
Generate candidates using:
- Next Move Engine state (
account_state,personal_signal_memory, andnext_move_queue) when available - recent topic distribution
- historical performance
- comment demand
- time since the last post
- content-type balance
- semantic-neighborhood fit
- concept-library extension opportunities
Step 3.5: External Freshness Filter
Before finalizing recommendations, check each candidate with WebSearch.
Classify each candidate:
- Green - recommend as-is
- Yellow - recommend with a sharper angle or reframe
- Red - drop because the topic is too saturated and no fresh angle is clear
Replace Red candidates when possible so the user still gets 3-5 strong options.
If WebSearch is unavailable, clearly mark every topic as freshness_external: unverified.
Freshness Audit
Each /topics run must append one JSON line per checked candidate to threads_freshness.log:
{"ts":"<ISO>","run_id":"<uuid4>","skill":"topics","candidate":"<topic slug>","status":"performed|unavailable|skipped_by_user","verdict":"green|yellow|red","web_search_query":"<query or null>"}Do not mark a search as performed if it did not run.
Step 4: Output Recommendations
Start by naming the recommended next move in the user's language. If the user writes in Chinese, avoid unnecessary English jargon and explain internal IDs such as S2 in Chinese. If the user writes in English, professional English terms are fine; still explain AK-specific IDs the first time.
Recommend 3-5 topics. For each one, include:
### Recommendation 1: [Topic Name]
- Source: Comment demand / Historical high performer / Concept extension / Content balance
- Reasoning: [Specific data-backed reason]
- Related historical posts: [Best comparable post and why it matters]
- Estimated range: [Directional only when data is thin]
- External freshness: Green / Yellow with reframe / Unverified
- Self-repetition risk: None / Recent / High
- Suggested angle: [1-2 viable angles]
- Notes: [concept-library reminder, comment demand note, or freshness caution]Special Scenarios
If the user has a topic bank
Read it and integrate it, but do not modify it.
If the user has been quiet for several days
If the last post was 3 or more days ago:
- mention that the comeback post has extra importance
- bias toward a topic type the user historically handles well
If data is thin
Use knowledge/data-confidence.md.
- no comment data -> say recommendations are based mostly on historical performance
- fewer than 5 posts -> do not pretend the signal is strong; ask for more history or pasted samples
Output Format
Comment Insights Summary
- top recent repeated questions
- the topic with the strongest emotional reaction
Recommended Topics
- ordered by priority
- each one backed by evidence
Reminders
- time since the last post
- recent topic distribution
- any freshness or repetition warnings
© akseolabs-seo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/topics of akseolabs-seo/AK-Threads-booster.
Open the folder on GitHubat commit cc08954
Compare with similar skills
Topics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Topics this skillakseolabs-seo/AK-Threads-booster | 275 | — | ~1.8k | Automated safety check: Notes | MIT | |
| Socialcoreyhaines31/marketingskills | 54k | 4 repos | ~4.5k | Automated safety check: Pass | MIT | |
| HumanizerAzure-Samples/interview-coach-agent-framework | 173 | 38 repos | ~5.8k | Automated safety check: Pass | MIT | |
| Avoid AI Writingconorbronsdon/avoid-ai-writing | 4.9k | 3 repos | ~8.1k | Automated safety check: Pass | MIT | |
| JavaScript Concept Fact Checkerleonardomso/33-js-concepts | 67k | 1 repos | ~5k | Automated safety check: Pass | MIT | |
| User-Facing Text Cleanupguillaumemeyer/watermarks-remover | 24k | — | ~3.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Humanizer
Azure-Samples/interview-coach-agent-framework
Remove signs of AI-generated writing from text. An agent skill from Azure-Samples/interview-coach-agent-framework.
Avoid AI Writing
conorbronsdon/avoid-ai-writing
Audit and rewrite content to remove AI writing patterns ("AI-isms").
JavaScript Concept Fact Checker
leonardomso/33-js-concepts
Verifies the technical accuracy of JavaScript concept pages by checking code examples, MDN and ECMAScript claims and external links through a five-phase method.
User-Facing Text Cleanup
guillaumemeyer/watermarks-remover
Audits prose for invisible Unicode characters and rewrites it while keeping facts, citations, code and required disclosures unchanged and the writer's voice intact.
Install Anti Slop
trycompai/crm
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository.
More from akseolabs-seo/AK-Threads-booster
All 12 skills in this repoVoice
akseolabs-seo/AK-Threads-booster
Deep analysis of user's historical posts and comment replies to build a comprehensive Brand Voice profile.
Optimize
akseolabs-seo/AK-Threads-booster
Self-contained compound loop: read threadsskilllearnings.log, cluster the misses, propose concrete sub-skill rule edits, and apply them with the user's approval.
Panel
akseolabs-seo/AK-Threads-booster
Launch or prepare the optional local visual panel for AK-Threads-Booster.
Update
akseolabs-seo/AK-Threads-booster
Check AK-Threads-Booster for upstream GitHub updates, safely fast-forward the local skill repo, or install an opt-in weekly Codex automation that keeps the skill on the latest version.
Draft
akseolabs-seo/AK-Threads-booster
Select a topic and generate a draft based on the user's Brand Voice.
Refresh
akseolabs-seo/AK-Threads-booster
Refresh threadsdailytracker.json. An agent skill from akseolabs-seo/AK-Threads-booster.
Related
Categories
Questions about Topics
What does Topics do?
Mine insights from comments and historical data to recommend the next worthwhile topics. Topics is an agent skill from akseolabs-seo/AK-Threads-booster. Mine insights from comments and historical data to recommend the next worthwhile topics.
When should I use Topics?
Topics fits situations like: writing & Content work in your project.
How do I install Topics in Claude Code?
Run `npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a claude-code`. Or copy the skill folder (skills/topics in akseolabs-seo/AK-Threads-booster) into .claude/skills/topics in your project. Claude Code loads it when a task matches its description.
How do I install Topics in Codex?
Run `npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a codex`. Or copy the skill folder (skills/topics in akseolabs-seo/AK-Threads-booster) into .agents/skills/topics in your project. Codex loads it when a task matches its description.
Can I use Topics in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add akseolabs-seo/AK-Threads-booster --skill topics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/topics, .gemini/skills/topics, .github/skills/topics and .opencode/skills/topics in your project.
What does Topics need to run?
Going by SKILL.md and its folder, Topics needs the command-line tools its instructions call (python). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash, WebSearch.
Does Topics access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Topics safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Topics use?
Topics is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Topics use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Topics?
Skills that share tags, products or a category with Topics: Social (coreyhaines31/marketingskills, 54k stars), Humanizer (Azure-Samples/interview-coach-agent-framework, 173 stars), Avoid AI Writing (conorbronsdon/avoid-ai-writing, 4.9k stars) and JavaScript Concept Fact Checker (leonardomso/33-js-concepts, 67k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Topics?
akseolabs-seo (a GitHub user) maintains it in akseolabs-seo/AK-Threads-booster, which has 275 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on July 3, 2026.
Source: akseolabs-seo/AK-Threads-booster on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.