skills.rest
MaiconGambini
MaiconGambiniCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

harness-cursor-parity

Validates Cursor alignment with the OpenCode harness without duplicating goal state or exposing MCP secrets.

Updated Jul 29, 2026
Search Tags:#configuration#mcp#secrets#opencode#cursor#harness#parity
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-cursor-parity-maicongambini
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-cursor-parity
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-cursor-parity
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-cursor-parity-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running the OpenCode harness alongside Cursor risk configuration drift: duplicated /goal state, leaked MCP secrets, and agents added before permission profiles exist. This Skill provides a checklist to keep Cursor as a safe secondary execution surface while OpenCode remains the source of truth. ## Core Features & Use Cases - Parity Checks: Verifies that .cursor/skills/ contains only minimal portable harness skills and that no duplicate /goal state exists. - Secret Hygiene: Confirms the Cursor MCP inventory does not print secret values. - Agent Gating: Ensures Cursor agents are not added until permission profiles exist. - Use Case: Before onboarding a teammate who uses Cursor, run this check to confirm handoff and status files are readable by both OpenCode and Cursor without leaking credentials. ## Quick Start Check whether my Cursor configuration stays aligned with the OpenCode harness without duplicating goal state or exposing MCP secrets.

Frequently Asked Questions about harness-cursor-parity

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

FAQPage Schema
How do I keep Cursor aligned with the OpenCode harness?▼

Keep OpenCode as the source of truth for /goal, PREVC, evidence, and handoff, and treat Cursor as a secondary execution surface. Verify .cursor/skills holds only minimal portable harness skills and that handoff/status files are readable by both tools.

How do I check Cursor MCP configuration for leaked secrets?▼

Review the Cursor MCP inventory and confirm it does not print secret values in plaintext. The parity check flags any MCP configuration where credentials would be exposed during inspection.

When can I add agents to Cursor in an OpenCode harness setup?▼

Add Cursor agents only after permission profiles exist. Adding agents before permission profiles are defined breaks the parity contract and can bypass the harness's access controls.

Should Cursor duplicate the /goal state from OpenCode?▼

No. OpenCode remains the single source of truth for /goal state, PREVC phases, evidence, and handoff. Cursor should read shared handoff and status artifacts rather than maintaining its own copy of goal state.

What are the limitations of using Cursor with the OpenCode harness?▼

Cursor is a secondary execution surface, not a replacement runtime. It cannot own PREVC state or evidence tracking, and its skills directory must stay minimal and portable to avoid configuration drift.

Related Skills

Explore More Software Engineering Skills→
alexmeckesalexmeckes
26

godot-interactive

Manage persistent Godot 4.x editor sessions for scene inspection and live node edits.

Community
Advanced
NEXUZ-SYSNEXUZ-SYS
1

using-devflow

Orchestrate PREVC planning, review, execution, validation, and confirmation workflows.

Official
Advanced
spigellspigell

k8s-security

Audit Kubernetes RBAC permissions, policy compliance, secrets access, and network isolation.

Community
Advanced
TrebuchetDynamicsTrebuchetDynamics
9

gormes-openclaw-parity

Classify OpenClaw-only behavior against Hermes parity gaps for Gormes adoption decisions.

Official
Intermediate