aura-bench-local-iteration

Automate local memory-bench iterations for Cursor Cloud Agents against Neon DB.

1|4|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/AuraHQ-ai/aura --skill aura-bench-local-iteration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aura-bench-local-iteration
Source: https://github.com/AuraHQ-ai/aura/tree/main/.cursor/skills/aura-bench-local-iteration
Command: npx skills add https://github.com/AuraHQ-ai/aura --skill aura-bench-local-iteration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast local memory-bench iteration loop for Cursor Cloud Agents to quickly validate changes against the Neon DB in a disposable local workspace.

Core Features & Use Cases

  • Deterministic mid-size LongMemEval runs against the agent's own Neon DB to surface real memory behavior.
  • Persistent local workspace (bench-local-<key>) that can be inspected after runs and re-used for iteration.
  • Supports triage, inspection, and re-run workflows to iterate on code and prompts faster than CI.

Quick Start

Run a mid-size memory bench in a persistent local workspace and inspect the results to guide development.

Frequently Asked Questions about aura-bench-local-iteration

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

FAQPage Schema
How do I run local memory-bench iterations against a Neon DB?

Local memory-bench iterations run deterministically against your Neon DB by utilizing a persistent local workspace to validate memory changes quickly. This disposable workspace enforces mid-size runs to surface real memory behavior without relying on slower CI pipelines.

Can I inspect stored memories after a LongMemEval run?

Yes, you can inspect stored memories after a LongMemEval run. The process uses a persistent local workspace that remains available post-execution, enabling detailed triage and re-run workflows to guide iterative development and debugging.

What is the best way to debug long memory evaluation loops for cloud agents?

The best way to debug long memory evaluation loops is using a persistent local workspace designed for triage and inspection. It supports background execution and re-run workflows, allowing faster iteration on code and prompts than standard CI environments.

Does this local debugging approach support background execution?

Yes, local debugging supports background execution for memory-bench iterations. This allows you to run deterministic mid-size evaluations against your Neon DB while continuing other development tasks in your persistent local workspace.

Why use a persistent local workspace instead of CI for memory validation?

A persistent local workspace enables faster memory validation by allowing direct inspection, triage, and re-runs of stored memories. Unlike CI, the workspace remains intact between iterations, accelerating the debug and prompt tuning loop significantly.