CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

67%

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-claude/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

61%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 actionable, well-structured guidance with concrete tool-call examples and a clear step sequence, undermined by repetitive guardrail restatements and a memory-recording step that assumes success instead of validating it. Trimming duplication and adding a verification checkpoint before writing combinations would lift the weakest dimensions.

Suggestions

State the guardrail once (in Core Concepts or Step 1) and reference it elsewhere; also state the catalog URL and 9-category list a single time to remove duplicated content.

Replace Step 4's 'Assume the task was completed successfully' with an explicit validation checkpoint — verify the task outcome (or confirm with the user) before running memory_write, so only verified combinations enter institutional memory.

Move the full 9-category catalog listing and/or the extended examples into a reference file (e.g. references/catalog.md) and link to it, keeping SKILL.md a lean overview.

DimensionReasoningScore

Conciseness

The body is mostly efficient and teaches genuinely novel material (agent-memory-mcp calls, catalog URL, guardrail logic), but the guardrail is restated four times (Overview, Core Concepts, Step 1, Example 1 plus Best Practices), the catalog URL is repeated verbatim twice, and all 9 categories are listed inline then re-referenced. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than level 2's noticeably padded profile.

3 / 5

Actionability

Concrete, near-executable guidance dominates: exact memory_write/memory_search/memory_read call syntax with arguments, a fetchable catalog URL, and a worked guardrail example. Minor gaps remain — 'the current environment's skill list or equivalent discovery mechanism' is vague, and Step 4's 'Assume the task was completed successfully' instructs recording without any success check — so it sits at 'mostly executable guidance with minor gaps' rather than fully copy-paste-ready level 5.

4 / 5

Workflow Clarity

The four-step sequence is clearly ordered with bracketed trigger conditions and decision branches (if YES stop / if NO proceed; memory found / not found), but validation checkpoints are missing — Step 4 explicitly says to 'Assume the task was completed successfully' before recording a combination, an anti-checkpoint that risks persisting unverified knowledge. This matches 'steps listed but validation gaps; checkpoints missing or implicit'.

3 / 5

Progressive Disclosure

No bundle files exist, and the single-file structure uses clear, well-ordered sections (When to Use, Core Concepts, Step-by-Step, Examples, Best Practices) that are easy to navigate. Minor gaps: at ~110 lines, the full 9-category catalog listing and the extended examples could be split into reference files, keeping SKILL.md leaner — 'good structure; most content appropriately placed; minor organization gaps' rather than the well-signaled multi-file ideal of level 5.

4 / 5

Total

14

/

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 communicates a clear and fairly specific capability set for a niche meta-skill, but it omits any 'when to use' trigger guidance and lacks the natural phrases users would say when needing it. Adding a 'Use when...' clause with concrete trigger terms would resolve the two weakest dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when a task spans multiple domains requiring several skills, when unsure which skills to pick, when asked to orchestrate or combine skills, or when looking up previously successful skill combinations.'

Include natural user phrasings/synonyms such as 'orchestrate skills', 'combine skills', 'pick the right skills', and 'complex multi-step task' so the description matches what users actually say.

Replace the vague 'understands task requirements' with the concrete evaluation action it performs, e.g. 'evaluates task complexity to decide whether specialized skills are needed'.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'dynamically selects appropriate skills', 'tracks successful skill combinations using agent-memory-mcp', 'prevents skill overuse for simple tasks' — though 'understands task requirements' is generic filler. Coverage has minor gaps (catalog discovery, memory retrieval are unstated), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive level 5 or the 1-2-action level 3.

4 / 5

Completeness

The 'what' is clear (evaluate tasks, select skills, track combinations, guard against overuse), but there is no 'Use when...' clause or equivalent explicit trigger guidance — 'for simple tasks' describes a guardrail condition, not when to invoke the skill. Per the judging guidelines, a missing 'Use when...' caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ('skill combinations', 'simple tasks', 'agent-memory-mcp'), but the natural phrases a user would say — 'orchestrate skills', 'combine skills', 'which skill should I use', 'complex multi-step task' — are absent. This matches 'some relevant keywords but missing common variations or synonyms', below level 4's good coverage and above level 2's purely generic set.

3 / 5

Distinctiveness Conflict Risk

The meta-skill orchestration niche with memory-backed combination tracking is mostly distinct from domain-specific skills, though 'understands task requirements, dynamically selects appropriate skills' could overlap with other orchestration/planning meta-skills. This fits 'mostly distinct; minor overlap risk' better than the clear-niche level 5 or the overlap-prone level 3.

4 / 5

Total

14

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

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