@alavida/agentpack

Compiler-driven lifecycle CLI for source-backed agent skills

getting-started-skillgraphs

lifecycle
117 linesSource

Use when starting from an empty repo or empty skillgraph and needing the first correct authoring loop, lifecycle framing, repo-root routing, and inspect/validate/dev command flow in agentpack.

Agentpack - Getting Started Skillgraphs

Setup

sh
npm install -g @alavida/agentpack
cd knowledge-base
agentpack author inspect domains/value/skills/copywriting
agentpack publish validate domains/value/skills/copywriting
agentpack author dev domains/value/skills/copywriting

Core Patterns

Start in the authoring repo

sh
cd knowledge-base
agentpack publish validate domains/value/skills/copywriting
agentpack author stale

Run source-backed commands from the repo that owns the files declared by your source bindings.

Use the authored workflow first

sh
agentpack author inspect domains/value/skills/copywriting
agentpack publish validate domains/value/skills/copywriting
agentpack author dev domains/value/skills/copywriting

Switch to consumer install only after publishing

sh
cd consumer-repo
npm install @alavida/value-copywriting
agentpack skills list
agentpack skills enable @alavida/value-copywriting

Common Mistakes

CRITICAL Wrong repo root for source-backed commands

Wrong:

sh
cd tooling/agentpack
agentpack publish validate ../knowledge-base/domains/value/skills/copywriting

Correct:

sh
cd knowledge-base
agentpack publish validate domains/value/skills/copywriting

source bindings resolve relative to the current repo root, so validating from the wrong repo breaks provenance checks.

Source: docs/introduction.mdx

HIGH Starting with npm install instead of authoring validation

Wrong:

sh
npm install @alavida/value-copywriting

Correct:

sh
agentpack author inspect domains/value/skills/copywriting
agentpack publish validate domains/value/skills/copywriting

npm install is the consumer lifecycle; authored skills need inspect and validate first.

Source: skills/agentpack-cli/SKILL.md

MEDIUM Treating the dashboard as the authoring surface

Wrong:

sh
agentpack author dev domains/value/skills/copywriting

Correct:

sh
edit domains/value/skills/copywriting/SKILL.md
agentpack author dev domains/value/skills/copywriting

The localhost workbench is for visibility during author dev, not the source of truth for authored behavior.

Source: docs/cli-skills.mdx

References