operations▌

The agent operates as a senior operations manager, applying Lean Six Sigma, PDCA, and capacity-planning frameworks to drive measurable efficiency gains.

Complete financial clarity for indie businesses: profit analysis, tax planning, cash flow forecasting, and multi-venture tracking. \n \n Calculates true profitability using a structured formula that accounts for COGS, operating expenses, owner salary, and tax reserves \n Tracks finances separately across multiple businesses with comparative P&L analysis and runway forecasting \n Provides quarterly estimated tax planning with payment schedules and S-corp vs. sole proprietor guidance \n Inclu

|

This skill provides comprehensive guidance for AWS cost optimization, monitoring, observability, and operational excellence with integrated MCP servers.

Analyze files and retrieve metadata using Claude's native tools without modifying files.

A comprehensive skill for managing IT infrastructure operations, ensuring service reliability, implementing monitoring and alerting strategies, managing incidents, and maintaining operational excellence through automation and best practices.

Expert guidance for AI assistants on choosing the right geospatial tools from the Mapbox MCP Server. Focuses on selecting tools based on what the problem requires - geometric calculations vs routing, straight-line vs road network, and accuracy needs.

Frameworks for building and scaling product operations functions across growing teams. \n \n Bridges product and operations by creating systems that enable PMs to focus on strategy rather than operational overhead like release management, enablement, and cross-functional coordination \n Standardizes processes, tooling, and insights across product teams while preserving PM decision-making authority; product ops informs, not decides \n Addresses common scaling challenges: surfacing user research a

Best practices guide for writing efficient, type-safe GraphQL operations and organizing them with fragments. \n \n Covers queries, mutations, subscriptions, and fragments with naming conventions, variable syntax, and directive usage \n Emphasizes core principles: request only needed fields, name all operations, use variables instead of hardcoded values, and include id fields for cacheability \n Recommends colocating fragments with components and using @include / @skip directives for conditional

OCI monitoring setup, alarm configuration, and troubleshooting for metrics, logs, and observability gaps. \n \n Covers metric namespace patterns, alarm threshold gotchas (sparse data handling, trigger delays), and missing data strategies across OCI services \n Provides decision trees for log collection troubleshooting, Service Connector setup, and IAM policy requirements \n Highlights critical anti-patterns: metric lag (10-15 minutes), dimension requirements, notification channel setup, and Clou