メニュー
Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants to apply leave / absence in Workday (sick leave, casual leave, planned leave, comp off, etc.) for one or more days, invoked as /apply-workday-leave. Review-first — it shows the absence plan (dates, type, hours) and waits for confirmation before submitting, then reconciles the timesheet so the leave day carries no project hours. Drives the user's real Chrome via the chrome-cdp CLI (logs in through login-microsoft-sso).
Use when the user wants to review and approve their pending Workday "My Tasks" approvals via the browser — invoked as /approve-workday-tasks. Lists pending items and approves only the ones the user explicitly selects. Drives the user's real Chrome via the chrome-cdp CLI (logs in through login-microsoft-sso).
Use when the user wants to fill in their Workday timesheet for the current week (hours per weekday against a project), invoked as /fill-workday-timesheet. Review-first — shows the week's planned hours and waits for confirmation before saving. Drives the user's real Chrome via the chrome-cdp CLI (logs in through login-microsoft-sso).
Use when the user wants a list of their meetings for a week from the Outlook (Microsoft 365) calendar — invoked as /list-week-meetings. Read-only: it reads the week's events and presents them grouped by day (time, title, organizer, online/in-person, status). Drives the user's real Chrome via the chrome-cdp CLI (logs in through login-microsoft-sso, app outlook).
Use to ensure an authenticated browser tab for an app behind your organization's Microsoft (Entra) SSO — e.g. Workday, Engage, Outlook — driven by the `chrome-cdp` CLI. It drives the user's real, already-logged-in Chrome, so it types no credentials; it navigates to the app and, if redirected to a sign-in page, clicks that app's SSO entry, which bounces back in via the live session. A building block for the automation skills — invoke it first (with the target app) so they operate on a logged-in tab. Invoked as /login-microsoft-sso.
Use when the user wants to record an activity in Engage (the org's activity/points platform) — e.g. a billed work week, a phone interview, or an attended course/class (e.g. ImprovingU) — invoked as /record-engage-activity. Fills the Add Activity form (category, type, date, quantity, notes) and submits only after user confirmation; can derive a class's date/hours from Outlook. Drives the user's real Chrome via the chrome-cdp CLI (logs in through login-microsoft-sso).
| name | second-brain-query |
| description | Answer questions against the knowledge base wiki. Use when the user asks a question about their collected knowledge, wants to explore connections between topics, says "what do I know about X", or wants to search their wiki. |
| allowed-tools | Bash Read Write Edit Glob Grep |
Answer questions by searching and synthesizing knowledge from the wiki.
Read wiki/index.md to identify relevant pages.
Scan all category sections (Sources, Entities, Concepts, Synthesis) for entries related to the question.
If qmd is installed (check with command -v qmd), use it for search:
qmd search "query terms" --path wiki/
This is especially useful when the wiki has grown beyond ~100 pages where scanning the index becomes inefficient.
For exploratory or fuzzy questions, prefer hybrid semantic search when embeddings exist (check qmd status):
qmd query "natural language question" --path wiki/
Read the wiki pages identified by the index or search.
Follow [[wikilinks]] to pull in related context from linked pages.
Read enough pages to give a thorough answer, but don't read the entire wiki.
If the wiki pages don't fully answer the question, check relevant source summaries in wiki/sources/ for additional detail.
Only go to files in raw/ as a last resort.
Match the answer format to the question:
Always cite wiki pages using [[wikilink]] syntax.
Example:
According to [[Source - Article Title]], the key finding was X. This connects to the broader pattern described in [[Concept Name]], which [[Entity Name]] has also explored.
When an answer leans on a page whose frontmatter says ingest: light (find them with grep -l '^ingest: light' wiki/sources/*.md), disclose it and offer an upgrade:
"This comes from a light-ingested source; want me to deep-ingest it for entity/concept coverage?"
If the answer produces something worth keeping — a comparison, analysis, new connection, or synthesis — offer to save it:
"This comparison might be useful to keep in your wiki. Want me to save it as a synthesis page?"
If the user agrees:
wiki/synthesis/ with proper frontmatterwiki/index.md under Synthesiswiki/log.md: ## [YYYY-MM-DD] query | Question summary[[wikilinks]] for all internal references.
Never use raw file paths./second-brain-ingest — process new sources into wiki pages/second-brain-lint — health-check the wiki for issues