
Knowledge Locator
- 103 installs
- 325 repo stars
- Updated August 2, 2026
- athola/claude-night-market
knowledge-locator is an agent skill that defines spatial, semantic, and temporal index schemas for memory-palace agent knowledge retrieval.
About
knowledge-locator (documented as index-structure in the bundled readme) specifies the data structures behind spatial indexing of memory palace content for agent systems that organize knowledge by place, concept, and time. Solo builders experimenting with memory-palace or Night Market–style agents get a concrete JSON schema for spatial_index, semantic_index, and temporal_index, including keywords, associations, access frequency, decay rates, and relationship graphs. The skill fits the build phase when you are implementing retrieval—not when you are validating a business idea or launching SEO. It assumes you are designing storage and query paths (hierarchical lookup, similarity via concept clusters, staleness via temporal decay) rather than writing end-user docs. Intermediate-to-advanced agent authors use it as a reference contract between locator components and downstream skills that depend on knowledge-locator in the same repo family.
- Documents primary index JSON schema: spatial coordinates from palace through area plus concept_data and sensory_signatur
- Three index types: spatial (hierarchical O(log n)), semantic (clusters + relationship graph), temporal (timeline, access
- Supports wildcard matching at any spatial hierarchy level
- Covers index maintenance including rebuild operations (per index-structure spec)
- Tagged advanced complexity with ~350 estimated tokens in frontmatter metadata
Knowledge Locator by the numbers
- 103 all-time installs (skills.sh)
- Ranked #4,276 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/athola/claude-night-market --skill knowledge-locatorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 103 |
|---|---|
| repo stars | ★ 325 |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | athola/claude-night-market ↗ |
What it does
Model and maintain spatial, semantic, and temporal indices for memory-palace agent knowledge so concepts can be located by palace path, keywords, or access patterns.
Who is it for?
Best when you're implementing custom agent memory or memory-palace architectures and need a shared index contract across skills.
Skip if: Skip if you want turnkey RAG over PDFs, simple note search, or launch/growth analytics without building agent memory infrastructure.
When should I use this skill?
Implementing or extending knowledge-locator / index-structure dependencies when designing agent memory indexing.
What you get
You implement aligned spatial, semantic, and temporal indices with documented maintenance and lookup characteristics for downstream locator logic.
- Index schema definitions for spatial, semantic, and temporal stores
- Maintenance guidance for index rebuild and decay handling
By the numbers
- Three index types: spatial, semantic, temporal
- Spatial hierarchical lookup described as O(log n) traversal
Files
Table of Contents
- What It Is
- Quick Start
- Search Palaces
- List All Palaces
- When to Use
- Search Modalities
- Core Workflow
- Target Metrics
- Detailed Resources
- PR Review Search
- Quick Commands
- Review Chamber Rooms
- Context-Aware Surfacing
- Integration
Knowledge Locator
A spatial indexing and retrieval system for finding information within and across memory palaces. Enables multi-modal search using spatial, semantic, sensory, and associative queries.
What It Is
The Knowledge Locator provides efficient information retrieval across your memory palace network by:
- Building and maintaining spatial indices for fast lookup
- Supporting multiple search modalities (spatial, semantic, sensory)
- Mapping cross-references between palaces
- Tracking access patterns for optimization
Quick Start
Search Palaces
python scripts/palace_manager.py search "authentication" --type semanticVerification: Run python --version to verify Python environment.
List All Palaces
python scripts/palace_manager.py listVerification: Run python --version to verify Python environment.
When To Use
- Finding specific concepts within one or more memory palaces
- Cross-referencing information across different palaces
- Discovering connections between stored information
- Finding information using partial or contextual queries
- Analyzing access patterns for palace optimization
When NOT To Use
- Creating new
palace structures - use memory-palace-architect
- Processing new
external resources - use knowledge-intake
- Creating new
palace structures - use memory-palace-architect
- Processing new
external resources - use knowledge-intake
Search Modalities
| Mode | Description | Best For |
|---|---|---|
| Spatial | Query by location path | "Find concepts in the Workshop" |
| Semantic | Search by meaning/keywords | "Find authentication-related items" |
| Sensory | Locate by sensory attributes | "Blue-colored concepts" |
| Associative | Follow connection chains | "Related to OAuth" |
| Temporal | Find by creation/access date | "Recently accessed" |
Core Workflow
1. Build Index - Create spatial index of all palaces 2. Optimize Search - Configure search strategies and heuristics 3. Map Cross-References - Identify inter-palace connections 4. Test Retrieval - Validate search accuracy and speed 5. Analyze Patterns - Track and optimize based on usage
Target Metrics
- Retrieval latency: ≤ 150ms cached, ≤ 500ms cold
- Top-3 accuracy: ≥ 90% for semantic queries
- Robustness: ≥ 80% success with incomplete queries
Detailed Resources
- Index Structure: See
modules/index-structure.md - Search Strategies: See
modules/search-strategies.md - Cross-Reference Mapping: See
modules/index-structure.md
PR Review Search
Search the review chamber within project palaces for past decisions and patterns.
Quick Commands
# Search review chamber by query
python scripts/palace_manager.py search "authentication" \
--palace <project_id> \
--room review-chamber
# List entries in specific room
python scripts/palace_manager.py list-reviews \
--palace <project_id> \
--room decisions
# Find by tags
python scripts/palace_manager.py search-reviews \
--tags security,api \
--since 2025-01-01Verification: Run python --version to verify Python environment.
Review Chamber Rooms
| Room | Content | Example Query |
|---|---|---|
decisions/ | Architectural choices | "JWT vs sessions" |
patterns/ | Recurring solutions | "error handling pattern" |
standards/ | Quality conventions | "API error format" |
lessons/ | Post-mortems | "outage learnings" |
Context-Aware Surfacing
When starting work in a code area, surface relevant review knowledge:
# When in auth/ directory
python scripts/palace_manager.py context-search auth/
# Returns:
# - Past decisions about authentication
# - Known patterns in this area
# - Relevant standards to followVerification: Run python --version to verify Python environment.
Integration
Works with:
memory-palace-architect- Indexes palaces created by architectsession-palace-builder- Searches session-specific palacesdigital-garden-cultivator- Finds garden content and linksreview-chamber- Searches PR review knowledge in project palaces
Index Structure
The Knowledge Locator maintains multiple indices for efficient multi-modal search.
Primary Index Schema
{
"spatial_index": {
"coordinates": {
"palace": "string",
"district": "string",
"building": "string",
"room": "string",
"area": "string"
},
"concept_data": {
"primary_concept": "string",
"keywords": ["list"],
"sensory_signature": "object",
"associations": ["related_concepts"],
"access_frequency": "number",
"last_accessed": "timestamp"
}
},
"semantic_index": {
"concept_clusters": {},
"relationship_graph": {},
"context_mappings": {}
},
"temporal_index": {
"creation_timeline": {},
"access_patterns": {},
"decay_rates": {}
}
}Index Types
Spatial Index
- Hierarchical path-based lookup
- O(log n) traversal for location queries
- Supports wildcard matching at any level
Semantic Index
- Keyword-to-concept mapping
- Concept clustering for similarity search
- Relationship graph for association traversal
Temporal Index
- Creation timeline for history queries
- Access frequency for hot/cold optimization
- Decay rates for staleness detection
Index Maintenance
- Rebuild: Full reindex when structure changes significantly
- Incremental: Update affected entries on concept changes
- Compact: Remove deleted entries and optimize storage
Search Strategies
Effective search combines multiple strategies based on query type and context.
Strategy Selection
| Query Type | Primary Strategy | Secondary |
|---|---|---|
| Exact path | Spatial lookup | - |
| Keyword | Semantic search | Fuzzy match |
| Partial info | Multi-modal fusion | Associative walk |
| Discovery | Graph traversal | Random walk |
Strategy Implementations
Spatial Lookup
1. Parse path components 2. Traverse hierarchy 3. Return exact match or nearest ancestors
Semantic Search
1. Extract query keywords 2. Match against semantic index 3. Rank by relevance score 4. Return top-k results
Fuzzy Matching
1. Apply edit distance tolerance 2. Check phonetic similarity 3. Expand query with synonyms 4. Merge and rank results
Associative Walk
1. Start from known concept 2. Follow association edges 3. Score by path relevance 4. Return connected concepts
Optimization Techniques
- Query caching - Cache frequent queries
- Index partitioning - Split by palace for parallelism
- Hot path optimization - Preload frequently accessed paths
- Lazy loading - Load deep indices on demand
Related skills
How it compares
Reference data-structure spec for agent memory—not a hosted vector DB integration or a documentation co-authoring workflow.
FAQ
Who is knowledge-locator for?
Advanced developers and agent authors wiring memory-palace or multi-modal knowledge systems who need index schemas and maintenance rules.
When should I use knowledge-locator?
During build while designing agent-tooling storage and retrieval—when defining how palace/district/room paths, keywords, and access decay map to query APIs.
Is knowledge-locator safe to install?
Treat it as documentation-heavy agent guidance; review the Security Audits panel on this Prism page before enabling tools in your agent runtime.