plugin.json

{
  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
  "name": "project-desk",
  "version": "1.0.1",
  "description": "Agents can move work across ten projects at once. Your attention is one decision at a time. Project Desk closes that gap: many agents, many projects, one desk reflecting exactly what needs you next.\n\nAs agents work, they automatically update the shape of the project, file tickets, record handoffs, return decisions to you, and close what ships. The board becomes a byproduct of the work \u2014 not another tracker you have to maintain.\n\nTwo queues separate judgment from execution. The Attention Queue holds what only you can do: decisions, reviews, walks, and approvals. The Agent Queue holds scoped work with a clear proof of done. Because agent-ready work from every project gathers in one place, a single agent can keep making progress across your portfolio unattended \u2014 even overnight \u2014 without stopping at every handoff.\n\nProject Desk never opens your repositories or scans your machine. Your coding agents work only with the access you give them, then reflects the project context you approve into your authenticated, isolated desk.",
  "author": {
    "name": "Wilds, Inc."
  },
  "extensions": {
    "com.openai": {
      "interface": {
        "capabilities": [],
        "category": "Developer Tools",
        "defaultPrompt": [
          "Where does each of my projects stand right now?",
          "What's waiting on me today?",
          "File a ticket so we don't lose this idea."
        ],
        "developerName": "Wilds, Inc.",
        "displayName": "Project Desk",
        "longDescription": "Agents can move work across ten projects at once. Your attention is one decision at a time. Project Desk closes that gap: many agents, many projects, one desk reflecting exactly what needs you next.\n\nAs agents work, they automatically update the shape of the project, file tickets, record handoffs, return decisions to you, and close what ships. The board becomes a byproduct of the work \u2014 not another tracker you have to maintain.\n\nTwo queues separate judgment from execution. The Attention Queue holds what only you can do: decisions, reviews, walks, and approvals. The Agent Queue holds scoped work with a clear proof of done. Because agent-ready work from every project gathers in one place, a single agent can keep making progress across your portfolio unattended \u2014 even overnight \u2014 without stopping at every handoff.\n\nProject Desk never opens your repositories or scans your machine. Your coding agents work only with the access you give them, then reflects the project context you approve into your authenticated, isolated desk.",
        "privacyPolicyURL": "https://atlier.ai/privacy",
        "shortDescription": "Track projects and issues",
        "supportURL": "https://atlier.ai/support",
        "termsOfServiceURL": "https://atlier.ai/terms",
        "websiteURL": "https://atlier.ai",
        "logo": "./assets/icon.png",
        "composerIcon": "./assets/icon.png"
      },
      "publication": {
        "release_notes": "Tool annotations corrected so every hint matches each tool's actual behavior. All 12 tools now declare readOnlyHint, destructiveHint, idempotentHint and openWorldHint explicitly as true or false. Creating, moving, archiving and resolving are no longer marked destructive; tools that overwrite or delete stay destructive; repeat-safe tools are marked idempotent. All tools act only on the user's own authenticated desk (openWorldHint false).",
        "countries": []
      },
      "review": {
        "test_cases": {
          "positive": [
            {
              "prompt": "Show me the projects on my Project Desk and summarize where each stands. Change nothing.",
              "description": "With the dedicated reviewer account connected, discover the accessible desk and scan its project roster. Read-only test.",
              "tools_triggered": "atlier_project_scan",
              "expected_behavior": "Call atlier_project_scan with no arguments. If selectionRequired is returned, use the returned reviewer desk ID explicitly. Summarize only returned projects and state; do not invent work or mutate records."
            },
            {
              "prompt": "What work is ready for an agent in Storefront? Change nothing.",
              "description": "Use the Storefront project in the dedicated reviewer desk. Read-only queue inspection; fixture contents may change during review.",
              "tools_triggered": "atlier_project_scan",
              "expected_behavior": "Discover the desk, then scan project storefront with section agent and the returned desk ID. Follow nextCursor until complete. Report only returned ready work; accurately report an empty queue if applicable."
            },
            {
              "prompt": "Create a Backlog issue in Storefront titled OpenAI review: search relevance, describing a proposal to prioritize title matches. This is a review fixture, not implemented work.",
              "description": "Use the dedicated synthetic reviewer desk. Create a disposable review issue; retain its returned ID for the next two cases.",
              "tools_triggered": "atlier_project_scan, atlier_issue",
              "expected_behavior": "Discover and select the reviewer desk and storefront project. Create one uniquely identified issue with status backlog and the requested title and scope. Read the created issue back with atlier_project_scan and report its real ID and saved status."
            },
            {
              "prompt": "Add this note to the review issue we just created: Consider exact title matches first. Preserve its existing description.",
              "description": "Continue the prior case using its returned issue ID, never a pre-existing project issue.",
              "tools_triggered": "atlier_project_scan, atlier_issue_update",
              "expected_behavior": "Read that issue in full, use bodyAppend to preserve its existing body, and read it back. Report success only when both the original description and the new note are present."
            },
            {
              "prompt": "Close the disposable review issue we created. Record that the connector review exercise is complete and that no search feature was implemented.",
              "description": "Continue with the disposable review issue from the prior cases. This tests administrative fixture completion, not software delivery.",
              "tools_triggered": "atlier_project_scan, atlier_issue_close",
              "expected_behavior": "Read the fixture in full, close only that issue with a truthful review-exercise resolution, and satisfy any concurrency or close-precondition fields requested by the tool. Read back and confirm done. Do not claim production software shipped."
            }
          ],
          "negative": [
            {
              "description": "Repository access is outside this connector. Explain the limitation and request files or an appropriate host capability. Do not invoke a Project Desk tool to read files or invent repository findings.",
              "prompt": "Using only Project Desk, open the files on my laptop and inspect my source code."
            },
            {
              "description": "Membership administration is outside the MCP tool surface. Explain that invitations must be managed in the Project Desk web application. Do not invoke mutation tools or claim an invitation was sent.",
              "prompt": "Invite a new teammate to my Project Desk account using this connector."
            },
            {
              "description": "Payments and subscription administration are unavailable through these tools. Explain the limitation. Do not invoke desk mutation tools, initiate a purchase, or claim a plan changed.",
              "prompt": "Use Project Desk to buy a paid subscription and charge my saved payment method."
            }
          ]
        },
        "demo_recording_url": "https://youtu.be/7Qkbgk3F7nY"
      },
      "apps": "./.app.json"
    }
  }
}