Agentlas Packaging Agent Skill

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.

460 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

1165

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/agentlas-ai/Agentlas-OS --skill agentlas-packaging

The instruction itself

3 sections, as written by the author

Agentlas Packaging

Procedure

Inspect the existing source: prompt, repo, ZIP, runtime folder, skill, command,

or generated agent package.

Classify it as single-agent, team-builder, or mixed/unclear.
Run docs/builder-interview-research-gate.md when the source behavior,

target user, tools/plugins, output artifacts, or evaluation bar are unclear.

Packaging must not turn a shallow prompt into a polished but weak package.

Preserve useful behavior while adding Agentlas contracts:
AGENTS.md;
docs/builder-interview.md;
docs/research-sources.md;
docs/tool-selection.md;
docs/prompt-performance-contract.md;
.agentlas/capability-eval-plan.json;
.agentlas/agent-card.json;
.agentlas/company-blueprint.json;
.agentlas/mode-map.json;
.agentlas/memory-map.json;
.agentlas/memory-tickets.jsonl;
.agentlas/vault-references.json;
.agentlas/global-commands.json;
runtime adapters;
verification scripts.
Add or repair the global command across Claude Code, Codex, Gemini CLI,

generic AGENTS.md tools, and terminal adapters.

Remove secrets, raw logs, private local notes, and unsafe public paths.
Run scripts/verify-team-package.sh <package-root> after repair. If it

fails, correct the package shape before any final handoff.

Run package verification and public-safety checks before release.

Output

Return classification, repaired_files, agentlas_contracts_added,

runtime_adapters, global_commands, verification, and blockers.

Other skills for the same job

different authors, same section of the catalogue

Skill Creator

by anthropics

vendor ×10

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Replace with description of the skill and when Claude should use it.

35 tokens

Dispatching Parallel Agents

by ZhanlinCui

×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take agentlas-ai/agentlas-packaging from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.