core
Identity, routing, communication style, memory protocol, task protocol, decision frameworks, and clarification for TARS
npx skills add majiayu000/claude-skill-registry --skill core-ajayjohn-tars-work-assistant --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Implements identity, routing, communication style, memory protocol, task protocol, decision frameworks, and clarification for TARS. Acts as the strategic intelligence layer, with MCP-based calendar and task integrations and memory-driven decision rules. It defines how TARS should route requests, how it resolves memory and context, and how it interacts with user prompts and memory updates.
How it works
Outlines an authoritative role for TARS as a trusted advisor. Uses MCP servers for calendar and task integrations (v2.1+), with legacy options (v2.0) during transition. Establishes truth source priority (user input, session context, memory files, integrations) and proactive memory learning triggers. Specifies an intelligent router to classify requests by signal and provides a signal-to-route mapping table for various tasks (e.g., remember this -> memory, analyze -> think, daily/weekly briefing -> briefing). Defines invocation name and routing behavior across natural language and slash commands. Also details automatic housekeeping side-effects that occur after certain actions (e.g., extract memory, save journal) and cross-tool interaction rules.
When to use it
Uses triggers like memory updates, organizational context changes, or new entities to prompt memory persistence and routing adjustments. Activation is automatic per session, and is involved in all primary routing decisions and memory handling as per the defined signals and actions.
What it can touch
Notes integration with MCP tools for calendar and tasks via configured MCP servers. It references tools and scripts in the routing/signals table but does not enumerate executable commands beyond high-level routing expectations. The skill itself is described as auto-loaded and global, affecting how other skills are invoked and how data flows between memory, journal, and tasks.
Caveats
License is MIT. Declares frontmatter-scoped purposes, scope, and maintenance notes related to cross-references. No explicit user-visible guarantees of outcomes; behavior depends on upstream MCP integrations and memory state. The skill is non-invocable by users (user-invocable: false).
<!-- MAINTENANCE: If modifying this skill, run tests/validate-docs.py to check for broken cross-references. See CONTRIBUTING.md. --> # Core framework ## Identity ### Role You are the strategic intelligence layer for the user. You operate as TARS, a trusted advisor who combines deep organizational context with rigorous analytical capability. ### Integrations TARS uses MCP (Model Context Protocol) servers for calendar and task integrations (v2.1+). Legacy HTTP/CLI integrations (v2.0) remain supported during transition. **Calendar integration** -- Read/write access via MCP server (preferred) or legacy provider. Check `<mcp_servers>` context first, then `reference/integrations.md` for legacy config. Use for schedule, agenda, meetings, availability queries. Always resolve dates to YYYY-MM-DD before querying. **Task integration** -- Read/write access via MCP server (preferred) or legacy provider. Check `<mcp_servers>` context first, then `reference/integrations.md` for legacy config. Use for all task creation, editing, completion, and queries. **Optional integrations** -- Project tracker, documentation, and other MCP servers enhance functionality but are not required. **Migration note**:
- Identity
- Role
- Integrations
- User profile
- Organization
- Truth source priority
- Proactive learning triggers
- TARS invocation
- Routing
- Intelligent router
- Signal table
- Routing rules
- File map
- Automatic housekeeping
Step 1: Archive expired content
python3 scripts/archive.py {workspace_path} --auto
Step 2: Health check (index validation, broken wikilinks, naming issues)
python3 scripts/health-check.py {workspace_path}
Step 3: Sync scheduled items and detect memory gaps
python3 scripts/sync.py {workspace_path}What does the core skill do?
Identity, routing, communication style, memory protocol, task protocol, decision frameworks, and clarification for TARS
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill core-ajayjohn-tars-work-assistant --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.