CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentlas

Single entry point for every Agentlas command: /agentlas network, /agentlas build, /agentlas storm, /agentlas goal, /agentlas one, /agentlas upload, /agentlas cloud, /agentlas hub, /agentlas local, /agentlas browser, /agentlas call, /agentlas search.

Quality

55%

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 ./.agents/skills/agentlas/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

36%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 is a tidy 12-command index with a clear hyphenated/spaced/Hephaestus mapping, but it is purely descriptive: no execution steps, no validation, and no pointers to per-command detail. As the 'single entry point' it leaves Claude with nothing actionable beyond command normalization.

Suggestions

State explicitly what Claude should do when a command arrives (e.g., 'When /agentlas <command> <args> is invoked, execute the corresponding /hep-<command> skill with the same args') so the routing action is an instruction rather than an implied correspondence.

Add per-command execution workflows or reference files (e.g., commands/build.md) covering the multi-step operations like upload's gate-scan-publish flow, including validation checkpoints before publish.

Trim the table to command name + description and let the stated 1:1 mapping rule carry the hyphenated/spaced/hep variants, cutting roughly two-thirds of the table cells.

DimensionReasoningScore

Conciseness

The body is short with no padded prose or explanations of known concepts, but the table repeats each command name across three columns ('/agentlas-network <goal>', '/agentlas network <goal>', '/hep-network <goal>') that are all mechanically derivable from the stated rule 'Both hyphenated forms ... and space-separated forms ... are fully supported and correspond 1:1 to the Hephaestus (/hep-<command>) shortcuts'. Roughly two-thirds of the table cells are redundant given that rule, so it could be tightened considerably.

3 / 5

Actionability

The only concrete guidance is the command-normalization rule and one-line purpose hints per command (e.g., 'Design & package single agents or multi-agent teams'); there are no steps, procedures, or instructions for what to actually do when any command is invoked. It describes rather than instructs, sitting just above the purely-vague anchor because the mapping rule and per-command summaries are specific.

2 / 5

Workflow Clarity

No sequence of actions is stated for any of the 12 commands the skill fronts (staffing workforces, running execution loops, publishing packages), and no validation checkpoints exist despite commands like upload ('Gate scan & publish agent/team packages') implying batch/gated operations. The table itself is a coherent index, which keeps this just above the incoherent/no-structure anchor, but every execution workflow is a gap.

2 / 5

Progressive Disclosure

The body is well-organized (heading, mapping rule, clean table) but claims to be the 'Single entry point for every Agentlas subsystem and capability' while providing no references to where any subsystem's detail lives — no bundle files exist and no paths are cited. The simple-skill exception for under-50-line skills requires 'no need for external references', which does not hold for a 12-subsystem router, so this lands at 'some structure but references missing'.

3 / 5

Total

10

/

20

Passed

Description

53%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 well-scoped and unambiguous about which commands it fronts, with low conflict risk thanks to the branded, enumerated command list. However, it describes no concrete capabilities, omits any 'Use when...' trigger guidance, and offers only literal command names with no natural-language synonyms.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user invokes an /agentlas or /hep command or asks to staff, build, or publish Agentlas agents'.

Briefly state what the key commands do (e.g., 'build designs and packages agents; storm runs a force-robust execution loop') so the description conveys capabilities, not just command names.

Include a few natural-language synonyms users might say beyond the literal slash commands, such as 'agent teams', 'workforce staffing', or 'browser automation'.

DimensionReasoningScore

Specificity

It names the domain ('every Agentlas command') and enumerates 12 concrete command tokens (/agentlas network, build, storm, ...), which is more concrete than a bare domain label, but it states no verb-object capabilities for any command — what 'network', 'build', or 'storm' actually do appears only in the body, not the description. This matches 'names domain and some concrete content, but not comprehensive' rather than score 4's 'lists several specific actions'.

3 / 5

Completeness

The 'what' is reasonably clear (a single entry point routing 12 named commands), but there is no 'Use when...' clause or equivalent trigger guidance anywhere, which caps completeness at 3 per the judging guidelines. It does not reach score 4 because the 'when' is only weakly implied by the command list itself.

3 / 5

Trigger Term Quality

The command tokens are exactly what a user would type to invoke the skill, so they are relevant keywords, but the description includes no natural-language variations or synonyms (e.g., 'agent teams', 'workforce', 'browser automation') — only the literal slash-command names. This matches 'some relevant keywords but missing common variations or synonyms' rather than score 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The description is tightly scoped to the 'Agentlas' proper noun with an enumerated command list, making it clearly distinguishable from generic skills. It stops short of score 5 because the body reveals closely related Hephaestus shortcuts and per-command variants that this entry point overlaps with, and the absence of explicit trigger phrases leaves minor overlap risk with those sibling command skills.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agentlas-ai/Agentlas-OS

Path

.agents/skills/agentlas/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.