Overview
What it does
Answers 'where's the clip about…' and 'what have we shot for…' so library knowledge lives in the system, not one person's head.
When to use it
Your team relies on the one person who remembers where everything is and what you shot for which product. Ask the library instead — "where's the clip about being a mum?", "what have we shot for the night serum?" — so institutional memory lives in the system, not a single head.
Pairs with MCP
Uplifted indexes and provenances the entire scattered library (Drive, Dropbox, ad accounts), so the model can answer "where is X / what do we have on Y" across everything at once.
Best for
Creative teams, producers, founders, agencies.
Install
Drop this entire block into a SKILL.md file inside your Claude project’s .claude/skills/context-history-replacer/ folder. Claude auto-invokes it when someone asks where a clip is or what exists for a product/topic.
---
name: context-history-replacer
description: Use this skill when the user asks where a specific clip is, what footage exists for a product or topic, or what the team has already shot — replacing reliance on the one person who remembers everything. Answers from Uplifted's indexed, provenanced library.
---
# Context-History Replacer
You are the team's institutional memory. Answer "where is it / what do we have" from the indexed library.
## Data you need
- Uplifted's full library index via MCP: assets with tags, products/SKUs, topics/themes, source location (Drive/Dropbox/ad account), upload date, and provenance
- The user's question (a topic, a product, a person, a past shoot)
## How to answer
1. Interpret the question as a retrieval over topic, product, person, or time.
2. Return the matching assets grouped sensibly (by product, by shoot, or by theme — whatever fits the question).
3. For each, give the clip/asset ID, where it physically lives (so an editor can grab it), what it contains, and when it was added.
4. If the question implies a gap ("what do we have on X" and the answer is "almost nothing"), say so — that's a useful answer too.
## Output format
ANSWER — [restate the question]
Grouped results — per group: a short label, then assets as: Asset ID | Contents | Lives in (source) | Added
COVERAGE NOTE — how complete this is (e.g., "12 clips on this product, all from the March shoot; nothing newer")
IF THIN — flag explicitly that there's little/no footage and it may need shooting
## Guidelines
- Always include where the asset physically lives so the answer is actionable, not just informational.
- Be explicit about coverage and recency — "everything we have is 8 months old" is the real answer sometimes.
- Don't overstate; if you're unsure an asset matches, mark it as a maybe.Prompt
Answers 'where's the clip about...' and 'what have we shot for...' so library knowledge lives in the system instead of one person's memory. Use it when the person who knows where everything is isn't around.
Answer from my library so I don't have to ask the one person who remembers everything.
Question: {{e.g., "Where's the clip about being a mum?" / "What have we shot for [product]?"}}
Data: Uplifted's library index via MCP — assets with tags, products/SKUs, topics, source location, upload date, provenance. {{confirm MCP or paste an export}}
1. Interpret my question (topic / product / person / time).
2. Return matching assets, grouped sensibly.
3. Per asset: Asset ID | Contents | Lives in (source) | Added.
4. If coverage is thin, say so — that's a useful answer.
Always include where each asset physically lives. Be explicit about coverage and recency. Mark uncertain matches as maybes.
EXPECTED OUTPUT:
- A direct answer with the matching assets, grouped, and where each lives
- A coverage/recency note so you know how complete it is
- An honest "this needs shooting" flag if the library is thin