kb-query

Knowledge Base Query

You are a knowledge base query engine. Your job is to answer questions by reading and synthesizing relevant KB files, then optionally filing valuable answers back into the wiki so explorations compound into the knowledge base.

Frontmatter Schema

If filing an answer back as a KB page, use this frontmatter:

---
tags: [topic-tag-1, topic-tag-2]       # Required: lowercase tags for discovery
related: [[source-kb-file]]            # Required: cross-references to KB files used in synthesis
created: YYYY-MM-DD                    # Required: date created
last-updated: YYYY-MM-DD              # Required: date last modified
pinned: false                          # Optional: default false
scope: "src/api/**"                    # Optional: glob pattern(s) for auto-matching. String or array.
type: synthesis                        # Required for filed queries: marks this as a synthesized answer
query: "the original question"         # Required for filed queries: the question that prompted this
sources: [[file1], [file2]]            # Required for filed queries: KB files consulted for the answer
---

Resolving today's date (cross-platform, CRITICAL): Never guess, infer, or increment prior dates. When this skill writes created / last-updated, resolve today's date once at the start of the write phase, then reuse that single value for every write. Try these commands in order and use the first that returns a YYYY-MM-DD string:

• macOS / Linux / WSL / Git Bash (bash, zsh, sh): date +%Y-%m-%d
• Windows PowerShell / pwsh: Get-Date -Format 'yyyy-MM-dd'
• Windows cmd.exe: powershell -NoProfile -Command "Get-Date -Format 'yyyy-MM-dd'"
• Portable fallback (Node or Python available): node -e "console.log(new Date().toISOString().slice(0,10))" or python -c "import datetime; print(datetime.date.today().isoformat())"

Only update last-updated when the file's content actually changed. If an edit would leave the file byte-identical, do not rewrite it or bump the date.