CtrlK
BlogDocsLog inGet started
Tessl Logo

tiktok

TikTok platform integration. Manage videos, view analytics, and track engagement.

34

Quality

31%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./public/skills/0xterrybit/tiktok/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 identifies a clear platform niche (TikTok) which aids distinctiveness, but the capabilities listed are high-level and lack specificity. The absence of a 'Use when...' clause significantly weakens its ability to guide skill selection, and the trigger terms could be expanded to cover more natural user language.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about TikTok videos, TikTok analytics, posting to TikTok, or tracking TikTok engagement metrics.'

Expand trigger terms to include natural variations like 'social media', 'views', 'followers', 'likes', 'TikTok API', 'short-form video', and 'content performance'.

Make capabilities more specific, e.g., 'Upload and schedule TikTok videos, retrieve view/like/share counts, analyze audience demographics, and monitor trending content performance.'

DimensionReasoningScore

Specificity

Names the domain (TikTok) and some actions ('manage videos, view analytics, track engagement'), but these are fairly high-level and not deeply specific concrete actions like 'upload videos, schedule posts, pull view counts'.

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, which per the rubric caps completeness at 2, and the 'what' is also fairly weak, so this lands at 1.

1 / 3

Trigger Term Quality

Includes 'TikTok', 'videos', 'analytics', and 'engagement' which are relevant keywords, but misses common user variations like 'social media', 'views', 'followers', 'likes', 'TikTok API', or 'short-form video'.

2 / 3

Distinctiveness Conflict Risk

The explicit mention of 'TikTok' makes this clearly distinguishable from other social media or video skills; it's unlikely to conflict with YouTube, Instagram, or generic video management skills.

3 / 3

Total

8

/

12

Passed

Implementation

22%

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 with no actionable content. It lists features and example prompts but provides zero concrete guidance on how to interact with TikTok's API — no endpoints, no SDK code, no authentication flow details, and no error handling. Claude would be unable to perform any TikTok integration tasks based solely on this skill.

Suggestions

Add concrete, executable code examples showing actual TikTok API calls (e.g., fetching analytics via the TikTok API with specific endpoints and request/response formats).

Document the authentication flow beyond just setting an environment variable — include token scopes, refresh logic, and error handling for expired tokens.

Provide a step-by-step workflow for at least one core task (e.g., retrieving video analytics) with validation checkpoints such as checking API response status codes.

Either add detailed API reference content or create and reference supporting bundle files (e.g., API_REFERENCE.md, EXAMPLES.md) for advanced features.

DimensionReasoningScore

Conciseness

The content is short but much of it is filler — the feature bullet list and usage examples are vague placeholders that don't add actionable information. The setup section is lean, but the rest doesn't earn its tokens.

2 / 3

Actionability

There is no concrete code, no API endpoints, no executable commands, no SDK usage examples. The 'usage examples' are just natural language prompts with no indication of what tools or APIs to call. Claude would not know how to actually interact with TikTok from this skill.

1 / 3

Workflow Clarity

There is no workflow described at all — no steps, no sequences, no validation. For an integration skill that presumably involves API calls, authentication flows, and data retrieval, the complete absence of any process guidance is a significant gap.

1 / 3

Progressive Disclosure

The content is short and organized with clear headers, which is fine for a simple skill. However, there are no references to any supporting files, and the content is too thin to serve as a useful overview — it's not a monolith, but it's also not a well-structured entry point to deeper content.

2 / 3

Total

6

/

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.

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

Repository
Demerzels-lab/elsamultiskillagent
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.