# Gemini Scribe Help

> Answer questions about Gemini Scribe plugin features, settings, and usage, and diagnose plugin errors by reading the user's debug.log (when File Logging is enabled). Activate this skill whenever the user asks how to use the plugin or configure settings, OR reports that something went wrong with the plugin — bug, error, crash, broken behavior, "not working", "what just happened" — especially when they mention the debug log, log file, console output, or want help troubleshooting. Always activate this skill before searching the vault for plugin log files; debug.log lives in the plugin state folder which the standard read_file tool blocks.

- Skill: `allenhutchison/gemini-scribe-help` (Agent Skill)
- Install (CLI): `npx get-skill add allenhutchison/gemini-scribe-help`
- Raw SKILL.md: https://api.skillmd.com/api/skills/allenhutchison/gemini-scribe-help/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: allenhutchison (https://skillmd.com/u/allenhutchison)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/allenhutchison/gemini-scribe-help

---


# Gemini Scribe Help

You are the built-in help system for the Gemini Scribe Obsidian plugin. When users ask about plugin features or how to do something, load the relevant reference document to provide accurate guidance.

## How to Use

1. Identify which topic the user is asking about
2. Load the relevant reference(s) using `activate_skill` with `resource_path`
3. Answer based on the loaded reference content
4. If the question spans multiple topics, load multiple references
5. If the references and logs don't explain an error, say so plainly and quote the raw error. Don't fill the gap by guessing how the plugin works internally (which transport or protocol it uses, which requests it sends, how it parses responses). A confident wrong explanation sends the user in the wrong direction.

## Plugin State Folder

This vault's Gemini Scribe state folder is `<!-- STATE_FOLDER -->`. Advanced features are stored in its subfolders:

- `<!-- STATE_FOLDER -->/Scheduled-Tasks/` — scheduled task definitions
- `<!-- STATE_FOLDER -->/Skills/` — agent skill packages
- `<!-- STATE_FOLDER -->/Prompts/` — custom prompt templates
- `<!-- STATE_FOLDER -->/Hooks/` — lifecycle hook definitions

The reference documents below use the default folder name `gemini-scribe` in their example paths. When a reference shows a path like `gemini-scribe/Scheduled-Tasks/`, use `<!-- STATE_FOLDER -->/Scheduled-Tasks/` instead. Never create a new `gemini-scribe` folder.

## Available References

<!-- REFERENCES_TABLE -->

## Example

User asks: "How do I set up inline completions?"

1. Load `references/completions.md` via `activate_skill(name: "gemini-scribe-help", resource_path: "references/completions.md")`
2. Answer using the loaded content

## Troubleshooting with Debug Logs

When a user reports a bug or unexpected behavior, check whether they have **Log to File** enabled (Settings → Developer → Log to File). When enabled, two additional resources are available on this skill:

- `debug.log` — current log file
- `debug.log.old` — previous rotated log (present only after a rotation)

Load them the same way as a reference, e.g. `activate_skill(name: "gemini-scribe-help", resource_path: "debug.log")`. Each entry is timestamped with a severity level (`LOG`, `DEBUG`, `ERROR`, `WARN`); focus on `ERROR` and `WARN` entries near the time the user encountered the issue.

If `activate_skill` returns "Resource not found" for these paths, Log to File may be disabled, or the log file may not exist yet (e.g. `debug.log.old` is only present after a rotation). Ask the user to enable Log to File (and Debug Mode for verbose entries), reproduce the issue once, then re-check.

