AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Douyin Account Data

skill-oyorf-personal-workbench-skills-douyin-account-data · by oyorf

Collect the user's own authorized Douyin Creator Center analytics on macOS or Windows, validate the official exports, and update the complete data contract consumed by Personal AI Workbench. Use when the user asks to pull, refresh, validate, or display their own Douyin account data in the Workbench. Do not use for other creators, public-account scraping, private messages, content strategy, or top…

No reviews yet
0 installs
12 views
0.0% view→install

Install

$ agentstack add skill-oyorf-personal-workbench-skills-douyin-account-data

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-oyorf-personal-workbench-skills-douyin-account-data)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
27d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Douyin Account Data? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Douyin Account Data

Scope

Only collect data from a Douyin Creator Center account that the user has explicitly authorized. Use Ego Lite on macOS or the bundled Playwright adapter on Windows. Produce data facts for Personal AI Workbench; do not generate content recommendations, account strategy, or publishing actions.

The Windows adapter uses a dedicated local browser profile and the same official-export, validation, and atomic-publish pipeline as macOS. Linux remains unverified; on Linux, explain the limitation and use manually downloaded official Excel files unless the user explicitly asks to test the adapter there. Never claim partial data is complete.

Required inputs

Resolve both paths before collection:

  • Personal AI Workbench root containing Workbench/server/vault-index.mjs.
  • A private knowledge-base root where 30_self_media/douyin/ may be written.

Prefer paths explicitly provided by the user, then PERSONAL_DASHBOARD_ROOT and PERSONAL_DASHBOARD_VAULT_ROOT. If either path remains unknown, ask the user. Never guess a username, home directory, repository name, or Vault name.

Read [platform-support.md](references/platform-support.md) when setup, Ego Lite, login, Windows, or Linux is involved. Read [data-contract.md](references/data-contract.md) before changing collection coverage or the Workbench output schema.

Safety gate

Before running:

  1. Confirm the account belongs to the user or the user is authorized to access it.
  2. On macOS, confirm Ego Lite is installed and onboarding is complete. On Windows, confirm the Playwright requirements and Chromium browser are installed.
  3. On macOS, confirm the user has logged into Creator Center inside Ego Lite. On Windows, open the headed Playwright browser and let the user complete first-run QR login or verification there.
  4. Confirm the target knowledge base is private and is not the public synthetic demo directory in a Git repository.
  5. Confirm node, Python, and openpyxl are available. macOS also requires jq and ego-browser; Windows requires the Python playwright package and an installed Playwright Chromium browser.

Never read, print, copy, or export cookies, passwords, login tokens, or session parameters. On Windows, Playwright may keep the user's login state only inside its dedicated local profile outside the Skill repository, Workbench, and Vault; never inspect, copy, or commit that directory. Let the user complete first-run QR login in the visible browser. Stop and hand control back on CAPTCHA, phone confirmation, account selection, permission denial, or rate limiting.

Collect and publish

On macOS, run the Ego Lite entry point:

bash /scripts/collect.sh \
  --dashboard-root  \
  --vault-root 

On Windows PowerShell, after completing the setup in [platform-support.md](references/platform-support.md), run:

.\.venv\Scripts\python.exe skills\douyin-account-data\scripts\collect_playwright.py `
  --dashboard-root "" `
  --vault-root ""

Do not run scripts/playwright_collect.py directly for a normal collection. It is the low-level browser backend; collect_playwright.py adds temporary-directory isolation, validation, rollback, and atomic publishing.

The script must:

  1. Reuse the authorized login state from Ego Lite on macOS or the dedicated Playwright profile on Windows.
  2. Download official account, follower, work, collection, and per-work detail exports into a uniquely created system temporary directory.
  3. Capture only the page evidence required for fields without official Excel coverage.
  4. Inventory and parse the exports.
  5. Reject missing, duplicate, invalid, or internally inconsistent data.
  6. Build the exact Workbench model using the installed Workbench parser.
  7. Atomically replace /30_self_media/douyin/ only after all quality gates pass.
  8. Delete temporary exports and page snapshots on success or failure.
  9. Verify the published current.json before reporting success.

Use --work-ids only when the user explicitly asks to refresh specific work details or when automatic discovery cannot find them. Never place real work IDs in this repository or its documentation.

Completion report

Report:

  • collection status;
  • target current.json path;
  • capture time;
  • number of works and deep-detail packages;
  • account daily row count and collection count;
  • quality status;
  • whether temporary sources were deleted;
  • any unavailable fields or platform coverage limits.

Do not print raw downloaded rows, private page text, work IDs, account identifiers, local browser paths, or session-bearing URLs.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.