7edf5bc4d0
Major updates: - Added 35+ new skills from awesome-opencode-skills and antigravity repos - Merged SEO skills into seo-master - Merged architecture skills into architecture - Merged security skills into security-auditor and security-coder - Merged testing skills into testing-master and testing-patterns - Merged pentesting skills into pentesting - Renamed website-creator to thai-frontend-dev - Replaced skill-creator with github version - Removed Chutes references (use MiniMax API instead) - Added install-openclaw-skills.sh for cross-platform installation - Updated .env.example with MiniMax API credentials
1.3 KiB
1.3 KiB
name, description, risk, source, date_added
| name | description | risk | source | date_added |
|---|---|---|---|---|
| wiki-qa | Answer repository questions grounded entirely in source code evidence. Use when user asks a question about the codebase, user wants to understand a specific file, function, or component, or user asks "how does X work" or "where is Y defined". | unknown | community | 2026-02-27 |
Wiki Q&A
Answer repository questions grounded entirely in source code evidence.
When to Use
- User asks a question about the codebase
- User wants to understand a specific file, function, or component
- User asks "how does X work" or "where is Y defined"
Procedure
- Detect the language of the question; respond in the same language
- Search the codebase for relevant files
- Read those files to gather evidence
- Synthesize an answer with inline citations
Response Format
- Use
##headings, code blocks with language tags, tables, bullet lists - Cite sources inline:
(src/path/file.ts:42) - Include a "Key Files" table mapping files to their roles
- If information is insufficient, say so and suggest files to examine
Rules
- ONLY use information from actual source files
- NEVER invent, guess, or use external knowledge
- Think step by step before answering
When to Use
This skill is applicable to execute the workflow or actions described in the overview.