CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentlas-cloud

Use when the user types /agentlas-cloud, /agentlas cloud, or /hep-cloud to staff only from the signed-in owner's private Cloud packages.

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 ./codex/plugins/agentlas-core-engine-meta-agent/skills/agentlas-cloud/SKILL.md
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.

An extremely lean alias stub that is token-efficient and structurally correct as a redirect, but it carries almost no standalone value: no executable guidance, and its only reference (hephaestus-cloud/SKILL.md) is not present in the bundle, so a reader following it cold would hit a dead end.

Suggestions

Ensure the referenced target hephaestus-cloud/SKILL.md actually ships alongside this skill (or reference it by a path that resolves in the installed bundle), since the body's sole instruction depends on it.

Add 1-2 concrete fallback lines describing what 'staff specialist roles from the owner's private Agentlas Cloud repository' entails (e.g. which command to run or which section of the target protocol to start with) so the skill is minimally actionable if the target is unavailable.

Consolidate the heading, description, and body alias statements — '/agentlas-cloud, /hep-cloud' and 'Alias for hephaestus-cloud and /agentlas cloud' repeat the same alias information twice in three lines.

DimensionReasoningScore

Conciseness

The 6-line body is entirely lean — no concept explanations, no padding, every line serves the redirect. The 'Alias for...' line slightly duplicates the heading but this is trivially small.

5 / 5

Actionability

The only guidance is the pointer "See [hephaestus-cloud](hephaestus-cloud/SKILL.md) for full execution protocol" — a high-level hint with no executable steps, and the referenced path does not exist in the skill's bundle (no references/, scripts/, assets/, or sibling directory), so the body provides no self-contained actionable instruction.

2 / 5

Workflow Clarity

The single redirect action is stated unambiguously, but the entire workflow is delegated to an external, unverifiable reference with no checkpoints — the body itself defines no sequence a reader could follow if the target is absent.

3 / 5

Progressive Disclosure

A pure one-level-deep, clearly signaled reference — exactly the right structure for an alias skill — with no bundle files to organize. Held below 5 because the body has no internal organization (bare heading plus prose) and its sole reference target is dangling within the bundle.

4 / 5

Total

14

/

20

Passed

Description

73%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 well-targeted, concise trigger-first description whose command-based triggers are precise and natural. Its main weakness is the underspecified 'what' — 'staff' from 'private Cloud packages' conveys the domain but almost nothing about the actual capability.

Suggestions

Expand the 'what' clause with 1-2 concrete actions, e.g. 'Staff specialist roles (e.g. reviewers, researchers) from the signed-in owner's private Agentlas Cloud packages, restricted to that repository only.'

Add one or two natural non-command trigger phrases (e.g. 'workforce', 'cloud packages', 'private packages') so users who describe the need without typing the command can still match the skill.

DimensionReasoningScore

Specificity

"staff only from the signed-in owner's private Cloud packages" names the domain (private Cloud packages) and one concrete action (staffing), but the action is never elaborated — no mention of what roles, packages, or operations are involved.

3 / 5

Completeness

Both parts are present: an explicit "Use when the user types..." trigger clause and a what-statement ("staff only from the signed-in owner's private Cloud packages"). The 'when' is fully explicit while the 'what' is thin and underspecified, so it does not reach the level-5 anchor.

4 / 5

Trigger Term Quality

The three natural command variants ("/agentlas-cloud", "/agentlas cloud", "/hep-cloud") are exactly the phrases a user would type, giving good keyword coverage, but there are no synonyms or descriptive keywords (e.g. "workforce", "specialist roles", "private packages") beyond the literal command forms.

4 / 5

Distinctiveness Conflict Risk

Exact-command triggers create a clear niche with minimal wrong-skill risk, but the description self-identifies as an alias of hephaestus-cloud and the generic words "staff" and "Cloud" carry minor overlap risk with closely related skills.

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

agentlas-ai/Agentlas-OS

Path

codex/plugins/agentlas-core-engine-meta-agent/skills/agentlas-cloud/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.