CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

team-builder-packaging

Use when generating or auditing a multi-role agent team package with orchestrator, workers, handoffs, Memory Ticket outputs, and runtime adapters (PM Soul, Memory Curator, Policy Gate, eval and QA are OS-resident).

Quality

80%

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 ./codex/plugins/agentlas-core-engine-meta-agent/runtime-support/skills/team-builder-packaging/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 a lean, well-sequenced procedure with concrete file paths, a copy-paste manifest example, and an explicit pre-completion verification step with failure handling. Weaknesses are minor: the verify-fix loop is never explicitly re-entrant, and two referenced files are absent from the skill bundle.

Suggestions

Close the validation loop explicitly: after correcting a failed package, instruct to re-run scripts/verify-team-package.sh until it passes before reporting completed.

Ship or clarify the location of contracts/builder-interview-research-gate.md and scripts/verify-team-package.sh, since neither exists in the skill bundle (no references/ or scripts/ directories).

Briefly state what the interview-research-gate contract covers or summarize its required outputs so the roster step is executable without the external file.

DimensionReasoningScore

Conciseness

The body is lean with no explanations of concepts Claude already knows, and every step carries actionable content. Minor tightening is possible — the deprecated-alias enumeration ("entrypoint, orchestrator, entry; workers, members, team") and step 9b's motivational aside ("published, charged for as a team, and can never be called") add tokens — so it sits just below the every-token-earns-its-place anchor.

4 / 5

Actionability

Concrete guidance throughout: exact file paths (docs/builder-interview.md, .agentlas/global-commands.json, manifest.json), a copy-paste manifest JSON snippet, and a runnable command ("scripts/verify-team-package.sh <package-root>"). It is not fully copy-paste ready because the contents of the referenced interview-research-gate contract and the worker agent.md files are never specified, leaving minor gaps.

4 / 5

Workflow Clarity

A clear numbered sequence (1–11) with an explicit validation step ("Run scripts/verify-team-package.sh <package-root> before reporting completed") and specific failure guidance ("If it fails, do not hand off a result; correct the package by..."). It falls short of anchor 5 because the feedback loop is never explicitly closed — there is no instruction to re-run verification after correcting the package.

4 / 5

Progressive Disclosure

For a ~55-line instruction-only skill, the Procedure/Output section split is appropriate and content is well-organized with no monolithic bulk. However, the body references "contracts/builder-interview-research-gate.md" and "scripts/verify-team-package.sh" while no references/, scripts/, or assets/ bundle directories exist, so those pointers cannot be resolved — a minor navigation gap that keeps it below a 5.

4 / 5

Total

16

/

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.

The description clearly delimits a niche domain, lists concrete package components, and includes an explicit "Use when" trigger clause. Its main weaknesses are limited action coverage (only "generating or auditing") and a when-clause that restates the actions instead of giving user-side trigger phrases.

Suggestions

Rewrite the when-clause with user-side trigger phrases, e.g. "Use when the user asks to build, scaffold, or audit an agent team package".

Add natural synonyms and variations users might say ("create", "generate", "multi-agent team", "agent roster") to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names two concrete actions ("generating or auditing") and enumerates specific package components ("orchestrator, workers, handoffs, Memory Ticket outputs, and runtime adapters"), matching the several-specific-actions anchor. It is not a 5 because action coverage rests on only two verbs with no finer-grained operations named.

4 / 5

Completeness

Both "what" (generate/audit a multi-role agent team package with the listed components) and "when" ("Use when generating or auditing...") are explicitly present. It is not a 5 because the when-clause merely restates the actions rather than giving concrete user-side trigger phrases, and not a 3 because nothing is missing or merely implied.

4 / 5

Trigger Term Quality

It includes natural domain terms a user would say ("agent team", "orchestrator", "workers", "handoffs", "team package"). A few natural terms are missing — no synonyms like "build", "create", or "scaffold" a team, and no file-extension or alternate phrasing triggers — so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Highly niche vocabulary ("multi-role agent team package", "Memory Ticket", "PM Soul", "Policy Gate", "runtime adapters") carves out a clear trigger niche with essentially no overlap risk against generic skills.

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 possibly missing (scripts/verify-team-package.sh)

Warning

Total

15

/

16

Passed

Repository

agentlas-ai/Agentlas-OS

Path

codex/plugins/agentlas-core-engine-meta-agent/runtime-support/skills/team-builder-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.