{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifsmvtazzdk4p7wqjjzt65t2utrg5jz33ppkqcscq4e7w6xrodc3m",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mmwaaucbvmp2"
  },
  "path": "/t/chatgpt-business-skills-appear-installed-enabled-in-ui-but-are-not-available-at-runtime/1380754#post_9",
  "publishedAt": "2026-05-28T13:43:33.000Z",
  "site": "https://community.openai.com",
  "textContent": "Additional note: we are now seeing what looks like the same class of issue with Company knowledge / connectors. In the UI, Slack is enabled for the chat under Company knowledge. However, in the actual chat runtime, Slack is not exposed as an available connector/tool, and the assistant reports that it cannot access Slack even though the UI shows it as enabled.\n\nThis looks structurally similar to the Skills issue: the UI/backend state says a capability is enabled, but the runtime does not mount or expose the corresponding resource/tool. This may indicate a broader workspace-level propagation or enabled-state caching issue, not only an isolated Skills problem.",
  "title": "ChatGPT Business Skills appear installed/enabled in UI but are not available at runtime"
}