claudecodex

Pendo Novus

UX review and evidence-backed next-work and portfolio investment decisions powered by Pendo product analytics.

5 on GitHubby Pendov0.6.0Proprietaryupdated 1 month agocode-review
/

Plugin novus from marketplace pendo in pendo-io/novus-plugin. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (6)

  • build-impact

    Explain what a team's shipped improvements add up to for customers in a product area, why they matter, and what evidence supports their value. Also use to verify a specific change, launch, or experiment, or when a builder explicitly requests an individual impact report. Portfolio allocation belongs

  • build-investment

    Use when a leader asks whether engineering investment is going to the right goals or product areas, whether to sustain or change that investment, or needs a planning-cycle or portfolio review. Explaining the value of a team's shipped improvements belongs to build-impact.

  • usage-brief

    Use when a builder wants current usage for the product area a PR, ticket, or proposed feature touches, and an evidence-based read of the customer benefit it could create. Can prepare a PR or ticket comment and post it after confirmation. Use build-impact to evaluate shipped outcomes.

  • ux-review

    Reviews uncommitted or branch-local code changes for real UX problems before a PR is opened — wrong visual semantics, unpersisted UI state, poor discoverability, missing loading and error states, removal of well-used paths, redundant UI. When the Novus MCP server is connected it backs findings with

  • verify-instrumentation

    Use when a decision depends on Pendo/Novus behavioral data and you need to know whether the measured surface is instrumented well enough to trust — before starting work, before reading impact numbers, or as the measurement-trust sub-check for build-impact, build-investment, whats-next, or usage-brie

  • whats-next

    Use when a builder asks what to build next, whether to finish, continue, narrow, pause, or switch current engineering work, what to defer, or when an autonomous coding agent must steer among bounded work options. Not for team-level portfolio allocation or designing an experiment for an already selec

MCP servers (1)

  • novus

    connects to: https://novus-api.pendo.io/mcp

View source on GitHub novus.pendo.io

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

ecc

claudecodex

Harness-native ECC operator layer - 71 agents, 314 skills, 98 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses

200 skills · 98 commands · 71 agents · 1 MCP server · hooks

affaan-m/ECC 302,088

Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives

1 command

anthropics/claude-code 155,476

Professional UI/UX design intelligence for AI coding assistants. Includes searchable databases of styles, colors, typography, charts, and UX guidelines for React, Next.js, Astro, Vue, Nuxt.js, Nuxt UI, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose, Angular, Laravel, JavaFX, and Three.js.

7 skills

nextlevelbuilder/ui-ux-pro-max-skill 148,759

agent-skills

claudecodex

Production-grade engineering skills covering every phase of software development: spec, plan, build, verify, review, and ship.

25 skills · 4 agents

addyosmani/agent-skills 116,782

Design fluency for frontend development. 1 skill with 24 commands (/impeccable polish, /impeccable audit, /impeccable critique, etc.) and curated anti-pattern detection.

1 skill · 4 agents · hooks

pbakaus/impeccable 109,099

Maintain Pendo Novus?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted