CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cross-agent-delegation

Cross-agent task routing — Codex auto-review, Kimi delegation by complexity score (iCPG + Claude reasoning), iCPG + Mnemos mandatory for all agents

58

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cross-agent-delegation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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 content is highly actionable with a clear, validated multi-step orchestration workflow and strong sequencing, undermined mainly by duplicated sections (two Step 4 headings and two 'When NOT to Delegate' lists) that hurt conciseness.

Suggestions

Merge the two '### When NOT to Delegate' sections (lines ~86 and ~136) into one authoritative list to remove redundancy.

Fix the duplicate '### Step 4' headings — renumber 'Read Results' to Step 5 (or similar) so the sequence is unambiguous.

Consider moving the iCPG and Mnemos per-call command tables into reference bundle files so the main SKILL.md stays a lean overview.

DimensionReasoningScore

Conciseness

The body is largely efficient tables and code, but it carries redundant structure — two '### Step 4' headings (Delegate via Bash / Read Results) and two '### When NOT to Delegate' sections with overlapping bullets — that should be tightened, landing at 'mostly efficient but some unnecessary content' rather than 4.

3 / 5

Actionability

It provides concrete, executable bash (icpg queries, mnemos checkpoints, kimi --print invocation, complexity auto-collect) that is mostly copy-paste ready, with only minor gaps like the '<specific task description>' placeholder.

4 / 5

Workflow Clarity

The routing table, override checklist, and full ASCII orchestration flow lay out a clear sequence with explicit validation checkpoints (tdd-loop-check, tests pass) and a feedback loop (Codex findings re-prompt Kimi → fix → retry), matching the top anchor.

5 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized with clear section headers and one-level navigation, placing most content appropriately with only minor organization gaps (the iCPG/Mnemos quick-reference blocks could live separately).

4 / 5

Total

16

/

20

Passed

Description

62%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 is specific and distinct, naming concrete cross-agent routing actions, but lacks any explicit 'when to use' trigger guidance and leans on internal jargon (iCPG, Mnemos) over natural user phrases.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill (e.g., when multiple AI CLI tools are available and a task should be delegated).

Soften jargon with a natural-language gloss so trigger terms match what a user would actually say (e.g., 'complexity score' → 'how hard a change is').

Ensure the description answers both 'what' and 'when' explicitly to lift completeness above the missing-trigger cap of 3.

DimensionReasoningScore

Specificity

Names several concrete actions — 'Codex auto-review', 'Kimi delegation by complexity score', 'iCPG + Mnemos mandatory' — with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the comprehensive 5.

4 / 5

Completeness

It states a clear 'what' (cross-agent routing, Codex review, Kimi delegation) but has no 'Use when...' or equivalent trigger clause, so per the missing-trigger cap it cannot exceed 3.

3 / 5

Trigger Term Quality

Relevant terms like 'cross-agent', 'task routing', 'Codex auto-review', and 'Kimi delegation' appear, but jargon-heavy items ('iCPG', 'Mnemos') dominate and common natural variations are missing, so it sits at 'some relevant keywords' rather than 'good coverage'.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche — orchestrating delegation specifically among Claude, Kimi, and Codex — with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

15

/

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

alinaqi/maggy

Path

skills/cross-agent-delegation/SKILL.md

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.