Skills
Reusable expertise, setup notes, and declared capabilities.
Got it working?
Ship the setup.
Lineage turns your agent workflow environment into an inspectable package someone else can approve, enable, and run with Claude Code or Codex.
$
curl -fsSL https://agenticlineage.vercel.app/install.sh | shWhat is Lineage?
Lineage packages the environment around a workflow.
A working agent flow is rarely just one prompt. Lineage keeps the skills, workflow steps, agents, policies, references, setup material, declared capabilities, and provider adapters together as one inspectable package.
8Package signals
1Manifest
2Provider adapters
resume-workflow@0.1.0lineage.yaml
author
local setup
local setup
problem
rebuild by hand
rebuild by hand
package
workflow env
workflow env
receiver
inspect + approve
inspect + approve
enable
local project
local project
Claude
Codex
Package contents
Everything in its place.
A Lineage package is a normal folder with a lineage.yaml manifest. The receiver should be able to open it, see what it declares, and understand what may be enabled locally.
Agents
Roles, workers, provider adapters, and entrypoints.
Workflows
Ordered steps, checks, references, and validations.
Policies
Rules and local expectations the receiver can inspect.
package/
├── lineage.yaml
├── skills/
├── workflows/
├── agents/
├── policies/
├── references/
├── setup material
├── capabilities
└── adapters/Current runtime flow
Package. Inspect. Run locally.
The current loop is distribution-first: validate before sharing, verify downloaded content, approve local enablement, then preview provider materialization before anything is written.
$ lineage init user
$ lineage package init resume-workflow
$ lineage package validate ./resume-workflow
$ lineage login
$ lineage package publish ./resume-workflow
$ lineage add resume-workflow
$ lineage inspect resume-workflow
$ lineage run claude --dry-run
$ lineage run codex --dry-run- Package, validate, then share or publish
lineage add, inspect, approve, enable locally- Run with Claude Code or Codex after a dry run
Provider adapters
Works around
your tools.
Lineage does not replace the agent provider or account. It prepares provider-specific local files through adapter boundaries, then hands execution back to the Claude Code or Codex command the receiver uses.
Read architecture ->
Claude
Materializes package context for Claude Code workflows.
In repoCodex
Materializes package context for Codex workflows.
In repoRegistry and example
Browse packages, then inspect locally.
Published package pages show version, digest, publisher, provider compatibility, declared capabilities, and a bootstrap prompt. GitHub verifies publisher identity; package artifacts are not signed.
FilePurposeReceiver inspectsStatus
lineage.yamlDeclares
resume-workflow, version 0.1.0, exports resume-review.manifestValidatedskills/resume-reviewReviews resume material for clarity, evidence, role fit, and missing details.skill filesInspectable
workflows/resume-reviewConfirms target role, finds missing evidence, suggests truthful revisions, and summarizes.workflow stepsRunnable
references/source-notes-template.csvTemplate for receiver-provided local source notes.local setupApproved first
Trust model
Visible before it changes your project.
Lineage validates package shape, checks downloaded archives against registry-reported digests, surfaces declared capabilities, and asks before setup writes or first materialization changes. A clean result is not a guarantee of intent, PII safety, or instruction-risk scanning.
Why a package, not a prompt
Share the working environment, not a reconstruction job.
Your workflow already has structure: skills, steps, references, policies, setup expectations, and provider-specific context. Lineage packages those pieces so the next person can inspect them, approve them, and run them locally instead of rebuilding from memory.