app-setup

Installation
SKILL.md

App Setup

Take a developer from "I need an app for this integration" to an app that is owned by a business portfolio and has the use cases the integration needs.

Rules

  • Get the developer's agreement before every write. devtools_app_create, devtools_business_create, devtools_app_business_manage and devtools_app_use_cases_manage ask for confirmation. If the client supports elicitation, the server prompts the developer directly and executes on the first call, so say what you are about to do before calling. Otherwise the first call returns a summary and a confirm_token; show the summary, and after the developer agrees, repeat the call with the same arguments plus that confirm_token.
  • Pass the skill name on every call. Every devtools_* call passes skill_name app-setup, or the calling skill's name where When another skill runs this one says so.
  • Verify every write with its read before a dependent write or a retry. A write can report an error and still take effect. Check with devtools_app_list, devtools_business_list or devtools_app_use_cases before continuing.
  • Create at most one app. There is no delete-app tool, and a duplicate app counts against the developer's app limits. If the developer names an existing app that is not listed, treat it as ungranted and reauthorize instead of creating a replacement.
  • Nothing here can be undone over MCP. No tool deletes an app, unlinks a business or removes a use case. Reversal is a step in the App Dashboard.
  • Let the server explain a refusal. When a call is refused, show the developer the error's message as returned; it says what they need to do. Retry only if the message says to, and never create a replacement app or portfolio to get around a refusal. Then close tracking and stop.
  • Close tracking whenever you stop. Call devtools_skill_invocation with action end before you finish or hand control back for good. Asking the developer a question is not stopping.

Workflow

  1. Start tracking. Before any other work, call devtools_skill_invocation with action start and skill_name app-setup. Pass skill_name app-setup on every devtools_* call in the following steps. When another skill runs this one, follow When another skill runs this one instead.
Installs
7
GitHub Stars
29
First Seen
9 days ago