agentleFS
EtanHeyEtanHey/golems/skills/golem-powers/cursor-workflows/SKILL.md

cursor-workflows

Skill0 starsChanged 15 days agoApache-2.0View on GitHub

Run Cursor-workflow gather/recon via AutoCursor primitives. Triggers: cursor-workflow, autocursor gather, cursor gather.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill when the request asks for a cursor-workflow, autocursor gather, or cursor gather: read-heavy reconnaissance that can run …

    line 8
  2. Very specific:

    All reasoning and search in these workflows must stay behind the NO-API law: use the cursor-agent subscription path only, with no …

    line 28
  3. Very specific:

    If one of these workflows exhausts the shared Cursor quota through its own dispatch, report that dispatch as the cause.

    line 30
  4. Distinctive:

    Run the fuller example with:

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Cursor Workflows

Use this skill when the request asks for a cursor-workflow, autocursor gather, or cursor gather: read-heavy reconnaissance that can run through headless cursor-agent instead of spending Claude orchestration tokens.

The implementation lives in lib/autocursor.py and is intentionally portable: no golems imports, no worktree mutation, and no v0 edit flows. Worktree isolation is deferred until mutating workflows exist.

Primitives

  • agent(prompt, *, schema=None, label=None, timeout=900, resume=None, model=None) runs one headless cursor-agent -p --force --approve-mcps --output-format json <prompt>. Fleet canon #1 owns Cursor model selection. The implementation still exposes the legacy model parameter; a non-None value is a live out-of-scope defect at lib/autocursor.py:58-59 to remove in a separate lane, not an escape hatch. With schema, AutoCursor appends a JSON instruction, validates harness-side, retries malformed output, and records raw NDJSON logs to disk.
  • parallel(thunks, *, concurrency=8) runs a ThreadPoolExecutor barrier. Failed thunks return None. MAX_CHILDREN caps local concurrency.
  • pipeline(items, *stages) flows each item through stages independently. A failed item becomes None.
  • phase(title) prints an observability marker.
  • loop_until_dry(round_fn, *, dry_rounds=2, max_rounds=10) keeps gathering until consecutive rounds add no new stable-keyed findings.

Analyze

analyze/analyze.py takes gathered findings, clusters/ranks/deduplicates them, then produces a structured synthesis through autocursor.agent(schema=...). This workflow is pure local analysis: no web, no search backend, and no external API.

Quick-Deep-Research

research/research.py is the subscription-only research workflow from SPEC §8: cursor-native web search (NO exa, NO paid API) builds a web graph of sources, entities, and claims; cross-reference/verify flags conflicts instead of silently merging them; synthesis emits a cited report. Treat it as a cheaper, thorough+fast alternative to Gemini Deep Research, not as SOTA deep research.

All reasoning and search in these workflows must stay behind the NO-API law: use the cursor-agent subscription path only, with no Anthropic/OpenAI/Gemini/Exa keys or paid external APIs.

If one of these workflows exhausts the shared Cursor quota through its own dispatch, report that dispatch as the cause; never present the resulting resource_exhausted state as an external finding.

Example

from lib.autocursor import agent, parallel

schema = {
    "type": "object",
    "required": ["file", "findings"],
    "properties": {
        "file": {"type": "string"},
        "findings": {"type": "array"},
    },
}

results = parallel([
    lambda path=path: agent(f"Inspect {path} for TODOs and risks", schema=schema, label=path)
    for path in ["README.md", "AGENTS.md"]
])

Run the fuller example with:

python3 skills/golem-powers/cursor-workflows/scripts/example-gather.py README.md AGENTS.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.