baoyu-danger-x-to-markdown_skill

This skill converts X tweets and articles to markdown with YAML front matter, after user consent verification and optional media handling.
  • TypeScript

5.8k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill jimliu/baoyu-skills --skill baoyu-danger-x-to-markdown

  • SKILL.md8.6 KB

Overview

This skill converts X (Twitter) tweets, threads, and X Articles into clean Markdown files with YAML front matter. It extracts full article content or tweet threads, embeds metadata (author, url, coverImage, tweetCount), and can optionally download media into local imgs/ and videos/ folders. The tool requires explicit user consent because it uses a reverse-engineered X API.

How this skill works

Provide an X or Twitter URL and the script fetches the content, builds a Markdown document with YAML front matter, and writes the file to the chosen output directory. On first run it enforces a consent and preferences flow: users must accept a disclaimer for the reverse-engineered API and complete a blocking setup that defines media handling and output location. Media download is configurable and can be done automatically or after an interactive prompt.

When to use it

  • You want to archive a tweet, thread, or X Article as Markdown with metadata for note-taking or publishing.
  • You need consistent filename and folder structure like x-to-markdown/{username}/{tweet-id}.md.
  • You want local copies of images/videos alongside converted markdown files.
  • You need machine-readable output (YAML front matter) for static site generators or personal knowledge bases.
  • You prefer CLI batch conversion with options for JSON output and download controls.

Best practices

  • Always read and accept the disclaimer before using the tool — consent is required and tracked in a local consent file.
  • Complete the first-time setup (EXTEND.md) interactively to choose media behavior and output directory; do not skip or create defaults silently.
  • Prefer environment-variable authentication (X_AUTH_TOKEN, X_CT0) to avoid automating a browser login.
  • Use the --download-media flag or the interactive media prompt when you need local assets; keep remote URLs otherwise to save space.
  • Store EXTEND.md in your preferred scope (user or project) to keep consistent behavior across runs.

Example use cases

  • Save a long tweet thread as a single Markdown document with author and tweetCount metadata.
  • Convert an X Article into full Markdown for editing or publishing in a personal blog.
  • Archive media-heavy tweets and download images/videos to imgs/ and videos/ for offline access.
  • Integrate Markdown output into a static site generator by using the YAML front matter fields.
  • Batch-convert shared tweet links from research notes into a structured folder for later review.

FAQ

Yes. You must accept a disclaimer before any conversion; consent is stored locally and checked on subsequent runs.

Where are preferences saved?

Preferences are saved to EXTEND.md either in the project (.baoyu-skills/) or the user home (~/.baoyu-skills/) depending on your choice during setup.

How are media files handled?

Media behavior follows EXTEND.md settings: always download, never download, or ask each time. Downloaded media are saved next to the markdown file in imgs/ and videos/ and links are rewritten to local paths.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational