memento-taxonomy

Manages a knowledge graph taxonomy for the StakTrakr project using Neo4j.

8|3|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/lbruton/StakTrakr --skill memento-taxonomy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: memento-taxonomy
Source: https://github.com/lbruton/StakTrakr/tree/main/.claude/skills/memento-taxonomy
Command: npx skills add https://github.com/lbruton/StakTrakr --skill memento-taxonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a standardized taxonomy, naming conventions, and search patterns for managing a knowledge graph, ensuring consistency and efficient retrieval of information within the StakTrakr project.

Core Features & Use Cases

  • Standardized Naming: Enforces a clear Type: PROJECT-THEME-YYYYMMDD-HHMMSS pattern for entities like Handoffs, Sessions, and Insights.
  • Entity Type Definitions: Clearly defines when to use specific entity types (e.g., STAKTRAKR:DEVELOPMENT:HANDOFF, STAKTRAKR:FRONTEND:INSIGHT).
  • Required Observations & Tags: Mandates essential data points and tags for every entity to ensure completeness and project isolation.
  • Search Patterns: Provides optimized queries for finding the latest handoffs, insights by topic, and work by version or project.
  • Use Case: When saving a development session, this Skill ensures it's logged with all necessary metadata, including the active Linear project and next steps, allowing for seamless continuation later.

Quick Start

Use the memento-taxonomy skill to create a new handoff entity with the following details.

Frequently Asked Questions about memento-taxonomy

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

FAQPage Schema
How do I structure entity naming conventions for a knowledge graph in Neo4j?

Entity naming conventions for a Neo4j knowledge graph use a standardized Type: PROJECT-THEME-YYYYMMDD-HHMMSS pattern to ensure consistent data organization and retrieval. This structure applies to entities like Handoffs, Sessions, and Insights.

How do I search for the latest development handoffs and insights in a knowledge graph?

You search for development handoffs and insights using optimized query patterns like search_nodes and semantic_search functions. These patterns retrieve specific entities by topic, version, or project while enforcing required tags and observations.

What taxonomy is needed to manage development sessions and handoffs?

Managing development sessions and handoffs requires a taxonomy defining specific entity types like STAKTRAKR:DEVELOPMENT:HANDOFF and STAKTRAKR:FRONTEND:INSIGHT. It mandates essential observations and tags to ensure project isolation and data completeness.

Can I use this taxonomy to isolate knowledge graph data by active Linear project?

Yes, you can isolate knowledge graph data by active Linear project. The taxonomy mandates specific tags for every entity to ensure strict project isolation and prevent data overlap across different development streams.

What metadata is required when logging a development session to a knowledge graph?

Logging a development session requires metadata including the active Linear project, next steps, required observations, and specific tags. This ensures seamless continuation of work and complete retrieval of session history.

How does semantic search work with tagged knowledge graph entities?

Semantic search works with tagged knowledge graph entities by utilizing defined safety rules and entity structures within Neo4j graph storage. It leverages standardized naming and mandated tags to retrieve matching sessions and insights efficiently.