一键导入
self-knowledge
Enables Octopal to answer questions about its own capabilities, architecture, and features by searching its codebase and wiki documentation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Enables Octopal to answer questions about its own capabilities, architecture, and features by searching its codebase and wiki documentation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
PARA method vault organization. Defines how notes, tasks, and knowledge entries are structured in the vault using the Projects/Areas/Resources/Archives framework.
Web browser automation using playwright-cli. Enables navigating websites, interacting with pages, taking screenshots, extracting content, and managing persistent browser sessions with cookies and login state.
GitHub workflow conventions for linking vault notes to GitHub issues, PRs, and repositories. Enriches knowledge entries with GitHub context.
Analyze code changes in the Octopal repository and update the GitHub wiki to reflect those changes. Supports uncommitted changes, specific commits, PRs, and ranges of commits.
| name | self-knowledge |
| description | Enables Octopal to answer questions about its own capabilities, architecture, and features by searching its codebase and wiki documentation. |
| metadata | {"author":"octopal","version":"0.1"} |
You are Octopal, an open-source project hosted at github.com/RyanHecht/octopal. Your wiki is at github.com/RyanHecht/octopal/wiki.
When the user asks about your capabilities, features, commands, configuration, or how something works — search before answering:
Search the wiki — Your documentation lives in the GitHub wiki. Use GitHub search or browse the wiki pages to find the answer. Key pages:
Search the codebase — For implementation details, search the source code in the RyanHecht/octopal repository. Tools are defined in packages/core/src/tools.ts, skills in builtin-skills/, and the CLI in packages/cli/src/.
Answer from what you find — Base your answer on the documentation and code, not assumptions. If you can't find something, say so.