Index At Creation
- 452 installs
- 3.9k repo stars
- Updated January 26, 2026
- parcadei/continuous-claude-v3
index-at-creation is an agent skill that instructs developers to index artifacts immediately at write time—via PostToolUse hooks and single-file flags—so handoffs and files are queryable without waiting for batch jobs.
About
index-at-creation is a Claude Code skill from parcadei/continuous-claude-v3 that prevents stale retrieval by indexing artifacts when they are created instead of at session end or on a schedule. The pattern hooks indexing to the same event that writes the artifact—for example a PostToolUse Write hook right after handoff creation—and uses a `--file` flag for fast single-file indexing rather than deferred batch passes. Developers reach for index-at-creation when agent memory, handoff files, or search indexes must be available to the next tool call in the same session. The skill explicitly warns against SessionEnd batching, cron jobs, or assuming data will appear soon enough for time-sensitive downstream logic.
- index-at-creation
Index At Creation by the numbers
- 452 all-time installs (skills.sh)
- +2 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #930 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/parcadei/continuous-claude-v3 --skill index-at-creationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 452 |
|---|---|
| repo stars | ★ 3.9k |
| Last updated | January 26, 2026 |
| Repository | parcadei/continuous-claude-v3 ↗ |
How do you index agent artifacts at creation time?
Use index-at-creation for development tasks
Who is it for?
Developers building Claude Code hook pipelines where the next step depends on freshly written files being searchable right away.
Skip if: Batch ETL or nightly reindex jobs where latency until the next scheduled run is acceptable.
When should I use this skill?
An agent writes handoffs or knowledge files and downstream tools must query them in the same session without SessionEnd batch indexing.
What you get
Immediately indexed handoff or artifact files, hook-triggered single-file index runs, and queryable records within the same agent session.
- PostToolUse indexing hook
- Single-file index command
- Creation-time indexing policy
By the numbers
- Documents PostToolUse Write hook as the recommended immediate indexing trigger
Files
Index at Creation Time
Index artifacts when they're created, not at batch boundaries.
Pattern
If downstream logic depends on artifacts being queryable, index immediately at write time.
DO
- Index handoffs in PostToolUse Write hook (immediately after creation)
- Use
--fileflag for fast single-file indexing - Trigger indexing from the same event that creates the artifact
DON'T
- Wait for SessionEnd to batch-index
- Rely on cron/scheduled jobs for time-sensitive data
- Assume data will be available "soon enough"
Source Sessions
- a541f08a: "Index at artifact creation time, not at SessionEnd"
- 1c21e6c8: "If downstream logic depends on artifacts, index at the moment they're created"
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Pick index-at-creation for same-session queryability; use scheduled reindexing only when eventual consistency is acceptable.
FAQ
When should index-at-creation run?
index-at-creation runs at artifact write time, typically from a PostToolUse Write hook immediately after the file is created. Waiting for SessionEnd, cron, or scheduled jobs is discouraged when downstream logic needs the data now.
How does index-at-creation index a single new file?
index-at-creation recommends triggering the indexer from the creation event and passing a --file flag for fast single-file indexing instead of rebuilding the entire index at batch boundaries.