← KnowzCodeCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to KnowzCode
Snapshot Sep 30, 2026 · 23:16 UTC · version 1.0.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Check KnowzCode project health, active work, and pending captures. Use for status, setup verification, or troubleshooting. Knowz MCP is optional.",
"included_files": [],
"name": "status",
"skill_md_contents": "---\nname: status\ndescription: \"Check KnowzCode project health, active work, and pending captures. Use for status, setup verification, or troubleshooting. Knowz MCP is optional.\"\n---\n\n# /knowzcode:status — Project status\n\nReport local KnowzCode health without starting or resuming work. Knowz MCP is optional and never blocks this report.\n\n## Instructions\n\n1. Check whether `knowzcode/` exists and whether the core files are present.\n2. Inspect `knowzcode/knowzcode_tracker.md` for `[WIP]`, `[VERIFIED]`, and planned work.\n3. Count active and completed WorkGroups in `knowzcode/workgroups/` if that directory exists.\n4. Count queued items in the project-root `knowz-pending.md` when present. If legacy `knowzcode/pending_captures.md` exists, report it separately as migration input; do not count it as a second active queue.\n5. If Knowz MCP is available, call `mcp__knowz__list_vaults` with `includeStats: true` and report vault availability. If not, report that Knowz enhancement is unavailable and the local workflow still works. Do not tell the user to paste an API key or run `/knowz setup <api-key>`.\n6. End with one practical action: initialize, continue work, flush captures, or (only if they want vaults) open Grok Bot Plugins / Cursor Marketplace → search **Knowz** → **Add** → **Authorize**.\n\n## Output format\n\n```text\n## KnowzCode Status\n\nFramework: {Initialized | Not initialized}\n Core files: {N}/4 present (loop, tracker, project, architecture)\nTracker: {W} WIP, {V} verified, {P} planned\nWorkGroups: {A} active, {C} completed\nPending captures: {Q} queued\nMCP & vaults: {Connected — N vault(s) | Not connected (optional — workflow still works)}\n\nNext: {one concrete suggested action}\n```\n\nOmit non-applicable lines. Keep secrets out of the report.\n"
}SHA-256 of public snapshot: d8cf165b179d4e3f72f1ca3e3929d4fb81ecbe01d0f83a2779eaedc432fc0ca3