Skip to content

ericrisco/rsc-harness / skills/tiktok-api

tiktok-api

Verified

Use when connecting a real TikTok account to code via the Content Posting, Display and Business Account APIs — OAuth, chunked video publish with status polling, and pulling views, watch time and impression sources, then logging that performance into the wiki as a dated feedback record. Covers short-lived tokens breaking a cron, unverified pull-from-URL ownership, and rate limits. NOT what to post or how to package it (that is `shortform-strategy` and `shortform-packaging`).

FileKindSize
SKILL.mdskill md18.8 KB
evals/README.mdmarkdown1.2 KB
evals/cases.yamlconfig4.3 KB
references/metrics-and-publish.mdmarkdown4.0 KB
references/oauth-setup.mdmarkdown4.7 KB
references/wiki-schema.mdmarkdown4.6 KB
scripts/verify.shexecutablescript4.4 KB

evals/README.md

View on GitHub
# Evals — tiktok-api

These are routing and coverage checks run by the skill harness, not live API tests. No
TikTok or OAuth network calls are made. `should_trigger` asserts this skill fires on
TikTok transport/ingestion prompts — including the non-obvious ones (24h access-token
death, `url_ownership_unverified` on PULL_FROM_URL, `rate_limit_exceeded` at 6/min, and
the Display-can't-give-watch-time distinction) and the Spanish/Catalan phrasings.
`should_not_trigger` asserts the right sibling wins on intent (`shortform-strategy` /
`shortform-packaging` / `shortform-editing`), on multi-network posting
(`social-publisher`), on other platforms (`instagram-api`), and on generic connector
work (`api-connector-builder`). `capability` is a rubric for a generated answer to the
daily-cron scenario — graded on whether it covers token refresh, the chunked
init→PUT→poll publish flow, the correct Display-vs-Business API split, the 6/min
throttle, least-privilege scopes + the audit caveat, append-not-overwrite wiki
ingestion, secret hygiene, and the 24–48h metric-lag caveat. Run them through the
repo's standard skill-eval runner against `cases.yaml`. The companion `scripts/verify.sh`
is a separate static, no-network linter you can point at integration code.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall