agentlas-core-engine-meta-agent

Use when creating a single Agentlas agent, creating a multi-agent team, or packaging an existing local/external agent into Agentlas architecture. Make sure to use this for /meta-agent requests.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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.

A concise, well-sequenced instruction-only meta-agent skill with a clear verification step and clean structure. It could tighten actionability on a couple of abstract steps and add error-recovery guidance for the verification step.

Suggestions

Spell out what 'Run mode classification' (step 3) and 'Load only the matching support skills' (step 6) actually do — name the file or decision logic so the step is executable rather than implied.

Add a brief feedback loop after step 10 ('Verify with scripts/verify-package.sh') describing how to handle verification failures before returning output.

Fix the duplicated 'Codex, Codex' in step 9, which looks like a typo and slightly undercuts the otherwise concrete adapter list.

Dimension	Reasoning	Score
Conciseness	Lean, terse procedural steps with no padding or explanation of concepts Claude already knows; every line carries instruction ('Read AGENTS.md', 'Run mode classification').	5 / 5
Actionability	Names concrete file paths (AGENTS.md, .agentlas/mode-map.json, .agentlas/global-commands.json) and a verify command (scripts/verify-package.sh), but some steps like 'Run mode classification' and 'Load only the matching support skills' leave the specific mechanism implied rather than spelled out.	4 / 5
Workflow Clarity	Ten clearly numbered steps with an explicit final verification checkpoint (step 10), but no feedback loop describing what to do when verify-package.sh fails, which keeps it just below the top anchor.	4 / 5
Progressive Disclosure	Under 50 lines with clean ## Procedure and ## Output sections and no bundle files to disclose; per the simple-skill exception, well-organized sections alone warrant the top score.	5 / 5
	Total	18 / 20 Passed

Description

87%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.

A strong, well-structured description that clearly states both capability and trigger conditions with a distinct niche. Minor room to improve keyword synonym coverage and tighten the abstract 'architecture' framing.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions ('creating a single Agentlas agent', 'creating a multi-agent team', 'packaging an existing local/external agent') but 'into Agentlas architecture' is slightly abstract, leaving minor coverage gaps rather than full comprehensiveness.	4 / 5
Completeness	Explicitly answers both what (create/package agents into Agentlas architecture) and when ('Use when...', 'Make sure to use this for /meta-agent requests') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural trigger coverage with 'Use when creating...', 'multi-agent team', and the explicit '/meta-agent requests', but lacks synonyms or alternate phrasings users might say.	4 / 5
Distinctiveness Conflict Risk	The 'Agentlas' niche brand and '/meta-agent' command trigger give it a clear, distinct niche with minimal overlap risk against generic agent skills.	5 / 5
	Total	18 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: agentlas-ai/Agentlas-OS
Path: .agents/skills/agentlas-core-engine-meta-agent/SKILL.md
Commit: a7988bb

Reviewed: 4 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.