From 8l-cq
Display cq knowledge store statistics — tier counts (local/private/public), domains, recent local additions, and confidence distribution.
npx claudepluginhub onezero1ai/8th-layer-marketplace --plugin 8l-cq# /cq:status Display a summary of the cq knowledge store. ## Instructions 1. Call the `status` MCP tool (no arguments needed). 2. Format the response as a readable summary using the sections below. ## Output Format Present the results using this structure: The `tier_counts` field contains the tier breakdown. Display all tiers present in the response. Omit tiers with a count of 0. The `recent` field reflects the local store only. When a remote is configured and reachable, units proposed via `Client.Propose` go directly to the remote and do not appear here. If `recent` is empty, rend...
/statusDisplay Conductor project status including overall progress, active tracks summary, and next actions. Optional [track-id] [--detailed] for per-track task details and blockers.
/statusDisplays compact planning status from task_plan.md: current phase and progress, phase list with icons, error count, and planning file checks.
/statusShows active and recent Codex jobs for this repository in a compact Markdown table, including review-gate status. Pass job ID for full details; supports --wait, --timeout-ms, --all.
/statusDisplays current design system state from .interface-design/system.md including direction, foundation, depth, tokens, patterns, and last updated time. Suggests setup options if no system found.
/statusChecks current session status and measures goal drift to assess alignment and progress in the conversation.
/statusDisplays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.
Share bugs, ideas, or general feedback.
Display a summary of the cq knowledge store.
status MCP tool (no arguments needed).Present the results using this structure:
## cq Knowledge Store
### Tier Counts
local: {count} | private: {count} | public: {count}
*local* = on this machine only; *private* = shared with everyone who can reach the same `CQ_ADDR`; *public* = open commons (not yet available).
### Domains
{domain}: {count} | {domain}: {count} | ...
### Recent Local Additions
- {id}: "{summary}" ({relative time})
- ...
### Confidence Distribution
■ 0.7-1.0: {count} units
■ 0.5-0.7: {count} units
■ 0.3-0.5: {count} units
■ 0.0-0.3: {count} units
The tier_counts field contains the tier breakdown. Display all tiers present in the response. Omit tiers with a count of 0.
The recent field reflects the local store only. When a remote is configured and reachable, units proposed via Client.Propose go directly to the remote and do not appear here. If recent is empty, render the section as (no recent local additions) so users understand the scope.
If the response includes promoted_to_remote, add this line after the total count:
Promoted {promoted_to_remote} knowledge units to the remote store at startup.
When all tier counts are 0 (or tier_counts is absent):
promoted_to_remote: Show the header, tier counts line, and promotion line. Omit Domains, Recent Local Additions, and Confidence sections (there is no data to display).promoted_to_remote: Display only: "The cq store is empty. Knowledge units are added via propose or the /cq:reflect command."