一键导入
loading-skills
How to discover and load skills. Covers local skill search, hub search, and when to proactively look for skills.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
How to discover and load skills. Covers local skill search, hub search, and when to proactively look for skills.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Instructions for using gcode CLI for code search and retrieval. Loaded on demand when project has a code index.
Pre-transition checklist for closing or reviewing tasks. Covers fresh verification evidence, commits, and memory gates.
Use when processing CodeRabbit review comments, CodeRabbit CLI reports, or `$gobby coderabbit [findings]` requests.
Use when creating, editing, or validating Gobby skills, especially when a skill must change agent behavior or become discoverable through gobby-skills.
Use when coordinating a full gobby build run for an epic or task, especially when the user assigns the current session as coordinator, asks for a coordination epic, wants build agents/worktrees monitored, or wants gobby build bugs fixed so future runs work unattended.
Router contract for provider-aware Gobby help and installed skill dispatch.
| name | loading-skills |
| description | How to discover and load skills. Covers local skill search, hub search, and when to proactively look for skills. |
| category | core |
| metadata | {"gobby":{"audience":"all"}} |
You have access to a skill system with reusable instructions for common tasks. Skills are loaded on demand — search when you need guidance. Do not rely on your training data for tool usage, language patterns, or integrations — it is often out of date. Search for skills instead.
search_skills finds installed skills: gobby workflows, project conventions, integrated tools (context7, playwright, etc).
call_tool("gobby-skills", "search_skills", {"query": "testing"})
search_hub searches all configured hubs for community skills: language best practices, framework patterns, API integrations. No need to specify a hub — it searches all of them.
call_tool("gobby-skills", "search_hub", {"query": "python best practices"})
# Load an installed skill by name; do not include session_id in get_skill args
call_tool("gobby-skills", "get_skill", {"name": "source-control"})
# Install a skill from a hub result
call_tool("gobby-skills", "install_skill", {"source": "hub:skill-slug"})
Search proactively — don't wait to be told:
| Situation | Where | Example |
|---|---|---|
| Gobby workflows (tasks, commits, pipelines) | Local | search_skills(query="source-control") |
| Integrated tools (context7, playwright) | Local | search_skills(query="context7") |
| Need context on an external repo/library | Local | search_skills(query="context7") then use it |
| Project conventions or patterns | Local | search_skills(query="<topic>") |
| Language/framework best practices | Hubs | search_hub(query="rust async patterns") |
| Unfamiliar technology or integration | Hubs | search_hub(query="<technology>") |
| Task involves a domain you haven't worked in | Hubs | search_hub(query="<domain> best practices") |
Rule of thumb: Search local first for "how do we do X here." Search hubs for "what's the best way to do X in general."
Direct get_skill results load the skill body into your tool output; follow them before continuing.