CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentlas-operations

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

Quality

86%

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

The canonical home for this skill is agentlas-operations in agentlas-ai/Agentlas-OS

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 exceptionally lean and actionable operations skill: exact tool invocations, parameters, and failure semantics throughout, with a validated main workflow. The only notable flaws are the skipped section number (no section 2) and the reference to an INDEX.md that is absent from the bundle.

DimensionReasoningScore

Conciseness

Every line carries operational content — tool names, parameters, and measured gotchas marked '실측' — with no explanation of concepts the model already knows and no padding. The hostModelPolicy paragraph is dense constraint language ('Never launch unless executionAllowed is true'), not over-explanation.

5 / 5

Actionability

Names exact tools, parameters, and syntax throughout: 'workforce.search_candidates' with 'sourceScope=network', 'workforce.prepare_execution(projectDir 필수)', 'marketplace.search_agents', 'get_runtime_bundle', 'agentlas.memory.preflight', the JSON field '"supersedes":"<h:16hex>"', and concrete error semantics ('owner_only', 503 'WRITE_MODE=blocked'). For an instruction-only skill this is fully executable guidance.

5 / 5

Workflow Clarity

Section 1 gives a clear 6-step sequence with explicit checkpoints (validate_selection rejecting redacted copies, the executionAllowed launch gate), and the pitfalls section supplies error semantics. Not 5 because section numbering skips from 1 to 3 and the asset/memory flows have thinner validation; not 3 because the main workflow's checkpoints are explicit.

4 / 5

Progressive Disclosure

Well-organized sections with a single clearly-signaled, one-level-deep reference ('[INDEX.md](INDEX.md)') declared as the canonical tool registry. Not 5 because INDEX.md is not present in the bundle (no references/, scripts/, or assets/ directories exist), leaving a dangling link; not 3 because structure and reference signaling are otherwise good.

4 / 5

Total

18

/

20

Passed

Description

78%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 specific, distinctive description that clearly bounds an internal operations niche and includes an explicit when-clause. Its main limitations are noun-phrase topic areas instead of concrete action verbs and the absence of trigger synonyms or variations.

Suggestions

Convert topic nouns into concrete action verbs, e.g. 'workforce 로스터를 재사용하고 부족할 때만 후보를 검색·선발한다' (reuse rosters, search and select candidates only when short), to lift specificity.

Add one or two natural trigger variations users might say, such as '에이전트 모집', '후보 검색', or 'workforce 편성', so trigger_term_quality reaches comprehensive coverage.

DimensionReasoningScore

Specificity

Lists four named operation areas — 'hep-network 편성', 'cargo/Agent Cloud·marketplace 활용', 'workforce 로스터 재사용', '메모리 계약' — going beyond the 1-2 concrete actions of anchor 3. It falls short of anchor 5 because '활용' (utilization) and '메모리 계약' (memory contract) are topic nouns rather than concrete action verbs.

4 / 5

Completeness

Both parts are explicit: the 'what' enumerates four procedure domains, and the 'when' is stated as 'One(개인 에이전트)이 Agentlas를 조작할 때 이 절차를 따른다' (follow this when One operates Agentlas). Not 3 because the when-clause is explicitly present; not 5 because it is a single trigger condition without multiple concrete trigger phrases.

4 / 5

Trigger Term Quality

Domain terms 'Agentlas', 'hep-network', 'workforce 로스터', 'cargo', 'Agent Cloud', 'marketplace', and 'One(개인 에이전트)' match what an operator of this system would naturally say, giving good keyword coverage. It is not 5 because no synonyms or common variations are offered.

4 / 5

Distinctiveness Conflict Risk

Proper-noun system names (Agentlas, hep-network, One personal agent) establish a clear niche with distinct triggers and minimal conflict risk with any other skill.

5 / 5

Total

17

/

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-operations/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.