📦

tiktok-api

Name: tiktok-api
Author: fetcher-sh

コンテンツリビジョン r1 中リスク 📁 ファイルシステムへのアクセス🌐 ネットワークアクセス🔑 環境変数⚙️ 外部コマンド

Explore TikTok Data with Fetcher.sh

Official TikTok access can require application review and does not fit quick, read-only research. This skill guides paid Fetcher.sh requests for posts, profiles, comments, and discovery feeds.

対応: Claude Codex Code(CC)

📊 67 十分

Maintain this Skill? Claim it 📊 67 十分

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

Review the Skillstore skill "tiktok-api" from https://skillstore.io/skills/fetcher-sh-tiktok-api.md and its manifest at https://skillstore.io/api/skills/fetcher-sh-tiktok-api/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/fetcher-sh-tiktok-api.md 署名済み manifest GET /api/skills/fetcher-sh-tiktok-api/manifest 署名済み lockfile GET /api/skills/fetcher-sh-tiktok-api/lockfile

テストする

「tiktok-api」を使用しています。 Find the most-liked AI agent posts from this month.

期待される結果:

A ranked summary of matching posts with creator names, engagement totals, publication dates, and links.
A short synthesis of repeated topics and notable outliers.

「tiktok-api」を使用しています。 Review the profile and recent posts for a specified creator.

期待される結果:

A profile overview followed by recent post themes, engagement observations, and the identifiers needed for deeper queries.

「tiktok-api」を使用しています。 Create a weekly hashtag monitoring workflow with a $2 budget.

期待される結果:

A bounded polling plan with endpoint order, cursor storage, deduplication rules, cost estimates, and a concise weekly report format.

セキュリティ監査

中リスク

v1 • 2026/8/14 バージョン別レポートを開く

All 154 static alerts are false positives caused by Markdown links, code formatting, redacted placeholders, and documented calls to expected endpoints. No prompt injection, hidden execution, unrelated destination, or real embedded secret was found. Paid third-party requests and automatic x402 settlement still create a spending risk that users should control.

スキャンされたファイル

664

解析済み行数

レビュー項目

誤検知を無視

確認済みのセキュリティ上の懸念 (1)

中

SKILL.md:73-75 SKILL.md:195-208

Paid Requests Can Settle Before Data Delivery

The skill supports paid calls and automatic x402 retries. It states that settlement precedes delivery and upstream failures receive no refunds.

The payment behavior and no-refund condition are explicitly documented, including automatic signing and retries.

リスク要因

📁 ファイルシステムへのアクセス (9)

references/endpoints.md:10 references/faq.md:19 references/scenarios.md:16 SKILL.md:64 SKILL.md:198 SKILL.md:217 SKILL.md:218 SKILL.md:219 SKILL.md:223

🌐 ネットワークアクセス (41)

🔑 環境変数 (33)

⚙️ 外部コマンド (50)

監査者: codex

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

https://skillstore.io/skills/fetcher-sh-tiktok-api/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdownバッジ

[![Skillstore security assessment](https://skillstore.io/badges/skills/fetcher-sh-tiktok-api/security.svg)](https://skillstore.io/skills/fetcher-sh-tiktok-api?utm_source=security_passport_badge)

HTMLバッジ

<a href="https://skillstore.io/skills/fetcher-sh-tiktok-api?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/fetcher-sh-tiktok-api/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

埋め込みカード

<iframe src="https://skillstore.io/embed/skills/fetcher-sh-tiktok-api.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

学術引用 (APA · BibTeX · CFF)

APA形式の引用

fetcher-sh. (2026). tiktok-api security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/fetcher-sh-tiktok-api/audits/1

BibTeX形式の引用

@techreport{fetcher-sh-fetcher-sh-tiktok-api-2026,
  author = {fetcher-sh},
  title = {tiktok-api security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/fetcher-sh-tiktok-api/audits/1},
  note = {Author version unspecified}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "tiktok-api security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "fetcher-sh"
date-released: "2026-08-14"
url: "https://skillstore.io/skills/fetcher-sh-tiktok-api/audits/1"
identifiers:
  - type: other
    value: "skillstore:fetcher-sh-tiktok-api:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

Track content trends

Search recent or most-liked posts for selected keywords and compare recurring topics.

Research creator audiences

Resolve creator profiles, review their posts, and paginate follower or following lists.

Build a research pipeline

Collect paginated post, hashtag, sound, location, and comment data for downstream analysis.

これらのプロンプトを試す

Find recent posts

Search TikTok for posts about [keyword] from [date range]. Return the most recent results with creator, date, engagement, and link.

Review a creator

Look up TikTok creator [handle]. Summarize the profile and recent posts, then identify recurring themes and engagement patterns.

Monitor a hashtag

Resolve hashtag [name], collect its posts across available pages, and summarize new post IDs, creators, themes, and engagement since [date].

Design a controlled pipeline

Plan a paginated TikTok collection for [research goal]. Include endpoints, cursor handling, deduplication, regional scope, cost limits, retries, and privacy controls.

ベストプラクティス

Confirm the expected call count and budget before pagination or scheduled polling.
Keep the Bearer key in a protected environment variable and redact it from logs.
Store cursors and post IDs so repeated runs can resume and avoid duplicate paid calls.

回避

Do not expose Bearer credentials in prompts, reports, source control, or shared logs.
Do not run unbounded polling or pagination without explicit cost and stop limits.
Do not treat returned fields, availability, or platform compliance as guaranteed.