Business & Operations
Operations, strategy, finance, sales, support, management, and planning
Browse business & operations skills
Showing 32,593–32,616 of 32,626 skills
Quantitative scoring of niche viability for lifestyle SaaS ($1-3M ARR, solo/duo team). Use after completing a first-pass evaluation to generate a weighted score and go/no-go decision. Triggers on requests like "score this niche", "rate this opportunity", "should I pursue this", or "give me a scorecard for [niche]". Produces a 0-100 weighted score with clear decision thresholds.
First-pass evaluation of niche SaaS ideas through a lifestyle business lens ($1-3M ARR, solo/duo team). Use when evaluating a new niche hypothesis, researching a vertical software opportunity, or validating whether a market is worth pursuing. Triggers on requests like "evaluate this niche", "is this a good market", "research this vertical", or "first pass on [industry] software idea". Distribution-first methodology—kills ideas without concrete go-to-market paths.
Generate niche SaaS ideas based on founder expertise, industry access, and mandatory workflow patterns. Use when you want to discover lifestyle SaaS opportunities ($1-3M ARR, solo/duo team) that match your unique advantages. Triggers on requests like "generate niche ideas", "find SaaS opportunities for me", "what niches should I explore", "help me find a vertical SaaS idea", or "discover business opportunities". Outputs 5-10 concrete hypotheses ready for first-pass evaluation.
This document outlines a flexible and comprehensive architecture for designing game skill systems. The approach is modular, allowing for adaptation to various game genres by composing different data, logic, and event-handling components. **IMPORTANT NOTE**: This general framework represents the maximum feature set. It should be simplified or modified according to the specific game content and type. Examples are provided later in this document.
Plan mode on steroids. Push engineers to think with a product mindset before building. Structured intake, then concrete options.
Agent skill compiled from company onboarding docs in Notion
Salesforce administration using Salesforce CLI (sf/sfdx). Use when working with Salesforce metadata, custom objects, fields, users, profiles, permission sets, Flows, automation, or data management. Triggers on tasks involving sf/sfdx commands, Salesforce Setup configuration, metadata deployment, user security administration, or Salesforce data operations.
Build Keynote-style single-file HTML slide decks with brand-ready templates, minimal navigation, and Gemini nano banana media generation. Includes Narrative Engine integration for framework-driven deck creation with 17 proven storytelling structures and 5-agent review panel. Use when creating or editing slide decks, transforming content into presentations, or generating slide visuals.
--- name: Consoul Ticket Writer description: Expert at creating well-structured, properly estimated tickets for the Consoul project. Automatically activates when the user asks to create tickets, stories, epics, or issues for Consoul. Reviews codebase and research before writing tickets, follows Jira best practices, adds story points using modified Fibonacci scale, and includes relevant labels. Never makes assumptions - always researches the codebase and AI/LangChain integration patterns first...
Analyze collected requirements from interviews, detect ambiguities, generate structured specifications, and suggest implementation approaches
Strategic thinking framework integrating First Principles Analysis, Stanford Design Thinking, and MIT Systems Engineering for deeper problem-solving. Use for architecture decisions or root cause analysis.
Analyzes GCP costs and provides optimization recommendations including committed use discounts, rightsizing, and unused resources. Use when optimizing GCP spending or analyzing GCP costs.
Analyzes Azure costs and provides optimization recommendations including reserved instances, rightsizing, and unused resources. Use when optimizing Azure spending or analyzing Azure costs.
Analyze and optimize AWS costs with recommendations for Reserved Instances, right-sizing, and resource cleanup. Use when reducing AWS spending, analyzing costs, or optimizing cloud infrastructure expenses.
Gather and analyze competitive intelligence from multiple sources.
Analyze design docs, calculate velocity from recent work, and create realistic sprint plans with day-by-day breakdowns. Use when user asks to "plan sprint", "create sprint plan", or wants to estimate development timeline.
name: "sprint-progress-tracker" description: | Monitors and reports execution status across active sprints and tasks with real-time progress visibility. Activates when: checking sprint status, monitoring task progress, generating progress reports, calculating ETAs, identifying bottlenecks, or creating stakeholder status updates. Provides completion percentages, file counts, time elapsed, and estimated completion times. allowed-tools: - Read - Write - Grep - Glob - Bash - Todo
Designs system architecture, component specifications, and technical integration strategy. Use when: designing solutions, system architecture, technology stack, or integration approaches.
Recommend technology stacks based on project requirements, team expertise, and constraints. Use when selecting frameworks, languages, databases, and infrastructure for new projects.
Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints. Use when cto-architect needs to create actionable technical roadmaps from architecture designs.
Infrastructure and development cost estimation for technical projects. Use when planning budgets, evaluating build vs buy decisions, or projecting TCO for architecture choices.
Guide for creating Azure DevOps work items (Features, User Stories, Tasks). This skill should be used when working with ADO MCP tools to create work items with proper hierarchy and formatting.
Guide spec-driven development workflow (Requirements → Design → Tasks → Implementation) with approval gates between phases. Use when user wants structured feature planning or says "use spec-driven" or "follow the spec process".
Track and manage development tasks