CtrlK
BlogDocsLog inGet started
Tessl Logo

agentlas-operations

Agentlas 시스템 운용 절차 — hep-network 편성, hep-graph 자동화, cargo/Agent Cloud·marketplace 활용, workforce 로스터 재사용, 메모리 계약. One(개인 에이전트)이 Agentlas를 조작할 때 이 절차를 따른다.

63

Quality

75%

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-operations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 an efficiently written, actionable operational procedure with concrete tool calls and a well-sequenced, validation-gated core workflow. Its main gaps are missing example payloads and a non-bundled INDEX.md reference.

DimensionReasoningScore

Conciseness

The body is lean and dense — short numbered/bulleted procedures with no padding and no explanation of concepts Claude already knows; every line earns its place and competence is assumed.

5 / 5

Actionability

Concrete tool calls with parameters are given throughout (workforce.search_candidates with sourceScope=network, get_runtime_bundle BYOM, agentlas.memory.preflight), but full example payloads are absent, leaving minor gaps versus copy-paste-ready 5.

4 / 5

Workflow Clarity

Section 1 is a clearly sequenced 5-step workflow with explicit validation gates (validate_selection, reject-abbreviated results, preflight) and decision conditions, but some later sections are bullet lists rather than fully checkpointed sequences.

4 / 5

Progressive Disclosure

Content is well-organized into five labeled sections and stays under 50 lines, but the body references INDEX.md as a canonical index while no bundle files are shipped, a minor organization gap versus the clean self-contained 5.

4 / 5

Total

17

/

20

Passed

Description

67%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 clearly scopes a distinct operational niche and names concrete procedure areas, with an explicit when-clause tied to the acting agent. It is held back by jargon-heavy trigger terms and a when-clause that names the actor rather than natural trigger situations.

Suggestions

Add a 'Use when ...' clause naming concrete trigger situations (e.g., composing a workforce roster, installing a marketplace agent, writing a memory event) rather than only naming the acting agent.

Soften technical jargon with one or two natural user-facing phrases or synonyms so the description triggers on how a user would actually phrase the need.

Convert the domain labels into verb-object actions (e.g., 'compose hep-network rosters', 'automate repeatable tasks with hep-graph') for fuller concreteness.

DimensionReasoningScore

Specificity

Lists several concrete procedure areas — 'hep-network 편성, hep-graph 자동화, cargo/Agent Cloud·marketplace 활용, workforce 로스터 재사용, 메모리 계약' — but these are domain labels rather than fully fleshed verb-object actions, leaving minor gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

Answers both what (five operation areas) and when ('One(개인 에이전트)이 Agentlas를 조작할 때 이 절차를 따른다'), but the when-clause identifies the actor rather than naming concrete trigger situations, so it is not the fully explicit 5.

4 / 5

Trigger Term Quality

Relevant system-domain keywords (hep-network, hep-graph, cargo, workforce, marketplace) are present but lean technical jargon; natural user-facing phrasings and synonyms a user would actually say are missing.

3 / 5

Distinctiveness Conflict Risk

The Agentlas-system-operation niche is clearly distinct from unrelated skills, but the broad 'operates Agentlas' framing leaves minor overlap risk with sibling Agentlas 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
agentlas-ai/Agentlas-OS
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.