repo-b-mass-index-ops

Build and query a bounded non-sharded index for repository and service lookups.

2|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-mass-index-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-b-mass-index-ops
Source: https://github.com/grtninja/skill-arbiter/tree/main/skill-candidates/repo-b-mass-index-ops
Command: npx skills add https://github.com/grtninja/skill-arbiter --skill repo-b-mass-index-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Builds and queries a bounded non-sharded index to accelerate repository and service lookup tasks.

Core Features & Use Cases

  • Build or refresh a bounded non-sharded index for fast repository lookups.
  • Run connector, bridge, and endpoint-adjacent queries against the index.
  • Escalate to safe-mass-index-core for non-service discovery tasks and evidence collection.

Quick Start

Use the repo-b-mass-index-ops skill to initialize the index and perform a sample query against the local repo.

Frequently Asked Questions about repo-b-mass-index-ops

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

FAQPage Schema
How do I accelerate repository and service lookups during triage?

To accelerate repository and service lookups, you can build and query a bounded non-sharded index to enable fast retrieval of repository sets and integration points during triage.

What is a bounded non-sharded index and when do I need it?

A bounded non-sharded index is a localized data structure that accelerates repository lookups without sharding overhead, needed when running connector, bridge, and endpoint-adjacent queries for service discovery.

Can I run connector and bridge queries against the repository index?

Yes, you can run connector, bridge, and endpoint-adjacent queries directly against the bounded non-sharded index to support fast lookups and evidence gathering workflows.

How do I build and refresh a non-sharded index for repository lookups?

You build and refresh a bounded non-sharded index by initializing the mass-indexing operation for common repository sets, which then supports fast repository lookups and escalation workflows.

When should I escalate mass-indexing tasks to safe-mass-index-core?

You should escalate to safe-mass-index-core for non-service discovery tasks and evidence collection when the bounded non-sharded index operations extend beyond standard repository and service lookups.

Are there limitations to using a bounded non-sharded index for mass indexing?

The bounded non-sharded index is designed for safe, bounded mass-index operations on common repository sets, meaning it is not intended for unbounded or highly distributed sharded indexing scenarios.