Skip to content
cccskills
FreePublished on GitHub

caveman-explore

Read-only repository explorer. Use PROACTIVELY for cold-start exploration, broad cross-file localization, or when a direct search has failed and you need to find where something lives. Skip it when the issue already names the exact file or symbol, or a previous turn already returned usable file:line evidence. Returns only compact path:line citations; its reads and greps never enter the main conversation.

The English summary is being prepared. Showing the original description.

See how to install

Files included (3)

  • SKILL.md2.1 KB
  • package.json329 B
  • tests/skill-file.test.mjs2.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

You are FastContext, a fast, cheap, read-only repository explorer. Another agent (the solver) delegates a localization question to you. Your only job is to find WHERE the relevant code lives and report it as a compact list of file paths with line ranges. You never edit files, run commands, or propose a solution.

How to work:

  1. Issue several tool calls IN PARALLEL in your first turn — cast a broad net. Cover complementary hypotheses at once: likely path patterns (Glob), symbol and string matches (Grep), and reading the most promising files (Read). Do not probe one file at a time when you can fan out.
  2. Follow the evidence over one or two more turns only if needed. Stop as soon as you can name the relevant locations. You are optimizing for the solver's token budget, so finish fast.
  3. Only cite line ranges you actually read. Never invent or estimate a range, and never cite a range past the end of a file. A precise small range beats a vague large one.

Your reply MUST be ONLY an evidence block: one citation per line, nothing else. No preamble, no explanation, no summary, no markdown headings. Use exactly this shape, one per line:

path/to/file.ext:START-END reason it is relevant

Example reply:

src/router/pick.go:42-71 route selection — where a model is chosen src/router/pick_test.go:18-40 the table test covering pick()

If you genuinely cannot find anything relevant, reply with the single line:

no relevant locations found

That honest answer is better than a guess. The solver reads your citations and nothing else from your work, so keep the list short, specific, and correct.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Configures best-practice alerting policies for AI agents using OpenTelemetry (OTel) metrics, generating output as Terraform (.tf) configuration files. Use when analyzing, writing, or deploying alerting policies to monitor agent latency, error rates, token usage, and quality metrics. Don't use for standard infrastructure monitoring unrelated to AI agents, or when the agent is not instrumented with OpenTelemetry (for Reliability, Cost, Safety, Security alerts). NOTE: Reliability, Cost, Safety, and Security alerts use generic OTel metrics and work across runtimes (such as Cloud Run, Vertex AI). Quality alerts rely on Vertex AI Online Monitors and are strictly bound to Vertex AI deployments.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 19, 2026

Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a specific model is deployable (`gcloud ai model-garden models list-deployment-config`), query deployment cost, troubleshoot deployment errors (like quota limits), or undeploy/clean up endpoints. Also use when copying and deploying a 1P Tuned Model. Don't use for pure listing/discovery questions of the form "is X deployed?", "list my endpoints", or "which regions have models running?" — for those use `agent-platform-endpoint-management`. Don't use for public Vertex AI deployments (use the `vertex-deploy` skill) or for running model evaluations (use the `agent-platform-eval-flywheel` skill).

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 19, 2026

Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model evaluations.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 19, 2026

Measures and improves the quality of AI models and agents on Google Cloud using the Eval Quality Flywheel methodology. Use when evaluating an agent or model, building an eval dataset, picking or writing evaluation metrics, analyzing failures, comparing results before and after a fix, or when guidance is needed on Agent Platform eval methodology — including dataset schema, LLM-as-judge scoring, and common failure causes. For fine-tuning, use agent-platform-tuning. For general production deployment, use agent-platform-deploy.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 19, 2026

Connects to and performs inference with Google Cloud Agent Platform GenAI models, including First-Party Gemini models and Third-Party OpenMaaS models (Llama, DeepSeek, Qwen, etc.). Use when asked to perform inference, ask a model a question, run a test prompt, execute chat completions, or generate code for calling Gemini or OpenMaaS models, authenticate with GenAI SDK, OpenAI SDK, or legacy Agent Platform SDK, configure base URLs and global/regional endpoints, or troubleshoot 429 Resource Exhausted (DSQ), 400 User Validation, or 404 Not Found errors. Don't use for deploying models to endpoints or for running model evaluations.

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 19, 2026

Guides agents and users through migrating from Gemini API in Google AI Studio to Gemini Enterprise Agent Platform (formerly Vertex AI). Use this skill when moving applications to Google Cloud, to leverage Cloud credits, or to unify inferencing with other Cloud infrastructure (IAM, billing, telemetry).

The English summary is being prepared. Showing the original description.

vaila-multimodaltoolbox/vaila21Updated Oct 19, 2026

See all skills by vaila-multimodaltoolbox

Report a problem with this skill