Nm Leyline Storage Templates

Consult this skill when designing storage and documentation systems

Security Scan

This is an instruction-only documentation/templates skill whose requirements and runtime instructions are consistent with its stated purpose (template patterns and lifecycle management); it does not request secrets, installs, or external endpoints.

Purpose & Capability

The name/description (storage/templates, lifecycle, maturity) matches the included content: YAML/markdown templates, naming conventions, promotion workflows, and example scripts. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

Runtime instructions include shell and Python examples that read and manipulate local markdown/frontmatter (find, grep, mv, yaml.safe_load) — this is expected for a storage/templates tool. There are no instructions to transmit data to external endpoints or to access secrets. Users should note the scripts will read and modify local files and may mv files when promoting content.

Install Mechanism

No install spec or packaged code is provided (instruction-only). That minimizes risk: nothing is downloaded or written by the skill itself. Some integration examples reference a 'leyline' Python package and a separate Claude plugin for a richer experience, but those are optional examples rather than hidden installs.

Credentials

The skill requests no environment variables, credentials, or config paths. Example scripts access the filesystem (markdown files) which is appropriate for this domain and proportional to the stated functionality.

Persistence & Privilege

always is false and the skill does not request persistent system-level presence or modify other skills/configs. Autonomous invocation is allowed by platform default but is not combined with any broad privileges here.

Assessment

This skill is instruction-only documentation for templates and lifecycle management and appears internally consistent. Before using: (1) review and test the example scripts in a safe directory or repo backup — they read and can rename/move files (mv) when promoting content; (2) if you plan to use the Python integration snippets, install and inspect any referenced packages (e.g., leyline.storage_templates) yourself rather than running unverified code; (3) no credentials or network exfiltration are requested by the skill, but exercise normal caution when pasting or running scripts on production content. If you need the automation, consider running it in a sandbox or with version control to ensure recoverability.

Night Market Skill — ported from claude-night-market/leyline. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

Table of Contents

• Overview
• When to Use
• Core Concepts
• Template Types
• Maturity Lifecycle
• Quick Start
• Basic Template Structure
• Core Content
• Metadata
• File Naming Conventions
• Domain Applications
• Common Patterns
• Promotion Workflow
• Template Selection Guide
• Integration Pattern
• Detailed Resources
• Exit Criteria

Storage Templates

Overview

Generic template patterns and lifecycle management for structured content storage. Provides reusable templates, maturity progression models, and file naming conventions that work across different storage domains.

When To Use

• Building knowledge management systems
• Organizing documentation with maturity stages
• Need consistent file naming patterns
• Want template-driven content creation
• Implementing lifecycle-based workflows

When NOT To Use

• Simple storage without lifecycle or structure needs

Core Concepts

Template Types

Type	Purpose	Maturity	Lifetime
Evergreen	Stable, proven knowledge	High	Permanent
Growing	Active development	Medium	1-3 months
Seedling	Early ideas	Low	1-2 weeks
Reference	Tool/version-specific	N/A	Until deprecated

Maturity Lifecycle

seedling → growing → evergreen → archive
    ↓         ↓          ↓           ↓
 1-2 weeks  1-3 months  permanent  deprecated

Verification: Run the command with --help flag to verify availability.

Quick Start

Basic Template Structure

---
title: [Content Title]
created: [YYYY-MM-DD]
maturity: seedling|growing|evergreen|reference
tags: [relevant, tags]
---

# [Title]

## Core Content
[Main information]

## Metadata
[Context and attribution]

Verification: Run the command with --help flag to verify availability.

File Naming Conventions

Type	Pattern	Example
Evergreen	topic-name.md	functional-core-pattern.md
Growing	topic-name.md	async-patterns.md
Seedling	YYYY-MM-DD-topic.md	2025-12-05-template-idea.md
Reference	tool-version.md	python-3.12-features.md

Domain Applications

Add domain-specific fields to templates:

• memory-palace: palace, district for knowledge organization
• sanctum: scope, version for commit templates
• spec-kit: phase, status for specifications

See modules/template-patterns.md for detailed examples.

Common Patterns

Promotion Workflow

Seedling → Growing:

• Accessed more than once
• Connected to other entries
• Expanded with new insights

Growing → Evergreen:

• Proven useful over 3+ months
• Stable, not frequently edited
• Well-connected in system

Evergreen → Archive:

• Superseded by newer knowledge
• Technology/approach deprecated
• No longer applicable

Template Selection Guide

Stability	Purpose	Template
Proven	Long-term	Evergreen
Evolving	Active development	Growing
Experimental	Exploration	Seedling
Versioned	External reference	Reference

Integration Pattern

# In your skill's frontmatter
dependencies: [leyline:storage-templates]

Verification: Run the command with --help flag to verify availability.

Detailed Resources

• Templates: See modules/template-patterns.md for detailed structures
• Lifecycle: See modules/lifecycle-stages.md for maturity progression

Exit Criteria

• Template selected for use case
• File naming convention applied
• Maturity stage assigned
• Promotion criteria understood

Troubleshooting

Common Issues

Command not found Ensure all dependencies are installed and in PATH

Permission errors Check file permissions and run with appropriate privileges

Unexpected behavior Enable verbose logging with --verbose flag