From ops-suite
Search and analyze logs from services and containers. Use when asked about "logs", "errors", "exceptions", "log search", "error messages", "stack trace", "application errors", "debug logs".
npx claudepluginhub weorbitant/workbench-dev --plugin ops-suiteThis skill is limited to using the following tools:
Check if `/tmp/ops-suite-session/config.json` exists:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Check if /tmp/ops-suite-session/config.json exists:
config.yaml, parse it, and write to /tmp/ops-suite-session/config.json for other skills to reuse.
If neither exists, tell the user to copy config.example.yaml to config.yaml and fill in their values. Stop here.Extract:
orchestrator — determines which adapter to loadenvironments — available environments and their connection detailsRead the adapter file at adapters/{orchestrator}.md (in this skill's directory).
If the adapter does not exist, tell the user that the orchestrator {orchestrator} is not yet supported and stop.
If $ARGUMENTS contains an environment name, use it. Otherwise ask the user.
If $ARGUMENTS contains a service name, use it. Otherwise list available services and ask.
Store selected environment config as env and service name as {service}.
Start with recent errors (last 200 lines with error/exception filtering):
If the user asks about a specific pattern or entity: 4. Pattern search — Use adapter command to grep for specific patterns 5. Context around errors — Get lines before/after each match for context
If the user wants live monitoring: 6. Follow logs — Use adapter command to tail/follow logs (warn that this runs indefinitely)
If the service has multiple replicas:
If a container recently restarted, use the adapter's "previous container logs" command to capture the crash output.
Present results in this format:
Service: {service}
Environment: {env_name}
Time range: last {duration}
Error Summary:
Total errors: {count}
Unique error types: {count}
Error Breakdown:
1. {error_type} — {count} occurrences — {frequency pattern}
Sample: {first occurrence snippet}
2. ...
Affected Entities:
- {entity_id}: {error_type} at {timestamp}
- ...
Pattern:
{description of when errors started, frequency trend, correlation with events}
Recommended Next Steps:
- {action items based on findings}
Based on the error patterns found, suggest specific next steps:
→ Run `/ops-suite:db-migrate {env_name}` to check and apply pending migrations.
→ Run `/ops-suite:queue-triage {env_name}` to diagnose failed messages.
Use ops-suite:service-status with arguments: {service} {env_name}.
Use session state from /tmp/ops-suite-session/ — do not re-ask for environment.