Skip to content
Skills Library
Documents & office · Review & audit

refresh-context

/refresh-context

Review and refresh an existing personal-context.md or company-context.md — check what has gone stale, fill gaps against the current template, and update the file. Use when the user says "refresh my context", "review my context", "is my context still up to date", "my context is stale", or after a change in role, offer or positioning. Complements personal-context and company-context, which build a file from scratch.

Licence
MIT
Last repository change
16.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Review and refresh an existing personal-context.md or company-context.md — check what has gone stale, fill gaps against the current template, and update the file. Use when the user says "refresh my context", "review my context", "is my context still up to date", "my context is stale", or after a change in role, offer or positioning. Complements personal-context and company-context, which build a file from scratch.

Triggers from the description

refresh my contextreview my contextis my context still up to datemy context is stale
Original author description

Review and refresh an existing personal-context.md or company-context.md — check what has gone stale, fill gaps against the current template, and update the file. Use when the user says "refresh my context", "review my context", "is my context still up to date", "my context is stale", or after a change in role, offer or positioning. Complements personal-context and company-context, which build a file from scratch.

How it works

  1. Which skill to use
  2. How to run it
  3. Section reference
  4. Notes
Original SKILL.md headings · 44 lines, 498 words
SKILL.md preview
---
name: refresh-context
description: Review and refresh an existing personal-context.md or company-context.md — check what has gone stale, fill gaps against the current template, and update the file. Use when the user says "refresh my context", "review my context", "is my context still up to date", "my context is stale", or after a change in role, offer or positioning. Complements personal-context and company-context, which build a file from scratch.
---

# refresh-context — keep your context files current

Your job is to review a context file that **already exists** and bring it up to date — a maintenance pass, not a rebuild. A stale context is worse than none: it makes AI confidently wrong in your name.

## Which skill to use

- **No file yet** → use the `personal-context` or `company-context` skill to build one.
- **File exists, needs a check-up** → this skill.

If the user asks to "build" and a file already exists, the build skills handle that too — this skill is for an explicit *review / refresh / audit* pass.

## How to run it

1. **Find the files.** Look in the current directory for `personal-context.md` and `company-context.md`. If neither exists, say so and point to the build skills. If both exist, refresh them one at a time (ask which first).

2. **Read and date-check.** Read the file. Find the `_Last updated: YYYY-MM_` line and say how old it is in plain terms ("this was last updated 5 months ago"). Give a two-line summary of what the file currently says so the user has it in mind.

3. **Go section by section — probe, don't just ask "what changed?"** For each section, read it back in one line and check:
   - Is this **still true**? Roles, offers, clients and positioning drift over time.
   - Is anything **aspirational-but-not-real**, or no longer how they actually work?
   - Anything to **cut** — an old side project, a client you no longer serve, a goal you hit or dropped?
   Ask them to confirm, correct, or cut. Keep it a quick pass, not a full re-interview.

4. **Check for gaps against the template.** Compare the file's sections to the reference list below. If a useful section is missing, offer to add it — don't force it.

5. **Rewrite and report.** Apply the changes, keep the user's own words and tone, refresh the `_Last updated:_` line to the current month, and keep the footer line intact. Then show a short summary of what changed, e.g. *"updated: offer, clients · added: goals · removed: old side project."*

## Section reference

Refresh against the same structure the build skills use (match whatever language the file is in):

- **personal-context** — Identity · Background · Day to day · How I work · Communication & voice · Goals · How AI should help me · Anything else
- **company-context** — The company · Offer · Customers · Personas · Positioning & messaging · Voice · Team · Client-facing know-how · Anything else

Polish files use the translated headings (e.g. `Tożsamość`, `Oferta`) — keep the file's existing headings, don't switch languages.

## Notes

- Work **in the file's language**.
- **Never overwrite without confirmation** — show what you'll change first, then write.
- Respect privacy — don't add sensitive data the user didn't offer.
- If the directory is a shared or git-tracked repo, remind them not to commit personal details by accident.

Versions

The database has no other skills named refresh-context.

Database snapshot: 13.11.2026 · package version 23abd81de39a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100company-context
    Interview the user to build or update a reusable company context file for AI tools — what the company does, its offer, clients, personas, positioning, voice, and the questions clients ask most. Use when the user says "build our company context", "create company context", "set up…
  • 100personal-context
    Interview the user to build or update a reusable "about me" context file for AI tools — who they are, their role and background, how they work, and how they want AI to help. Use when the user says "build my personal context", "create my about-me context", "set up my AI context",…
  • 86update-context
    Update the current directory's .agentcontext file with what happened in this conversation (work completed, work still to do) and prune anything that's gone stale. Works in any project. Use when the user says "update context", "save this to context", "update the agent context".
  • 100agents-md-generator
    Generate or update an AGENTS.md / CLAUDE.md / context file for a repo. Use when the user says "set up CLAUDE.md", "generate AGENTS.md", "write a context file for this repo", "document this codebase for AI agents", or when a fresh repo has none. Also use when an existing context…
  • 100refresh
    Detect drift in .arkhe/roadmap/ context files and regenerate them from the current codebase state. Scaffolds context directory if missing. Use when user runs /roadmap:refresh, mentions "refresh context", "update context", "init roadmap", "stale context", or "scaffold roadmap".
  • 90context-anchor
    Interviews the team once and writes a single GTM_CONTEXT.md (ICP, positioning, voice, proof, competitors) that every other GTM skill reads, then scores how fresh and complete it is. Use when: set up gtm context, company context file, shared positioning file, brand context, icp…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.