CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/tiktok-automation/SKILL.md

The canonical home for this skill is tiktok-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and well-structured, with exact tool slugs, parameter schemas, and validation checkpoints in the core upload/publish flow. Its main weaknesses are redundancy (pitfalls and tool listings repeated across sections, the Quick Reference table, and the Common Patterns section) and the lack of an explicit error-recovery loop inside the main workflow steps.

Suggestions

De-duplicate: the "Video Publish Flow" pattern, "Known Pitfalls" section, and Quick Reference table all restate workflow details — keep one authoritative treatment (e.g., the table plus workflows) and trim the rest.

Integrate error recovery into the main workflow as an explicit feedback loop, e.g., "If FETCH_PUBLISH_STATUS returns a failure state, read the error details, fix, and re-upload" rather than leaving it in a scattered pitfalls section.

Add one concrete example of constructing the video/photo file object (including where s3key comes from) to close the actionability gap.

DimensionReasoningScore

Conciseness

The body is mostly efficient — tool sequences, key parameters, and pitfalls with no explanations of concepts Claude already knows — but "Common Patterns / Video Publish Flow" restates Workflow 1, "Known Pitfalls" repeats the per-workflow pitfalls, and the Quick Reference table re-lists every tool and parameter, so it could be meaningfully tightened; this fits the 3 anchor rather than the 4 anchor's "minor instances" of over-explanation.

3 / 5

Actionability

Concrete guidance throughout: exact tool slugs (e.g., "TIKTOK_UPLOAD_VIDEO"), required/optional flags, enum values ("privacy_level: 'PUBLIC_TO_EVERYONE', ..."), parameter object shapes, and polling intervals ("5-10 seconds"). Minor gaps — no example request payload, and how to obtain the video object's "s3key" is never explained — keep it at 4 rather than the fully copy-paste-ready 5.

4 / 5

Workflow Clarity

Sequences are clear with explicit validation checkpoints: "poll FETCH_PUBLISH_STATUS until processing is complete before publishing" and "Confirm connection status shows ACTIVE before running any workflows", plus recovery guidance (re-auth on 401, exponential backoff on 429). It falls short of the 5 anchor because the failure branch (what to do when status reports failure mid-flow) is not integrated as an explicit feedback loop in the main workflow steps.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers, per-workflow structure, and a Quick Reference table for navigation; no references are used or needed. At ~175 lines the per-tool parameter and pitfall detail could be split into a reference file, and the under-50-line simple-skill exception does not apply, so it matches the 4 anchor (good structure, minor organization gaps) rather than 5.

4 / 5

Total

15

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 specific and highly distinctive, with concrete action verbs and natural TikTok-related trigger terms. Its main weakness is the absence of any "when to use" clause, which caps completeness and leaves the trigger context implicit.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user wants to upload, publish, or post content to TikTok or check their TikTok profile/stats."

Replace the generic phrase "manage content" with a concrete action such as "list published videos" to close the specificity gap.

Include a few natural synonym phrases (e.g., "post to TikTok", "TikTok stats") to broaden trigger coverage.

DimensionReasoningScore

Specificity

Quotes like "upload/publish videos, post photos, ... view user profiles/stats" list several concrete actions, matching the anchor for several specific actions with minor gaps; "manage content" is generic and coverage (e.g., listing videos) is incomplete, so it falls short of the comprehensive 5 anchor.

4 / 5

Completeness

The "what" is clear (automate TikTok tasks: upload/publish videos, post photos, view profiles/stats), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; it is not 4 because the "when" is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"TikTok", "upload", "publish videos", "post photos", and "profiles/stats" are natural phrases users would say, giving good keyword coverage; a few natural variants (e.g., "post to TikTok", "TikTok analytics") are missing, so it sits between the 3 and 5 anchors but noticeably above the midpoint.

4 / 5

Distinctiveness Conflict Risk

"Automate TikTok tasks via Rube MCP (Composio)" carves out a clear niche with distinct triggers (TikTok, upload/publish videos, post photos), posing minimal conflict risk with other skills; no closely related skill would trigger on these terms, matching the 5 anchor.

5 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/tiktok-automation/SKILL.md

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.