Search saved Knowledge pages and answer questions about documents, meetings, people, or projects with source citations. The skill checks relevant records and evidence so responses can distinguish current information, historical context, and gaps in what was retrieved.
Find and answer from saved Knowledge vault pages with source citations. Use for questions about stored documents, meetings, people, or projects; not for recalling conversation history or searching the web.
Run score Not tested
See how to installSearches saved Knowledge pages, reads relevant records, and builds answers from the retrieved material. It can answer questions about documents, meetings, people, and projects while showing where the information came from. When several records are combined, it distinguishes a summary from differing accounts and checks history so older information is not presented as current. For date questions, it separates when an event happened from when it was recorded.
Use it when you need evidence from saved knowledge, want to check meeting decisions, or need to trace a project's history. It does not recall conversation history or search the web.
Searching and reading Knowledge are read-only. A search with no results does not prove that the vault contains no relevant information. To save new information for later, use the separate knowledge-capture skill.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 26, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Read shared conventions. This workflow is read-only.
knowledge_grep({query}), including for named people, projects
and pages whose exact stored identity is not already known: literal words, all by
default; try a concise variant, any, or phrase when useful. No embeddings,
regex, graph traversal or server-side synthesis is available. Narrow by
ontology type/kind when appropriate; use knowledge_records and pagination
for an inventory, not a ranked search pretending to be exhaustive.knowledge_lookup({query}) only for an already-known exact record ID,
full title or declared alias. It does not perform keyword search. If it returns
missing, fall back to knowledge_grep before concluding no relevant record
exists. Preserve ambiguous as ambiguity and inspect candidates rather than
choosing one.knowledge_record. Read enough context to support
the answer. Compact metadata is included by default; request
includeEvidence: true for source locators, excerpts and attribution support,
and metadataView: "full" for arbitrary domain fields. Connections default
to compact identities/endpoints/uncertainty; request view: "full" only for
richer metadata/evidence, and includeCards: true with full view for prose.
Follow body/evidence/connection pagination as needed. Compare the hit's
citation hash/revision to the readback. Restart on changes rather than combine
incompatible revisions. Use includeReferences only for declared structured
connections; prose links do not populate that list automatically.index.snapshot. If an API pagination bound prevents exhausting results,
narrow the query or state the coverage limit. Do not claim the vault lacks
something solely because a short ranked list did not contain it.Recall itself is read-only. If the selected Knowledge memory policy calls for
remembering genuinely new durable information, use knowledge-capture separately.
Do not re-save retrieved summaries as new evidence or enrich entities merely
because they appeared in an answer.
Use knowledge_chronicle_day for a day/week, knowledge_chronicle_since for an occurrence range, knowledge_timeline for an entity's dated records or a chosen timeField, and knowledge_chronicle_last_seen for latest dated context. Resolve an entity to a stable page ID first. Dated mentions do not prove attendance. For keyword/inventory queries add since/until and timeField to knowledge_grep or knowledge_records. occurred_at answers when something happened; recorded_at and updated_at answer when records were created/changed. Never substitute one for the other. Resolve relative query dates with the user's timezone, preserving explicit offsets; day queries accept an IANA timezone. Source date-only values stay date-only. Follow nextOffset with unchanged filters and returned snapshot. Temporal eligibility="include_inactive" includes superseded/expired material, never withdrawn records or a reconstruction of past system state. Last-seen uses occurredOnOrBefore for the occurrence cutoff; do not pass asOf or historical. Use includeSources=true for deduplicated source identities on temporal pages. Markdown-only timelines and undated records are not inferred, and no matches do not prove absence.
Use knowledge_evidence_read with the record id and observed path/sha256 to read an exact retained UTF-8 passage. Supply inclusive startLine/endLine when known. Follow nextCursor with unchanged id/path/hash and omit or repeat line bounds. A null nextCursor completes the passage. In contrast, record.nextEvidenceOffset only completes the citation list; excerptTruncated still requires source reading. The tool verifies bytes and line bounds, not the truth of an interpretation. Use knowledge_attachment for binary originals. Never infer complete review from an excerpt or a successful structural verifier.
Query freshness distinguishes queriedAt from scannedAt; keyword results also have indexedAt. A reused scan retains its observation time. Compare snapshot values only across pages with unchanged query filters and eligibility.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Set up and authenticate the 1Password CLI, then supply stored passwords and API keys to commands or configuration. The skill covers desktop integration, service accounts, and interactive sign-in while keeping secrets out of chat and logs.
Route requests from OpenClaw to external coding agents such as Claude Code or Cursor. Start or continue sessions using ACP, a protocol for connecting agents, or relay prompts directly through acpx while preserving conversation context.
Add a model provider to OpenClaw and verify it with a real response. The skill validates configuration, keeps credentials in environment or file references, and reports test results and any default model changes.
Prepare an agent activity transcript for a GitHub pull request or issue. Extract relevant prompts, decisions, and results from local logs, remove sensitive material, and preview the edited record before separately authorized publication.
Manage Apple Notes on macOS through memo, a command-line tool. Create, browse, search, edit, delete, and move notes between folders, or export selected notes to HTML or Markdown for use outside the app.
Manage Apple Reminders from your Mac with remindctl, a terminal tool. View tasks by date, add or edit reminders, organize lists, and mark tasks complete or delete them, including personal to-dos that sync to iOS.