How does this skill differ from a standard marketing copywriter?

This skill eliminates marketing hype by generating technical documentation focused on license verification, specific failure modes, and clear 'not-for' criteria that typical sales pages omit.

What information do I need to provide to generate a tool page?

You only need to provide the tool name and a primary documentation URL; the skill then crawls the technical specs to build the structured reference page.

What specific sections are included in the generated output?

The output is structured using the 'Tech-Gurunomics' framework, which includes a one-line job description, a verified license section, a failure mode matrix, and a claims-check checklist.

Is this skill compatible with different AI agent platforms?

Yes, the skill is designed to work across most major AI agent platforms and LLM interfaces that support web browsing or document analysis.

What kind of technical troubleshooting information does the skill provide?

The 'failure modes' section provides specific symptoms, technical causes, and actionable 'fix or skip' guidance to help users troubleshoot issues before they escalate.

How does the skill ensure the technical accuracy of the tools it analyzes?

The skill includes a 'claims-check' checklist and a last-verified date field, ensuring that all performance claims are either cited from documentation or explicitly labeled as estimates.

Honest Tool Page Writer Skill for Technical Docs

Ollama

One-line job

Ollama is a local inference runner for downloading and serving language models on a computer.

What it replaces

It can replace some hosted API calls, recurring inference spend, or manual setup for a local model workflow. It is not a drop-in replacement for every hosted model or managed team service.

License + verify

Check the current Ollama repository and its LICENSE file before publishing. Verify Ollama separately from each model and dependency. License summaries are not legal advice.

Failure modes

Model will not start → incomplete download or insufficient resources → re-check the model name, disk space, and documented requirements; skip if hardware is unsuitable.
Responses are slow → model size or context exceeds available resources → reduce context or choose a smaller model; do not promise a fixed speed.
Command is not found → the CLI is not installed or not on PATH → follow primary install documentation and confirm the documented version command.
Behavior changed → model files, prompts, or defaults changed → record the exact model tag and re-check its documentation.

For / not for

For: local, inspectable model workflows; operators willing to manage downloads and updates.

Not for: guaranteed hosted uptime; workflows that cannot keep model files locally; anyone expecting benchmark or quality guarantees.

Last-verified

ESTIMATE / unverified — operator must fill in the ISO date and exact repository license, install path, and model documentation checked.

Next step

Read the primary Ollama install and model documentation, then test one small model locally.

Claims check

Re-check live repository and model licenses.
Fill the last-verified date and URLs.
Remove rankings, hype, and unsupported performance claims.
Label non-cited numeric claims ESTIMATE.

About this skill

What it does

Turns a tool name and primary documentation URL into a clear, single-tool reference page in the Tech-Gurunomics structure.

What the page covers

One-line job and what the tool replaces
License name, how to verify it, and a not-legal-advice note
Concrete failure modes with symptom, cause, and fix or skip guidance
Who it is for and not for, last-verified date, and one next step

Guardrails

No rankings, hype, invented user counts, borrowed screenshots, or unsupported performance claims. Numeric claims must be cited or labeled ESTIMATE. The output ends with a claims-check checklist.

Frequently Asked Questions

Honest Tool Page Writer