nanocoai/nanoclaw / .claude/skills/add-cursor
add-cursor
FlaggedUse Cursor (local Agent SDK) as a full agent provider — planning, tool orchestration, MCP tools, session resume — alongside or instead of Claude. Cursor-account sign-in or API key, held by the credential gateway. Per-group via `ncl groups config update --provider cursor`. Distinct from using Cursor as a cloud agent (those run on Cursor VMs and are not this provider).
payload/container/agent-runner/src/providers/cursor.conformance.test.ts
View on GitHub/**
* Runtime-contract conformance for the cursor payload, run through the core's
* own reusable suite (provider-contracts/testing/conformance.ts): registered
* contract identity, factory construction, contract shape, and live
* configuration probes.
*
* The suite exists only on the contract core. On the standalone providers
* branch and on a pre-contract install the file is absent, so this skips
* there. The contract modules are loaded dynamically for the same reason: a
* static import would fail to resolve where the core does not carry them.
*/
import fs from 'fs';
import { describe, it } from 'bun:test';
const CONFORMANCE_SUITE = '../provider-contracts/testing/conformance.ts';
const hasContractCore = fs.existsSync(new URL(CONFORMANCE_SUITE, import.meta.url));
if (hasContractCore) {
await import('./index.js');
await import('../provider-contracts/index.js');
const { cursorRuntimeContract } = await import('../provider-contracts/cursor.js');
const { defineProviderConformance } = await import('../provider-contracts/testing/conformance.js');
// The default fixtures suffice: the inference capability answers `model`,
// and the MCP capability answers the server map.
defineProviderConformance('cursor', cursorRuntimeContract);
} else {
describe.skip('runtime provider contract: cursor', () => {
it('needs the contract core', () => {});
});
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |