Library

The library is your personal content store at ~/.syllago/content/. Unlike registries (shared, read-only locally) or loadouts (bundled configurations), the library is fully read-write. You own this content and can add, edit, or remove it freely.

Directory structure

Content is organized by type. Each item is a directory containing a .syllago.yaml metadata file and one or more content files.

~/.syllago/content/
├── rules/
│   ├── typescript/
│   │   ├── .syllago.yaml
│   │   └── typescript.md
│   └── security/
│       ├── .syllago.yaml
│       └── security.md
├── skills/
│   └── develop-docs/
│       ├── .syllago.yaml
│       └── develop-docs.md
├── agents/
├── hooks/
├── commands/
└── loadouts/

The .syllago.yaml file stores metadata like the item’s name, description, content type, and provider compatibility. The accompanying files hold the actual content that gets exported to providers.

Adding content

There are three ways to get content into your library.

Import from a provider

Pull content from an existing provider setup into syllago. This is the most common starting point — bring in what you already have.

# Discover what a provider has
syllago add --from claude-code

# Add only a specific content type
syllago add skills --from claude-code

# Add a specific item by name
syllago add rules/my-rule --from cursor

# Preview what would be written without actually writing
syllago add --from claude-code --dry-run

# Add everything
syllago add --all --from claude-code

Syllago handles format conversion automatically. A Cursor rule becomes a universal syllago item that can later be installed to Claude Code, Kiro, or any other supported provider.

See syllago add --help for full options.

Create from scratch

Scaffold a new content item with the correct directory structure and metadata template.

# Create a new skill
syllago create skills my-new-skill

# Create a provider-specific rule
syllago create rules my-rule --provider claude-code

This creates the directory, .syllago.yaml, and a starter content file — ready for you to edit.

See syllago create for full options.

Browsing and inspecting content

List content

# Show all content grouped by type
syllago list

# Show only library content
syllago list --source library

# Filter by content type
syllago list --type skills

# JSON output for scripting
syllago list --json

The --source flag accepts: library, shared, registry, builtin, or all (default).

See syllago list for full options.

Inspect an item

View the full metadata and content details for any item.

# Inspect by type/name
syllago inspect skills/my-skill

# Provider-specific content uses type/provider/name
syllago inspect rules/claude-code/my-rule

See syllago inspect for full options.

Exporting to providers

Once content is in your library, install it to any supported provider. Syllago converts between provider formats automatically.

# Install a specific item to Cursor
syllago install my-rule --to cursor

# Install all skills to Kiro
syllago install --to kiro --type skills

For project-scoped providers (Kiro, Cline, Zed), content is written to the current working directory’s provider config.

See syllago install --help for full options.

How it connects

The library sits at the center of the syllago workflow:

• Providers are the source and destination. Import from one, export to many.
• Registries are shared content you consume. Registry items appear alongside library items when you run syllago list --source all, but they live in separate cloned repos.
• Loadouts bundle library content into named configurations that can be applied or reverted as a unit.

For an overview of how all three collections work together, see Collections.