work-integrationslisted

# Crew integrations Inspect current state before changing it, and distinguish account-level setup from selection for this project. MCP setup has its own `work-mcp` skill. ## Secrets - Call `list_secrets` before creating, replacing, or deleting a secret. - `set_workflow_secret` and `delete_workflow_secret` manage project-scoped secrets in Crew (legacy tool names for the shared project store). There is no account-level secret: a credential shared across projects must be a global, promoted by an administrator (see below). - After `set_workflow_secret` succeeds, `$SECRET_<NAME>` is available to shell tools immediately in the current chat and remains available in later turns. Continue the requested work in the same chat; do not ask the user to start a new chat or session. Verify availability without printing the secret value. - Work stores attached secret names in `workflow.json` under `capabilities.selected_secrets`, using the AgentWorks workflow contract. Secret values remain encrypted outside the manifest. Respect the user's selections in **Setup > Secrets**; do not attach an unrelated credential. - A read-only workflow or Crew reference never grants its secrets. To reuse a credential across projects, an administrator must explicitly promote the source project/workflow secret with `manage_global_secret(action="promote")` or **Make global** in Setup > Secrets. Then explicitly select that global name in each destination Crew with `update_project_glo