keystone:index

Regenerate the .charter/INDEX.json file with current primitive data.

42|3|Updated May 31, 2026
One-click install
npx skills add https://github.com/tacoda/keystone --skill keystone-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: keystone:index
Source: https://github.com/tacoda/keystone/tree/main/internal/framework/scaffold/templates/charter/skills/keystone-index
Command: npx skills add https://github.com/tacoda/keystone --skill keystone-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures the charter remains consistent by updating the index when changes are made, preventing discrepancies between the charter's representation and its actual content.

Core Features & Use Cases

  • Index Regeneration: Automatically refreshes the .charter/INDEX.json file with the latest data.
  • Agent Synchronization: Helps agents maintain accurate information on available primitives during session start.
  • Workflow Integrity: Prevents agents from accessing stale data, maintaining workflow integrity.

Quick Start

Use 'keystone index' to regenerate the charter index.

Frequently Asked Questions about keystone:index

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

FAQPage Schema
How do I regenerate the INDEX.json file for a Keystone charter?

Agents need an up-to-date charter index to access current primitive data during session initialization. Regenerating INDEX.json prevents agents from operating on stale data, maintaining workflow integrity and avoiding discrepancies between the charter's representation and its actual content.

When should I update the charter index to synchronize agent sessions?

The Keystone index regeneration works specifically with the .charter/INDEX.json file format. It automatically updates primitive data within this JSON structure to provide synchronization and accuracy for agents running the Keystone charter.

Does the Keystone index skill require any dependencies to refresh INDEX.json?

No, the Keystone index skill does not require any external dependencies or components to regenerate the INDEX.json file. It operates independently to ensure your charter remains consistent and up-to-date for agent initialization.

Why does my agent have stale primitive data during session initialization?

Agents access stale primitive data when the .charter/INDEX.json file is not regenerated after charter changes. Running the 'keystone index' command updates the index, preventing discrepancies and ensuring workflow integrity.