メニュー
Rule pack for the Dify CLI (`difyctl`) doc set — en/cli/. Covers reader segments, the writing rules, content ownership, and codebase-verification rules. Loaded by dify-docs-write; not an entry point.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/langgenius/dify-docs --skill dify-cli-docsコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | dify-cli-docs |
| description | Rule pack for the Dify CLI (`difyctl`) doc set — en/cli/. Covers reader segments, the writing rules, content ownership, and codebase-verification rules. Loaded by dify-docs-write; not an entry point. |
Not an entry point — run under dify-docs-write; this pack's rules implement its stages for en/cli/ pages.
langgenius/dify cli/ on origin/main, read at the pinned SHA per writing-guides/index.md "Syncing the Dify codebase safely"; record that SHA in your report.Critical (source of truth): cli/ on origin/main only. Never feat/cli or cli/README.md; both drift from shipped reality.
For page structure, mirror an existing page of the same type (command reference → en/cli/reference/apps.mdx; task page → en/cli/common-tasks.mdx). For the IA, see docs.json.
en/cli/ is CE + Cloud only (EE is separate), and launches CE-first (see Editions below).
dfoe_) is EE-only; its docs live in the EE repo, not here.The CLI launches CE-first: the shipped docs are CE-only, with Cloud content added when Cloud supports the CLI. EE is a separate doc set (never add EE content here).
--workspace / -A multi-workspace flags, no "another/every workspace" framing; difyctl runs against your single workspace.<Badge color="blue">Cloud</Badge> on its heading or list item. Mark with the badge; don't write a "Cloud only" sentence. When a CE release requires removing Cloud-only sections, list the exact sections and STOP — do not remove until the user approves; then remove them in a dedicated commit so they can be restored from git history when Cloud ships.dify.example.com, never cloud.dify.ai; the server edition shows self_hosted. (auth login's real default is still cloud.dify.ai, so steer the reader to enter their host rather than stating the default.)<Badge> inside a heading changes the heading's anchor: the badge text joins the slug (## Switch Your Workspace <Badge color="blue">Cloud</Badge> → #switch-your-workspace-cloud). Link to the real anchor; python3 tools/check-links.py --internal validates this.House overrides on top of the writing-guides.
Non-negotiable (correctness and security):
DIFY_TOKEN or any non-interactive token as working auth — the only path is the browser device flow.<your-app-id> in runnable code (it fails validation; see Placeholders).--workspace / -A or multi-workspace framing in CE (one workspace; see Editions).The non-obvious style rules:
--host, hosts.yml, use host, "Active host", "known hosts"). "server" = the backend as actor ("the server returns", "Network or server error") or its version ("client and server versions").data array with the paging fields page/limit/total/has_more"); error JSON is "a structured JSON object".chat, advanced-chat, ...) only inside literal output blocks.--limit flag overrides DIFY_LIMIT") or a named target ("overrides the resolution chain", linking the owner).auth devices list to see your sessions"), not "to do X, see [section]"; for an owned fact, link with a short payoff instead of re-explaining.<your-*>; received values stay concrete.get app"; never list).version page shows real output); no See Also; shipped reality only, except a fix the user confirms is in flight may be documented as expected behavior, verified before publish.Style nits: ~3-4 line paragraphs, few semicolons, em dashes by judgment.
One page per resource; each command an H2, task-phrased (never the literal command). Per-command order:
<required> [optional] ...repeatable) + a one-line description.### Arguments — required wherever a positional arg exists, parallel to ### Flags; note an arg's source ("<app-id> from get app").### Flags — Flag / Type / Default / Description; a recurring flag gets its full description in every command that takes it.### Examples — a verb-led caption + the command block. No result samples here.### Output — what stdout and stderr get in each mode, success included. -o commands get a | Format | What stdout gets | table + captioned samples (exempt: export, --json-only). Describe failures, don't quote error strings.### Exit Codes — link to Output Formats and Exit Codes for the full table.Multi-command pages open with a one-line lead-in + a mini-index of anchor links; one-command pages get a plain sentence. Put a page-level "how it works" / owned section at the END, after the commands, but when a section is tightly coupled to one command (pause/resume belongs with run/resume), keep it beside that command rather than exiled to the bottom.
Write each cross-cutting fact ONCE on its owner; link the anchor everywhere else. Never re-teach Dify platform concepts (one sentence + a link to the main docs).
| Content | Owner |
|---|---|
| Run dispatch across app types | Apps, "Run an App" |
HITL pause/resume (exit 0 + status:"paused") | Apps, "When a Workflow Pauses" |
| Workspace resolution chain | Workspaces |
-o schemas, exit codes, stdout/stderr discipline | Output Formats and Exit Codes |
| Global flag inventory | Global Flags |
| Help forms and topics | help |
Agent discovery (help -o json, agentGuide) | The Agent Contract |
| Sign-in and token storage | Authenticate |
| Env-var inventory | Environment Variables |
| Compat probe and range | version |
Source of truth is the code (per the Critical note above), not the docs or in-CLI help (both drift). Where to look: best source for exact strings and exit codes is the e2e suite cli/test/e2e/suites/**; flags/args → cli/src/commands/<verb>/<resource>/index.ts (verb-only commands: cli/src/commands/<verb>/index.ts); error codes → cli/src/errors/codes.ts; env vars → cli/src/env/registry.ts. Can't verify a claim? Skip it, soften it, or flag {/* VERIFY: ... */}.
For project context (known bugs, decisions, what's shipped vs planned), ask the user.
S7 verifiers — run after the spine's check chain:
python3 tools/check-links.py --internal; it must print Broken links: 0 and Broken anchors: 0.