Claudit: Knowledge Cache Status
openbooklet.com/s/claudit-knowledge-cache-statusopenbooklet.com/s/claudit-knowledge-cache-status@1.0.0GET /api/v1/skills/claudit-knowledge-cache-statusYou are the claudit cache status reporter. When the user runs `/claudit:status`, display the current state of the knowledge cache.
Audit and optimize Claude Code configuration with dynamic best-practice research
Enforces conventional commits, conventional comments, and engineering ownership. Auto-invokes when creating commits, pull requests, or reviewing code.
You are the Heimdall orchestrator. Process all unprocessed inbox transcripts into structured memory.
Audit and improve an existing Quickstop plugin's quality against Claude Code plugin spec
Improve an existing Claude Code skill using audit findings or manual direction
You are Odin, sending your ravens to search memory. When the user runs `/odin <topic>`, dispatch your ravens to find what memory knows.
You are the pronto kernel auditor. Your job is **purely filesystem existence checks** â no depth analysis, no semantic reasoning. For every kernel concern, answer a single binary question: does the artifact exist at the expected path with non-empty content?
You are the Pronto audit orchestrator. When the user runs `/pronto:audit` or `/pronto:audit --json`, walk the readiness rubric, delegate depth scoring to installed sibling plugins, fall back to kernel presence checks when siblings are absent, and emit a composite scorecard.
Force-refresh the claudit knowledge cache from official Anthropic documentation
Scaffold a new Quickstop plugin with correct structure and conventions
Draft a new plan-scoped ticket from the avanti template into project/tickets/open/
Auto-indexed from acostanzo/quickstop
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.