CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

git-delegation

将所有 git 操作委托给 Manager 执行。Worker 无法直接访问 git credentials，因此任何需要认证的 git 操作（clone、push、fetch 等）都需要通过此机制委托给 Manager。

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./manager/agent/worker-skills/git-delegation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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.

The body delivers highly actionable, copy-paste-ready delegation protocols with a clear step-by-step workflow and explicit error-recovery guidance. Its main weakness is token efficiency: it re-explains basic git commands and repeats the same message template multiple times where a single parameterized example would suffice.

Suggestions

Delete the 'What Can Be Delegated' glossary (git clone - Clone repositories, etc.) — Claude already knows what these commands do; a single line stating 'any git command can be delegated' preserves the information.

Collapse the three Advanced Operations examples into one line noting that rebase/cherry-pick/merge follow the identical git-request format, instead of repeating the full template each time.

Trim the 'Step-by-Step Workflow' and 'Advanced Operations' sections to a single canonical message template plus a field description, since the format is already fully specified under 'Message Format'.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: a 16-entry glossary explaining what "git clone - Clone repositories" and "git stash - Stash changes" do (concepts Claude already knows), and the Advanced Operations section repeats the full git-request message template verbatim three times for one-line command differences. This matches anchor 2's several padded sections rather than anchor 3's mostly-efficient-with-some-tightening.

2 / 5

Actionability

Fully executable guidance throughout: copy-paste ready message formats with exact paths (/root/agentteams-fs/shared/tasks/{task-id}/workspace/{repo-name}), a concrete env-var lookup (echo $AGENTTEAMS_MATRIX_DOMAIN), exact success/failure response formats (git-result:/git-failed:), and good/bad request contrast examples.

5 / 5

Workflow Clarity

A clear 5-step sequence with a pre-flight checkpoint (processing-marker check), wait-for-response semantics, and an explicit error-recovery loop ("read the error and send ONE corrected request"). Minor validation gaps (no post-clone or post-sync verification) keep it below anchor 5.

4 / 5

Progressive Disclosure

A single well-sectioned file with clear headers and easy navigation; the message format, workspace convention, and critical rules are appropriately placed. The command glossary and repetitive Advanced Operations examples could be split into a reference file, giving minor organization gaps consistent with anchor 4.

4 / 5

Total

15

/

20

Passed

Description

75%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.

The description clearly communicates both the capability (delegating authenticated git operations to the Manager) and the condition under which it applies, using concrete operation names as triggers. It would score higher with a more comprehensive list of delegatable operations and an explicit "Use when..." trigger clause.

DimensionReasoningScore

Specificity

Names the concrete domain (delegating git operations to the Manager) and lists specific operations ("clone、push、fetch 等"), plus the blanket "all git operations" claim. It stops short of anchor 5 because coverage is not comprehensive (commit, merge, rebase, tag unlisted) and is well above anchor 3's 1-2 concrete actions.

4 / 5

Completeness

The "what" is clear (delegate all git operations to the Manager) and the "when" is explicitly stated ("任何需要认证的 git 操作...都需要通过此机制委托给 Manager"), so it exceeds anchor 3. It is not anchor 5 because the trigger guidance is phrased as rationale ("Worker 无法直接访问 git credentials，因此...") rather than a direct "Use when..." directive.

4 / 5

Trigger Term Quality

Includes natural keywords users would say ("git", "clone", "push", "fetch", "credentials", "delegate") with good coverage, but common variations like pull, commit, merge, and rebase are missing, matching anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The Worker/Manager/credentials context carves a clear niche with minimal conflict risk, though the blanket "将所有 git 操作" claim overlaps with any other git-related skill (e.g., a github-operations skill), matching anchor 4's minor overlap risk.

4 / 5

Total

16

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

agentscope-ai/AgentTeams

Path

manager/agent/worker-skills/git-delegation/SKILL.md

Revision

8a661dd

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill