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

76%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 procedure is well-sequenced and lean, with a genuine verify-and-fix loop before handoff. However, most contract-authoring steps name outputs without saying how to produce them, and the two referenced bundle files are missing entirely, leaving both actionability and navigation incomplete.

Suggestions

Ship the referenced bundle files (contracts/builder-interview-research-gate.md and scripts/verify-team-package.sh) or remove the references — as written, both paths dangle with nothing behind them.

Add concrete authoring guidance for the contract files (e.g., a minimal agent-card.json or AGENTS.md template, or pointers to a contracts/ reference) so steps 4, 6, and 7 are executable rather than naming outputs only.

Move the step-5 workforce résumé spec into a dedicated reference file (e.g., references/workforce-card.md) and keep only the field/count summary in SKILL.md, which also fixes the inline-content-that-should-be-separate issue.

Concretize step 9 by naming the exact verification/public-safety commands to run (or fold it into the step-8 script) so the final release checkpoint is explicit.

DimensionReasoningScore

Conciseness

The body is a lean ~55-line procedure with no explanations of concepts Claude already knows; steps are mostly file lists and commands. Not a 5 because step 5 spends ~18 lines on inline workforce-ontology detail plus rationale ('a card without them is invisible to every WorkOrder') that is justification rather than instruction.

4 / 5

Actionability

Some concrete guidance exists — the verify command 'scripts/verify-team-package.sh <package-root>', the gate contract path, an explicit contract file list, and precise field constraints (roles 0-4, communities 1-5, skills 3-12) in step 5. But key steps are high-level hints: 'runtime adapters', 'verification scripts', 'Add or repair the global command across Claude Code, Codex, Gemini CLI' give no specifics on how to author the ~14 contract files, so the guidance is incomplete for execution.

3 / 5

Workflow Clarity

A clear 9-step numbered sequence with an explicit validation checkpoint and feedback loop: 'Run scripts/verify-team-package.sh... If it fails, correct the package shape before any final handoff', plus pre-release verification in step 9. Not a 5 because step 9 ('Run package verification and public-safety checks') names no concrete checks or commands, leaving the final checkpoint implicit.

4 / 5

Progressive Disclosure

Two section headers (Procedure, Output) give basic structure, but the body references 'contracts/builder-interview-research-gate.md' and 'scripts/verify-team-package.sh' that do not exist in the bundle (no references/, scripts/, or assets/ directories), so navigation leads nowhere. The ~20-line workforce-résumé spec inlined in step 5 is content that clearly belongs in a separate reference file.

3 / 5

Total

14

/

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 strong, well-scoped description with an explicit 'Use when' clause, named actions, and concrete delivery targets. Its main gap is that the 'when' side enumerates packaging targets rather than natural user trigger phrases, and it assumes familiarity with the Agentlas vocabulary.

DimensionReasoningScore

Specificity

The description lists three concrete actions ("converting, repairing, or packaging") applied to a named source type ("an existing local or external agent/team") plus five concrete delivery targets ("local install, Agentlas import, Codex plugin use, Claude adapter use, or open-source release"). Not a 5 because the verbs themselves are generic and coverage of what 'converting' entails is unspecified.

4 / 5

Completeness

Both parts are present: an explicit "Use when converting, repairing, or packaging..." trigger clause and a clear statement of what the skill operates on. Not a 5 because the 'when' is expressed as delivery targets rather than concrete user-side trigger phrases (e.g., 'when the user asks to package an agent'), and 'what' stops short of naming the key artifacts produced.

4 / 5

Trigger Term Quality

Good natural keyword coverage for this niche: users needing this skill would plausibly say "package", "convert", "repair", "agent/team", "Codex plugin", "Claude adapter", and "open-source release". Not a 5 because synonyms like "wrap", "publish", or "redistribute" are missing and "Agentlas architecture" leans on proprietary jargon.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Agentlas packaging/migration) with triggers anchored on proprietary terms (Agentlas, Codex plugin, Claude adapter) that no other generic skill would match. Minimal conflict risk.

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

agentlas-ai/Agentlas-OS

Path

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