detect-product

Detect product capabilities across UI, API, and code paths.

25|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/parhumm/jaan-to --skill detect-product
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-product
Source: https://github.com/parhumm/jaan-to/tree/main/adapters/codex/skillpack/skills/detect-product
Command: npx skills add https://github.com/parhumm/jaan-to --skill detect-product

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and quantify product capabilities and constraints in a repository by aggregating evidence from surfaces, copy, and code to support data-driven decisions about features, pricing, and instrumentation.

Core Features & Use Cases

  • Evidence-based detection across UI routes, API endpoints, and code paths to surface real product capabilities.
  • Monetization and entitlement mapping, including gating logic and tier implications.
  • Cross-platform evidence linking to show consistency across platforms and facilitate traceability.

Quick Start

Analyze a repository to extract evidence-backed product insights and structured findings.

Frequently Asked Questions about detect-product

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

FAQPage Schema
How do I detect product capabilities from a software repository?

Product capability detection aggregates evidence across UI routes, API endpoints, and code paths to surface real features. It builds a 3-layer evidence model from surfaces, copy, and code to support data-driven decisions.

What is evidence-based product analysis for monetization and entitlements?

Evidence-based product analysis identifies monetization gates and entitlement logic by examining code paths and UI constraints. It maps gating logic and tier implications to reveal how features are restricted across different pricing levels.

How do I map cross-platform feature consistency across web and mobile?

Cross-platform feature consistency is mapped by linking related evidence across web, mobile, and backend surfaces. Standardized IDs and related evidence links ensure traceability when the same product capability appears on multiple platforms.

Can I extract analytics and instrumentation constraints from backend code?

Yes, you can extract analytics instrumentation and constraints from backend code paths. The detection process identifies existing tracking implementations and structural constraints, producing structured findings linked via standardized traceability IDs.

Does product capability detection work without external dependencies?

Yes, product capability detection works without external dependencies. It operates directly on typical software repositories to analyze surfaces, copy, and code paths to generate structured product insights and monetization findings.

When do I need a 3-layer evidence model for product analysis?

A 3-layer evidence model is needed when quantifying product capabilities and constraints to support data-driven decisions about features and pricing. It ensures findings are traceable by aggregating surface, copy, and code evidence with standardized IDs.