index

Audits workspace files against configured folder, naming, and document rules.

5|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/baek-labs/hames --skill index-baek-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: index
Source: https://github.com/baek-labs/hames/tree/main/packages/claude/skills/index
Command: npx skills add https://github.com/baek-labs/hames --skill index-baek-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Workspace files drift out of sync with their configured folder structures, naming conventions, and document rules over time, and manual audits are slow and error-prone. This Skill performs a read-only audit of every registered workspace and shared docs folder, reporting violations, judgment items, and unreadable files without modifying anything. ## Core Features & Use Cases - Read-only compliance audit: Runs runtime/index.js audit against the configured AI work root, checking placement, naming, and semantic document rules across all workspaces or a single target. - Authorized index repair: Generates a repair plan with runtime/index.js plan, presents the exact proposed changes with a plan_hash, and applies them only after explicit user approval via runtime/index.js apply --approved --plan-hash. - Safe failure handling: Preserves manual text and links, reports broken references instead of rewriting them, and never deletes original files when indexing fails. - Use Case: After weeks of ad-hoc file creation, invoke /index to see which documents violate folder rules, which need human judgment, and which indexes are stale—then approve a bounded repair plan. ## Quick Start Ask the AI to run /index and audit whether all workspace files follow their configured folder and naming rules.

Frequently Asked Questions about index

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

FAQPage Schema
How do I audit workspace file organization with /index?▼

Invoke /index or ask for a file organization audit. The skill resolves the configured AI work root and runs runtime/index.js audit, optionally scoped with --target to one workspace, then reports violations, judgment items, and unreadable files separately.

How do I repair stale workspace indexes safely?▼

Request an index repair explicitly. The skill runs runtime/index.js plan, shows the exact proposed index changes with a plan_hash, and only after your approval runs apply with --approved --plan-hash. It repairs index blocks only and re-audits afterward.

Does the index audit move or delete my files?▼

No. The audit is strictly read-only and never repairs indexes, moves documents, renames files, or deletes anything. Even an authorized repair only updates index blocks; moving or editing original documents requires a separate specific request.

What happens if the workspace root is not configured?▼

The skill requires a configured AI work root. If the root is unconfigured, it directs you to run /setup first rather than inventing folders or rules, since audits depend on the registered workspace configuration.

Why does the audit report items needing judgment instead of marking everything healthy?▼

Semantic document rules require reading actual content, and a path check alone cannot prove meaning. The skill flags uncertain, unreadable, or unsupported items separately and asks you to confirm judgment calls rather than pretending compliance.