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.
Install with Tessl CLI
npx tessl i github:davepoon/buildwithclaude --skill tiktok-automation71
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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.
This description effectively communicates specific TikTok automation capabilities with good distinctiveness through platform and tool specificity. However, it lacks an explicit 'Use when...' clause that would help Claude know exactly when to select this skill, and could benefit from more natural trigger terms users might actually say.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to post to TikTok, manage TikTok content, or check TikTok analytics'
Include additional natural trigger terms users might say: 'social media posting', 'TikTok analytics', 'schedule TikTok content', 'TikTok automation'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'upload/publish videos, post photos, manage content, and view user profiles/stats'. These are clear, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what' with specific actions, but lacks an explicit 'Use when...' clause. The 'when' is only implied through the action descriptions rather than explicitly stated. | 2 / 3 |
Trigger Term Quality | Includes relevant keywords like 'TikTok', 'videos', 'photos', 'upload', 'publish', but missing common variations users might say like 'social media', 'post to TikTok', 'TikTok analytics', or 'schedule posts'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche - TikTok automation via specific MCP tool (Rube/Composio). Unlikely to conflict with other skills due to platform-specific focus and tool specification. | 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 guidance with clear sequencing and validation steps for TikTok automation. However, it lacks concrete executable examples (actual API call structures with sample parameters) and contains some redundancy in pitfall documentation. The content would benefit from tighter editing and actual code/JSON examples showing exact parameter formats.
Suggestions
Add concrete executable examples showing actual tool calls with sample parameter values (e.g., a complete TIKTOK_UPLOAD_VIDEO call with realistic video object structure)
Consolidate repeated pitfalls (video requirements, rate limits) into a single 'Known Pitfalls' section rather than duplicating across workflows
Include a sample response structure for key operations like upload and status check to help with response parsing
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundancy - pitfalls are repeated across sections (e.g., video requirements mentioned multiple times), and some explanations could be tighter. The quick reference table duplicates information already covered in workflows. | 2 / 3 |
Actionability | Provides tool names and parameter lists, but lacks executable code examples. The 'Video Publish Flow' is pseudocode-style numbered steps rather than actual API calls with concrete parameter values. No copy-paste ready examples with real parameter structures. | 2 / 3 |
Workflow Clarity | Clear multi-step sequences with explicit validation checkpoints - notably the upload->poll status->publish flow with explicit 'poll until complete' instructions. Each workflow marks steps as [Required] or [Optional] and includes feedback loops for status checking. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is in one file. The external toolkit docs link is good, but the skill itself is quite long (~180 lines) and could benefit from splitting detailed pitfalls or the quick reference into separate files. | 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 | |
- 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.