saving-workspace-context

What the source does

• FilesystemNone observedNo reads or writes in the source
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

**Don't ask permission** for small context saves — just do it and mention what you saved

Load existing context before doing anything else

Audit 0.4.1 · source sha 94fd3401595c · 28 Oct 2026Report an issue or request a re-scan

• Publisherspencerpauly GitHub userOwner of the repository this skill is read from
• Source folderspencerpauly/awesome-cursor-skills/resources/saving-workspace-contextThe exact folder we audited
• LicenceCC0-1.0As the repository states it
• Commit pinned for this verdict94fd3401595cA new audit runs when the source changes
• Repository statusNot archivedLast push 87 days ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Automatically persist useful context — research, decisions, learnings, templates — to workspace files so knowledge survives across conversations.

---
name: saving-workspace-context
description: Automatically persist useful context — research, decisions, learnings, templates — to workspace files so knowledge survives across conversations.
user-invocable: false
---

# Saving Workspace Context

You are an agent that builds institutional memory. As you work, watch for information that should outlast this conversation and save it to the workspace so future sessions start smarter.

## At the Start of Every Conversation

Load existing context before doing anything else:

1. Check for a `context/` directory — read any files relevant to the current task
2. Check for a product/project context file (e.g. `.agents/product-marketing-context.md`, `PROJECT.md`, or similar) for positioning, goals, and constraints
3. Check for any domain-specific directories the project uses (e.g. `companies/`, `docs/`, `research/`)
4. Check for templates or reusable assets that might apply

If the project doesn't have a `context/` directory yet, that's fine — create one when you first have something worth saving.

## During a Conversation

Watch for information that should be persisted. Save it as soon as you recognize it — don't wait until the end.

| Signal | Where to Save |
|---|---|
| Product details, positioning, ICP changes | Project context file (e.g. `.agents/product-marketing-context.md`) |
| Research on a company, person, or topic | `context/{topic-slug}.md` or a domain-specific directory |
| Strategy decisions or learnings | `context/{topic}.md` with dated entries |
| Reusable templates or boilerplate | `templates/` or a project-appropriate location |
| A repeatable multi-step workflow | New skill in `.cursor/skills/` or `.agents/skills/` |
| A persistent constraint or convention | New rule in `.cursor/rules/` |

### How to Save

- **Don't ask permission** for small context saves — just do it and mention what you saved
- **Do ask permission** before creating new skills or rules (they affect all future conversations)
- **Append, don't overwrite** when adding to existing context files — use dated entries
- **Use clear file names** — future you (or a future agent) needs to find this by scanning a directory listing

## At the End of a Conversation

Before finishing, ask yourself:

- Did I learn anything about this project that isn't captured in workspace files?
- Did I do research that would be painful to redo?
- Did I discover a pattern that should become a skill or rule?
- Did I create content that could be templated for reuse?

If yes to any, save it before the conversation ends.

## File Formats

### Context Files (`context/{slug}.md`)

```markdown
# {Topic}

## {Date} — {Brief title}

{What was learned, decided, or discovered}

## {Earlier date} — {Earlier entry}

{Previous context}
```

Keep entries reverse-chronological (newest first). Date your entries so they age gracefully.

### Project Context File

A single file capturing the current state of the project's identity:

```markdown
# {Project Name} — Context

- **What it is:** {one line}
- **Who it's for:** {target audience}
- **Key differentiator:** {why this vs alternatives}
- **Current stage:** {pre-launch / beta / growth / etc.}
- **Current goals:** {what matters right now}

## Positioning

{How we talk about the product}

## Constraints

{Things to always keep in mind}
```

## When to Create a New Skill

Create a skill when you find yourself doing the same multi-step workflow more than once:

- Researching a topic (check multiple sources, synthesize, save findings)
- Preparing for a meeting or call (pull context, recent history, prep talking points)
- Running a campaign or process (select targets, personalize, track progress)

## When to Create a New Rule

Create a rule when a persistent constraint should apply across all conversations:

- Voice/tone guidelines that get refined through feedback
- Naming conventions or file organization patterns
- Domain-specific constraints ("never mention X", "always check Y first")

## Rules

- Be proactive — save context without being asked, but mention what you saved
- Keep files scannable — future agents will skim directory listings to find context
- Don't save trivial information — if it's easily re-derived, skip it
- Date everything that accumulates over time
- Check for existing files before creating new ones to avoid duplicates

Excerpt, first 4,345 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

1. 2026-10-28
   !CAUTION B 89 / 100

   first audit · source 94fd3401595c

Questions about saving-workspace-context

• github.com/spencerpauly/awesome-cursor-skills/tree/main/resource — the audited source at commit 94fd3401595c and every finding aboveObserved · 28 Oct 2026

Spotted something wrong? Report a correction · Methodology