core

Define governance rules for TARS identity, routing, memory, and task protocols.

1|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ajayjohn/tars-work-assistant --skill core-ajayjohn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core
Source: https://github.com/ajayjohn/tars-work-assistant/tree/main/.claude-plugin/skills/core
Command: npx skills add https://github.com/ajayjohn/tars-work-assistant --skill core-ajayjohn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes identity, routing decisions, memory protocol, task protocol, decision frameworks, and clarification for TARS to ensure consistent behavior across workflows and components.

Core Features & Use Cases

  • Identity governance to establish a trusted user persona and workspace context
  • Routing discipline to select the correct skill path for each request
  • Memory and task protocol definitions to maintain a durable knowledge graph and task lifecycle
  • Clarification and escalation rules to handle ambiguity and ensure safe outcomes

Quick Start

Run the bootstrap to initialize core identity, routing, and memory components.

Frequently Asked Questions about core

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

FAQPage Schema
How do I centralize identity and routing decisions for consistent AI workflow behavior?

Memory protocol and task lifecycle management maintain a durable knowledge graph by defining rules for memory persistence, task tracking, and structured interactions across all components relying on core behavior.

How does a decision framework handle ambiguity and escalation in task routing?

The decision framework handles ambiguity and escalation through predefined clarification flows that detect uncertain requests, prompt for missing information, and safely escalate issues to ensure correct routing outcomes.

Can I integrate MCP-based calendars and tasks with core routing and memory protocols?

You initialize core identity, routing, and memory components by executing the bootstrap process, which sets up the fundamental governance rules and prepares the system to handle structured interactions and routing decisions.

When should I use a centralized memory protocol instead of component-level state management?

Use a centralized memory protocol when multiple components need consistent routing decisions, durable knowledge persistence, and structured task lifecycles, avoiding the fragmentation and inconsistency of isolated component-level state management.