一键导入
wiki-query
Read a project/team/global vault and return the system-context payload your runtime feeds to the LLM for synthesis. Single-vault scope (Phase 1).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Read a project/team/global vault and return the system-context payload your runtime feeds to the LLM for synthesis. Single-vault scope (Phase 1).
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | Wiki Query |
| description | Read a project/team/global vault and return the system-context payload your runtime feeds to the LLM for synthesis. Single-vault scope (Phase 1). |
| version | 1.0.0 |
| category | knowledge |
| skillType | claude-skill |
| assignableRoles | ["developer","qa","tpm","designer","frontend-developer","backend-developer","fullstack-dev","qa-engineer","product-manager","architect","generalist","team-leader","researcher"] |
Read a vault (<project>/.crewly/wiki/, ~/.crewly/teams/<id>/wiki/, or ~/.crewly/global-wiki/) and get back the structured context the caller's LLM uses for synthesis.
Per Atlas v2.1 §3, this skill does not call an LLM itself. It emits the LLM-agnostic system-context (vault SCHEMA, recent log entries, candidate pages by keyword overlap). The caller's runtime concatenates this with the per-LLM task-instruction prompt at prompts/<runtime>.md and makes the LLM call locally.
| Flag | Required | Description |
|---|---|---|
--vault <path> | yes | Absolute path to a vault root (must contain SCHEMA.md). |
--query <text> | yes | Natural-language question. Used for keyword-overlap candidate ranking. |
--top-k <n> | no | How many candidate pages to return (default 5). |
--recent-log <n> | no | How many tail log entries to include (default 20). |
--json <obj> | alt | Pass all fields as JSON. |
JSON with success, result.context. The context has:
vault — scope, id, absolute pathschemaSummary — frozen folders, llm-curated layout, write_policyrecentLog — last N entries (most-recent first), with timestamp / sourceType / caller / bodycandidatePages — top-K pages by keyword overlap with querycallerNotes — synthesis hints the LLM should honor (e.g. refuse writes into frozen paths)bash execute.sh \
--vault ~/Desktop/projects/crewly-projects/crewly/.crewly/wiki \
--query "what did we decide about Crewly Pro pricing in May"
400 invalid_input — missing vault/query or bad topK404 schema_missing — vault has no SCHEMA.mdPlan and create a NESTED team hierarchy (parent coordination team + per-stream child teams) for a complex multi-stream goal. Use INSTEAD of recommend-team/materialize-team when the goal names 2+ parallel work-streams (e.g. frontend + backend + DevOps). Onboarding-only.
Search the live web for a query and return ranked results (title, URL, snippet) as JSON. Works with no API key (DuckDuckGo HTML fallback) and uses the Brave Search API or SerpAPI automatically when BRAVE_API_KEY / SERPAPI_KEY is set. Any agent can call it for research, competitor analysis, market/trend lookups, fact-checking, finding sources to cite, or grounding a non-software goal (marketing, growth, commerce) in real-world information.
Transcribe a local audio (or video) file to text with timestamps using Whisper. Defaults to local whisper.cpp (free, offline, word/segment-level timestamps) and automatically falls back to the OpenAI Whisper API (whisper-1) when the local engine is not installed. Any agent can call it for meetings, podcasts, voice notes, interviews, or video audio tracks.
Accept and take the next available task from the task queue. Use when an agent is idle and ready to pick up the highest-priority unassigned task. For assigning tasks to specific agents, use assign-task instead.
Register the agent as active with the Crewly backend on startup. Use when an agent first launches and needs to join the team and become visible to the orchestrator. For confirming responsiveness after registration, use heartbeat instead.
Analyze git changes and produce a structured code review with automated checks for missing tests, debug statements, potential secrets, large changes, and dependency modifications. Use when reviewing staged changes, unstaged diffs, recent commits, or branch comparisons before submitting a pull request. For task-level quality gates, use check-quality-gates instead.