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.
SkillScore100Maintained
Automatic
◆Writing & Editing pack
Last verified 8/16/2026
What it changes
Passed 22 of 22 test cases with the skill, and 18 of 22 without it.
Without skill82%
With skill100%
Checks it passed that the model alone missed
The response classifies UI runner setup clicks as volatile companion content.
The response places fast-changing MLOps tool UI steps into companion materials.
The response classifies pipeline security tradeoffs as durable manuscript content.
and 2 more in the full report
4 fixed18 passed either way0 still failing0 broke
Pass-rate lift
+18 pp
Tokens
+24%
Agent turns
0%
Response time
+3%
Model gemini-3.6-flashMeasured 8/16/2026v122 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
I am preparing a book proposal on Python Data Pipelines using Pandas and Polars. I need a structured evaluation of my manuscript layout to ensure it won't be obsolete in 18 months. Please evaluate my outline and return a durability strategy.
What was checked, without and with the skill
Checked
Without skill
With skill
The response structures the output with a durability diagnosis section.
Passed
Passed
The response includes a table separating core manuscript content from companion material.
Missed
Passed
case-07 · gemini-3.6-flash · 8/16/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md81 linessingle file
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.
Reference Routing
Need
Read
Evergreen concepts and terminology
references/core/knowledge.md
Durability and split rules
references/core/rules.md
Book vs companion examples
references/core/examples.md
Fast durability checklist
references/core/checklist.md
Split book and companion resources
workflows/split-book-and-companion.md
Workflow
1. Identify The Durable Promise
State the reader outcome that should remain valuable for several years.
If the promise depends on one vendor, one UI, or one narrow tool version, decide whether the book is intentionally edition-based or should be reframed.
Neural search via Exa MCP for web, code, and company research. Use when the user needs web search, code examples, company intel, people lookup, or AI-powered deep research with Exa's neural search engine.