CtrlK
BlogDocsLog inGet started
Tessl Logo

antigravity-skill-orchestrator

A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.

48

Quality

51%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/antigravity-skill-orchestrator/SKILL.md

The canonical home for this skill is antigravity-skill-orchestrator in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

60%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 skill body is well-structured with a clear sequenced workflow and concrete memory-tool examples, but it suffers from repeated guardrail restatements and abstract discovery guidance that limit conciseness and actionability. It is a solid, navigable overview that would benefit from tightening and more executable detail.

Suggestions

Consolidate the guardrail message into one section and reference it rather than restating it in the Overview, Core Concepts, Step 1, Best Practices, and Example 1.

Replace abstract discovery instructions with concrete, executable steps (e.g., an actual command or tool call to list locally available skills and a worked fetch command for the catalog URL).

Add a verification checkpoint in Step 4 before recording a combination so success is confirmed rather than assumed, and capture failure cases as memory for future avoidance.

DimensionReasoningScore

Conciseness

The body is mostly on-point but restates the guardrail across the Overview, Core Concepts, Step 1, Best Practices, and Example 1, and includes some obvious filler ('Not every task requires a specialized skill', 'Over-engineering simple tasks wastes tokens and time'), so it could be tightened.

3 / 5

Actionability

The memory_search/memory_read/memory_write examples are concrete and copy-pasteable, but the core selection guidance is abstract ('Query the locally available skills using the current environment's skill list or equivalent discovery mechanism', 'Scan the catalog's 9 main categories') with no executable command for discovery.

3 / 5

Workflow Clarity

A clear four-step sequence (Evaluate -> Retrieve Past Knowledge -> Discover/Select -> Apply/Track) with numbered sub-steps and decision branches (YES/NO stop, memory-exists/not, local-sufficient/not) provides most checkpoints, though it merely assumes success in the tracking step without verifying the combination actually worked.

4 / 5

Progressive Disclosure

The body is a single well-organized SKILL.md with clear section headers and one-level-deep external pointers (the catalog URL and the @agent-memory-mcp skill) with no nested references; no bundle files are provided, and content is appropriately placed with minor organization gaps around the inlined 9-category list and worked examples.

4 / 5

Total

14

/

20

Passed

Description

42%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 purpose but lacks explicit trigger guidance and leans on technical jargon over natural user language, capping completeness and trigger-term quality. It is serviceable but not optimized for discoverability.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when orchestrating multiple skills for a complex multi-domain task, combining skills, or recalling past successful skill combinations.'

Replace abstract verbs ('understands task requirements') with concrete actions the orchestrator performs, such as 'evaluates task complexity, selects minimal skill sets, and records proven combinations'.

Include everyday synonyms users would say ('combine skills', 'pick the right skills', 'reuse a workflow that worked before') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

It names the domain and several actions ('dynamically selects appropriate skills', 'tracks successful skill combinations', 'prevents skill overuse'), but the verbs read more abstractly than anchor-4 examples like 'extracts text, fills forms, converts to images', and 'understands task requirements' is vague filler.

3 / 5

Completeness

It gives a clear 'what' (a meta-skill that selects, tracks, and guards against skill overuse) but entirely omits any 'when to use it' guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

The description relies on technical jargon ('meta-skill', 'agent-memory-mcp', 'skill overuse') with only generic keywords like 'task requirements' and 'skills'; it lacks the natural phrases a user would actually say, and contains no 'Use when...' trigger terms.

2 / 5

Distinctiveness Conflict Risk

The orchestration-plus-memory niche ('tracks successful skill combinations using agent-memory-mcp') is somewhat specific, but broad phrases like 'understands task requirements' and 'selects appropriate skills' leave overlap risk with general task-evaluation skills.

3 / 5

Total

11

/

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.

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
administrakt0r/AI-Agents-Safe-Coding-Skills
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.