# Graph-of-Skills

Graph-of-Skills is connected as an MCP server. Before starting a task that involves a file format
(Word, PowerPoint, Excel, PDF and similar), a named tool, framework or API, or this team's own
conventions (commit format, error shape, migration rules, house style), call `retrieve_skill_bundle`
with one sentence describing the task, then follow a returned skill that matches. Skip the call for
plain code edits, debugging, explanations and questions that need no outside knowledge.

Describe the task as an action and its object, such as "plan a client discovery call and scope the
project", not a topic such as "consultancy conversations". If the results do not fit, retry once or
twice with a narrower sentence before deciding no skill exists, and judge fit from the returned
content. A returned skill needs no installing; use it from the response.

If no skill exists after those retries, offer to write one with `create_skill`, and call it only when
the person says yes. The person must see the draft in the terminal first, and the skill stays pending
until they confirm it in their dashboard.