docs(tiktok): warn that content_posting_method UPLOAD never publishes

[giladresisi]

Why

With content_posting_method: "UPLOAD", TikTok does not publish the post — it drops the media into the account's TikTok app inbox, where the user must manually finish and publish it within 24 hours or it's discarded. The Postiz API still reports the post as successfully published, so an agent that picks UPLOAD (the natural choice when a user says "upload this video") silently never posts.

PROVIDER_SETTINGS.md listed the enum with no explanation, and it's what an agent following this skill actually reads.

Changes (docs/markdown only)

• PROVIDER_SETTINGS.md — spell out the consequence of UPLOAD and name DIRECT_POST as the default to use.
• SKILL.md — add hard Rule 3: TikTok posts must use DIRECT_POST unless the user explicitly asked to finish the post in the TikTok app. Also stop the integrations:settings example from discarding .output.rules, so upstream provider guidance reaches skill users.

Related

• Mirrors app fix fix(tiktok): default content_posting_method to DIRECT_POST postiz-app#1687
• Companion docs docs(tiktok): document which settings apply per posting method and media type postiz-docs#231

Note: the media-type axis (which settings apply to video vs. photo posts) is a follow-up PR stacked on this one.

🤖 Generated with Claude Code

[postiz-contribution]

Contribution-checker quality warning
Heuristic score: 15/100 (low). This is a non-blocking warning surfaced by the project's quality settings.

Heuristics that flagged:

• Excessive inline code references: 8 inline refs (>3)
• AI watermark phrase: Matched: "Generated with Claude Code"
• Commit message too long: Longest: 837 chars
• Excessive added comments: 8 added comment lines (ratio 1.60)

If this is a genuine contribution, please add detail to your PR description and tighten the diff scope before reviewers look at it.

[coderabbitai]

Warning

Review limit reached

@giladresisi, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cb4ad7dd-9ee4-4efa-96ca-34faf0be161d

📥 Commits

Reviewing files that changed from the base of the PR and between 41c5a9d and a557cd5.

📒 Files selected for processing (2)

• PROVIDER_SETTINGS.md
• SKILL.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/tiktok-posting-method

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}