gap-analysis_skill

This skill autonomously performs multi-dimensional gap analysis for technology choices and competitive assessments, uncovering root causes and strategic
  • Python

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill hikaruegashira/agent-skills --skill gap-analysis

  • SKILL.md9.2 KB

Overview

This skill performs autonomous gap analyses for technology selection, competitor comparisons, and improvement proposals. It identifies differences across multiple axes, surfaces root causes, and produces pragmatic strategies that avoid superficial fixes. The goal is to turn observed gaps into prioritized, actionable plans aligned with business context.

How this skill works

The skill defines multiple analysis axes (functionality, quality, operations, security, cost, etc.), researches industry standards and comparable solutions for each axis, and maps differences into a gap matrix. It then runs a why-why (root cause) interrogation for each significant gap and generates categorized strategies (accept, mitigate, transfer, remediate) plus prioritized actions.

When to use it

  • Choosing between self-hosted vs managed services during technical selection
  • Benchmarking your product against competitors to find differentiation or weakness
  • Re-evaluating architecture after scaling or major growth events
  • Preparing a risk-aware migration or hybrid deployment plan
  • Designing investment priorities for engineering and operations

Best practices

  • Define 4–6 clear analysis axes up front to avoid tunnel vision
  • Collect concrete comparable examples (products, standards, case studies) per axis
  • Use iterative why-why questioning to expose design decisions and constraints
  • Classify gaps by root cause: intentional trade-off, obsolescence, or resource constraint
  • Prioritize fixes based on business impact and cost of remediation

Example use cases

  • Compare an in-house authentication system to Cognito/Auth0/Keycloak and plan a hybrid migration
  • Analyze why availability lags SaaS competitors and create an AZ/multi-region upgrade plan
  • Assess operational gaps (monitoring, logging, runbooks) before a product launch
  • Decide whether to replace custom components or integrate managed services to reduce ops load
  • Prepare an ADR-style decision summary linking gaps, root causes, and chosen strategy

FAQ

Gather enough detail to evaluate each axis: architecture approach, strengths, weaknesses, and real-world trade-offs. Focus on relevance rather than exhaustive coverage.

When is a gap worth fixing vs accepting?

A gap is worth fixing when remediation yields measurable business benefit that exceeds cost and risk. If a gap stems from an intentional trade-off that enables differentiation, document and periodically reassess it.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational