exists

Diagnose Recall knowledge gaps and trigger /learn or /anchor remediation.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Nerfherder16/BrickLayer --skill exists
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: exists
Source: https://github.com/Nerfherder16/BrickLayer/tree/main/.claude/skills/exists
Command: npx skills add https://github.com/Nerfherder16/BrickLayer --skill exists

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies missing or weak recall coverage in Recall and automatically fills gaps to improve knowledge quality and recall reliability.

Core Features & Use Cases

  • Coverage diagnosis: Searches Recall to reveal what is known about a topic and where gaps exist.
  • Gap filling: Automatically stores newly identified information to strengthen Recall coverage.
  • Guided remediation: Suggests next steps (e.g., /learn, /anchor) when gaps are detected.

Quick Start

Describe a topic you want Recall to audit and let /exists report and fill gaps.

Frequently Asked Questions about exists

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

FAQPage Schema
How do I diagnose knowledge gaps in my memory and verify existing coverage?

To diagnose recall knowledge gaps, search your memory store to evaluate what is known about a topic and identify missing coverage. This reveals weak areas and reports exactly where information is incomplete or absent.

What is the best way to automatically fill missing information detected in Recall?

The best way to fill missing information in Recall is to trigger guided remediation flows that store newly identified data. This automatically anchors new knowledge to strengthen overall coverage and reliability.

How do I check if my memory store has enough knowledge about a topic before relying on it?

To check if your memory store has enough knowledge about a topic, perform a coverage diagnosis. This searches Recall, evaluates existing understanding, and highlights specific gaps to ensure information is sufficient.

When should I anchor new information instead of just storing it in my knowledge base?

You should anchor new information when diagnosing Recall reveals weak coverage that needs structural reinforcement. If a gap requires durable context, guided remediation suggests anchoring over standard storage.

Can I use this to detect weak recall coverage and automatically trigger learning flows?

Yes, you can detect weak recall coverage and automatically trigger learning flows. When gaps are found during the knowledge audit, the system suggests next steps like /learn or /anchor to remediate them.

Does diagnosing recall gaps require any specific external dependencies or components?

Diagnosing recall gaps requires no external dependencies or components. The Skill operates independently to search Recall, evaluate existing knowledge coverage, and identify missing information.