git-delegation

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

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

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

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.

The body is highly actionable and workflow-clear with explicit validation and error-recovery loops, and is well structured for a single-file skill. Its main weakness is verbosity from repeating the message template and rules verbatim multiple times, which inflates the token budget without adding information.

Suggestions

Define the `git-request:` message format once in the Message Format section and reference it from the workflow/advanced examples instead of repeating the full template six times.

Consolidate the repeated workspace-path and 'plan first, send once' guidance into a single Critical Rules entry rather than restating across sections.

Move the verbose 'Good vs Bad' multi-request example into a short principle plus a single canonical example to cut redundant tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but the full git-request message template is repeated nearly verbatim six times across sections and several rules are restated, so it could be meaningfully tightened by defining the format once and referencing it.	3 / 5
Actionability	Fully executable guidance throughout: exact message templates, real `mc mirror`/`agentteams-sync` commands, concrete workspace path patterns, and copy-paste-ready examples covering clone, branch, commit, push, rebase, cherry-pick, and merge.	5 / 5
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints (processing-marker check before changes, sync before/after) and a defined error-recovery feedback loop via `git-failed:` ('read the error and send ONE corrected request').	5 / 5
Progressive Disclosure	Well-organized single-file structure with clear section headers, a comparison table, a separated step-by-step workflow, and an advanced-operations section; no bundle files exist. Minor gaps only — the ~310 lines of repeated templates could arguably be consolidated, but navigation is easy.	4 / 5
	Total	17 / 20 Passed

Description

58%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 conveys a clear, specific niche (auth-required git delegation to Manager) with concrete example operations, but lacks an explicit 'Use when...' trigger clause and has moderate keyword coverage. Adding natural trigger phrasing and more synonym/verb coverage would lift completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a Worker needs to run authenticated git commands (clone, push, fetch, pull) and lacks git credentials.'

Broaden natural trigger terms to include common variations users say: 'push code', 'clone a repo', 'pull changes', 'commit and push', 'git authentication'.

State the what/when split more sharply so the 'when' is explicit rather than implied by the credential constraint.

Dimension	Reasoning	Score
Specificity	Names the domain (delegating git operations to Manager) and lists several concrete authenticated operations — "clone、push、fetch 等" — plus the general class of any auth-required git command; minor coverage gaps keep it just below comprehensive.	4 / 5
Completeness	It clearly states what the skill does (delegate git ops to Manager), but the 'when' is only weakly implied via the Worker/credential constraint rather than an explicit 'Use when...' trigger clause, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Relevant keywords (git, clone, push, fetch, credentials, delegate) are present, but common natural synonyms and variations a user would say are limited, so it sits at 'some relevant keywords' rather than full coverage.	3 / 5
Distinctiveness Conflict Risk	The credential-isolation delegation niche is clearly distinct from generic git skills; only minor overlap risk with the related github-operations skill, which the body itself disambiguates.	4 / 5
	Total	14 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 223ddc2

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.