Installs into .claude/skills of the current project.
Are you the author of Ask Brain?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/zzoretich-ask-brain)
---
name: ask-brain
description: Ask the vault a question — a script assembles the relevant memories, you answer from them (or --local lets the local provider answer)
---
<!-- generated by tools/build-codex-plugin.js from plugin/; edit the source there, not this file -->
> Host: Codex CLI, through the `agenticos` plugin. Invoke as `$agenticos:ask-brain`. `<plugin root>` is the plugin's folder, two levels above the folder that holds this SKILL.md; the `aos` launcher is `<plugin root>/bin/aos`. The tools of the `agenticos` MCP server are named `mcp__agenticos__<tool>`.
Answer the question **the text the user wrote after `$agenticos:ask-brain`** from the vault:
1. Bash: `aos ask the text the user wrote after `$agenticos:ask-brain`` (fallback: `sh "<plugin root>/bin/aos" ask the text the user wrote after `$agenticos:ask-brain``). `the text the user wrote after `$agenticos:ask-brain`` stays **unquoted**: the script joins every non-flag word back into the question, and `--local` is recognized only as a separate word (a quoted `"… --local"` would put a literal `--local` inside the question). Without `--local` it prints a `<<<AOS_CONTEXT feature=ask>>> … <<<END>>>` block: the system prompt, the retrieved memories with their paths, and the expected answer format. Answer the question yourself from that block, citing the source paths it lists.
2. With `--local` as one of the words (e.g. `$agenticos:ask-brain what did I decide about tags --local`) the script answers through the configured provider instead; relay its output verbatim.
3. If the script errors, fall back to the `recall` tool of the `agenticos` MCP server (`mcp__agenticos__recall`) and `memory_read` (`mcp__agenticos__memory_read`), then answer.