Update to WOTT

{
  "description": "Manage projects in wott by finding, reviewing, creating, and updating projects. Use when the user wants to work with wott projects or needs project information as context for a task.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 258
    },
    {
      "relative_path": "assets/wott-small.png",
      "size_in_bytes": 52883
    },
    {
      "relative_path": "assets/wott.png",
      "size_in_bytes": 490946
    },
    {
      "relative_path": "evaluations/README.md",
      "size_in_bytes": 5092
    },
    {
      "relative_path": "evaluations/ambiguous-project.json",
      "size_in_bytes": 2031
    },
    {
      "relative_path": "evaluations/create-project.json",
      "size_in_bytes": 1709
    },
    {
      "relative_path": "evaluations/find-project.json",
      "size_in_bytes": 1347
    },
    {
      "relative_path": "evaluations/project-workflow.json",
      "size_in_bytes": 1769
    },
    {
      "relative_path": "evaluations/update-project.json",
      "size_in_bytes": 2193
    },
    {
      "relative_path": "examples/create-project.md",
      "size_in_bytes": 1412
    },
    {
      "relative_path": "examples/find-project.md",
      "size_in_bytes": 1440
    },
    {
      "relative_path": "examples/update-project.md",
      "size_in_bytes": 1405
    },
    {
      "relative_path": "reference/project-tool-reference.md",
      "size_in_bytes": 19382
    },
    {
      "relative_path": "reference/project-workflows.md",
      "size_in_bytes": 6523
    }
  ],
  "name": "project-management",
  "skill_md_contents": "---\n\nname: project-management\ndescription: Manage projects in wott by finding, reviewing, creating, and updating projects. Use when the user wants to work with wott projects or needs project information as context for a task.\nmetadata:\n  short-description: Manage wott projects and project context\n\n---\n\n# Project Management\n\nUse the wott MCP server to help the authenticated user find, understand, create, and update projects.\n\nProjects represent larger areas of work and may contain related notebooks and knowledge.\n\n## Quick start\n\n1. Identify what the user wants to do with a project.\n2. For project-specific workflows, consult the relevant guide in `reference/`.\n3. Find the relevant project using `search_project` or `get_projects`.\n4. Retrieve project details with `get_project` when the task requires project-specific information.\n5. Create or update projects using the appropriate MCP tool.\n6. Use project information as context when it is relevant to the user's broader task.\n7. Confirm the MCP operation succeeded before reporting a change.\n\n## Tool-call guardrails\n\n* Always use the authenticated wott user.\n* Never ask the user for a Firebase UID, OAuth access token, Firebase credentials, Firestore credentials, or internal server secrets.\n* Never fabricate project IDs.\n* Do not access another user's projects.\n* Do not perform a write operation when the target project or requested change is ambiguous.\n* For updates, modify only the fields requested by the user.\n* Do not claim a project was created or updated unless the MCP tool confirms success.\n* If a write operation fails, report the failure accurately.\n* Do not blindly retry a failed write operation when it could create a duplicate or unintended change.\n* Use the tool schemas exposed by the wott MCP server as the source of truth for available arguments and fields.\n\n## Workflow\n\n### 1. Find or identify a project\n\nUse `search_project` when the user refers to a project by:\n\n* Name\n* Topic\n* Keyword\n* Description\n\nUse `get_projects` when the user wants to browse or see their projects.\n\nFor detailed project lookup and disambiguation rules, read:\n\n`reference/project-workflows.md`\n\nIn particular, use the project identification workflow when the user says things such as:\n\n* \"Find my robotics project.\"\n* \"Open my AI project.\"\n* \"Which project is about humanoid robotics?\"\n* \"Show me my projects.\"\n\nIf exactly one project clearly matches, continue.\n\nIf multiple projects could match, ask the user to clarify.\n\nIf no project matches, clearly tell the user.\n\nDo not guess when selecting a project for a write operation.\n\n### 2. Read a project\n\nUse `get_project` when the user wants details or information from a specific project.\n\nIf the user provides a project ID, use it directly.\n\nIf the user provides only a name or description, resolve the project first.\n\nFor the detailed read workflow, consult:\n\n`reference/project-workflows.md`\n\nFor available tool arguments and expected project data, consult:\n\n`reference/project-tool-reference.md`\n\n### 3. Create a project\n\nUse `create_project` when the user clearly asks for a new project.\n\nBefore creating a project:\n\n1. Determine the project name.\n2. Determine any other required fields from the MCP tool schema.\n3. Check for an obvious duplicate when appropriate.\n4. Ask for missing required information when it cannot be safely inferred.\n5. Create the project.\n6. Verify the returned result.\n\nFor the complete creation workflow, read:\n\n`reference/project-workflows.md`\n\nFor the tool's input and output details, read:\n\n`reference/project-tool-reference.md`\n\nSee:\n\n`examples/create-project.md`\n\nfor a concrete example of the expected workflow.\n\nDo not create a project merely because the user discusses an idea.\n\n### 4. Update a project\n\nUse `update_project` when the user asks to modify an existing project.\n\nBefore updating:\n\n1. Identify the target project.\n2. Resolve the project if necessary.\n3. Determine exactly which fields the user wants changed.\n4. Update only those fields.\n5. Verify the result.\n6. Report the change.\n\nFor detailed update and ambiguity handling, read:\n\n`reference/project-workflows.md`\n\nFor the current tool schema, read:\n\n`reference/project-tool-reference.md`\n\nSee:\n\n`examples/update-project.md`\n\nfor a concrete update workflow.\n\nNever overwrite unrelated project information.\n\n### 5. Build project context\n\nUse project information as context when the user's task depends on an wott project.\n\nFor example:\n\n> Help me continue working on my robotics project.\n\nFollow this general workflow:\n\n```text\nidentify project\n      ↓\nsearch_project\n      ↓\nget_project\n      ↓\nuse project information as context\n      ↓\ncontinue with user's task\n```\n\nFor more detailed context-building workflows, consult:\n\n`reference/project-workflows.md`\n\nWhen the task also requires notebook information, use the `notebook-management` skill and preserve the project context.\n\n### 6. Project and notebook context\n\nProjects and notebooks may be related.\n\nWhen the user asks for information across a project and its notebooks:\n\n1. Identify the project.\n2. Retrieve the project when necessary.\n3. Find relevant notebooks.\n4. Retrieve relevant notebook information.\n5. Combine the relevant information into context.\n\nDo not assume a notebook belongs to a project unless the relationship is established by the user or wott.\n\nFor detailed project workflows and tool behavior, read:\n\n`reference/project-workflows.md`\n\nFor notebook-specific workflows, use the `notebook-management` skill.\n\n## Project identification rules\n\nWhen a user gives a project name:\n\n1. Search for the project.\n2. Compare the returned results with the user's request.\n3. If exactly one project is an obvious match, use it.\n4. If multiple projects match, ask the user to clarify.\n5. If no project matches, tell the user.\n\nWhen the user provides a project ID, do not search unnecessarily. Use the provided ID directly when the tool accepts it.\n\nNever fabricate IDs.\n\n## Project creation rules\n\nCreate a project only when the user clearly requests creation.\n\nExamples:\n\n* \"Create a project called Robotics.\"\n* \"Start a project for my robotics research.\"\n* \"Create a new project for this idea.\"\n\nBefore creation, check for an obvious duplicate when appropriate.\n\nIf a matching project already exists, avoid creating an unnecessary duplicate. Ask the user whether they want to use the existing project or create a separate one when the distinction matters.\n\nFor detailed creation behavior, read:\n\n`examples/create-project.md`\n\n## Project update rules\n\nOnly modify information the user requested.\n\nFor example, if the user says:\n\n> Rename my robotics project to Physical AI Research.\n\nOnly change the project name.\n\nDo not replace the description or other project fields unless requested.\n\nFor detailed update behavior, read:\n\n`examples/update-project.md`\n\n## Search and discovery\n\nUse `search_project` when the user is trying to locate a project by topic, name, keyword, or description.\n\nUse `get_projects` when the user wants to browse their projects.\n\nFor search and project-resolution examples, read:\n\n`examples/find-project.md`\n\nFor the complete search workflow, read:\n\n`reference/project-workflows.md`\n\n## Authentication\n\nAll project operations must use the authenticated wott user.\n\nThe model must never request or expose:\n\n* Firebase UID\n* OAuth access token\n* Firebase credentials\n* Firestore credentials\n* Internal server secrets\n\nNever attempt to access another user's projects.\n\n## Errors\n\nIf a project cannot be found, tell the user clearly.\n\nIf multiple projects match a potentially destructive or modifying request, ask the user to clarify.\n\nIf wott returns an authorization error, do not attempt to bypass it.\n\nIf an MCP operation fails, report the failure accurately.\n\nNever claim success unless the tool result confirms it.\n\n## References and examples\n\nThe `reference/` directory contains detailed project-management guidance that should be consulted when the task requires more specific workflow or tool information.\n\n* `reference/project-workflows.md` — detailed workflows for finding, reading, creating, updating, resolving ambiguous project references, and building project context.\n* `reference/project-tool-reference.md` — wott project MCP tools, tool annotations, proposed input schemas, output schemas, structured output, and project data representation.\n\nThe `examples/` directory contains concrete examples of common project-management workflows.\n\n* `examples/create-project.md` — creating a new wott project and handling duplicates or missing information.\n* `examples/update-project.md` — identifying and safely updating an existing project.\n* `examples/find-project.md` — finding projects, resolving ambiguous matches, and using project results to build context.\n\nRead the relevant reference or example file when it provides guidance needed for the current task. Do not load unrelated reference files unnecessarily.\n"
}