saving-workspace-context

Q: How do I install saving-workspace-context?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill saving-workspace-context in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/saving-workspace-context/ (personal) or .claude/skills/saving-workspace-context/ (project).

by spencerpaulyProductivity & Automation

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

Installs: 500
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill saving-workspace-context

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads saving-workspace-context automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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:

Check for a context/ directory — read any files relevant to the current task
Check for a product/project context file (e.g. .agents/product-marketing-context.md, PROJECT.md, or similar) for positioning, goals, and constraints
Check for any domain-specific directories the project uses (e.g. companies/, docs/, research/)
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`)

# {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:

# {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

FAQ

What does the saving-workspace-context skill do?

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

How do I install saving-workspace-context?

Run npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill saving-workspace-context in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/saving-workspace-context/ (personal) or .claude/skills/saving-workspace-context/ (project).

Which AI agents can use saving-workspace-context?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is saving-workspace-context safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains saving-workspace-context?

It is published by spencerpauly in spencerpauly/awesome-cursor-skills. It has 500 recorded installs.