TikTok platform integration. Manage videos, view analytics, and track engagement.
49
Quality
38%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./public/skills/0xterrybit/tiktok/SKILL.mdQuality
Discovery
40%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 benefits from naming a specific platform (TikTok) which provides strong distinctiveness, but suffers from lack of explicit trigger guidance and somewhat generic action verbs. The capabilities listed are high-level rather than concrete, and there's no 'Use when...' clause to help Claude know when to select this skill.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user mentions TikTok, TikTok videos, TikTok analytics, or social media video content'
Replace generic verbs with specific actions: instead of 'Manage videos', specify 'upload videos, schedule posts, edit captions, delete content'
Include additional natural trigger terms users might say: 'short-form video', 'viral content', 'TikTok account', 'followers', 'views'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TikTok platform) and some actions ('Manage videos, view analytics, and track engagement'), but these are somewhat generic and not comprehensive - doesn't specify concrete actions like 'upload videos', 'schedule posts', 'download metrics', etc. | 2 / 3 |
Completeness | Describes what it does (manage videos, view analytics, track engagement) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this is weaker than that. | 1 / 3 |
Trigger Term Quality | Includes 'TikTok' which is a strong natural keyword, plus 'videos', 'analytics', and 'engagement'. However, missing common variations users might say like 'social media', 'short videos', 'viral', 'followers', 'views', or 'TikTok account'. | 2 / 3 |
Distinctiveness Conflict Risk | 'TikTok' is a highly specific platform identifier that creates a clear niche. Unlikely to conflict with other social media skills (Instagram, YouTube, etc.) due to the explicit platform name. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder - it's concise but provides almost no actionable guidance. It lists features without explaining how to use them, provides no API examples or code, and the 'usage examples' are just natural language queries rather than implementation details. Claude would not know how to actually interact with TikTok's API from this content.
Suggestions
Add concrete API call examples for each feature (e.g., actual HTTP requests or SDK code for fetching analytics, listing videos, etc.)
Provide at least one complete workflow, such as 'How to retrieve video performance metrics' with specific steps and code
Include example response formats so Claude knows what data to expect and how to parse it
Add references to TikTok API documentation or link to detailed feature guides if they exist
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean with no unnecessary explanations. Every line serves a purpose - setup, features list, and usage examples are all minimal. | 3 / 3 |
Actionability | No concrete code, API calls, or executable commands provided. The 'Usage Examples' are just natural language prompts, not actual implementation guidance. Features are listed but not explained how to use them. | 1 / 3 |
Workflow Clarity | No workflows defined. No steps for video management, analytics retrieval, or any other feature. Just a feature list without any process or sequence. | 1 / 3 |
Progressive Disclosure | Content is brief and organized into clear sections, but there are no references to additional documentation for the detailed features mentioned. The features list suggests complexity that isn't addressed anywhere. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
45f9fac
Table of Contents
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.