Content Structure

Lore packages use a standard directory layout. The structure varies slightly depending on the package kind.

Standard Layout (Skill, Rule, Spec, Template)


my-skill/
├── manifest.yaml          ← Required: package metadata
├── README.md              ← Displayed in the package hub
├── LICENSE                ← License text
└── content/
    ├── en-US.md           ← Default language (required)
    └── pt-BR.md           ← Additional translations (optional)

Packages must be runtime-agnostic. Do not include platform-specific files (e.g., SKILL.md, .cursorrules, AGENTS.md) inside the package. These are generated by the CLI at install time.

MCPServer Layout

MCPServer packages do not contain a server implementation — they contain an installation descriptor that the CLI uses to configure an existing MCP server in the target AI runtime.


my-mcp-server/
├── manifest.yaml          ← Required: includes mcp: transport config
├── README.md              ← Displayed in the package hub
├── LICENSE
└── content/
    ├── en-US.md           ← Description of what the MCP server provides
    └── pt-BR.md           ← Optional translation

The key difference from other kinds is the mcp: field in manifest.yaml, which declares the transport configuration (see manifest.yaml Reference).

When a user runs lore pull my-org/my-mcp-server:1.0.0, the CLI:

Reads the mcp.transports config from the manifest
Detects the active AI runtime (Claude Code, Cursor, etc.)
Writes the MCP server entry into the runtime’s config file (e.g., ~/.claude/settings.json)

See Authoring an MCPServer Package for the full guide.

Content Files

Content files are plain Markdown files located in content/. Each file is named after the IETF BCP 47 language tag it represents.

For Skill, Rule, Spec, and Template packages, the content file contains the AI instructions:


# Azure Architect
 
You are an Azure architecture specialist. When helping with Azure infrastructure:
 
1. Default to managed services over IaaS when possible
2. Always configure diagnostic settings for all resources
3. Use Azure Policy for governance at scale
...

For MCPServer packages, the content file describes what the MCP server provides — its tools, resources, and how to use them:


# My MCP Server
 
Provides tools for interacting with the My Service API.
 
## Available Tools
 
- `get_resource` — fetches a resource by ID
- `list_resources` — lists all resources with optional filters
- `create_resource` — creates a new resource
 
## Authentication
 
Set the `MY_API_KEY` environment variable to your API key.
You can generate one at https://example.com/settings/api-keys.

README.md

The README.md is displayed in the Lore package hub at lore.infraestrutura.app. Write it for human readers, not AI consumption. It should explain what the package does, how to use it, and any prerequisites.