athola/storage-templates
plugins/leyline/skills/storage-templates/SKILL.md
Provides templates and lifecycle patterns for storage and documentation systems. Use when organizing knowledge storage, config lifecycle, or naming conventions.
$ install --global
skillsauthnpx skillsauth add athola/claude-night-market storage-templatesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 27, 2026, 4:47 AM110.6s6 files scanned
SKILL.md
- name:
- storage-templates
- description:
- Provides templates and lifecycle patterns for storage and documentation systems. Use when organizing knowledge storage, config lifecycle, or naming conventions.
- alwaysApply:
- false
- category:
- infrastructure
- dependencies:
- []
- complexity:
- beginner
- model_hint:
- fast
- estimated_tokens:
- 600
- progressive_loading:
- true
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,districtfor knowledge organization - sanctum:
scope,versionfor commit templates - spec-kit:
phase,statusfor 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.mdfor detailed structures - Lifecycle: See
modules/lifecycle-stages.mdfor maturity progression
Exit Criteria
- Template selected for use case
- File naming convention applied
- Maturity stage assigned
- Promotion criteria understood
Related Skills
athola/ideate
research
VerifiedTrustedCommunity
Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.
304SKILL.mdUpdated Jun 8, 2026
athola/plugins/sanctum/skills/validate-pr
tools
VerifiedTrustedCommunity
--- name: validate-pr description: Use when you need a diff-derived test plan for a PR: reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions. alwaysApply: false category: validation tags: - pr - validation - test-plan - diff - revert-test - evidence tools: [] usage_patterns: - diff-derived-test-plan - revert-test-quality-check - evidence-capture complexity: intermediate model_hint: standard estimated_tokens: 650
304SKILL.mdUpdated Jun 8, 2026
athola/decision-journal
development
VerifiedTrustedCommunity
Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.
304SKILL.mdUpdated Jun 8, 2026
athola/graduated-implementation
development
VerifiedTrustedCommunity
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.
304SKILL.mdUpdated Jun 8, 2026