published-track

Records published content and engagement metrics across social platforms in a SQLite database.

8.5k|1.4k|Updated Apr 24, 2024
One-click install
npx skills add https://github.com/TeamWiseFlow/wiseflow --skill published-track
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: published-track
Source: https://github.com/TeamWiseFlow/wiseflow/tree/main/crews/main/skills/published-track
Command: npx skills add https://github.com/TeamWiseFlow/wiseflow --skill published-track

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Tracking what was published where, and how each post performed, becomes unmanageable when you publish to WeChat, Douyin, Bilibili, Xiaohongshu, Twitter/X and a dozen other platforms. This Skill centralizes all publish records and engagement metrics into one local SQLite database with per-platform tables.

Core Features & Use Cases

  • Publish Recording: After any publish skill finishes, record the post with title, URL, content type, account alias, and automatic DNA linkage read from dna-meta.json, using upsert semantics keyed on source folder and publish date.
  • Metrics Fetching and Updating: Automatically fetch engagement stats (plays, likes, comments, shares, favorites) for Bilibili, Douyin, and Kuaishou via HTTP APIs with cookie sessions, or manually backfill metrics supplied by the user.
  • Query and Distribution Management: Query records per platform, check whether content was already published, list items pending distribution, and update distribution status.
  • Use Case: After publishing a WeChat article and a Douyin video, record both into the database, then let the nightly heartbeat job fetch the latest play and like counts so the content-calibrator can evaluate DNA performance.

Quick Start

Ask the agent to initialize the published-track database and record the article you just published to WeChat with its URL.

Frequently Asked Questions about published-track

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track published posts across multiple social media platforms?

Use the record command after each publish to store title, URL, content type, and account into per-platform SQLite tables. The database supports WeChat, Douyin, Bilibili, Xiaohongshu, Twitter/X, YouTube, and more, with upsert semantics keyed on source folder and publish date.

How to automatically fetch engagement metrics for Douyin and Bilibili videos?

Run the fetch-metrics command with the platform and row id. It checks cookie session validity, calls the platform HTTP API to retrieve plays, likes, comments, and shares, then writes the results into the database in one step.

Which platforms support automatic metrics fetching in published-track?

Automatic HTTP-based fetching supports Bilibili, Douyin, and Kuaishou. Xiaohongshu, WeChat Official Accounts, and WeChat Channels route to separate camoufox browser-based engagement tools, while other platforms require browser reading or manual entry.

What happens when I record the same content twice?

Recording is an upsert keyed on source folder and publish date. Re-recording the same content on the same day updates the existing row instead of inserting a duplicate, while a different publish date creates a new row for genuine republishing.

Why does fetch-metrics return SESSION_EXPIRED for Douyin?

The stored cookie session has expired or is missing required fields. Re-login through the login-manager skill to refresh the cookies in the central login store, then rerun the fetch command.