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 does a good job listing specific TikTok automation capabilities and is clearly distinguishable from other skills due to its platform-specific focus. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could be broader to capture more natural user language variations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to automate TikTok actions, upload videos to TikTok, manage their TikTok account, or check TikTok analytics.'
Include more natural user-facing trigger terms like 'social media', 'TikTok analytics', 'schedule TikTok post', or 'TikTok account management' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: upload/publish videos, post photos, manage content, and view user profiles/stats. Also includes the operational instruction to search tools first for current schemas. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific TikTok automation tasks, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the tasks described. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords 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 mention of 'Rube MCP (Composio)' is technical jargon unlikely to be used by users. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific platform (TikTok) and integration (Rube MCP/Composio). Unlikely to conflict with other skills given the narrow, well-defined niche. | 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 moderate verbosity with duplicated pitfall information and lacks concrete executable examples showing actual MCP tool call syntax. The content would benefit from being split across files and including copy-paste-ready invocation examples.
Suggestions
Add concrete, executable examples of actual MCP tool calls with full parameter structures (e.g., a complete RUBE_SEARCH_TOOLS call and a TIKTOK_UPLOAD_VIDEO call with realistic parameter values).
Consolidate duplicated pitfall information — video format requirements and authentication notes appear in both workflow-specific and general pitfall sections.
Extract the detailed per-workflow parameter lists and pitfalls into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with the quick reference table and core workflow sequences.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is moderately efficient but includes redundant information — the 'Known Pitfalls' section repeats content requirements and video specs already stated in workflow-specific pitfalls. The quick reference table is useful but some content could be tightened. Several pitfall items explain things Claude would know (e.g., 'implement exponential backoff on 429 responses'). | 2 / 3 |
Actionability | Tool names and parameter lists are concrete and specific, but there are no executable code examples or actual MCP call syntax shown. The 'Video Publish Flow' is pseudocode-level rather than showing exact tool invocations with parameter structures. Key parameters like the video file object structure (s3key, mimetype, name) are mentioned but not demonstrated with concrete examples. | 2 / 3 |
Workflow Clarity | Multi-step workflows are clearly sequenced with numbered steps, explicit tool ordering, and validation checkpoints (polling FETCH_PUBLISH_STATUS before publishing). The video upload flow includes a feedback loop for status polling and clear separation of upload vs. publish steps. Error recovery guidance is present (re-authenticate on 401, check error details on failed publishes). | 3 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a quick reference table, but it's a monolithic document (~150 lines of detailed content) with no references to supporting files. The repeated pitfalls sections and detailed parameter lists for each workflow could be split into separate reference files. The external link to Composio docs is helpful but no bundle files support progressive disclosure. | 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
c911a92
- 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.