Add plugin: jcaiagent7143-ui/linkdigest v0.1.5

[jcaiagent7143-ui]

Plugin Submission

Plugin information

• Author: jcaiagent7143-ui
• Plugin name: linkdigest
• Version: 0.1.5
• Source repository: https://github.com/jcaiagent7143-ui/linkdigest-mcp (plugin source under dify/, updated to 0.1.5 in commit e9a4f1c)
• Contact: apify@linkdigest.dev

Submission type

• New plugin
• Version update

What changed

One new optional tool parameter and one copy correction. No new dependencies, no new permissions, no new network domains. The diff between 0.1.3 (the version on the marketplace) and 0.1.5 touches five files: manifest.yaml and provider/linkdigest.yaml (version, one help line), tools/digest_url.yaml, tools/digest_url.py and linkdigest_client.py (the parameter).

1. insight (boolean, optional, default false). When true, the service also returns a consumer-insight block over the post and the first comments its public share page served with it: audience, claims, objections and pain points, purchase-intent cues, products and prices named, and questions readers ask — each finding with a short quote that the service checks word for word against the post, marked verified true or false. It is an add-on billed by the service at +1 credit, like breakdown; it does not change what the plugin fetches or where (the same single JSON call to linkdigest.dev).
2. Credential help line. Keys can now be created with an email link as well as Google sign-in; the help text says so.

Unchanged and still true: one tool, digest_url; the plugin runs nothing locally and fetches only https://linkdigest.dev with the user's own key; the user's URL is sent as a JSON field and the service performs the fetch on its side; credential validation hits an endpoint that starts no digest and spends no credit.

Risk level

• Low risk
• Medium risk
• High risk

Unchanged from 0.1.0 to 0.1.3: the tool accepts a user-provided URL and sends it to an external service. The plugin itself fetches only linkdigest.dev; it does not fetch the user's URL. The service reads public posts only — no login, no cookie, no comment endpoint — and returns text.

Required checks

• I have read and followed the Marketplace submission requirements.
• I have read and comply with the Plugin Developer Agreement.
• I tested this plugin on Dify Community Edition and Dify Cloud, or documented any limitation below.
• The package contains only files needed at runtime.
• The package does not contain secrets, local credentials, .env files, .git directories, virtual environments, caches, logs, or IDE files.
• The package does not contain executables or bundled binaries, or I explained why they are required below.
• The plugin README includes setup steps, usage instructions, required APIs or credentials, connection requirements, and the source repository link.
• The plugin includes PRIVACY.md or a hosted privacy policy, and manifest.yaml references it.
• All user-facing text is primarily in English, with any localized README files following the i18n guidance.

README.md is entirely English; localized prose lives in README.zh_Hans.md. Locale-keyed values in the YAML files are label and description fields.

Limitation, documented as the third check requires: as with 0.1.1 and 0.1.3, I have not run this inside a Dify Community Edition or Dify Cloud instance. What was tested is in Local validation below: the packaged client against the live service with the new parameter, and the package's contents.

Security and privacy notes

• Network destination: linkdigest.dev only (declared in manifest.yaml), over HTTPS. Unchanged.
• Read-only tool. No command execution, no code execution, no SQL, no filesystem access, no browser automation, no proxying or crawling.
• The plugin does not fetch arbitrary URLs. The user's URL is sent as a JSON field to the LinkDigest API, which validates it and performs the fetch on its side.
• Personal data: the plugin sends the URL, the requested format, the optional language, the optional breakdown and insight flags, and the API key. Nothing else leaves the workspace. PRIVACY.md states this.
• API key is stored by Dify's credential store, sent only as an Authorization: Bearer header, never logged, and not echoed in error messages.

Local validation

$ dify-plugin-darwin-arm64 version          # official CLI from langgenius/dify-plugin-daemon releases
v0.6.10
$ dify-plugin-darwin-arm64 plugin package ./linkdigest -o linkdigest-0.1.5.difypkg
INFO plugin packaged successfully

$ unzip -l linkdigest-0.1.5.difypkg          # same 15 entries as 0.1.3
LICENSE, PRIVACY.md, README.md, README.zh_Hans.md, _assets/icon.png, linkdigest_client.py,
main.py, manifest.yaml, provider/{__init__.py,linkdigest.py,linkdigest.yaml}, requirements.txt,
tools/{__init__.py,digest_url.py,digest_url.yaml}
no __pycache__, no .env, no .git, no virtualenv; key-material regex finds nothing

$ # the packaged client against the live service, with the owner's own key:
$ #   digest_url(url, insight=true) -> 200, `insight` block present, 6 sections, every quote verified

Reviewer notes

Single file added: jcaiagent7143-ui/linkdigest/linkdigest-0.1.5.difypkg. The earlier packages are left in place, as with 0.1.1 and 0.1.3. Source is public in the repository above under dify/, identical to the package contents.

If you would prefer version updates to replace rather than accompany the previous packages, tell me and I will resubmit that way.

🤖 Generated with Claude Code

[crazywoola]

Verified publication eligibility for b66cca5: Pre Check Plugin and PR Risk Label both passed for this revision, and this PR is open and ready for review. Inspected the submitted manifest, README, and relevant tool/provider source: the plugin provides social-media content transcription, OCR, and summaries, with no Web3 functionality found. This approval covers publication eligibility.