context-status

Reports project context stack readiness including agent rules, Memory graph, telemetry, and Wiki status.

20|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/reddb-io/red-skills --skill context-status-reddb-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-status
Source: https://github.com/reddb-io/red-skills/tree/main/plugins/memory/skills/core/context-status
Command: npx skills add https://github.com/reddb-io/red-skills --skill context-status-reddb-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before starting a large task or self-improvement loop, agents need to know whether the project's context stack (agent rules, domain docs, ADRs, Memory graph, telemetry, and LLM Wiki) is actually ready. This Skill provides a read-only healthcheck that reports the full posture without mutating anything. ## Core Features & Use Cases - Read-only status report: Runs bootstrap.mjs status context to report committed context files, Memory init-chain state, graph store presence and freshness, hooks, Skill telemetry, and Wiki readiness. - Readiness score and recommendations: Produces a simple score of ready checks plus concrete setup recommendations, without ever triggering initialization or mutations. - Use Case: Before launching an /afk wave or onboarding a new agent, run the report to confirm CLAUDE.md, ADRs, the Memory graph, and .red/wiki/ are in place, then hand the recommendations to the user or calling workflow to decide on setup actions. ## Quick Start Ask the agent to run the context-status report and summarize the readiness score and recommendations before starting the next large task.

Frequently Asked Questions about context-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my project's agent context is ready before a large task?▼

Run the context-status report via `node bootstrap.mjs status context` to see committed context files, Memory mode, graph freshness, telemetry, and Wiki readiness. It returns a readiness score plus concrete recommendations, all without changing anything.

What does the context status report check in a repository?▼

The report checks CLAUDE.md/AGENTS.md, .red/CONTEXT.md, .red/CONTEXT-MAP.md, .red/adr/*.md, Memory init-chain state, graph store presence and freshness, hooks, Skill telemetry, and whether .red/agents/wiki.md and .red/wiki/ exist.

Can I get the context status output as JSON for automation?▼

Yes, append the --json flag to the status context command to emit machine-readable JSON. This is intended for automation pipelines that need to gate workflows on context readiness.

Does the context status check modify or initialize anything?▼

No, the diagnostic is strictly read-only. It never initializes Memory, ingests a graph, creates Wiki files, or enables hooks and telemetry; it only reports recommendations for the user or calling workflow to act on.

What should I do when the context readiness score is low?▼

Treat a low score as a signal to gather context, not a failure. Follow the listed recommendations, such as running `memory ingest . --root .` for a stale graph, and pair with the dev plugin's /context command for the full loop.