AI Agent Hub
Back to skills
CSDN Article Publishing Plus icon

CSDN Article Publishing Plus

Content Creation Updated 2026.08.29

Paste the following prompt into your AI chat to install this skill:

Please install @user_5dda6a29/csdn-article-publish-plus into my AI assistant following the guide at https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Publishing to CSDN is not just pasting text: the page may be logged out, the editor may sit in an iframe, control ref values can change after redesigns, and the post must be verified as published or under review. If a workflow only generates Markdown, the user still has to copy the title, paste the body, click publish, and handle failures manually.

How It Works

This skill targets a logged-in CSDN browser-automation environment and publishes Markdown content to a CSDN blog:
- Opens https://mp.csdn.net/mp_blog/creation/editor and checks login state;
- Locates the title field and editor area from the current page snapshot rather than hard-coded ref values;
- Fills the title and body from local Markdown, draft text, or provided content;
- Clicks publish and takes another snapshot to extract the article URL or review status.

Scope

It fits “publish existing content to CSDN” workflows, not bypassing login, guessing passwords, or mass fake-account operations. The title must satisfy CSDN length rules, the body must not be empty, and the flow should stop and ask for user action when a captcha, timeout, or page change blocks automated input.

Use Cases

  • After writing a Markdown technical note, publish it directly to a CSDN blog and capture the article URL.
  • When a local article draft contains frontmatter, fill its title and body into the CSDN editor and publish.
  • When CSDN publishing fails, inspect the page snapshot to distinguish logout, stale ref, or invalid title length.
  • After generating Markdown with a WeChat layout skill, publish the same article to CSDN with this skill.

Best For

  • Engineering bloggers who want to publish local Markdown drafts directly to CSDN.
  • Developers using browser automation for content distribution who need stable CSDN login and snapshot handling.
  • Operations staff publishing one technical article across platforms who need a CSDN blog link from Markdown.
  • QA engineers debugging publishing failures who need CSDN page-state checks for logout, ref drift, or title limits.