Evaluate documentation platforms and authoring tools by requirements, workflow fit, migration risk, content model, search, integrations, portability, support burden, and cost.
SkillScore91Maintained
Automatic
◆Doc Ops pack
Last verified 8/16/2026
What it changes
Passed 20 of 22 test cases with the skill, and 17 of 22 without it.
Without skill77%
With skill91%
Checks it passed that the model alone missed
The response evaluates content portability and lock-in risk for the proposed Markdown approach.
The response includes seat licensing and vendor lock-in migration costs in SaaS cost estimates.
The response warns against adopting a workflow that completely blocks non-engineering contributors.
and 1 more in the full report
4 fixed16 passed either way1 still failing1 broke
Pass-rate lift
+14 pp
Tokens
+12%
Agent turns
0%
Response time
-5%
Model gemini-3.6-flashMeasured 8/16/2026v120 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
Our technical writers want to move our public developer docs to plain Markdown files in GitHub so engineers can review PRs easily. However, our marketing and support teams worry that plain Markdown won't support interactive REST API testing or deep site analytics for readers. Provide an evaluation framework balancing these demands.
What was checked, without and with the skill
Checked
Without skill
With skill
The response evaluates both reader experience needs and author workflow friction separately.
Passed
Passed
The response evaluates content portability and lock-in risk for the proposed Markdown approach.
Missed
Passed
case-04 · 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.md42 linessingle file
Documentation Platform Selection
Use this skill to choose, compare, pilot, or migrate documentation platforms and authoring tools. It keeps the decision anchored in reader experience, author workflow, maintenance reality, and migration risk.
This skill is derived from paraphrased guidance in Christopher Gales and the Splunk Documentation Team's The Product Is Docs: Writing Technical Documentation in a Product Development Group, especially Chapter 17, "Tools and Content Delivery," plus related maintenance and audience guidance from Chapters 3 and 10. Do not copy book prose into user outputs. Source: https://link.springer.com/book/10.1007/978-1-4842-7217-6
Quick Start
Load guidelines.md to choose the smallest useful reference set.
State current pain, target reader experience, author workflow, and constraints.
Use workflows/evaluate-doc-platform.md to compare options.
Use workflows/plan-doc-migration-pilot.md when migration or pilot planning is needed.
Separate tool problems from process, ownership, and information architecture problems.
Return requirements, comparison, recommendation, migration risk, pilot plan, and open questions.
Default Output
When evaluating a documentation platform, return:
Decision context - current pain, audiences, content types, team workflow, and constraints.