CtrlK
BlogDocsLog inGet started
Tessl Logo

chinese-git-workflow

国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。

64

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/chinese-git-workflow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured reference for domestic Git platforms with concrete commands and complete CI examples, weakened by re-explaining standard Git/Conventional-Commits knowledge and by being a single large file with no progressive disclosure into reference files.

Suggestions

Move the per-platform CI/CD YAML blocks, the PR/MR template, and the .gitignore into separate files under references/ and link to them one level deep, keeping SKILL.md as an overview.

Trim or summarize the Git Flow branch-role explanations and the Conventional Commits type+emoji table, since Claude already knows these; keep only the China-specific deltas (e.g., TAPD/JIRA编号 linkage, 中文 commit examples).

Add an explicit '选择平台 → 配置 SSH/HTTPS/凭据 → 选分支模型 → 配置 CI → 提交/PR → 推送前过检查清单' numbered sequence so the implied workflow becomes a concrete validated process.

DimensionReasoningScore

Conciseness

Dense platform-specific config and CI YAMLs earn their place, but the body re-explains standard concepts Claude already knows (Git Flow branch roles, the full Conventional Commits type+emoji table, generic branch-naming conventions), so it could be tightened by offloading those to references.

3 / 5

Actionability

Provides copy-paste-ready git remote/SSH/config commands and complete CI pipeline definitions for Gitee Go, Coding CI (Jenkinsfile), 极狐 GitLab CI, and CNB, plus a .gitignore and PR template covering the common per-platform cases.

5 / 5

Workflow Clarity

Three branch models are presented with clear selection criteria ('适合:…') and rules, the section ordering implies a config→branch→CI→commit→PR sequence, and a pre-push 检查清单 acts as a validation checkpoint; minor gaps are the absence of explicit feedback loops, which a config-reference skill does not strictly require.

4 / 5

Progressive Disclosure

Section headers are well organized, but the entire ~543-line skill is a monolithic single file with no bundle files (references/, scripts/, assets/ absent) and no one-level-deep references, so content that belongs in separate files (per-platform CI configs, PR template, .gitignore, commit conventions) is fully inlined.

3 / 5

Total

15

/

20

Passed

Description

87%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 well-crafted description that names specific platforms and config domains, answers both what and when with an explicit invocation trigger, and stays in third person. Minor passive framing and a few missing synonyms keep it just short of perfect on specificity and trigger-term breadth.

DimensionReasoningScore

Specificity

Names four specific platforms (Gitee, Coding.net, 极狐 GitLab, CNB) and several concrete config areas (SSH/HTTPS/凭据/CI 接入/镜像同步), but frames them passively as '配置参考' (configuration reference) rather than action verbs, leaving minor coverage gaps relative to a fully action-oriented statement.

4 / 5

Completeness

Clearly states both what it does (国内 Git 平台 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置) and when to use it ('仅在用户显式 /chinese-git-workflow 时调用'), with a concrete explicit trigger phrase in third-person voice.

5 / 5

Trigger Term Quality

Good natural keyword coverage via the four named platforms plus SSH/HTTPS/CI/镜像同步 and an explicit /chinese-git-workflow trigger, but lacks common synonyms like 代码托管 or 私有化部署 that a user might naturally say.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (domestic Chinese Git platforms with named providers) and explicitly restricts auto-triggering, giving it distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

12

/

16

Passed

Repository
jnMetaCode/superpowers-zh
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.