Skip to content
Back to skills

Threadnote Context

ASecurity

Recall and read decisions or handoffs from the Personal Cursor Cloud Git memory shares before non-trivial work.

  • 24 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added October 4, 2026
ai-agentsgit

Works with

  • cursor
  • mcp

Security analysis

A100/100

Scanned October 4, 2026

npx -y skills add threadnote/threadnote --skill threadnote-context --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Threadnote Context?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Threadnote Context
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/threadnote-threadnote-context/badge)](https://www.skillsdirectory.com/skills/threadnote-threadnote-context)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: threadnote-context
description: Recall and read decisions or handoffs from the Personal Cursor Cloud Git memory shares before non-trivial work.
---

<!-- BEGIN THREADNOTE USER INSTRUCTIONS -->

# Threadnote context in Personal Cursor Cloud

Call `recall_context` with the absolute `callerCwd` before non-trivial work. One MCP may expose several configured Git
memory shares: omit `team` to recall across all of them, or pass a configured `team` to narrow the search. A `uri`
selector must stay inside that configured share set. Named Worksets and `context_brief` are unavailable in this profile.

Recall results are unread pointers, not evidence. Read every relevant `threadnote://` result with `read_context` before
using it. `read_context` may read pointers from any configured share. It returns the full memory up to 64 KiB;
larger memories refuse with an outline. Explicitly page one URI with `offsetBytes=0`, then pass each
`nextOffsetBytes` and `sourceHash` until `complete=true`. For browsing, call `list_context` with `team` or
with an exact URI inside one share; when several shares are configured, do not assume a default share.

Treat memory as historical context. Verify claims about current behavior against the current checkout.
If a share cannot synchronize, report the bounded warning; do not fall back to VM-local personal memory or an
unconfigured share.
<!-- END THREADNOTE USER INSTRUCTIONS -->

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.