tiktok-automation
Automate TikTok tasks via Rube MCP (Composio): upload/publish videos, post photos, manage content, and view user profiles/stats. Always search tools first for current schemas.
76
65%
Does it follow best practices?
Impact
97%
1.79xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/all-skills/skills/tiktok-automation/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is reasonably strong in specificity and distinctiveness, clearly identifying TikTok automation via a specific toolchain with concrete actions. Its main weaknesses are the lack of an explicit 'Use when...' clause and incomplete coverage of natural trigger terms users might use when requesting TikTok-related tasks.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to post to TikTok, upload TikTok videos, check TikTok analytics, or manage TikTok content.'
Include more natural user-facing trigger terms such as 'social media posting', 'TikTok analytics', 'schedule TikTok content', or 'TikTok account management' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: upload/publish videos, post photos, manage content, view user profiles/stats. Also specifies the tooling mechanism (Rube MCP via Composio). | 3 / 3 |
Completeness | Clearly answers 'what does this do' (automate TikTok tasks via specific tooling), but lacks an explicit 'Use when...' clause. The instruction to 'always search tools first' is operational guidance, not a trigger condition. Per rubric guidelines, missing 'Use when' caps completeness at 2. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'TikTok', 'upload', 'publish videos', 'post photos', 'user profiles/stats', but misses common user variations like 'social media posting', 'TikTok analytics', 'schedule posts', or 'video upload'. The technical terms 'Rube MCP' and 'Composio' are implementation details rather than user-facing trigger terms. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform (TikTok), specific tooling (Rube MCP/Composio), and specific actions. Unlikely to conflict with other skills unless there's another TikTok automation skill. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid workflow clarity with well-sequenced multi-step processes and validation checkpoints, particularly for the video upload/publish flow. However, it suffers from redundancy (content requirements and pitfalls repeated in multiple places), lacks concrete executable examples with actual parameter values, and could benefit from better progressive disclosure by splitting detailed reference material into separate files.
Suggestions
Add concrete examples with actual tool invocation parameters (e.g., a complete TIKTOK_UPLOAD_VIDEO call with sample video object, title, and expected response structure) rather than just listing parameter names.
Eliminate redundancy by consolidating content requirements and pitfalls into a single section rather than repeating video format specs and character limit warnings across multiple workflows.
Remove obvious/vague guidance like 'Content must comply with TikTok community guidelines' and 'check current TikTok guidelines' — these don't add actionable value.
Consider splitting the Known Pitfalls and Quick Reference into a separate REFERENCE.md to reduce the main file's length and improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately verbose with some redundancy — pitfalls are repeated across sections (e.g., video format requirements appear in both Workflow 1 and Known Pitfalls), and some information like 'Content must comply with TikTok community guidelines' is obvious padding. The quick reference table is useful but the overall document could be tightened significantly. | 2 / 3 |
Actionability | Tool sequences are clearly named and ordered, and key parameters are listed, but there's no executable code or concrete examples with actual parameter values. The 'Video Publish Flow' is pseudocode-level rather than showing actual tool invocations with sample payloads. Instructions like 'check current TikTok guidelines' are vague. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with explicit validation checkpoints — particularly the video upload flow which includes polling for status before publishing, and the setup flow which requires confirming ACTIVE connection status before proceeding. Error recovery guidance (re-authenticate on 401, exponential backoff on 429) is present. | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a useful quick reference table, but it's monolithic — all content is inline in one file with no references to separate detailed docs. The Known Pitfalls section repeats information from individual workflows and could be better organized or split out. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- davepoon/buildwithclaude
- Commit
7cc63f3
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.