CtrlK
BlogDocsLog inGet started
Tessl Logo

ci-workflow-sync

FastGPT CI workflow 双轨同步。当用户修改或新增 .github/workflows/ 下的 GitHub Actions workflow 时必须触发:同步更新 .forgejo/workflows/ 对应文件保持功能一致,或判断是否需要新建 Forgejo 版本。涉及 CI、GitHub Actions、Forgejo Actions、镜像构建、container registry、artifact、workflow yaml 改动、build-* workflow、test-* workflow 时也使用此技能。即使用户只提到"改一下 CI"或"加个 workflow"也应触发。

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The body is highly actionable with executable diffs, concrete commands, a decision tree, and a validation checklist, yielding strong actionability and workflow clarity. Conciseness and progressive disclosure are the weaker dimensions: repeated snippets add verbosity, and the large single-file structure has no reference-file split for its long pattern catalog.

Suggestions

De-duplicate the proxy-envs capture block — define it once in 模式 5 and have 模式 11 / the Before/After section reference it rather than re-paste it, to tighten conciseness.

Split the 11 transformation patterns and the full before/after example into separate reference files (e.g. references/patterns.md, references/before-after.md) linked one-level-deep from SKILL.md to improve progressive disclosure.

Move the static pairing inventory table to a reference file and keep only the decision tree and quick checks inline, since the skill itself notes the list drifts and must be re-checked with ls.

DimensionReasoningScore

Conciseness

Mostly efficient and packed with repo-specific knowledge Claude would not already know (exact vars.AB_* proxies, registry derivation, real diffs), but the proxy-envs capture snippet is repeated across 模式 5, 模式 11, and the Before/After section, and the full before/after re-shows patterns already detailed, so some tightening is possible.

2 / 3

Actionability

Provides fully executable YAML blocks, exact commands (yaml.safe_load check, actionlint, ls .forgejo/workflows/), real before/after diffs, and a copy-paste verification checklist — matching the 'fully executable, copy-paste ready' anchor.

3 / 3

Workflow Clarity

Sequences the work explicitly (同步操作流程 1→6), provides a decision tree, and embeds validation checkpoints (step 5 YAML validation) plus a checklist with a final user-notification feedback step, matching the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

No bundle files exist and the entire ~530-line skill is one monolithic file; the 11 transformation patterns and before/after section could be split into one-level-deep reference files, so content that should be separate is inline even though sections are well organized.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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

The description is specific, trigger-rich, complete, and distinct: it names concrete sync/creation-decision actions, enumerates natural keywords (including colloquial ones), gives explicit what-and-when guidance, and occupies a clear niche. Voice is appropriately third-person/declarative, so no specificity penalty applies.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "同步更新 .forgejo/workflows/ 对应文件保持功能一致" and "判断是否需要新建 Forgejo 版本" — rather than vague domain language, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both what (双轨同步、同步更新、判断新建版本) and when via explicit triggers ("当用户修改或新增...时必须触发", "涉及...时也使用此技能", "即使...也应触发"), meeting the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

Covers natural terms users would say — CI, GitHub Actions, Forgejo Actions, 镜像构建, container registry, artifact, build-*/test-* workflow, plus colloquial "改一下 CI" and "加个 workflow" — giving strong natural-keyword coverage.

3 / 3

Distinctiveness Conflict Risk

Targets a distinct FastGPT-specific niche (dual-track GitHub↔Forgejo CI sync) with triggers unlikely to overlap with other skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (534 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
labring/FastGPT
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.