tiktok-research
Research TikTok metadata, creators, comments, trends, and benchmark data for organic platform analysis.
What this skill does
# TikTok Research Skill Use this skill for organic TikTok platform research: keyword and hashtag sampling, competitor or creator sampling, profile enrichment, comments, trend and benchmark discovery, and dataset summaries. Apply shared rulebook and user-guidance rules from `postplus-shared`. ## Do Not Use When - The user wants paid ad intelligence. Route to `tiktok-ad-research`. - The user has already selected sounds and needs local downloads or audio extraction. Route to `tiktok-music-archive-downloader`. - The user asks for external articles, policy, or news rather than TikTok platform data. - The request requires unsupported shop creator analytics. ## Cost Discipline Keep the first pass bounded: - 3-5 strongest queries or 2-4 seed hashtags. - 5-12 results per hashtag or query. - Treat `limit` as the target shortlist or candidate goal, not as a per-query scrape size. - Do not collect comments, related videos, downloads, subtitles, or follower expansion in the first pass unless the current step truly needs them. - Run serially; inspect and refine before expanding. ## Collection Key Routing Use released hosted collection keys only with - `tiktok-videos`: keyword, hashtag, profile URL, music URL, direct video, and content-first creator discovery; local input shape `tiktok-scraper`. - `tiktok-users`: keyword account-search supplement; local input shape `tiktok-user-search-scraper`. - `tiktok-profiles`: profile enrichment from known handles; local input shape `tiktok-profile-scraper`. - `tiktok-related-videos`: graph expansion from shortlisted video URLs. - `tiktok-comments`: focused comment collection. `tiktok-scraper`, `tiktok-user-search-scraper`, `tiktok-profile-scraper`, and `tiktok-comments-scraper` are not hosted collection keys. Do not pass them to the collection runner. ## Creator Discovery Rule For creator discovery with follower-band, recent-activity, local-language, geo-fit, or content-fit constraints, do not default to plain account search. Prefer: 1. collect matched videos with `tiktok-videos`, 2. extract authors from `.items[].authorUsername`, 3. expand around strong seed videos if recall is weak, 4. enrich profiles with `tiktok-profiles`, 5. rank with profile plus content evidence. Use `tiktok-users` only as an account-search supplement unless the user explicitly asks for account-search recall. ## Default Workflow 1. Choose the route first: content-first, handle-first, graph-first, or mixed. 2. Keep the first hosted collection narrow when the brief is simple. 3. Put the compiled input under a `schemaVersion: 1` hosted envelope before running `postplus research collect --skill tiktok-research`. 4. Enrich profiles only after the content or account dataset exists. 5. Expand around strong seed videos only after a promising shortlist exists. 6. Summarize source surface, source query, strongest openings, repeated formats, creators, hashtags, and missing evidence. Keep raw datasets and intermediate files under `.postplus/`; keep final reports or shortlist exports outside `.postplus/` when the user needs them. ## Failure Modes - Do not answer TikTok collection tasks with generic web search. - Do not use paid ad data as organic creator or content evidence. - Do not route profile enrichment through unpublished keys or implementation names. - Do not pass bare local input JSON to hosted collection commands. - Stop on missing auth, unavailable PostPlus Cloud service, stable network failure, malformed collection output, or unsupported collection keys. ## Handoff - Creator shortlist or public contact signals -> `creator-outreach`. - Instagram creator discovery -> `instagram-creator-discovery`. - Paid ad hooks or objectives -> `tiktok-ad-research`. - Local benchmark video files or audio references -> `tiktok-music-archive-downloader`. - Hook, structure, shot, or spoken-line breakdown -> `video-analysis`. ## Public Command Boundary - Choose the smallest matching command or workflow from the user input and run it directly. - Readiness diagnostics: `postplus doctor --skill tiktok-research`. - If an owned CLI or script command fails, report the exact error and stop. Do not bypass the failure with metadata-only answers, readiness probing, local payload rewrites, fallback providers, or unpublished tools. - Use `postplus research schema --collection-key tiktok-comments --json` only when constructing or repairing an unknown request shape. - Hosted collection: `postplus research collect --skill tiktok-research --collection-key tiktok-comments --input <hosted-envelope.json> --output <collection-result.json>`. - Resume a pending collection: `postplus research collect --run-handle <runHandle> --output <collection-result.json>`. - Keep the first pass bounded; expand only after inspecting the first result. - If the CLI returns a quote-confirmation challenge, run `postplus quote confirm --json --challenge-file <challenge.json>` and retry with the returned token.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".