agentleFS
YangsonHungYangsonHung/awesome-agent-skills/skills/en/weixin-article-to-obsidian/SKILL.md

weixin-article-to-obsidian

Skill18 starsChanged 8 days agoMITView on GitHub

Use when saving a Weixin Official Account article from mp.weixin.qq.com into an Obsidian vault as Markdown with locally downloaded images and vault-style asset links.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user:

    line 14
  2. Distinctive:

    Do not use this skill when:

    line 23
  3. Distinctive:

    Read the target vault guidance first, especially directory rules, asset rules, and index maintenance rules.

    line 31
  4. Very specific:

    Run opencli weixin download if available:

    line 33
  5. Very specific:

    If opencli misses images, or if the article is a picture-page article, run the bundled script:

    line 39
  6. Very specific:

    Verify every image reference is an Obsidian vault link pointing under assets/<note-title>/.

    line 48
  7. Distinctive:

    If the vault requires topical indexes, update the local index page with a wiki link to the new note.

    line 49
  8. Distinctive:

    Use Obsidian image syntax, not regular Markdown image syntax.

    line 72
  9. Distinctive:

    Keep the source URL as a short metadata line unless the user asks to remove it.

    line 73
  10. Distinctive:

    Do not add YAML frontmatter unless the vault already requires it.

    line 74

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weixin Article to Obsidian

Overview

Capture a Weixin Official Account article into an Obsidian vault with local image assets. Prefer opencli weixin download for the initial article fetch, then verify and supplement the result by parsing the page source for picture-page images and article metadata.

When to Use

Use this skill when the user:

  • Provides an mp.weixin.qq.com article URL
  • Wants the article body saved as a Markdown note in an Obsidian vault
  • Wants article images downloaded locally instead of referenced from remote CDN URLs
  • Wants Obsidian image links such as ![[assets/title/image.png]]
  • Wants a repeatable workflow for Weixin article clipping

Do not use

Do not use this skill when:

  • The URL is not a Weixin Official Account article
  • The user only wants a visual theme extracted from the article
  • The user wants to publish Markdown back to Weixin
  • The target is not a local Markdown or Obsidian knowledge base

Instructions

  1. Read the target vault guidance first, especially directory rules, asset rules, and index maintenance rules.
  2. Choose the semantic note directory from the article topic. Do not default to a generic clipping folder when the vault has a more specific category.
  3. Run opencli weixin download if available:
opencli weixin download --url "https://mp.weixin.qq.com/s/example" --output /tmp/weixin-article --download-images true -f yaml
  1. If opencli misses images, or if the article is a picture-page article, run the bundled script:
python3 scripts/download_weixin_article.py "https://mp.weixin.qq.com/s/example" \
  --vault-root /path/to/obsidian-vault \
  --target-dir "FrontEnd/security"
  1. Review the generated Markdown and remove platform chrome, duplicated metadata, recommendation blocks, or reward prompts if any remain.
  2. Verify every image reference is an Obsidian vault link pointing under assets/<note-title>/.
  3. If the vault requires topical indexes, update the local index page with a wiki link to the new note.

Script Behavior

scripts/download_weixin_article.py:

  • Attempts opencli weixin download first and reuses its Markdown body when it is complete enough
  • Fetches the article HTML directly as a fallback or supplement
  • Extracts title, account name, publish time, description/body text, and picture-page image URLs
  • Downloads images into assets/<safe-title>/
  • Writes a Markdown note into the requested --target-dir
  • Emits a JSON summary with the note path, asset directory, image count, and whether opencli ran

Important options:

  • --vault-root: Obsidian vault root. Defaults to the current working directory.
  • --target-dir: Relative note directory inside the vault. Defaults to the vault root.
  • --title: Override the extracted title and asset folder name.
  • --locale: Use zh or en metadata labels. Defaults to zh.
  • --overwrite: Replace an existing Markdown note with the same title.

Output Rules

  • Save Markdown under the chosen content directory.
  • Save images under assets/<note-title>/, relative to the vault root.
  • Use Obsidian image syntax, not regular Markdown image syntax.
  • Keep the source URL as a short metadata line unless the user asks to remove it.
  • Do not add YAML frontmatter unless the vault already requires it.

Validation Checklist

  • The note exists in the selected directory.
  • The asset folder exists and contains all expected article images.
  • rg "mmbiz|data:image|http" <note> only shows the source URL, not remote image links.
  • Image links render as ![[assets/...]].
  • The topical index is updated when required by the vault.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.