dify-cli-docs

Draft and edit difyctl CLI documentation verified against langgenius/dify source.

175|388|Updated Mar 11, 2025
One-click install
npx skills add https://github.com/langgenius/dify-docs --skill dify-cli-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dify-cli-docs
Source: https://github.com/langgenius/dify-docs/tree/main/.claude/skills/dify-cli-docs
Command: npx skills add https://github.com/langgenius/dify-docs --skill dify-cli-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you draft and edit Dify CLI documentation that stays consistent with repository writing standards and matches the actual shipped behavior of difyctl. It reduces the risk of publishing incorrect commands, unsupported edition details, or duplicated guidance across the CLI doc set.

Core Features & Use Cases

  • CLI doc authoring guidance: Provides a structured workflow for writing pages under en/cli/, including page structure, command reference sections, and task-oriented openers.
  • Code-verified accuracy: Requires behavior claims to be checked against the langgenius/dify cli source on origin/main, helping prevent drift from unofficial branches or outdated README content.
  • Edition and ownership rules: Enforces CE-first documentation, Cloud badging rules, and content ownership so shared concepts are documented once and linked elsewhere.
  • Use Case: When updating a difyctl command page, use this Skill to mirror the right page pattern, verify flags and exit behavior in source code, and keep the content aligned with Dify's CLI documentation conventions.

Quick Start

Ask the AI to draft or revise an en/cli/ page for difyctl and verify every command behavior against the langgenius/dify cli source on origin/main.

Frequently Asked Questions about dify-cli-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write Dify CLI documentation that matches the actual difyctl behavior?

To write accurate Dify CLI documentation, draft or revise en/cli/ pages by verifying every command flag, output behavior, and authentication claim against the langgenius/dify cli source code on the origin/main branch to prevent documentation drift.

What is the best way to structure difyctl command reference pages?

The best way to structure difyctl command reference pages is to follow the repository writing guide, which enforces task-oriented openers, CE-first edition rules, and cross-linked ownership of shared concepts to keep documentation consistent.

How do I verify difyctl command flags and exit behavior against the source code?

You verify difyctl command flags and exit behavior by checking behavior claims directly against the langgenius/dify cli source on origin/main, ensuring your CLI documentation does not rely on outdated README content or unofficial branches.

Does Dify CLI documentation require edition-specific guidance for Cloud and CE?

Yes, Dify CLI documentation requires edition-specific guidance by enforcing CE-first documentation rules and Cloud badging rules, ensuring shared concepts are documented once and linked elsewhere to maintain clear content ownership.

Can I use existing README files to update Dify CLI command references?

You should not rely on existing README files to update Dify CLI command references; instead, validate all difyctl output behavior and authentication claims against the langgenius/dify cli source on origin/main for code-verified accuracy.