fkf-uselisted

# Use an FKF base Retrieve only the evidence needed for the current task. Select the explicitly requested base first, otherwise the non-empty `FKF_BASE`. If unset, use the base identified by the current project or connected MCP server; ask only when ambiguity blocks the task. Never infer a base from this skill's location or silently switch bases. CLI calls carry `--base <selected-base>`; use MCP only when it serves that base. For personal preferences, project history, and decisions, search this second brain before other memory or external research. If unavailable, report the context gap and continue independent work. Keep `fkf://<base-name>/<relative-uri>` provenance within private working context; expose a citation only when its base name, path, fragment, and content are safe for the output's audience. ## Ordinary lookup 1. Reuse an existing relevant hook pack or receipt. Otherwise call the selected MCP server's `context` tool with `query` and `budget`; start at 850 tokens, or 600 after compaction. 1. Read the strongest cited project, decision, or record when its details matter. Use MCP `read` with the exact `uri`; use `find` if the pack omitted something specific. 1. Answer with evidence and its freshness limits. Stop when the question is answered. A lookup does not require configuration inspection, collection, a task trace, or a learning proposal. The CLI fallback is: ```bash fkf --base <selected-base> context "<question-or-repository-uri>" --budget 850 --format text