analyze-codebase

Analyzes an existing codebase to identify licensable capabilities and classify them as access gates or rate limits.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/Sidub-Inc/Monaiq.AI.Plugin2 --skill analyze-codebase-sidub-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: analyze-codebase
Source: https://github.com/Sidub-Inc/Monaiq.AI.Plugin2/tree/main/skills/analyze-codebase
Command: npx skills add https://github.com/Sidub-Inc/Monaiq.AI.Plugin2 --skill analyze-codebase-sidub-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams with an existing application often struggle to determine which parts of their code could be licensed, gated, or monetized. This Skill scans the codebase and produces an evidence packet of licensable capabilities with suggested feature keys, removing the guesswork from monetization planning. ## Core Features & Use Cases - Codebase Scanning: Reads project configuration files (package.json, *.csproj, Program.cs, appsettings.json) and key business-logic areas such as controllers, services, middleware, and route handlers to detect the tech stack and structure. - Capability Classification: Classifies each finding as an Access feature (binary yes/no gate) or a RateLimit feature (metered quota) using the scenario taxonomy, and suggests stable FeatureKey values. - Catalog Gap Analysis: When a product catalog already exists, compares catalog features against codebase findings to distinguish existing coverage from gaps. - Use Case: A developer with a .NET 8 Web API wants to know what to monetize. The Skill scans controllers and services, identifies premium endpoints and compute-intensive operations, and outputs a table of capabilities with suggested FeatureKeys ready for pricing design. ## Quick Start Ask the assistant to analyze your codebase and identify which capabilities could be licensed or rate-limited for monetization.

Frequently Asked Questions about analyze-codebase

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

FAQPage Schema
How do I identify which parts of my codebase can be monetized?▼

Run a codebase analysis that scans controllers, services, middleware, and route handlers for premium modules, valuable API endpoints, data exports, integrations, and compute-intensive operations. Each finding is classified as an access gate or a rate limit with a suggested feature key.

What is the difference between an access feature and a rate limit feature?▼

An access feature is a binary yes/no gate, used for premium modules, feature flags, or exclusive content. A rate limit feature is metered with a quota per time window, used for API calls, data exports, or batch operations. The heuristic is: yes/no means access, how many means rate limit.

Does codebase analysis work with .NET and Node.js projects?▼

Yes, the analysis reads project configuration files such as package.json, *.csproj, Program.cs, Startup.cs, appsettings.json, and tsconfig.json to detect the tech stack, then scans the relevant business-logic directories for that platform.

Can I compare codebase findings against my existing product catalog?▼

Yes, when products already exist, the analysis lists current catalog features and compares them against codebase findings. The output distinguishes capabilities already covered by the catalog from gaps that represent new monetization opportunities.

What are the limitations of automated codebase monetization analysis?▼

The analysis is read-only and evidence-bounded: it summarizes file paths, areas, and observed patterns without quoting secrets or dumping full files. If evidence is missing or stale, it routes to a narrower prerequisite step rather than producing a low-confidence recommendation.