update-model-research

Name: update-model-research
Availability: InStock
Author: whichguy

Update local-model prompt documentation with current Ollama model families and version findings.

Updated Apr 17, 2026

Search Tags:#versioning #documentation #research #citations #ollama #local-model #model-prompts

Ready to run

npx skills add https://github.com/whichguy/c-thru --skill update-model-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: update-model-research
Source: https://github.com/whichguy/c-thru/tree/main/skills/update-model-research
Command: npx skills add https://github.com/whichguy/c-thru --skill update-model-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps local-model prompt documentation up-to-date with the latest Ollama model families, version changes, and community findings to ensure accurate client-facing guidance.

Core Features & Use Cases

Tracks active model families from config/model-map.json and inventories their references in docs/local-model-prompt-techniques.md.
Aggregates version notes, open issues, citations, and community findings to generate delta-ready doc changes.
Produces per-model option recommendations and citations suitable for the model-map parameter defaults workflow.

Quick Start

Run /update-model-research to refresh docs/local-model-prompt-techniques.md with the latest model findings.

Frequently Asked Questions about update-model-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep local model prompt documentation updated with Ollama version changes?▼

To keep local model prompt documentation updated with Ollama version changes, automate the synchronization of version references, open issues, and community findings into your docs/local-model-prompt-techniques.md file. This ensures client-facing guidance stays accurate across all active model families defined in your configuration map.

What is the best way to track community findings and citations for local model prompts?▼

Tracking community findings and citations for local model prompts involves aggregating version notes and open issues across active model families, then generating delta-ready documentation changes. This process enforces provenance and produces per-model option recommendations suitable for parameter defaults workflows.

Can I automate prompt technique versioning across multiple Ollama model families?▼

Yes, you can automate prompt technique versioning across multiple Ollama model families by reading active models from config/model-map.json and inventorying their references. The system generates delta-ready changes to update documentation with current version references and community findings.

Does Ollama model documentation update automatically require external dependencies?▼

Ollama model documentation updates do not require external dependencies, as the process relies solely on internal configuration files like config/model-map.json and docs/local-model-prompt-techniques.md. It aggregates version notes and community findings to generate client-actionable changes.

Why does local model prompt documentation go out of sync with current model updates?▼

Local model prompt documentation goes out of sync with current model updates because new model families, version changes, and community findings continuously emerge without automated tracking. Manually updating version references and open issues across all active models leads to outdated guidance.

What format do I need for generating per-model option recommendations for Ollama models?▼

Generating per-model option recommendations for Ollama models requires defining active model families in config/model-map.json and updating docs/local-model-prompt-techniques.md. The output includes delta-ready changes with citations, enforcing client-actionability and provenance for parameter defaults.