CtrlK
BlogDocsLog inGet started
Tessl Logo

git-delegation

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

61

Quality

72%

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

85%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 templates, clear sequencing, and explicit error-handling checkpoints, its main weakness being redundancy from repeating the same message format across multiple sections.

Suggestions

Collapse the repeated full message templates into one canonical example and have later sections show only the differing operations list.

Merge the 'What Can Be Delegated' list and the comparison table to remove duplication of the delegable-commands information.

DimensionReasoningScore

Conciseness

The content is accurate and concrete but repeats the full message template many times (Message Format, Step 2, Step 5, and three Advanced examples) and duplicates the delegation scope as both a list and a table; not 3 because it could be tightened substantially.

2 / 3

Actionability

Provides copy-paste-ready message templates, real workspace paths, the domain-lookup command, and complete operation lists — fully executable guidance with specific examples.

3 / 3

Workflow Clarity

A clear 5-step sequence with explicit response states (git-result:/git-failed:), a processing-marker validation checkpoint, and an error-recovery loop (read the error, send one corrected request).

3 / 3

Progressive Disclosure

Single well-organized SKILL.md with no bundle files needed; sections (delegable commands, message format, workflow, advanced, critical rules) are clearly labeled and navigable, which earns 3 for a self-contained skill.

3 / 3

Total

11

/

12

Passed

Description

60%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 and accurately conveys the delegation mechanism for authenticated git operations, but it lacks an explicit trigger clause and leans on internal architecture jargon rather than natural user phrasing.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when a Worker needs to run git commands that require authentication such as clone, push, or fetch').

Reframe the description in natural user-facing terms alongside the technical mechanism so trigger terms match what a user would actually say.

Clarify the boundary with github-operations in the description itself so it is distinguishable without reading the body.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("clone、push、fetch 等") within the git domain, matching the top anchor rather than the vague 'names domain and some actions' level below.

3 / 3

Completeness

Clearly states what the skill does but the 'when' is only implied through the credential explanation, with no explicit 'Use when...' trigger clause — which caps completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Includes relevant keywords (clone, push, fetch) but frames everything around the internal 'Manager/Worker/credentials' mechanism rather than natural user phrasing; missing common variations. Not 3 because a user would not naturally say 'delegate to Manager'.

2 / 3

Distinctiveness Conflict Risk

Targets a clear niche (auth-gated git operations for Workers) yet overlaps with adjacent skills such as github-operations; not 3 because the boundary is only disambiguated in the body, not the description.

2 / 3

Total

9

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
agentscope-ai/AgentTeams
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.