langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #911] [MERGED] feat(kurokobo/knowledge_toolbox): bump knowledge_toolbox plugin to version 0.0.2 #1260

New Issue
Closed
opened 2026-02-22 17:52:52 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 17:52:52 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/911
Author: @kurokobo
Created: 7/13/2025
Status: ✅ Merged
Merged: 7/15/2025
Merged by: @crazywoola

Base: main ← Head: bump-knowledge_toolbox-plugin-0.0.2

📝 Commits (1)

  • 93e2d22 feat(kurokobo/knowledge_toolbox): bump knowledge_toolbox plugin to version 0.0.2

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

📝 kurokobo/knowledge_toolbox/knowledge_toolbox.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

  • Added a new tool: Add File URL to Citations.

    ✅ Add File URL to Citations

    This is a tool to retrieve the download URLs for files included in the results of the Knowledge Retrieval node.
    With this tool, you can provide the download URLs of the files in the workflow results.

    Parameters

    • api_base_url
      • The base URL of the Knowledge API, with trailing /v1.
    • api_key
      • The API key for the Knowledge API.
    • context
      • The result of the Knowledge Retrieval node.
      • However, since Array[Object] cannot be selected directly here, please convert it to a string using a Template node or similar before inputting.
      • See the following section for details.
    • format
      • The format of the output. See following section for details.

    How to Input context

    You can input the result of the Knowledge Retrieval node to the context parameter as follows:

    • Connect new Template node to the Knowledge Retrieval node.
    • Select result (Array[Object]) as the arg1 of the Template node.
    • Connect new Add File URL to Citations node to the Template node.
    • Select output (String) of the Template node as the context of the Add File URL to Citations node.

    Output Format

    You can choose the output format:

    • full
      • Returns a complete object with the metadata of the Knowledge Retrieval node results, adding a download_url field.
      • You can specify this as a context variable in the LLM node. For example, by using prompts such as, "Please present the document you referred to with a download link using the URL in the download_url field", you can show users the actual document instead of just chunks.
      • However, due to technical limitations, if you specify this as a context variable in the LLM node, the chatbot's "Citations" feature will not work.
      • Additionally, depending on the accuracy of the LLM model, the URL may get rewritten during generation, resulting in invalid links.
    • minimal_json
      • Returns a JSON string with basic information such as file names and download URLs of the referenced documents.
      • For instance, if you provide this JSON to the LLM along with the usual context and have it present download links when needed, you can generate download links while still utilizing the chatbot's Citations feature.
      • However, depending on the accuracy of the LLM model, the URL may get rewritten during generation, resulting in invalid links.
    • minimal_markdown
      • Returns a list of Markdown formatted download links for the referenced documents.
      • By including this directly in the Answer node, you can completely prevent the issue of the URL being unintentionally altered by the LLM model and becoming unusable.
    • chunks_markdown
      • Returns a collapsible Markdown that contains the referenced chunks and download links for the documents.
      • This can be used to replace the default Citations feature of the chatbot, by placing the output of this tool in the Answer node directly.
  • Added new output format link to the Download File tool, which provides a Markdown download link.

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/911 **Author:** [@kurokobo](https://github.com/kurokobo) **Created:** 7/13/2025 **Status:** ✅ Merged **Merged:** 7/15/2025 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `bump-knowledge_toolbox-plugin-0.0.2` --- ### 📝 Commits (1) - [`93e2d22`](https://github.com/langgenius/dify-plugins/commit/93e2d228b1edb495fba208f6cc9c6697b15e8a86) feat(kurokobo/knowledge_toolbox): bump knowledge_toolbox plugin to version 0.0.2 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `kurokobo/knowledge_toolbox/knowledge_toolbox.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> - **Plugin Author**: kurokobo - **Plugin Name**: knowledge_toolbox - **Repository URL**: https://github.com/kurokobo/dify-plugin-collection/tree/main/tools/knowledge_toolbox ## 2. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description - Added a new tool: **Add File URL to Citations**. > ### ✅ Add File URL to Citations > > This is a tool to retrieve the download URLs for files included in the results of the Knowledge Retrieval node. > With this tool, you can provide the download URLs of the files in the workflow results. > > #### Parameters > > - `api_base_url` > - The base URL of the Knowledge API, with trailing `/v1`. > - `api_key` > - The API key for the Knowledge API. > - `context` > - The result of the Knowledge Retrieval node. > - However, since Array[Object] cannot be selected directly here, please convert it to a string using a Template node or similar before inputting. > - See the following section for details. > - `format` > - The format of the output. See following section for details. > > #### How to Input `context` > > You can input the result of the Knowledge Retrieval node to the `context` parameter as follows: > > - Connect new **Template** node to the Knowledge Retrieval node. > - Select `result` (`Array[Object]`) as the `arg1` of the **Template** node. > - Connect new **Add File URL to Citations** node to the **Template** node. > - Select `output` (`String`) of the **Template** node as the `context` of the **Add File URL to Citations** node. > > #### Output Format > > You can choose the output format: > > - `full` > - Returns a complete object with the metadata of the Knowledge Retrieval node results, adding a `download_url` field. > - You can specify this as a context variable in the LLM node. For example, by using prompts such as, _"Please present the document you referred to with a download link using the URL in the `download_url` field"_, you can show users the actual document instead of just chunks. > - However, due to technical limitations, if you specify this as a context variable in the LLM node, the chatbot's "Citations" feature will not work. > - Additionally, depending on the accuracy of the LLM model, the URL may get rewritten during generation, resulting in invalid links. > - `minimal_json` > - Returns a JSON string with basic information such as file names and download URLs of the referenced documents. > - For instance, if you provide this JSON to the LLM along with the usual context and have it present download links when needed, you can generate download links while still utilizing the chatbot's Citations feature. > - However, depending on the accuracy of the LLM model, the URL may get rewritten during generation, resulting in invalid links. > - `minimal_markdown` > - Returns a list of Markdown formatted download links for the referenced documents. > - By including this directly in the Answer node, you can completely prevent the issue of the URL being unintentionally altered by the LLM model and becoming unusable. > - `chunks_markdown` > - Returns a collapsible Markdown that contains the referenced chunks and download links for the documents. > - This can be used to replace the default Citations feature of the chatbot, by placing the output of this tool in the Answer node directly. - Added new output format link to the **Download File** tool, which provides a Markdown download link. ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection [Guidelines](https://docs.dify.ai/plugins/publish-plugins/publish-to-dify-marketplace/plugin-privacy-protection-guidelines): ### Data Collection <!-- Does your plugin collect any user personal data? If yes, please list what types of user personal data are being collected according to the Plugin Privacy Protection Guidelines (for example: Email address, IP address, Age, etc) --> ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 17:52:52 -05:00
yindo closed this issue 2026-02-22 17:52:53 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1260
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?