ops-settings

Manage post-setup credentials and integration status across configured services.

22|6|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Lifecycle-Innovations-Limited/claude-ops --skill ops-settings
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-settings
Source: https://github.com/Lifecycle-Innovations-Limited/claude-ops/tree/main/claude-ops/skills/ops-settings
Command: npx skills add https://github.com/Lifecycle-Innovations-Limited/claude-ops --skill ops-settings

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-setup credential management ensures integration statuses are visible, up to date, and easily updated without rerunning the full setup wizard, reducing downtime and manual follow-ups.

Core Features & Use Cases

  • Centralized credential health overview for all configured integrations.
  • Quick updates with immediate smoke tests to verify validity after changes.
  • Lightweight dashboards to spot missing or expired credentials and address them.

Quick Start

Open the OPS Settings panel and select an integration to update credentials, then run a smoke test to verify configuration.

Frequently Asked Questions about ops-settings

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify integration credentials after initial setup?

Verify integration credentials after setup by reading preferences.json to assess status, prompting for updates via AskUserQuestion, and executing a smoke test to confirm validity.

What is a post-setup credential health check?

A post-setup credential health check is a process to review configured integration statuses, identify missing or expired credentials, and update them without rerunning the full setup wizard.

How do I update Stripe or GitHub credentials without rerunning the setup wizard?

Update Stripe or GitHub credentials without rerunning the setup wizard by selecting the integration in the OPS Settings panel, applying changes via AskUserQuestion, and running a smoke test.

Can I smoke-test Slack and RevenueCat integrations after updating credentials?

Yes, you can smoke-test Slack and RevenueCat integrations immediately after updating credentials to verify configuration validity and ensure connectivity before resuming operations.

Does this credential management process work for all configured services?

Yes, this credential management process works for all configured services by reading preferences.json to assess integration statuses and prompting updates across GitHub, Stripe, RevenueCat, and Slack.

Why are my integration credentials showing as expired or missing?

Integration credentials show as expired or missing when status checks read from preferences.json detect invalid configurations, requiring updates via AskUserQuestion followed by a smoke test.