CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentlas-packaging

Use when converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 lean, largely actionable packaging procedure with concrete file paths, countable constraints, and an explicit verify-and-fix loop. The main weaknesses are the vague duplication between steps 8 and 9, missing execution specifics for the global-command and secret-removal steps, and a dense inline workforce-field spec whose referenced support files are not present in the bundle.

Suggestions

Merge step 9 into step 8, or name the exact public-safety check commands, to remove the vague overlap between "Run package verification and public-safety checks before release" and the verify-team-package.sh step.

Move the workforce résumé field specs (roles/communities/skills/knowledge counts and ontology graph rules) into a reference file such as references/workforce-card.md and link to it, keeping only the essentials in SKILL.md.

Give steps 6-7 concrete form: name the global command file per runtime adapter and provide a checkable rule for secret/path removal (e.g. a grep pattern or script invocation).

DimensionReasoningScore

Conciseness

The body is dense and procedural with no explanation of known concepts — e.g. "roles: 0-4 open `role:*` professional-responsibility ids" states constraints bare. It falls short of 5 only because of minor trimmable tokens: step 9 ("Run package verification and public-safety checks before release") duplicates step 8's verify script, and "Packaging must not turn a shallow prompt into a polished but weak package" is a rationale line rather than instruction. It is well above 3 (mostly efficient with no padded sections).

4 / 5

Actionability

Concrete, executable guidance dominates: "Run `scripts/verify-team-package.sh <package-root>`" plus exact paths (`.agentlas/agent-card.json`, `docs/research-sources.md`) and countable constraints ("skills: 3-12 open `skill:*` verb-object capability ids"). Not 5 because steps 6, 7, and 9 ("Add or repair the global command across Claude Code, Codex, Antigravity...", "Remove secrets, raw logs, private local notes", "Run package verification and public-safety checks") give direction without commands, file names, or checkable rules. Not 3 because the guidance is genuinely executable, not pseudocode or high-level hints.

4 / 5

Workflow Clarity

A clear 9-step sequence with an explicit validation branch: "Run `scripts/verify-team-package.sh <package-root>` after repair. If it fails, correct the package shape before any final handoff." Not 5 because step 9 is vague and overlaps step 8 (it says "Run package verification" without naming which check beyond the script already run), and the conditional research gate in step 3 has no completion checkpoint. Not 3 because a real validate-and-fix feedback loop is explicitly present, not merely implied.

4 / 5

Progressive Disclosure

The body has clear sections ("Procedure", "Output") but the files it cites — `contracts/builder-interview-research-gate.md` and `scripts/verify-team-package.sh` — are not present in any references/scripts/assets bundle directory, so the navigation cannot be verified as one-level-deep and resolvable. Additionally, ~15 lines of workforce-ontology field specs (step 5) are inlined where a reference file would fit. Not 2 because the structure is organized and references are clearly signaled inline, not buried; not 4 because the referenced files cannot be confirmed as real bundle files and step 5's dense spec is inline.

3 / 5

Total

15

/

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 description with an explicit "Use when" trigger, concrete destination-specific conditions, and a distinctive ecosystem term that sharply limits conflict risk. The only soft spots are unelaborated action verbs and a thin set of synonyms for natural triggering.

DimensionReasoningScore

Specificity

It lists several concrete actions — "converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture" — plus five concrete delivery targets ("local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release"). Not 5 because it never states what the packaging produces (contracts, verification, package shape), leaving minor coverage gaps; not 3 because multiple specific actions are named rather than 1-2.

4 / 5

Completeness

The description explicitly answers both questions: the gerund clause "converting, repairing, or packaging an existing local or external agent/team into Agentlas architecture" states the what, and the explicit "Use when..." with concrete destination triggers ("for local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release") states the when with specific trigger phrases. Not 4 because the when is not weakly implied or underspecified — it is explicit and enumerated.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "converting, repairing, packaging", "agent/team", "Agentlas import", "Codex plugin", "Claude adapter", "open-source release" — phrases a user of this niche would plausibly say. Not 5 because it lacks synonyms and variations (e.g. "bundle", "publish", "agent package") and leans on ecosystem jargon ("Agentlas architecture"); not 3 because coverage goes well beyond one generic keyword and includes several realistic trigger phrases.

4 / 5

Distinctiveness Conflict Risk

A clear niche with minimal conflict risk: the triggers center on a named ecosystem ("Agentlas architecture", "Agentlas import") plus specific delivery modes, so it would rarely fire for unrelated skills. It is far above "somewhat specific but could overlap" (3) and above "minor overlap risk with closely related skills" (4), since the distinctive ecosystem term and enumerated destinations make mis-triggering unlikely.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

agentlas-ai/Agentlas-OS

Path

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