Run any Skill in Manus with one click

vestige-context

Stars5

Forks0

UpdatedMay 1, 2026 at 20:28

Render the project's Vestige context pack — summary, recent decisions, open questions, recent activity — as a budget-bounded brief. Use at session start, before unfamiliar work, after a long pause, or when the user says "what's the state of this project?", "where are we?", "catch me up", "what have we decided?", "what's outstanding?", "give me the rundown". Returns a JSON envelope with `summary`, `decisions[]`, `open_questions[]`, `recent[]`. Token budget defaults to 1200 — pass `--budget-tokens` to adjust.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

conorluddy

conorluddy/Vestige

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

3 files

SKILL.md

readonly

name

vestige-context

description

Get the project context pack

Pull the durable Vestige memory an agent should read before doing serious work in this project. Same shape MCP tooling exposes via vestige_get_project_context.

When to fire

Session start. First time you're working on this project today, fire this once.
Cold start on unfamiliar code. About to refactor a module you haven't touched? Pull the pack first.
User explicitly asks. "What's the state?", "remind me where we are", "summarise this project for me".
Before a non-trivial decision. If you're about to commit to architecture, the pack tells you what you're already committed to.

Tie-breaker vs vestige-recall: the pack is broad (project-wide). Recall is narrow (one query). If you have a specific question, use recall — it's cheaper.

How to invoke

vestige context --json

--budget-tokens <n> (default 1200): caps the total pack size. Lower it (300–500) when context is tight; raise it (2400+) for a deep dive.
--per-section <n> (default 8): caps each list section.
--json (recommended for agents): structured envelope. Skip for human-readable markdown.

After invocation

The JSON envelope:

{
  "project_name": "…",
  "summary": { "id": "mem_…", "one_liner": "…", "available_depths": […] } | null,
  "decisions": [{ "id": "mem_…", "one_liner": "…", "score": …, "type": "decision" }, …],
  "open_questions": [ … ],
  "recent": [ … ],
  "warnings": []
}

For any card whose one_liner isn't enough, use vestige-show <id> to expand at higher fidelity. Cite handles (mem_…) when you reference a finding.

Idempotence & dedup

Read-only — calling repeatedly is safe and cheap, but pointless. Skip if:

You already pulled the pack this session and nothing has changed.
The user just asked a narrow question — don't pull the whole pack to answer "what's our SQLite version?", use vestige-recall "sqlite" instead.

More from this repository

same repository

vestige-scan-sessions

conorluddy/Vestige

Mine recent local coding-agent transcripts for memories worth keeping, using the `vestige_scan_sessions` MCP tool. Fire at session start (to catch up on what happened in prior sessions), when the user says "scan my sessions", "what did we work on recently?", "catch up from my transcripts", "ingest recent sessions", "mine my history", or when picking up a project after a pause. The tool hands you redacted, cursor-advanced turns from this project's Claude Code and Codex transcripts; you extract decisions/notes/preferences/questions inline and file each via `vestige_propose_candidate`. Opt-in — requires `[mcp] allow_scan_sessions = true` in `.vestige/config.toml`. Candidates land in the assimilation inbox for human review, never as durable memories directly.

2026-06-145

vestige-sources

conorluddy/Vestige

Use this skill when you need the raw source receipts for a memory or candidate — the typed evidence rows, not the narrative walk. Fire when the user says "what sources back mem_X?", "show me the source receipts", "list the sources for mem_X", or "filter sources by kind agent_session". Use `vestige-why` when you want the full provenance narrative including events; use this skill when you want the tabular source index only.

2026-05-085

vestige-trace-list

conorluddy/Vestige

Use this skill when you want to audit what queries the agent or CLI has run against project memory. Fire when the user says "what queries did the agent run?", "show recent trace events", "did anyone search for X recently?", or "list traces by caller mcp". Every vestige search, recall, expand, and context call writes a query_events row automatically — this skill surfaces them. Use vestige-trace-show to expand a single trace.

2026-05-085

vestige-trace-replay

conorluddy/Vestige

Use this skill to re-run a stored trace against the current memory store and diff the results against the original — answering "would the agent get the same answer today?". Fire when the user says "re-run trace_X", "replay that search", "diff trace_X against current state", or "did the answers drift?". Read-only: writes a NEW query_events row tagged with replay_of; never mutates the original trace or any memory. provider_match=false flags embedding drift.

2026-05-085

vestige-trace-show

conorluddy/Vestige

Use this skill when you want to expand a specific trace to its full detail — the query text, mode requested vs resolved, provider, result IDs, and scores. Fire when the user says "expand trace_X", "show me what trace_X returned", or "what did that search find?". Use vestige-trace-list first to find the trace_id, then this skill to inspect one in full.

2026-05-085

vestige-why

conorluddy/Vestige

Use this skill when you want to know where a memory came from, need to explain its provenance, or must audit what was captured and when. Fire when the user says "where did this come from?", "explain that memory", "why do we have mem_X?", "show provenance for X", "what's the source of mem_X?", or "trace this memory back". Works for both memories and pre-approval candidates. Soft-deleted memories are included — provenance is always inspectable.

2026-05-085

name

vestige-context

description

Get the project context pack

Pull the durable Vestige memory an agent should read before doing serious work in this project. Same shape MCP tooling exposes via vestige_get_project_context.

When to fire

Session start. First time you're working on this project today, fire this once.
Cold start on unfamiliar code. About to refactor a module you haven't touched? Pull the pack first.
User explicitly asks. "What's the state?", "remind me where we are", "summarise this project for me".
Before a non-trivial decision. If you're about to commit to architecture, the pack tells you what you're already committed to.

Tie-breaker vs vestige-recall: the pack is broad (project-wide). Recall is narrow (one query). If you have a specific question, use recall — it's cheaper.

How to invoke

vestige context --json

--budget-tokens <n> (default 1200): caps the total pack size. Lower it (300–500) when context is tight; raise it (2400+) for a deep dive.
--per-section <n> (default 8): caps each list section.
--json (recommended for agents): structured envelope. Skip for human-readable markdown.

After invocation

The JSON envelope:

{
  "project_name": "…",
  "summary": { "id": "mem_…", "one_liner": "…", "available_depths": […] } | null,
  "decisions": [{ "id": "mem_…", "one_liner": "…", "score": …, "type": "decision" }, …],
  "open_questions": [ … ],
  "recent": [ … ],
  "warnings": []
}

For any card whose one_liner isn't enough, use vestige-show <id> to expand at higher fidelity. Cite handles (mem_…) when you reference a finding.

Idempotence & dedup

Read-only — calling repeatedly is safe and cheap, but pointless. Skip if:

You already pulled the pack this session and nothing has changed.
The user just asked a narrow question — don't pull the whole pack to answer "what's our SQLite version?", use vestige-recall "sqlite" instead.