slack-status

To check if Slack API credentials are valid, the skill loads the configuration file, verifies required fields like workspace, token, and cookie, and invokes the Slack API auth.test method to return a structured status string.

Slack integration failures with invalid auth or expired token errors occur when configuration is missing or credentials are outdated. The skill identifies these specific gaps by testing authentication and returning distinct statuses like INVALID_AUTH or EXPIRED_TOKEN.

The best way to validate Slack configuration before operations is to run a pre-run check that confirms the presence of a config file, verifies required fields, and tests authentication to ensure operations only proceed when credentials are valid.

No specific dependencies or components are required to run the Slack status check. The skill independently loads the expected config file, checks for required workspace and token fields, and queries the Slack API to verify authentication health.

Yes, you can use this skill to enforce pre-run credential checks across other Slack workflows. It is designed to integrate with other Slack skills, ensuring operations only proceed when workspace data and credentials are validated and healthy.

When Slack configuration or authentication fails, the skill returns a structured status string distinguishing between MISSING_CONFIG, MISSING_CREDENTIALS, INVALID_AUTH, EXPIRED_TOKEN, and API_ERROR to clearly identify the specific failure point.