CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

system-migration-development

为 FastGPT 新增、修改或审查自动系统升级脚本及其注册信息。涉及系统迁移、升级任务、启动迁移、migration registry、checkpoint、全量重跑、独立模式、进度或失败数据时使用;普通业务更新和未接入自动升级框架的一次性手工清洗不使用。

Quality

90%

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

81%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 rigorous, project-grounded specification with excellent workflow sequencing, explicit validation and crash-recovery handling, and highly concrete APIs and file conventions. Its main gaps are pseudocode rather than executable examples, some repetition of key invariants across sections, and a monolithic structure that could offload detail to reference files.

Suggestions

Add one minimal executable TypeScript example — a registry entry (with progressSteps, i18nT keys, mode flags) and a skeletal task using context.getCheckpoint/reportFailedRecords/saveCheckpoint — so the guidance is copy-paste ready.

State the checkpoint-vs-error-snapshot persistence ordering rule once in a canonical section and reference it elsewhere, instead of repeating it in 状态能力, 分批断点续跑, and 交付前检查.

Move the detailed test-scenario matrix and the scheduling-mode/lease semantics into a reference file (e.g., references/testing.md, references/scheduling.md) to keep SKILL.md closer to an overview.

DimensionReasoningScore

Conciseness

The body is dense, project-specific rule-writing with no padding of concepts Claude already knows (no explanation of idempotency, Mongo, or leases), but the checkpoint/error-snapshot ordering invariant is restated in "脚本可使用的状态能力", "分批断点续跑" 关键约束, and again in "交付前检查". This matches the 4 anchor (efficient with minor instances that could be trimmed) rather than 3, since the repetition is deliberate emphasis of safety invariants rather than unnecessary explanation.

4 / 5

Actionability

Concrete guidance throughout: exact paths to inspect ("projects/app/src/migration/registry.ts"), exact Context APIs ("context.saveCheckpoint", "context.assertActive"), a mandated directory layout, specific constraints ("_id 或其他不可变、唯一且有索引的游标;不要使用 offset", "SYSTEM_MIGRATION_DELAY_SECONDS"), and verification commands ("App typecheck、相关 ESLint 和 git diff --check"). It falls short of 5 because the two recommended loops are pseudocode and there is no complete copy-paste TypeScript example of a registry entry or a task implementation.

4 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints: the loop embeds "assertActive", "校验该批结果并提交事务", and "执行全局完成校验"; crash-recovery feedback loops are specified ("进程可能在业务提交后、checkpoint 保存前退出"), and "交付前检查" provides a final checklist. Validation is thoroughly present, so the destructive/batch cap of 3 does not apply; this matches the 5 anchor (explicit validation, error-recovery loops, checklist).

5 / 5

Progressive Disclosure

No bundle files exist, so all content is inline in a single well-organized file with clear sections, a state-ownership table, and code blocks; navigation is easy and there are no nested or buried references. It stays at 4 rather than 5 because the ~250-line body inlines the full test-scenario matrix and detailed scheduling-mode semantics that could live in reference files, and the file is not the lean overview-plus-references shape the 5 anchor describes.

4 / 5

Total

17

/

20

Passed

Description

95%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: concrete actions, an explicit use-when clause with eight natural trigger terms, and explicit negative triggers that sharply bound its scope. Only minor room to broaden the action list beyond add/modify/review.

DimensionReasoningScore

Specificity

"为 FastGPT 新增、修改或审查自动系统升级脚本及其注册信息" lists three concrete actions (add, modify, review) on two specific artifacts, matching the anchor for several specific actions with minor gaps in coverage. It does not reach 5 because the action list is not comprehensive (e.g., testing and recovery-strategy design are core to the skill but unstated), and it is clearly above 3, which expects only 1–2 concrete actions.

4 / 5

Completeness

Both questions are explicitly answered: what ("新增、修改或审查自动系统升级脚本及其注册信息") and when ("涉及…时使用;…不使用"), with concrete trigger phrases plus explicit negative triggers. This matches the 5 anchor; the explicit "Use when" clause means the missing-trigger cap of 3 does not apply.

5 / 5

Trigger Term Quality

"涉及系统迁移、升级任务、启动迁移、migration registry、checkpoint、全量重跑、独立模式、进度或失败数据时使用" provides eight natural trigger terms, mixing domain Chinese phrases with actual codebase identifiers ("migration registry", "checkpoint") a user would naturally say. Coverage is comprehensive within the niche, matching the 5 anchor; it exceeds 4 because no common variation of the domain's terms is missing.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply bounded to FastGPT's automatic upgrade framework, and the exclusions "普通业务更新和未接入自动升级框架的一次性手工清洗不使用" prevent overlap with generic business-update or data-cleaning skills. Clear niche with distinct triggers and minimal conflict risk matches the 5 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

.agents/skills/system/system-migration-development/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.