CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fastgpt-docker-deploy

FastGPT Docker Compose self-hosting deployment workflow. Use when a user asks an AI agent to deploy FastGPT with Docker by referencing /deploy/SKILL.md, including creating an empty fastgpt directory, running the install script in non-interactive mode, starting Docker Compose, monitoring service health, troubleshooting compose issues, and returning the access URL plus root credentials and next steps.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced deployment runbook with executable commands, explicit health checkpoints, and strong error-recovery guidance. Its weaknesses are modest: some repetition (default ports stated three times), version-sensitive details embedded in the main flow, and optional overrides/troubleshooting inlined where a reference file would keep the core workflow leaner.

Suggestions

Consolidate the default port mapping (3000/3006/3003, legacy 9000) into a single location — it is currently repeated in 工作边界, step 6, and 最终回复.

Move version-sensitive details (v4.17/v4.16 versions, the '123456' initial-password behavior vs. legacy random password) into a versioned or 'legacy' section so the main flow stays stable over time.

Consider splitting the optional FASTGPT_* env-var override list and the 常见问题处理 detail into a references/ file, keeping SKILL.md focused on the core deployment sequence.

DimensionReasoningScore

Conciseness

Largely lean and command-first, but there are minor instances of trimming opportunity: the default ports (3000/3006/3003/9000) are repeated across 工作边界, step 6, and 最终回复; the language-matching paragraph restates behavior Claude already has; and time-sensitive version details ('main(v4.17)或 v4.16', initial password '123456' vs. old random password) sit inline rather than in a deprecated/version section. Fits the 'efficient; minor over-explanation' anchor, not the every-token-earns-its-place 5 anchor.

4 / 5

Actionability

Every step ships copy-paste-ready commands (docker -v, mkdir -p ~/fastgpt, curl -fsSL https://doc.fastgpt.cn/deploy/install.sh, FASTGPT_NON_INTERACTIVE=true bash install.sh, docker compose up -d, docker compose ps, curl -I http://localhost:3000) plus concrete env-var override examples like FASTGPT_MCP_ENDPOINT=https://mcp.example.com:3003. Fully executable guidance covering the common cases, matching the top anchor.

5 / 5

Workflow Clarity

A clear six-step sequence with explicit validation checkpoints: environment preflight, non-empty directory check with user confirmation before proceeding, waiting for running/healthy state with a named service list (fastgpt-app, fastgpt-mongo, etc.), and curl -I access verification. The 常见问题处理 section provides feedback loops (port conflict → set FASTGPT_PORT → re-run; Mongo 'Illegal instruction' → switch to 4.x image → rebuild), and data volumes are explicitly protected. Matches the explicit-validation-with-recovery anchor.

5 / 5

Progressive Disclosure

No bundle files exist, so this scores on structure alone: sections are well organized (目标 / 工作边界 / 部署流程 / 常见问题处理 / 最终回复) and navigation is easy, but the ~125-line body inlines the optional env-var override reference and detailed troubleshooting that could live in a references/ file. Fits 'good structure; minor organization gaps' rather than the appropriately-split 5 anchor.

4 / 5

Total

18

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: it names the domain precisely, enumerates concrete workflow actions comprehensively, and includes an explicit 'Use when...' trigger clause. The only gap is modest synonym coverage in trigger terms (e.g. 'install', 'self-host' as standalone phrases).

DimensionReasoningScore

Specificity

Lists multiple concrete actions covering the entire workflow: 'creating an empty fastgpt directory, running the install script in non-interactive mode, starting Docker Compose, monitoring service health, troubleshooting compose issues, and returning the access URL plus root credentials and next steps'. This matches the comprehensive-coverage anchor; the 4 anchor applies when actions have minor gaps, and here the deployment lifecycle is fully enumerated.

5 / 5

Completeness

Explicitly answers both: what ('FastGPT Docker Compose self-hosting deployment workflow' with enumerated steps) and when ('Use when a user asks an AI agent to deploy FastGPT with Docker by referencing /deploy/SKILL.md'). Both are concrete with explicit trigger phrasing, matching the top anchor rather than the 4 anchor where the 'when' could be more specific.

5 / 5

Trigger Term Quality

Good natural keyword coverage — 'deploy FastGPT', 'Docker', 'Docker Compose', 'self-hosting', 'troubleshooting compose issues' — but a few natural synonyms users would say are missing (e.g. 'install FastGPT', 'self-host FastGPT'). Not the 5 anchor, which requires comprehensive synonym coverage; clearly above the 3 anchor's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

Names a specific product (FastGPT) with a specific method (Docker Compose self-hosting), giving it a clear niche with distinct triggers and minimal conflict risk against any generic Docker or deployment skill. Far above the 'somewhat specific but could overlap' 3 anchor.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

labring/FastGPT

Path

document/public/deploy/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.