---
title: "novus"
description: "Novus skills for coding agents: UX review and evidence-backed next-work and portfolio investment decisions, powered by Pendo product analytics."
canonical: https://agentpluginsdirectory.com/plugins/novus
last-updated: 2026-09-27
---

# novus
Novus skills for coding agents: UX review and evidence-backed next-work and portfolio investment decisions, powered by Pendo product analytics.
- Slug: novus
- Publisher: pendo-io
- Repository: https://github.com/pendo-io/novus-plugin
- Manifest: plugin.json
- Version: 0.6.0
- License: Proprietary
- Category (editorial): code-review
- Skills: 6 (build-impact, build-investment, usage-brief, ux-review, verify-instrumentation, whats-next)
- MCP servers: 1 (novus)
- Stars: 5
- Repository created: 2026-08-11
- Repository last pushed: 2026-09-25
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/novus
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What novus does, in the publisher's words

Novus skills for coding agents, backed by Pendo product analytics.

Novus automatically instruments supported product surfaces. These skills help builders decide what to finish next, whether shipped work created customer value, and whether portfolio investment matches customer need, backed by product, planning, and delivery evidence.

Answers: What did this shipped work add up to, did it create customer value, and what should we do now?

- Planned: Linear/Jira initiatives, priorities, cycles, and intended capacity.
- Built: completed work and merged changes, estimated with team-level scope and complexity rather than surveillance metrics such as lines of code or raw PR counts.
- Experienced: Novus signals, adoption, funnels, frustration, feedback, account reach, and post-release outcomes.
- Use usage-brief when the question is how used the area your change touches is, and whether the change can grow that usage.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/pendo-io/novus-plugin/HEAD/README.md

## Skills

- build-impact: Use when someone asks whether a shipped change, set of pull requests, launch, experiment, or feature worked, created customer value, should roll out further, should continue, or should be rolled back, including weekly engineering-impact or "code in the wild" reports.
- build-investment: Use when a leader asks whether engineering investment is going to the right goals or product areas, where to invest more or less, or needs a roadmap-versus-reality, planning-cycle, quarterly allocation, or post-ship portfolio review. Not for choosing one builder's next task or designing an experime…
- usage-brief: Use when a builder wants to understand how much a product area is actually used today, and whether the PR or feature they are working on has potential to grow that usage, backed by real Pendo numbers. It leads with current usage, then reads the growth potential and the numbers that would show it w…
- 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. Backs findings with Novus product analytics when the Novus MC…
- 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-bri…
- 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 sele…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- novus: transport: streamable-http; url: https://novus-api.pendo.io/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.