102 AI Agent Skills for the full product lifecycle. Compatible with Trae / Claude Code. 9 modules from discovery to launch to growth. | 102 AI Agent Skills covering the full product lifecycle, compatible with Trae / Claude Code, with 9 modules from discovery to launch and growth.
Skill Claude CodeCodex
A tool for listing product assumptions and assessing their risks. An assumption is something a team believes about value, feasibility, usability, or growth but has not yet proven.
Skill Claude CodeCodex
A tool for designing experiments that test product assumptions, using methods such as A/B tests and usability tests. An A/B test compares two versions, while a usability test observes whether people can use a design successfully.
Skill Claude CodeCodex
A tool for defining the scope of an MVP, or minimum viable product—the smallest version that can test a product idea. It sorts features into essential, excluded, and optional groups while considering available resources.
Skill Claude CodeCodex
An assistant for usability testing, where people try a product so researchers can find user-experience problems.
Skill Claude CodeCodex
A workflow for designing a product measurement system across metrics, event tracking, and dashboards.
Skill Claude CodeCodex
A tool for configuring product-metrics dashboards, which are visual screens that show key measurements.
Skill Claude CodeCodex
A tool for building a product measurement system: a structured set of metrics used to understand product performance.
Skill Claude CodeCodex
A tool that creates a product tracking plan from a required product requirements document (PRD), which describes what a product should do.
Skill Claude CodeCodex
A workflow for coordinating product data analysis from separate analysis steps.
Skill Claude CodeCodex
A decision-making workflow for coordinating data-based product decisions.
Skill Claude CodeCodex
A workflow for designing or running an A/B test, where two versions are compared with different user groups.
Skill Claude CodeCodex
An automated system for checking product or business metrics, which are measurements such as sign-ups, revenue, or active users.
Skill Claude CodeCodex
A conversion-funnel analysis tool that examines the steps users take toward a goal, such as signing up or buying something.
Skill Claude CodeCodex
An automated analysis of user retention, including cohort analysis, which compares groups of users who started at the same time, and searches for the point when users first see value.
Skill Claude CodeCodex
A tool for producing structured Markdown data reports that combine funnel analysis, retention analysis, anomaly detection, trends, and recommended actions.
Skill Claude CodeCodex
An automated reporting process for building a team habit of making decisions from data.
Skill Claude CodeCodex
A data-to-action decision process based on four stages: define the question, analyse the data, reach a conclusion, and track execution.
Skill Claude CodeCodex
A guide for designing A/B tests, where different users see different versions of a change so their results can be compared.
Skill Claude CodeCodex
A process for running A/B tests, checking their results, and producing a complete report.
Skill Claude CodeCodex
A coordination guide for acquiring users, covering the work of bringing new people to a product.
Skill Claude CodeCodex
A coordination guide for user activation, meaning helping new users reach the first point where they understand the product's value.
Skill Claude CodeCodex
A coordination guide for planning and managing product growth, including attracting users, helping them get started, keeping them engaged, and earning revenue.
Skill Claude CodeCodex
A coordination guide for improving user retention, meaning how many users continue coming back over time.
Skill Claude CodeCodex
A revenue-orchestration skill described as covering commercialisation principles, coordination ideas, operating protocols, and a pipeline. The input does not provide enough detail to explain its specific actions.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: