aboutme-index

Locates relevant source files by searching keyword-based metadata and curated indexes.

1|Updated Dec 14, 2025
One-click install
npx skills add https://github.com/stickystyle/claude-skills --skill aboutme-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aboutme-index
Source: https://github.com/stickystyle/claude-skills/tree/main/skills/aboutme-index
Command: npx skills add https://github.com/stickystyle/claude-skills --skill aboutme-index

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

ABOUTME index provides a fast, human-curated way to locate files by their purpose within a codebase, replacing slow grep-based discovery and scattered docs.

Core Features & Use Cases

  • Index-driven discovery: read the index at .claude/aboutme-index.md to identify files by a given feature or task.
  • Search and filter: quickly filter results by keywords (e.g., auth, jwt) and jump to the relevant source files.
  • Use Case: when asked "which files handle authentication?" Claude can read a single index entry and point you to the relevant modules.

Quick Start

Read the index at .claude/aboutme-index.md to locate files by purpose and filter by keywords to narrow results.

Frequently Asked Questions about aboutme-index

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

FAQPage Schema
How do I find files by purpose instead of searching with grep?

File discovery by purpose is done by reading the ABOUTME index at .claude/aboutme-index.md, which provides human-curated entries to locate relevant source files without slow grep searches.

What is a human-curated code index and how does it work?

A human-curated code index maps file purposes to their locations using ABOUTME headers extracted from source files. It works by storing this mapping in .claude/aboutme-index.md for quick keyword filtering.

How do I locate which files handle a specific feature across the codebase?

To locate files handling a feature like authentication, read the single index entry in .claude/aboutme-index.md and filter by keywords such as auth to jump directly to the relevant modules.

Is file discovery using an index suitable for large codebases?

Index-driven discovery suits large codebases by replacing scattered docs and slow grep operations with fast, keyword-filtered lookups from a centralized .claude/aboutme-index.md file.

When should I avoid using grep for code search?

Avoid grep for code search when locating files by purpose or feature, as grep scans content patterns slowly; instead, use the ABOUTME index for instant, human-curated file discovery.

Do I need to prepare source files before using the ABOUTME index?

Source files require ABOUTME headers extracted and stored in the index at .claude/aboutme-index.md before file discovery can locate code by purpose and filter results by keywords.