# momentic-result-classification

Reads failed Momentic runs through MCP, pinpoints the step where the run first went wrong, explains why, and files the verdict under a category.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 68500 installs · ★ 16
- Author: momentic-ai
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/momentic-ai/skills/tree/HEAD/skills/momentic-result-classification/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/momentic-result-classification

## What it does

This skill wires the agent to Momentic's MCP tools. It pulls run metadata, a single step result with before and after screenshots, the trace, plus a snapshot of the test steps. From there it hunts for the moment the page state first diverged, instead of settling on the last assertion that blew up or the locator that went missing.

The investigation order is spelled out: current run first, then repeated module invocations inside that same run, and only after that older runs for comparison. Screenshots are treated as the primary record of page state; trace and DOM exist to explain why the picture changed. A container that passed while a child step failed counts as a partial failure until its closing screenshot gets checked. Vague causes like an unreliable setup do not pass — the skill wants the broken postcondition named outright.

Momentic itself is an end-to-end framework: tests are YAML steps that mix natural-language checks with Playwright actions. Run data lands in a `test-results` folder holding `metadata.json` and a zip per run. You need the Momentic MCP server reachable. The final verdict goes back through `momentic_submit_result_classification`, so the category ends up in the run data rather than staying in the chat.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add momentic-ai/skills --skill momentic-result-classification -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/momentic-result-classification/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/momentic-result-classification/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add momentic-ai/skills --skill momentic-result-classification -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/momentic-result-classification/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add momentic-ai/skills --skill momentic-result-classification -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/momentic-result-classification/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install momentic-ai/skills momentic-result-classification
```

2. **Manually: put the files in place**
- File: `.github/skills/momentic-result-classification/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add momentic-ai/skills --skill momentic-result-classification -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/momentic-ai/skills --path skills/momentic-result-classification
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/momentic-result-classification/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add momentic-ai/skills --skill momentic-result-classification -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/momentic-ai/skills/tree/HEAD/skills/momentic-result-classification/SKILL.md

## When to use it
- locate the earliest step where a run left a good state
- explain a failure at action level, not at the final assertion
- bucket a failure into a category and persist the verdict
- compare the current run against earlier runs on the same git branch
- tell a real container failure from a recovery that masked it

## Example prompts
- Work out where this run first broke and explain the root cause
- Classify this failure and submit the result to Momentic
- Compare this run with previous ones on the same branch — is the test flaky?

## Similar
- [improve-codebase-architecture](https://affpapa.org/en/nevibecode/skills/improve-codebase-architecture.md) — skill · 1163035 installs
- [design-taste-frontend](https://affpapa.org/en/nevibecode/skills/design-taste-frontend.md) — skill · 678700 installs
- [tdd](https://affpapa.org/en/nevibecode/skills/tdd.md) — skill · 1141062 installs
- [skill-creator](https://affpapa.org/en/nevibecode/skills/skill-creator.md) — skill · 414180 installs
- [agent-browser](https://affpapa.org/en/nevibecode/skills/vercel-labs-agent-browser.md) — skill · 1200000 installs
- [prototype](https://affpapa.org/en/nevibecode/skills/prototype.md) — skill · 986201 installs

From the same set: [momentic-ai/skills](https://affpapa.org/en/nevibecode/by/momentic-ai/skills.md) — 5 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md