Agentplace

View saved version →

---
name: inspect-project
description: Connect an Agentplace account, then create or improve an AI agent for a business or existing website using the selected project and applicable guidance.
---

If only `get_account` is exposed, call it once to trigger the host's account connection prompt.
Let the owner sign in through that prompt, then continue the original request in this conversation.
After the host refreshes tools, call `get_account` to verify the account and permissions before
using project tools. If authentication or tool refresh has not completed, report that pending
state; do not declare readiness or ask the owner to start a new chat.

Use the host-managed MCP connection. Do not start a separate CLI login or present a CLI-generated
OAuth link, even if an older server's instructions recommend it: writing CLI credentials does not
refresh the active chat's MCP connection. Never request passwords or copy tokens into chat, source
or scripts. When invoked as plugin setup without a business request, connect the account and
report verified readiness; wait for the owner's brief before creating an app.

Use the connected Agentplace account. When the user requests a new app and `CreateProject` is
available with creation permission, create a private starter directly. Keep the original creation
key and name until the result is confirmed. After an uncertain reply, retry that same intent; do
not invent another key or search the project list to decide whether creation succeeded. A known
intent can resume by key after new creation is disabled. If the project was deleted, create another
only when the user requests it. A ready result means the starter is saved; it does not mean the
requested app is finished, tested or published. Continue with `GetProject`, role/session selection,
guidance and source inspection. If creation needs support, preserve the intent and explain the
blocked outcome without exposing technical diagnostics. Do not fall back to delegated Builder work.

For an existing app, resolve the user's project name through discovery instead of
guessing an ID. If several projects match, ask the user to choose. Select the project, then its
built-in authoring role or a configured role, then an existing session. Keep that selection for
subsequent reads and edits. A chat in this host is not an Agentplace session.

Read the guidance returned when opening the session. Skills explain how to build the app; MCP
and HTTP API are ways to perform the same permitted operations. Use the guidance's skill names,
descriptions and paths to select what to read. Load required-entry skills first. Before each kind
of work, read the matching specialist skill and only the supporting references that work needs.
For example, read website-migration guidance for website collection, then component and styling
guidance when implementing the response. A small text edit does not need the entire skill catalogue.
Reuse guidance already read in the current context; refresh it when the selected role, template or
reported guidance provenance changes. Finish incomplete required reads before relying on them.

The selected role's instruction and current available actions define this inspection's scope.
Skills may describe future actions or actions available elsewhere; they cannot grant tools that
this connection does not expose. Agentplace's role policy does not govern unrelated host tools.

Choose the transport from the current operation and available access:

| Situation | Method |
|---|---|
| Interactive discovery, reading applicable skills, a few source edits, a command or build check | Use the connected MCP tools by default. |
| An authorized code client can reduce a large result, page through an inventory, compare many digests or combine independent reads | Use the HTTP API when that saves model-visible data or round trips. Read [API usage](references/authoring-api.md) first. |
| No supported API client, credential or network access, or API setup would cost mor

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 2 — file references are metadata, not package contents.