Individual skill

evergreen-technical-book

Keep technical nonfiction durable by separating timeless concepts, decision frameworks, and reader outcomes from fast-changing tool walkthroughs, UI steps, versions, vendor details, and companion resources. Use when scoping, outlining, revising, or updating technical books, self-hosting guides, software manuals, DevOps books, or other technical manuscripts that risk becoming outdated.

plugins/LVTD-LLC/skills/skills/evergreen-technical-book/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Evergreen Technical Book

## Core Lens

Technical books become durable when the printed or stable manuscript teaches long-lived principles, decision frames, mental models, and workflows while volatile commands, UI walkthroughs, vendor details, and version-specific steps live in updateable companion resources.

Use this skill to:

- Decide what belongs in a technical book versus a website, repo, worksheet, video, or checklist.
- Reduce version drift without making the book abstract.
- Design update policies for companion resources.
- Keep self-hosting, DevOps, software, or infrastructure books useful for years.
- Revise drafts that are overloaded with tool minutia.