← Back to Skills Marketplace
ymsha88

Parse Dedao

by ymsha88 · GitHub ↗ · v1.0.1 · MIT-0
cross-platform ⚠ suspicious
126
Downloads
1
Stars
0
Active Installs
2
Versions
Install in OpenClaw
/install parse-deodao-shared-link
Description
解析"得到"笔记分享链接(支持提取正文和下载图片)。自动提取得到(dedao.cn)分享链接的正文内容,并支持将文章中的图片保存到本地。当用户发送得到笔记分享链接时使用此技能。
Usage Guidance
This skill appears to implement a dedao.cn scraper, but it has several red flags you should address before running: (1) run_parse.js writes output to a hard-coded Windows path (D:/notes/biji/0000) instead of the documented ./images or a configurable outputDir — change this to a relative or configurable directory to avoid overwriting files; (2) SKILL.md and test files reference parseDedao/other exports but parse.js only exports parsePage — verify and fix the API surface so you know which functions will run; (3) the skill depends on Playwright/Chromium but includes no install steps — ensure you install Playwright and its browser binaries in a controlled environment; (4) review the code locally to confirm there are no hidden network endpoints or logging to unexpected services (there are none obvious in the supplied files); (5) run the scripts in a sandbox or VM with limited permissions first to confirm behavior and to prevent accidental writes to system drives. Given the inconsistencies, treat this as potentially useful but untrusted until you fix/configure the output paths and verify dependencies.
Capability Analysis
Type: OpenClaw Skill Name: parse-deodao-shared-link Version: 1.0.1 The skill bundle exhibits high-risk behaviors including the use of hardcoded absolute Windows file paths (`D:/notes/biji/0000`) in `scripts/run_parse.js` and `scripts/test_parse.js`, which could lead to unintended file overwrites. Additionally, `scripts/parse.js` launches the browser with the `--no-sandbox` and `--disable-setuid-sandbox` flags, significantly weakening the security posture of the browser automation. While these appear to be unintentional design flaws or artifacts of a local development environment rather than intentional malware, they represent significant vulnerabilities in a shared skill bundle.
Capability Assessment
Purpose & Capability
The name/description and most code align: parse a dedao.cn share link, extract text and images using Playwright. However there are incoherences: SKILL.md and examples mention parseDedao and other site-specific exports, but scripts/parse.js only exports parsePage. SKILL.md says images default to ./images/, but run_parse.js writes to a hard-coded Windows path (D:/notes/biji/0000). These mismatches suggest sloppy packaging and unexpected filesystem behavior.
Instruction Scope
SKILL.md describes extracting content and saving images and provides usage examples. The runtime code does that, but run_parse.js will write markdown and image files to an absolute path (D:/notes/...), which is not documented in SKILL.md. The parse implementation fetches pages and image URLs (network I/O) and writes files to disk — appropriate for a scraper but the undocumented hard-coded path and mismatched exported functions broaden scope unexpectedly.
Install Mechanism
There is no install spec (instruction-only plus shipped scripts). SKILL.md lists dependencies (Playwright and Chromium) but the package does not include installation steps. Playwright requires installing browser binaries and can be large; absence of an install mechanism means the environment must already provide these, which may confuse users and lead them to run the scripts in an environment missing required components.
Credentials
The skill requests no secrets or env vars, which is appropriate. However the code writes files to the local filesystem and uses a hard-coded absolute Windows path (D:/notes/biji/0000). This is disproportionate to the description's implied default of './images' and could overwrite or create files in unexpected locations. There are no network exfiltration endpoints in the code, but file-write behavior requires care.
Persistence & Privilege
The skill is not always-enabled and does not modify other skills or agent configs. It does, however, write persistent files to disk when executed (markdown and images). That is expected for this use case, but the hard-coded output location increases the chance of undesired persistence on the host.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install parse-deodao-shared-link
  3. After installation, invoke the skill by name or use /parse-deodao-shared-link
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.1
增加下载关键图片
v1.0.0
Initial release. - Added skill to parse "得到" (dedao.cn) note sharing links. - Automatically extracts the main content from shared dedao.cn note URLs, supporting dynamic (JavaScript-rendered) pages. - Utilizes Playwright with Chromium for headless browser-based content extraction. - Includes fallback selector logic to improve extraction success. - Provides detailed usage instructions and troubleshooting notes.
Metadata
Slug parse-deodao-shared-link
Version 1.0.1
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 2
Frequently Asked Questions

What is Parse Dedao?

解析"得到"笔记分享链接(支持提取正文和下载图片)。自动提取得到(dedao.cn)分享链接的正文内容,并支持将文章中的图片保存到本地。当用户发送得到笔记分享链接时使用此技能。 It is an AI Agent Skill for Claude Code / OpenClaw, with 126 downloads so far.

How do I install Parse Dedao?

Run "/install parse-deodao-shared-link" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Parse Dedao free?

Yes, Parse Dedao is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Parse Dedao support?

Parse Dedao is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Parse Dedao?

It is built and maintained by ymsha88 (@ymsha88); the current version is v1.0.1.

💬 Comments