Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, information-dense skill body: concrete tool slugs and parameters, correctly ordered multi-step workflows with status-polling validation checkpoints, and honest pitfall coverage. The main improvement opportunities are deduplicating content requirements between workflow pitfalls and the Known Pitfalls section, and adding a sample tool-call payload with a note on obtaining the video `s3key`.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — no explanations of what TikTok or MCP are, just tool slugs, parameters, and pitfalls. Minor trimming is possible: video/photo content requirements appear in both workflow "Pitfalls" and "Known Pitfalls", and the Quick Reference table restates tool slugs already listed per workflow. This matches anchor 4 (efficient, minor instances that could be trimmed) rather than anchor 3, since there is no concept-teaching padding. | 4 / 5 |
Actionability | Concrete, executable guidance throughout: exact tool slugs ("TIKTOK_UPLOAD_VIDEO"), parameter names ("publish_id", "privacy_level") with enumerated valid values ('PUBLIC_TO_EVERYONE', ...), and file-object shapes ("s3key", "mimetype", "name"). Falls short of anchor 5 because there is no copy-paste example of an actual tool invocation payload, and how to obtain an `s3key` for the video object is left unstated. | 4 / 5 |
Workflow Clarity | Each workflow has a numbered tool sequence with validation checkpoints: confirm connection is "ACTIVE before running any workflows", "poll FETCH_PUBLISH_STATUS until processing is complete before publishing", and "optionally poll status again to confirm publication". Error-recovery guidance exists (401 → re-authenticate, 429 → exponential backoff). It is not anchor 5 because feedback loops are described as prose ("Failed publishes include error details") rather than as explicit if-fail-then-retry steps in the sequences. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), so all content is appropriately self-contained in a single well-sectioned file with clear headers, per-workflow subsections, and a Quick Reference table for navigation. Structure is good with only minor organization gaps (some duplication between per-workflow pitfalls and the Known Pitfalls section), matching anchor 4; the skill exceeds the 50-line simple-skill case but has no content that clearly demands offloading. | 4 / 5 |
Total | 16 / 20 Passed |